JP2024002034A - Accident information display device, accident information display method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an accident information display device, and the like that can suitably display accident information.

SOLUTION: An acquisition unit 301 acquires extracted data (vehicle data, video data, automatic diagnosis data, etc.) extracted from an accident vehicle from a cloud storage server on the basis of access information. A display control unit 302 displays the accident information regarding the accident caused by the accident vehicle on the display screen of the terminal device on the basis of the extracted data acquired by the acquisition unit 301. A display control unit 302 has a function of determining the equipment type of the source of the extracted data on the basis of the extracted data and linked equipment information stored in a contractor DB 313, and displaying accident information according to the equipment type on the display device.

SELECTED DRAWING: Figure 9

COPYRIGHT: (C)2024,JPO&INPIT

Description

The present invention relates to an accident information display device, an accident information display method, and a program.

A system has been proposed that displays extracted data extracted from a call center operator's terminal device, a vehicle, and automobile insurance contract data when it is determined that a traffic accident has occurred (for example, Patent Document 1).

JP2017-46125A

In the system described in Patent Document 1, there is room for improvement regarding the display according to the type of equipment on the accident vehicle side and the display that takes operator convenience into consideration.

The present invention has been made in view of the above-mentioned circumstances, and an object of the present invention is to provide an accident information display device and the like that can suitably display accident information.

In order to achieve the above object, the accident information display device of the present invention includes:
an acquisition unit that acquires extracted data extracted from the accident vehicle;
a display control unit that displays accident information regarding an accident caused by the accident vehicle on a display device based on the extracted data acquired by the acquisition unit;
The display control unit displays the accident information on a display device according to a device that is a source of the extracted data.

The display control unit may display the type of device that is the source of the extracted data on a display device.

The display control unit may display on a display device an image corresponding to a type of device that is a source of the extracted data.

The accident information may include information about the degree of certainty of the information.

The display control unit may display the degree of certainty of the information depending on a device that is a source of the extracted data.

The display control unit may display information regarding accident response procedures.

The accident information may include information regarding the possibility of communication with the accident vehicle.

The display control unit may display video data of the accident as the accident information when the device that is the source of the extracted data includes a camera included in the accident vehicle.

The acquisition unit may acquire the extracted data via a communication terminal that can communicate with in-vehicle equipment of the accident vehicle.

In order to achieve the above object, the accident information display method of the present invention includes:
Obtain the extracted data extracted from the accident vehicle,
An accident information display method for displaying accident information regarding an accident caused by the accident vehicle on a display device based on the acquired extracted data, the method comprising:
The accident information is displayed on a display device according to the device that is the source of the extracted data.

In order to achieve the above object, the program of the present invention:
computer,
an acquisition unit that acquires extracted data extracted from the accident vehicle;
functioning as a display control unit that displays accident information regarding an accident caused by the accident vehicle on a display device based on the extracted data acquired by the acquisition unit;
The display control unit displays the accident information on a display device according to a device that is a source of the extracted data.

According to the present invention, accident information can be suitably displayed.

FIG. 1 is a diagram showing an example of an accident analysis system according to the present embodiment. FIG. 2 is a schematic diagram showing a state facing forward from inside the vehicle in this embodiment. It is a functional block diagram of a drive recorder concerning this embodiment. (A) to (D) are diagrams showing examples of types of equipment on the vehicle side according to the present embodiment. FIG. 2 is a functional block diagram of a terminal device according to the present embodiment. It is a flowchart showing an outline of usage registration processing in the accident analysis system according to the present embodiment. 2 is a flowchart showing an overview of startup processing in the accident analysis system according to the present embodiment. FIG. 2 is a functional block diagram of a comprehensive center server according to the present embodiment. FIG. 3 is a functional block diagram of an accident information display function of the comprehensive center server according to the present embodiment. FIG. 3 is a diagram showing a processing flow according to the present embodiment. FIG. 3 is a diagram illustrating an example of the configuration of a screen displayed on a terminal device of the general center in the present embodiment. (A) and (B) are diagrams showing an example of the configuration of an accident information screen displayed on a terminal device of a general center in this embodiment. (A) and (B) are diagrams showing an example of the configuration of an accident information screen displayed on a terminal device of a general center in this embodiment. It is a figure showing an example of analysis processing concerning this embodiment. FIG. 3 is a diagram showing a processing flow according to the present embodiment. FIG. 1 is a diagram showing an example of the hardware configuration of an accident analysis device according to the present embodiment. FIG. 1 is a functional block diagram of an accident analysis device according to the present embodiment. 2 is a flowchart outlining a processing procedure when the accident analysis device according to the present embodiment analyzes the situation of an accident. FIG. 2 is a diagram illustrating an example of the configuration of a screen displayed on a terminal according to the present embodiment.

Embodiments of the present invention will be described below with reference to the drawings. In addition, the same reference numerals are given to the same or corresponding parts in the figures.

FIG. 1 is a diagram showing an example of an accident analysis system according to the present embodiment. Accident analysis system 1 according to the present embodiment includes a vehicle 1000, an accident analysis device 10, a terminal 20, and a comprehensive center server 30. The vehicle 1000 is an automobile that receives the services of the accident analysis system 1, and is typically a vehicle 1000 owned by an insurance policyholder of an insurance company's automobile insurance. The vehicle 1000 is equipped with a drive recorder 1100 (see FIG. 2), and the drive recorder 1100 is connected to a cloud storage server (not shown) via a network (including a public line network, etc.) via wireless communication. and connects to the general center server 30. In this embodiment, description will be given on the assumption that the owner (driver) of vehicle 1000 has automobile insurance from an insurance company that provides the service of accident analysis system 1.

In this embodiment, the drive recorder 1100 is connected to a cloud storage server (not shown) and the general center server 30 via a network (including a public line network, etc.) via wireless communication as a network-connectable in-vehicle device. Although an example is shown in which the mirror 1300 is connected, for example, a mirror-type dedicated terminal device having similar functions may be prepared and installed in place of the mirror 1300.

A data storage area for this customer service will be secured on the cloud storage server. More specifically, for each drive recorder 1100 mounted on the vehicle 1000, a data storage area that can be accessed by the general center server 30 or the like is secured.

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 that handles accidents involving the vehicle 1000 and operated by each operator of the general center. . In addition, the operator of the general center communicates with the drive recorder 1100 installed in the vehicle 1000, a road service provider, an emergency organization (fire department, private emergency service provider), etc., for example, with a headset connected to a terminal device. You can now use it to make calls. Thereby, the operator takes action when an accident occurs in the vehicle 1000 or when there is a possibility of an accident.

Although not shown in the diagram, a road service provider system and an emergency organization system are also connected to the network, and these are also connected to a cloud storage server in response to a request from the general center server 30. Data is retrieved from the data storage area. Furthermore, as shown in FIG. 1, an accident analysis device 10 and a terminal 20 are connected to the network.

When the vehicle 1000 causes an accident, the accident analysis device 10 collects vehicle data measured by a sensor included in the vehicle 1000 (in the following description, for convenience, may be referred to as the "own vehicle"), which is the accident vehicle, and the vehicle. 1,000 drive recorders 1100 are acquired via the network from a cloud storage server, and based on the acquired vehicle data and video data, the situation of the accident caused by the vehicle 1000 is determined. It has the ability to analyze.

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 condition, and images generated by the accident analysis device 10. The terminal 20 may be any information processing device including a display, such as a PC, a notebook PC, a tablet terminal, or a smartphone.

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

FIG. 3 shows a functional block diagram of drive recorder 1100 according to this embodiment. The drive recorder 1100 installed in the vehicle 1000 includes a first communication section 1110, a second communication section 1120, a positioning section 1130, a recording section 1140, a recording section 1150, an acceleration measurement section 1160, and an automatic diagnostic data acquisition section. It has a section 1170, a control section 1180, and a data storage section 1200.

The control unit 1190 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 this customer service.

The first communication unit 1110 is a communication unit for communicating with a general center or the like using VoIP (Voice over Internet Protocol), for example. However, it may also be a call function of a general mobile phone. Further, the second communication unit 1120 is an interface for connecting to a network, and has a function of transmitting data to a cloud storage server, for example, in a packet.

Further, 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, GPS (Global Positioning System), and stores it in the data storage unit 1200.

The recording unit 1140 stores, for example, moving image data (video data) captured by a camera installed in the drive recorder 1100 in the data storage unit 1200. The recording unit 1150 stores sound data input from the microphone in the data storage unit 1200. The recording section 1150 may be integrated with the recording section 1140 in some cases. Further, it is assumed that the recording unit 1140 continuously performs recording when instructed to operate by the control unit 1180, for example, and stores the recording in the data storage unit 1200. It is assumed that the control unit 1180 can extract 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 recording section 1150. The recording unit 1140 can capture a moving image of the exterior of the vehicle 1000 and a moving image of the interior of the vehicle 1000.

Acceleration measurement section 1160 measures an acceleration value using, for example, an acceleration sensor and outputs it to control section 1180. Automatic diagnosis data acquisition section 1170 acquires automatic diagnosis data from automatic diagnosis system 1400 installed inside vehicle 1000 when instructed by control section 1180.

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 device data such as company name, organization name, vehicle registration number, automobile health insurance, etc. It stores the policy number of the contract, the policyholder's identifier (ID), telephone number, etc., and also stores the data acquired by each component in response to instructions from the control unit 1180.

Note that the equipment configuration within vehicle 1000 is not limited to that configured with drive recorder 1100 and automatic diagnosis system 1400. For example, instead of directly connecting the drive recorder 1100 to a cloud storage server or general center server 30, the driver may connect to a cloud storage server or general center server 30 via a communication terminal owned by the driver. .

FIG. 4 shows an example of equipment types on the vehicle 1000 side. As shown in FIG. 4(A), there may be only the drive recorder 1100, or as shown in FIG. 4(B), the drive recorder 1100 and the communication terminal 40 connected to the drive recorder 1100 may be configured. Alternatively, as shown in FIG. 4(C), it may be only the communication terminal 40, or as shown in FIG. 4(D), an automatic diagnosis system 1400 and a The communication terminal 40 may also be configured from the communication terminal 40. There may be other device types. For example, it may include other in-vehicle equipment such as a car navigation system.

The communication terminal 40 may be a smartphone, a tablet terminal, a notebook PC, or the like that can be connected to the drive recorder 1100 or the automatic diagnosis system 1400 wirelessly or by wire, and can be connected to a network via wireless communication. Furthermore, the communication terminal 40 may be a dedicated terminal specialized in communication functions. The communication terminal 40 may be an expansion terminal for connecting in-vehicle equipment that does not have a network connection function to a network. Note that in the following description, in-vehicle devices refer to devices other than the communication terminal 40 that are mounted on the vehicle 1000 (for example, the drive recorder 1100 and/or the automatic diagnosis system 1400).

The device type of the drive recorder 1100 shown in FIG. 4(A) assumes that the drive recorder 1100 is a model that can be directly connected to a cloud storage server or integrated center server 30. In FIG. 4(A), drive recorder 1100 may be connected to automatic diagnosis system 1400.

The device types of the drive recorder 1100 and the communication terminal 40 shown in FIG. I am assuming a certain case. In this case, vehicle data and video data acquired by the drive recorder 1100 are transmitted to the cloud storage server or the general center server 30 via the communication terminal 40. Further, vehicle data and video data acquired by the communication terminal 40 may be transmitted to a cloud storage server or the general center server 30. As described above, in this embodiment, even if the drive recorder 1100 does not have a connection function to a network, the accident analysis system 1 can be used by using the communication terminal 40, and more Services can be provided to drivers.

The device type of only the communication terminal 40 shown in FIG. This assumes the case of sending.

In addition to the equipment type of the communication terminal 40 and automatic diagnosis system 1400 shown in FIG. 4(D), the communication terminal 40 is connected to the automatic diagnosis system 1400 and the data of the automatic diagnosis system 1400 is It is assumed that the information can be acquired and transmitted to a cloud storage server or the general center server 30.

Note that the device types shown in FIG. 4 are merely examples, and other combinations and other devices may be incorporated.

FIG. 5 shows a functional block diagram of communication terminal 40 according to this embodiment. The communication terminal 40 includes a first communication section 401, a second communication section 402, a positioning section 403, a recording section 404, a recording section 404, an acceleration measurement section 405, an automatic diagnosis data acquisition section 407, and a control section. 408 , a display section 409 , an operation section 410 , a drive recorder data acquisition section 411 , and a data storage section 412 .

First communication unit 401, second communication unit 402, positioning unit 403, recording unit 404, recording unit 404, acceleration measurement unit 405, automatic diagnosis data acquisition unit 407, control unit 408, display unit 409, operation unit 410, drive recorder The data acquisition section 411 and the data storage section 412 include the first communication section 1110, second communication section 1120, positioning section 1130, recording section 1140, recording section 1150, acceleration measurement section 1160, and automatic diagnostic data acquisition section 1170 of the drive recorder 1100. , the control section 1180, and the data storage section 1200. These functions include a processor such as a CPU and a GPU included in the communication terminal 40, a memory, a storage device such as an HDD and/or an SSD, a communication IF that performs wired or wireless communication, an input device that accepts input operations, and an input device that outputs information. This is achieved through the cooperation of output devices.

The display unit 409 is configured with a liquid crystal display, an organic EL (Electro Luminescence) display, or the like, and is capable of displaying various information.

The operation unit 410 is configured with a touch panel or physical buttons, receives operations by the user (driver) of the communication terminal 40, and transmits signals corresponding to the operations to the control unit 408.

The drive recorder data acquisition unit 411 is a communication IF that performs wired or wireless communication with the drive recorder 1100, and acquires vehicle data and video data acquired by the drive recorder 1100. The acquired data is transmitted to a cloud storage server or the like via the control unit 408 and the second communication unit 402.

Note that the functions of the communication terminal 40 are not limited to those shown in FIG. 4, and may have other functions. For example, if the communication terminal 40 is a smartphone, it has general functions provided by a smartphone (for example, a function that allows the communication terminals 40 to communicate with each other).

Furthermore, the communication terminal 40 is connectable to at least the drive recorder 1100 and has the minimum function of being able to transmit data acquired from the drive recorder 1100 to the cloud storage server or the general center server 30 via the network. Some of the functions shown in FIG. 4 may be omitted, or a dedicated communication terminal may be used. When using a dedicated communication terminal having such minimum functions, connection settings with the in-vehicle device may be performed via another terminal such as a smartphone.

Next, a process flow for using the accident analysis system 1 in a case where the vehicle side equipment type includes the communication terminal 40 will be explained. FIG. 6 is a flowchart showing an overview of the usage registration process in the accident analysis system 1 according to the present embodiment. The usage registration process is a process for registering the communication terminal 40 so that it can be used in the accident analysis system 1. The usage registration process is a process for registering the communication terminal 40 so that it can be used in the accident analysis system 1. is executed.

When the communication terminal 40 detects a cooperative operation with an in-vehicle device (drive recorder 1100 and/or automatic diagnosis system 1400) (step S1; Yes), information on the in-vehicle device (device type, connection destination information, etc.) is stored as data. A cooperative process of registering the device data as part of the device data in the unit 412 is executed (step S2). The cooperative operation with the in-vehicle device may be performed by, for example, a predetermined operation using a dedicated application of the accident analysis system 1 after connecting to the in-vehicle device by wire or wirelessly. At this time, information on the communication terminal 40 may also be registered on the in-vehicle device side. After the cooperation, the communication terminal 40 is automatically connected to the in-vehicle device upon connection of a wired cable or detection by close proximity wireless communication.

When the communication terminal 40 detects the usage registration operation of the accident analysis system 1 (step S3; Yes), the policy number of the automobile insurance policy stored in the data storage unit 412 and the terminal identification information (telephone number) of the communication terminal 40 are detected. , the policyholder's ID, the token issued at the time of the contract, the e-mail address, etc.) and information on the cooperating in-vehicle devices (cooperative device information) are transmitted to the general center server 30 via the network (step S4). The usage registration operation may be, for example, a predetermined operation using a dedicated application of the accident analysis system 1. Note that the usage registration operation may be performed after the cooperation with the in-vehicle device is completed.

When the comprehensive center server 30 receives the policy number, terminal identification information, and cooperative device information from the communication terminal 40, it determines whether the insurance contract corresponding to the policy number is valid (step S5). If the insurance contract is valid (step S5; Yes), terminal identification information and cooperative device information are registered in association with the insurance contract (step S6). This allows the comprehensive center server 30 to know the type of equipment on the communication terminal 40 and the vehicle. When the registration of the terminal identification information and the cooperative device information is completed, the communication terminal 40 may be notified of the completion of the registration. Note that if the insurance contract is invalid, a notification to that effect may be returned to the communication terminal 40.

Note that registration of terminal identification information and/or linked device information is performed at the time of insurance contract, and in steps S4 and S5, for example, only the security number and terminal identification information of the communication terminal 40 are authenticated, and the authentication is successful. After that, registration for use of the accident analysis system 1 may be completed.

Note that it is also possible to make it possible to subscribe to insurance from the communication terminal 40 and input the terminal identification information and cooperation device information of the communication terminal 40 as necessary information, or to input the terminal identification information and cooperation device information from the communication terminal 40. The information may be acquired and stored in the comprehensive center server 30.

FIG. 7 is a flowchart showing an overview of startup processing in the accident analysis system 1 according to the present embodiment. The startup process is automatically executed in the vehicle-mounted device and the communication terminal 40 when the power of the vehicle-mounted device is turned on.

When the power of the on-vehicle device is turned on in response to, for example, starting the engine of the vehicle 1000 (step S51; Yes), the on-vehicle device connects to the linked communication terminal 40 by wire or wirelessly (step S52). The in-vehicle device searches for a connected communication terminal 40 using a wired cable or close proximity wireless communication, and attempts a connection. If the in-vehicle device fails to connect to the communication terminal 40 within a predetermined period, a connection error may be notified or the user (driver) may be prompted to operate or connect the communication device 40.

When the in-vehicle device connects to the already linked communication terminal 40, it transmits a start signal for starting the accident monitoring application to the communication terminal 40 (step S53). Thereafter, the on-vehicle device shifts to an accident monitoring state corresponding to the on-vehicle device (step S54). The accident monitoring state is a state in which vehicle data and video data can be acquired while monitoring accidents of the vehicle 1000, and if the in-vehicle device is the drive recorder 1100, acquisition of acceleration data and video data is started. Furthermore, if the in-vehicle device is the automatic diagnosis system 1400, acquisition of automatic diagnosis data is started.

When the communication terminal 40 receives the activation signal for the accident monitoring application from the in-vehicle device, it activates the accident monitoring application (step S41). The accident monitoring application only needs to be installed in the communication terminal 40 in advance. Further, the accident monitoring application may be automatically installed when the activation signal is received for the first time, or may be the same application as the application used in the usage registration process of FIG. 6. In this embodiment, since the accident monitoring application of the communication terminal 40 is started from the on-vehicle device, the accident monitoring application can be started automatically when the driver starts the engine. This makes it possible to prevent forgetting to start the accident monitoring application and to appropriately monitor accidents.

Note that the accident monitoring application may be activated manually by the driver. For example, if the device type on the vehicle 1000 side is only the communication terminal 40, the driver may manually start the accident monitoring application.

When the accident monitoring application is started, the communication terminal 40 accesses the general center server 30 and performs authentication processing (step S42). Here, the insurance policy number and terminal identification information are transmitted to the general center server 30, and the validity of the insurance contract is authenticated. If the insurance contract is valid, a notification to the effect that the authentication was successful is received from the general center server 30.

If the validity of the insurance contract is successfully authenticated (step S43; Yes), the communication terminal 40 shifts to an accident monitoring state in which it monitors accidents involving the vehicle 1000 (step S44). The accident monitoring state is a state in which data can be acquired from on-vehicle equipment, and may be a state in which vehicle data such as acceleration data is acquired in the communication terminal 40 itself. Then, when it is determined that an accident has occurred based on such information, the state may be such that the data acquired from the in-vehicle equipment and the data acquired by the communication terminal 40 can be transmitted to the comprehensive center server 30. Note that if the authentication of the validity of the insurance contract fails (step S43; No), an error may be notified or a retry may be prompted.

FIG. 8 shows a functional block diagram of the comprehensive center server 30. The general center server 30 includes, as functional units, a reception unit 311, a vehicle extraction unit 312, a subscriber database (DB) 313, a data acquisition unit 314, a data storage unit 315, a data output processing unit 316, and an input processing unit 316. It has a processing section 317, an analysis processing section 318, an external notification processing section 319, a countermeasure data storage section 320, a call processing section 321, and an insurance company notification section 322. The comprehensive center server 30 includes processors such as a CPU and GPU, a memory, a storage device such as an HDD and/or an SSD, a communication IF (Interface) for wired or wireless communication, an input device that accepts input operations, and outputs information. It has output devices that work together to realize these functional units. Note that the functions of the integrated center server 30 may be realized in cooperation with a terminal device connected to the integrated center server 30, so there may be a function provided on the terminal device side.

The receiving unit 311 receives an incoming call from the drive recorder 1100 or the communication terminal 40 addressed to a predetermined telephone number, identifies the telephone number of the drive recorder 1100 or the communication terminal 40 by the calling number notification, and extracts the telephone number from the vehicle. It outputs to section 312. Note that the receiving unit 311 transfers an incoming call from the drive recorder 1100 or the communication terminal 40 to the terminal device of an available operator based on predetermined rules.

The policyholder DB 313 includes, for example, terminal identification information (phone number, etc.), cooperative device information, automobile insurance contract data, and access information (for example, URI (Uniform Resource Identifier)) for identifying data storage areas in cloud storage servers. )) and are stored in association with each other. At least a part of the access information may be specified using some function from a telephone number, vehicle registration number, or the like.

The vehicle extraction unit 312 reads the contract data and access information stored in the contractor DB 313 from the phone number of the drive recorder 1100 or the communication terminal 40, and outputs the contract data and access information to the data output processing unit 316. The access information is output to the data acquisition unit 314.

The data acquisition unit 314 acquires data from the data storage area in the cloud storage server based on the access information and stores it 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 transferred, which is determined by the receiving unit 311.

The analysis processing section 318 performs predetermined analysis processing on the video data etc. stored in the data storage section 315, and outputs the analysis results to the terminal device via the data output processing section 316. The external notification processing unit 319 transmits data including access information and information for contacting the vehicle 1000 (such as the phone number of the drive recorder 1100 or the communication terminal 40) to the road service provider system or the emergency agency system. . The call processing unit 321 executes processing for making a call to the drive recorder 1100 or the communication terminal 40 in the vehicle 1000.

The input processing section 317 causes the data output processing section 316, analysis processing section 318, external notification processing section 319, call processing section 321, etc. to perform processing in response to instructions or input from the terminal device. Furthermore, the input processing unit 317 stores data regarding the measures taken in response to the incoming call from the drive recorder 1100 or the communication terminal 40 in the measures data storage unit 320. The data stored in the countermeasure data storage unit 320 includes access information and contract data, and may also include text data input on the terminal device.

The insurance company notification unit 322 sends an email to the insurance company (agency) that sold the automobile insurance etc. related to the vehicle 1000 where the accident occurred based on the data stored in the response data storage unit 320. Perform processing. This allows information to be shared with insurance companies.

FIG. 9 shows a functional block diagram of the accident information display function of the comprehensive center server 30. The comprehensive center server 30 includes an acquisition section 301, a display control section 302, and a contractor DB 313 as functional sections for the accident information display function. The integrated center server 30 includes a processor such as a CPU and a GPU, a memory, a storage device such as an HDD and/or an SSD, a communication IF that performs wired or wireless communication, an input device that accepts input operations, and an output device that outputs information. We will work together to realize these functions.

The acquisition unit 301 acquires extracted data (vehicle data, video data, automatic diagnosis data, etc.) extracted from the accident vehicle from a cloud storage server based on the above access information. The acquired data is stored in the data storage unit 315 (not shown).

The display control unit 302 displays accident information regarding the accident caused by the accident vehicle on the display screen of the terminal device based on the extracted data acquired by the acquisition unit 301. Furthermore, the display control unit 302 of this embodiment determines the equipment type of the source of the extracted data based on the extracted data and the linked equipment information stored in the contractor DB 313, and displays accident information according to the equipment type. It has a function to display on a display device. In this embodiment, the term "accident information" is used for convenience, but it is information about vehicles that have detected impact (acceleration) and have a high probability of an accident, and also includes information about vehicles that have not actually caused an accident. That is, the accident information regarding an accident caused by an accident vehicle may be information regarding a vehicle with a high probability of an accident.

Next, using FIGS. 10 to 15, a description will be given of the processing contents from the time an accident occurs until the insurance company is notified in the accident analysis system shown in FIG.

In FIG. 10, a case will be described in which the in-vehicle equipment (equipment type) of the vehicle 1000 is a drive recorder 1100 and an automatic diagnosis system 1400, as shown in FIG. In this case, some or all of the functions of the drive recorder 1100 may be executed by the communication terminal 40 having similar functions, or the drive recorder 1100 and the communication terminal 40 may transmit vehicle data (acceleration data), video data, etc. It may also be extracted. Instead of the first communication section 1110 and the second communication section 1120 of the drive recorder 1100, the first communication section 401 and the second communication section 402 of the communication terminal 40 connected to the drive recorder 1100 are used to perform calls and communications. Alternatively, the acceleration of the vehicle 1000 may be measured using the acceleration measurement unit 1160 of the drive recorder 1100 and the acceleration measurement unit 406 of the communication terminal 40 to determine whether an accident has occurred.

The control unit 1180 of the drive recorder 1100 causes the acceleration measurement unit 1160 to continuously measure acceleration, and determines whether the measured acceleration is equal to or greater than a predetermined first threshold value. In this embodiment, when it is determined that the acceleration measured in vehicle 1000 is equal to or higher than the first threshold value, it is determined that an accident has occurred or that the probability of an accident is high. The first threshold value may be determined in advance from vehicle collision data or the like. Here, the control unit 1180 assumes that an acceleration equal to or greater than the first threshold is detected (FIG. 10: Step S100).

Note that if an acceleration is detected that is greater than or equal to a second threshold and less than the first threshold, a button for manually calling the general center may be displayed on the display device. The second threshold value is, for example, a threshold value at which it is determined that the possibility of a major accident is low, but the possibility of a minor accident is possible. In this case, a call is made to the general telephone number of the general center, which is different from the telephone number used when acceleration equal to or greater than the first threshold is detected. The general center will respond under normal operations. Even in other cases, it may be possible to make a call to the general center from the drive recorder 1100.

When an acceleration equal to or higher than the first threshold is detected, the control unit 1180 reads device data from the data storage unit 1200, and extracts vehicle data including impact event data, 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 section 1130, the detected acceleration, and the automatic diagnosis data acquired by the automatic diagnosis data acquisition section 1170. The video data includes video data captured by the recording unit 1140 and sound data recorded by the recording unit 1150. As described above, the image data includes video data and the like for a certain period of time before the time when acceleration equal to or higher than the first threshold value is detected, and video data and the like for a certain period of time after that point. The automatic diagnosis data includes data indicating the presence or absence of damage to each of the engine, battery, fuel system, and the like. Note that the equipment data and impact event data are referred to as vehicle data.

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

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

Although it is described after step S103 for convenience of explanation, after step S100, the control unit 1180 causes the positioning unit 1130 to acquire position data at regular intervals, for example, and checks whether the vehicle 1000 is moving each time. judge. In a case where the object moves a predetermined distance (for example, 200 m) or more from the position in step S100, acceleration exceeding the first threshold value can be considered to be some kind of erroneous detection. Therefore, in that case, automatic calling to the general center is stopped.

That is, the control unit 1180 determines at any time whether the call stop condition is satisfied (step S104), and if the call stop condition is satisfied, the process is stopped (step S105). Note that, if a call stop condition is satisfied before transmitting the extracted data to the cloud storage server, the transmission of the extracted data may also be stopped.

On the other hand, if the call stop condition is not met, the control unit 1180 causes the first communication unit 1110 to automatically make a call to the general center (step S106). Note that when an accident occurs, the driver may be injured or too upset to speak, so even if the operator at the general center receives a call, the machine voice is played. Note that the operator at the general center recognizes from the machine voice that the operation according to this embodiment is necessary.

Furthermore, as will be described later, if the general center operator deems it necessary, a callback will be made, and the driver and operator will have a conversation at that time.

Note that 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 of the order shown in FIG.

The receiving unit 311 of the general center server 30 receives the incoming call from the vehicle 1000 (step S107), and outputs the telephone number obtained from the caller ID notification to the vehicle extracting unit 312. The vehicle extraction unit 312 reads the contract data and access information by searching the contractor DB 313 by phone 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. do.

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

When the cloud storage server receives the request for 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).

When the data acquisition unit 314 (or acquisition unit 301) receives the extracted data from the cloud storage server, it stores it in the data storage unit 315 (step S110). Then, the data output processing section 316 (or the display control section 302) causes the terminal device determined by the receiving section 311 to display an accident response screen including the extracted data and the contract data.

Specifically, the display control unit 302 searches the contractor DB 313 using the telephone number obtained in step S107, obtains cooperative device information (step S121), and determines the vehicle device type (step S122). ). Then, the display control unit 302 displays an accident response screen corresponding to the determined equipment type on the display screen of the terminal device (step S123).

FIG. 11 shows an example of the configuration of a display screen in a terminal device. In the example of FIG. 11, 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, and a fear level setting value down button 3106 , fear level setting button 3107 , analysis result display field 3108 , vehicle data (equipment data and impact event data) display field 3109 , callback instruction button 3110 , road service request button 3111 , rescue request button 3112 , a countermeasure data input field 3113, an end button 3114, a registration button 3115, an accident information display field 3200, an accident response procedure field 3201, and the like.

The contract data display column 3101 displays at least a portion of the data extracted from the contractor DB 313. Video display field 3102 displays video data received from vehicle 1000. The vehicle data (equipment data and impact event data) display column 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 necessity of a callback.

The accident information display field 3200 includes contract data 3101, a video display field 3102, and a vehicle data display field 3109, and mainly displays extracted data acquired from the vehicle 1000. In this embodiment, the accident information display field 3200 displays accident information according to the determined type of equipment on the vehicle 1000 side.

12 and 13 are diagrams showing specific examples of accident information for equipment types displayed in the accident information display column 3200. FIG. 12A shows a configuration example of the accident information display column 3200 when the device type is a drive recorder 1100 attached to the windshield of a vehicle. In this case, the accident information display field 3200 displays a device type display 3210 consisting of the words "Device Type: Windshield Mounted" indicating the device type and an image of the drive recorder 1100 attached to the windshield.

FIG. 12(B) shows a configuration example of the accident information display column 3200 when the device type is the drive recorder 1100 and a smartphone (communication terminal 40) linked with the drive recorder 1100. In this case, the accident information display column 3200 displays a device type display 3210 consisting of the words "Device type: Drive recorder smartphone cooperation" indicating the device type, an image of the drive recorder 1100 attached to the windshield, and an image of the smartphone. Ru.

FIG. 13A shows a configuration example of the accident information display field 3200 when the device type is only a smartphone (communication terminal 40). In this case, the accident information display field 3200 displays a device type display 3210 consisting of the text "Device type: Smartphone only" indicating the device type and an image of the smartphone.

FIG. 13B shows a configuration example of the accident information display column 3200 when the device type is the automatic diagnosis system 1400 and a smartphone (communication terminal 40) linked with the automatic diagnosis system 1400. In this case, the accident information display field 3200 displays a device type display 3210 consisting of the words "Device type: Automatic diagnosis system smartphone cooperation" indicating the device type and an image of the smartphone communicating with the vehicle 1000.

In this manner, in this embodiment, the type of equipment on the vehicle 1000 side that detected the occurrence of an accident (impact equivalent to an accident) is displayed in the accident information display field 3200 that displays accident information, so that the operator can It becomes easier to understand the equipment type, and it is possible to respond and make decisions according to the equipment type, improving convenience for the operator. Note that the device type display 3210 only needs to be prepared in advance according to the device type of the vehicle 1000, and if the device type display 3210 corresponding to the determined device type on the vehicle 1000 side is read out and displayed. good.

In addition, as shown in FIGS. 12 and 13, the accident information display column 3200 includes other information such as the date and time of the accident, the location, the size of the accident (the magnitude of the impact), and call information (the degree of certainty of the information, the phone number, etc.). number), vehicle information (information reliability, registration number, vehicle color), map, video (outside the vehicle, inside the vehicle), victim information (information reliability, name), diagnosis system 1400 cooperation partner information (manufacturer call center phone number, etc.) are displayed. Note that the types of information displayed are merely examples, and as long as accident information (data extracted from vehicle 1000) is displayed appropriately, other information may be displayed, or some information may be omitted. You can.

The date and time of the accident, the location, the size of the accident (the size of the impact), and the map may be displayed based on the impact event data.

In the call information, information regarding devices that can make a call is displayed as the degree of certainty of the possibility of a call. As shown in FIG. 12(A), if the drive recorder 1100 is attached to the windshield, it is almost certainly possible to make a call, but in the case of a smartphone, the driver may not have it at hand, The possibility of making calls is lower than with the attached drive recorder 1100. Therefore, in this embodiment, information regarding devices that can make calls is displayed. This improves convenience for the operator. A call with the target device may be started by clicking on the phone number included in the call information. In this case, if the certainty of callability is low, an alert to that effect may be issued. Note that the certainty level of callability (certainty level value and displayed characters) may be determined in advance according to the device type, and the accident information display column 3200 displays the certainty level of callability depending on the device type. It is sufficient if the certainty level is displayed.

Similarly, the reliability of information is also displayed for vehicle information and victim information. The degree of certainty of these pieces of information (the value of the degree of certainty and the characters to be displayed) may also be determined in advance according to the device type. Note that if the operator is able to confirm this information by talking to the driver, the operator may edit and update the information.

Further, in this embodiment, a color bar ac indicating the degree of certainty of the information is displayed on the call information, vehicle information, victim information, and cooperation destination information. The color of the color bar ac indicates the degree of certainty of the information, and the color bar ac is displayed in a color corresponding to the degree of certainty of the information according to the device type. In this embodiment, the reliability of information increases in the order of white > diagonal lines > black. By doing so, the operator can understand the degree of certainty of the information based on the color of the color bar ac, thereby improving convenience for the operator. Note that which color has a higher degree of certainty may be determined arbitrarily as long as it is easy to understand the degree of certainty. Furthermore, instead of expressing the degree of certainty by color, the degree of certainty of information may be shown by differences in design (display mode), numerical values, meters, etc.

Further, the images include images outside the vehicle and images inside the vehicle, and the presence or absence of images differs depending on the device type. FIG. 12A shows that an image outside the vehicle and an image inside the vehicle are displayed. That is, the drive recorder 1100 in FIG. 12(A) is capable of capturing images of the outside and inside of the vehicle. FIG. 12(B) shows that only the image outside the vehicle is displayed. That is, the drive recorder 1100 in FIG. 12(B) shows that it is possible to capture only images outside the vehicle. FIGS. 13A and 13B show that the device type does not include the drive recorder 1100, so neither the outside video nor the inside video is displayed. Note that it may be possible to display a video shot by a camera of a smartphone (communication terminal 40). In this way, if the device type includes a device that can take images outside the vehicle and/or inside the vehicle, video data is displayed.

The accident response procedure display column 3201 displays the accident response procedure of the operator of the terminal device. The accident response procedure display field 3201 may display an accident response procedure according to the magnitude of the accident (impact) and the type of equipment on the vehicle 1000 side. As for the accident response procedure, the order of operations to be performed by the operator, such as execution of analysis processing, input of response data, callback, road service, rescue, etc., may be rearranged and displayed according to the equipment type. For example, if the magnitude of the impact is large and the device type includes a device that can make calls, the callback priority may be set high. Furthermore, when the magnitude of the impact is small, the priority of execution of analysis processing and input of countermeasure data may be set high. By doing so, operator convenience is improved and an appropriate accident response can be performed. Incidentally, the accident response procedure may be displayed based on the results of analysis processing described later. The accident handling procedure display field 3201 may be included in the accident information display field 3200.

Further, the operator of the terminal device visually checks the video data displayed in the video display field 3102 and determines whether the video is a shocking video, such as a fatal accident, or a scary video. For example, the operator of the terminal device determines whether the video is a scary video according to a predetermined manual, and when determining that the video is a scary video, sets fear level setting information indicating that the video is a scary video. Specifically, the operator of the terminal device may, for example, give a fear level of ``3'' if the video is of a fatal accident, a fear level of ``2'' if the video involves massive bleeding, and a fear level of ``1'' if the video is of only a broken bone. Click the fear level setting value up button 3105 or the fear level setting value down button 3106 according to the fear level to display the fear level setting value according to the fear level in the fear level setting value display field 3104. , by clicking the fear level setting button 3107, the fear level setting information of the fear level setting value is set. Note that the fear level setting value is set to "0" as an initial value. In this embodiment, when the fear level setting value is set to "1" or more, the fear level setting information indicates that the image is a scary video, and the fear level setting value is set to "0". In this case, the fear level setting information indicates that the image is not a scary image. As will be described in detail later, the fear level setting information is associated with information such as the video data, identification information for identifying the accident, and the date and time of the accident, and is registered in the cloud storage server. The fear level setting values of fear level "0" to "3" correspond to multiple levels of setting values depending on the fear level of the scary video.

The handling data input field 3113 is a field in which the operator inputs necessary matters (handling data) regarding the accident. In the countermeasure data input field 3113, predetermined items (for example, no accidents/accidents, etc.) may be input using check boxes.

Further, 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 (FIG. 10: Step S112). The analysis process may be executed automatically without any instruction from the operator.

An example of the analysis process will be explained using FIG. 14. The analysis processing unit 318 searches for a predetermined collision sound from the sound data, for example, and determines 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. etc.) and outputs the determination result to the data output processing unit 316 as an analysis result (step S31).

Furthermore, the analysis processing unit 318 identifies 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), and determines the distance between the external object and the external object. The presence or absence of an accident (more specifically, the probability of an accident) is determined based on the distance (for example, the shortest distance), and the determination result is output as an analysis result to the data output processing unit 316 (step S32).

Further, the analysis processing unit 318 determines the possibility of self-propulsion, the necessity of repair, etc. from the automatic diagnosis data, and outputs the determination result to the data output processing unit 316 as an analysis result (step S33). For example, based on the presence or absence of engine damage, battery damage, and fuel system damage, it is determined whether a tow truck is necessary (self-propelled) or whether repairs are necessary even if self-propelled.

Furthermore, the analysis processing unit 318 extracts passenger information from the internal video data (video data inside the vehicle 1000 captured by the recording unit 1140), and outputs it to the data output processing unit 316 as an analysis result (step S34 ). For example, facial recognition technology is used to extract information such as the number of passengers, their age groups, and boarding locations. This information is used by the operator to determine whether a rescue request is necessary.

These are just examples of the analysis processing, and different processing may be added. For example, as for acceleration data, in the case of a three-axis sensor, values for each axis are obtained, but based on these, information such as the collision direction or the collision location on the vehicle may be extracted. Furthermore, instead of performing analysis processing for each data type, the probability of an accident may be determined overall. Furthermore, some of these may be executed instead of all of them.

Returning to FIG. 10, when such analysis processing is performed, the data output processing unit 316 displays the analysis results in the analysis result display column 3108 shown in FIG. 11 (step S113).

Based on such display content, the operator determines whether a response including a callback is necessary. If it is determined that no response including a callback is necessary, the user clicks the end button 3114. In response to the instruction to end, the input processing unit 317 determines that no response is necessary (step S114: No route), and ends the subsequent processing (step S115). Note that in this embodiment, if a response including a callback is not required, the process of step S209 (see FIG. 15), which will be described later, is not executed and the fear level setting value is not set (that is, the initial value is not set). However, for example, even if no response including callback is required (step S114: No route), step S209 The process may be executed, and then the process may be terminated.

On the other hand, if the operator determines that a response including a callback is necessary, the operator clicks, for example, a callback instruction button 3110. Then, the input processing unit 317 determines that action is required (step S114: Yes route), and the process shifts to the process in FIG. 15.

15, in response to a click on the callback instruction button 3110, the input processing unit 317 outputs the phone number of the drive recorder 1110 to the call processing unit 321, and makes a call to the phone number. By doing so, a call is made (step S200).

The operator and the driver or passenger of the vehicle 1000 confirm the situation over the phone. Specifically, it confirms whether an accident has occurred, whether there are any injuries, and whether road assistance is required (need for a tow truck, need for repairs, etc.). At this point, various advice may be given to the driver or passenger.

If it is confirmed that there is no accident, then, for example, a message to the effect that there is no accident is entered in the countermeasure data input column 3113 shown in FIG. 11, and the process is ended.

If the occurrence of an accident is confirmed, the fact that the accident has occurred is input into the countermeasure data input column 3113, for example. When the details of the accident are heard, the details may be input into the countermeasure data input field 3113. On the other hand, if the operator determines that road service is necessary based on the call, he or she clicks a road service request button 3111.

Returning to FIG. 15, when the road service request button 3111 is clicked, the input processing unit 317 determines that the road service is to be requested (step S201: Yes route), and requests the external notification processing unit 319 to access the extracted data. Information, contact personal data (such as the phone number of the drive recorder 1110), etc. are notified to the road service provider system (step S202). Note that the notification may include data regarding self-propellability and repairability (analysis results, confirmation results by telephone, etc.). At the same time, a call may be made to the road service provider.

The road service provider system receives 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 stored in the cloud storage server (step S204). For example, a call is made to the drive recorder 1110 to dispatch a tow truck or other vehicle to the location included in the equipment data.

Whether the operator does not request road service (step S201: No route) or requests road service (step S201: Yes route), if the operator determines that rescue is necessary based on the call, the operator can make a rescue request as shown in FIG. 11. Click button 3112.

When the rescue request button 3112 is clicked, the input processing unit 317 determines that the request is to request rescue (step S205: Yes route), as shown in FIG. Information, contact personal data, etc. are notified to the emergency organization system (step S206). Note that the notification may include passenger information (analysis results or confirmation results (such as the degree of injury) by telephone). At the same time, you may also make a call to an emergency institution. If rescue is not requested (step S205: No route), the process moves to step S209.

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

After taking such measures, the operator of the terminal inputs, for example, response data such as whether a road service is requested or not and whether a rescue is requested into the response data input field 3113 in FIG. click. Then, the countermeasure data input from the terminal device is output to the input processing section 317 of the general center server 30.

Whether the operator does not request rescue (step S205: No route) or requests rescue (step S205: Yes route), the operator can determine whether the video is a scary video based on the video data displayed in the video display field 3102 shown in FIG. The user then clicks on the fear level set value up button 3105 or the fear level set value down button 3106 to set the fear level set value (step S209).

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 fear level value displayed in the fear level setting value display field 3104 (fear level setting value) changes. Then, when the operator clicks the fear level setting button 3107, 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 fear level setting value being displayed is output to the input processing unit 317 of the general center server 30, and the fear level setting information is , is associated with the target extracted data (more specifically, the target video data) stored in the data storage area of the cloud storage server. In step S209, the general center server 30 associates the fear level setting information with the video data received from the cloud storage server, and stores the video data and fear level setting information in the data storage area of the cloud storage server. You can.

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 coping data storage unit 4020 together with fear level setting information and coping data associated with the video data (step S210).

Then, if the handling data includes data indicating that there has been an accident, the insurance company notification unit 322 specifies the email address from the insurance company code (agency code) included in the contract data, and sends the email address to the insurance company (agency code). A notification that the initial response to the accident has been completed is sent to (step S211). For example, by including access information in this notification, the insurance company (agency) can also check the data stored in the data storage area of the cloud storage server.

In this way, information can be shared and the insurance company (agency) can quickly carry out its activities. Note that a similar notification may be sent to other related parties, such as a safe driving manager of the company to which the driver of vehicle 1000 belongs. By performing the above-described processing, various customer services can be provided promptly and appropriately when an accident occurs.

In particular, by accumulating data on cloud storage servers, data can be shared not only with call centers, but also with roadside assistance, emergency agencies, and insurance companies (agencies), so that necessary services can be provided appropriately. become.

In addition, although the operator at the general center is the starting point for service, the analysis processing unit 318 can appropriately assist in making decisions, which not only eliminates unnecessary callbacks, but also enables the operator of the vehicle 1000 to This makes it possible to avoid placing an excessive burden on the driver or passengers. In other words, you will be able to have conversations that get to the point.

In addition, the recording unit 1150 continues recording after the data is sent to the cloud storage server by the control unit 1180, and records the interactions with the parties involved in the accident and the police and fire department after the accident occurs. Store data separately on a cloud storage server. In this way, advice on insurance compliance may be provided to the driver and the like. Even after the callback from the call center ends and the conversation with the driver etc. is over, the line remains connected so that the operator can check the surrounding sounds in real time and then give advice to the driver etc. It's okay.

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 is used to analyze the accident situation for insurance claim payment procedures such as negotiation of percentage of fault. Used for analysis. Incidentally, the accident types may be patterned using video data stored in a cloud storage server, acceleration data included in vehicle data, etc., and the cause of the accident and the amount of damage may be predicted.

Next, analysis of the accident situation by the accident analysis device 10 in the accident analysis system shown in FIG. 1 will be explained using FIGS. 16 to 19.

As described above, the accident analysis device 10 acquires vehicle data and video data from a cloud storage server via the network, and analyzes accidents caused by the vehicle 1000 based on the acquired vehicle data and video data. It has the ability to analyze the situation. Incidentally, the accident analysis device 10 stores an accident case database that associates the accident situation obtained through the analysis with information on past accident situations and past accident cases (hereinafter referred to as "accident cases"). It has a function of searching for an accident case corresponding to the situation of the accident caused by the vehicle 1000 by comparing the following. The accident analysis device 10 also creates an image showing the situation of the accident caused by the vehicle 1000 by mapping the position of the vehicle 1000 and the positions of other cars obtained by analyzing the situation of the accident on map data. It has the function to generate. The image showing the situation of the accident caused by vehicle 1000 may be of any kind, and may be, for example, an overhead view or a moving image.

The accident analysis device 10 may be composed of one or more physical information processing devices such as a mainframe, a workstation, or a personal computer (PC), or may be composed of a virtual computer running on a hypervisor. It may be configured using a typical information processing device or may be configured using a cloud server.

FIG. 16 is a diagram showing an example of the hardware configuration of the accident analysis device 10. The accident analysis device 10 includes a processor 11 such as a CPU or GPU, a memory, a storage device 12 such as an HDD and/or an SSD, a communication IF 13 that performs wired or wireless communication, an input device 14 that accepts input operations, and outputs information. It has an output device 15. The input device 14 is, for example, a keyboard, touch panel, mouse, and/or microphone. The output device 15 is, for example, a display and/or a speaker.

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

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

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

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. Note that the accident situation analyzed by the analysis unit 102 includes 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 the vehicle speed of the vehicle 1000 exceeds the speed limit. It may also include whether there is a person present or not.

Further, 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 analyzes the information indicating the absolute position of the vehicle 1000 (the positioning unit 1130) and information indicating the relative positional relationship between the vehicle 1000 and the other vehicle, which is obtained by analyzing the video of the other vehicle shown in the video data. The absolute position may be estimated. Furthermore, the analysis unit 102 may estimate the absolute positions of the vehicle 1000 and other vehicles in time series.

Furthermore, the analysis unit 102 estimates the absolute position of the vehicle 1000 by analyzing the video data, and combines the absolute position of the accident vehicle estimated by analyzing the video data with the position of the vehicle 1000 measured by the positioning unit 1130. The accident situation may be analyzed by regarding the absolute position obtained by averaging the absolute position based on a predetermined weight as the absolute position of the vehicle 1000.

In addition, the analysis unit 102 compares the image size of a portion of the video data where another vehicle is shown with data indicating the correspondence between the image size and the distance, and calculates the relative position of the vehicle 1000 and the other vehicle. The situation of the accident may be analyzed by estimating the distance between vehicle 1000 and the other vehicle, which is one piece of information indicating the relationship.

In addition, the analysis unit 102 compares the difference between the coordinates of the location where the other vehicle is shown in the video data and the center coordinate of the video data with data indicating the correspondence between the coordinates and the angle, and The accident situation may be analyzed by estimating the angular difference between the direction in which the vehicle 1000 is traveling and the direction in which another vehicle exists, which is one of the information indicating the relative positional relationship with the vehicle. .

The generation 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 onto map data. The image may include an overhead view or a moving image. For example, the generation unit 103 may generate a video in which images showing the circumstances of the accident are arranged in chronological order.

The search unit 104 compares the situation of the accident caused by the vehicle 1000 analyzed by the analysis unit 102 with an accident case DB (accident case data) that correlates the situation of the accident with past accident cases. It has a function to search for accident cases corresponding to the situation of the accident caused by the vehicle 1000. Furthermore, the search unit 104 may search for the percentage of fault of the vehicle 1000 in accidents caused by the vehicle 1000 as an accident case corresponding to the situation of the accident caused by the vehicle 1000.

Further, the accident case may include one or more correction ratios (correction information) for correcting the fault ratio. If there is a modification ratio corresponding to the situation of the accident caused by the accident vehicle among the one or more modification ratios, the search unit 104 may modify the fault ratio of the accident vehicle in accordance with the modification ratio.

The output unit 105 outputs information indicating the accident situation analyzed by the analysis unit 102, accident cases corresponding to the accident status searched by the search unit 104, and images indicating the accident situation generated by the generation unit 103 to the terminal 20. It has a function to output to.

Note that the functions of the accident analysis device 10 may be realized in cooperation with the terminal 20, so there may also be functions provided on the terminal 20 side. Further, the accident analysis device 10 and the terminal 20 may be integrated into one information processing device.

Next, the processing procedure when the accident analysis device 10 analyzes the accident situation caused by the vehicle 1000 will be explained with reference to FIG. 18. FIG. 18 is a flowchart showing an overview of the processing procedure when the accident analysis device 10 analyzes the situation of an accident. In the following description, it is assumed that vehicle data and video data each include time information or synchronization information. That is, in this embodiment, when analyzing video data at a certain point in time, it is possible to perform the analysis using vehicle data corresponding to that point in time. Conversely, when analyzing vehicle data at a certain point in time, it is possible to perform the analysis using video data corresponding to that point in time.

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 (step S10, step S11). Specifically, the accident analysis device 10 acquires the vehicle data and video data from a cloud storage server via a network. In addition, for example, vehicle data and video data are recorded in a non-temporary storage medium such as an SD card or a USB memory, and by connecting the recording medium to the accident analysis device 10, vehicle data and video data can be imported into the accident analysis device 10. You can do it like this. Alternatively, the information may be obtained from the general center server 30 via a network. Note that when acquiring the video data in step S11, fear level setting information associated with the video data is also acquired. Further, the processing in step S10 and step S11 corresponds to a receiving means and a receiving step.

Subsequently, the accident analysis device 10 acquires operator information indicating the information of the operator of the terminal 20 that accessed the accident analysis device 10 (step S12). The operator information includes operator identification information that identifies the operator, and permissible setting values that are setting values of fear images 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, the operator information stored in advance in the storage unit 100 corresponds to the operator identified by the operator identification information. Get operator information. Although the present embodiment shows an example in which the operator information is stored in advance in the storage unit 100, the operator information may be input to the accident analysis device 10 via the terminal 20. Note that in step S12, it is only necessary to obtain at least the allowable setting values of the operator of the terminal 20 that has accessed the accident analysis device 10. Note that the process in step S12 corresponds to an allowable setting value acquisition unit that obtains an operator's allowable setting value.

After executing the process in step S12, the accident analysis device 10 sets the fear level setting value indicated by the fear level setting information associated with the video data acquired in step S11 and the allowable setting value acquired in step S12. , and determines whether the fear level setting value exceeds the permissible setting value, that is, whether the fear level setting value of the video data acquired in step S11 exceeds the operator's permissible range ( Step S13).

If the fear level set value exceeds the allowable set value (step S13; Yes route), the accident analysis device 10 notifies the administrator to that effect (step S14). In step S14, for example, a message is sent to the pre-registered administrator terminal to the effect that the fear level setting value exceeds the permissible setting value, that is, the display of video data is restricted in analyzing the accident situation. We will notify you accordingly. In this manner, when the fear level setting value exceeds the allowable setting value, the video data acquired in step S11 is not displayed in the video display column 2102 shown in FIG. 19. That is, when the fear level setting value exceeds the permissible setting value, display of the video data is restricted. Note that the process in step S14 corresponds to notifying a user with specific authority to that effect when the display of video data is restricted in analyzing the accident situation.

On the other hand, if the fear level setting value is included in the tolerable setting value (if it is less than or equal to the tolerable setting value), the video data acquired in step S11 will be displayed in the video display field 2102 shown in FIG. . FIG. 19 shows an example of the configuration of a display screen on the terminal 20. In the example of FIG. 19, there is a basic information display field 2101 that displays basic information such as the date and time of the accident, a video display field 2102 that displays the video data acquired in step S11, and a password input field where the video display password is entered. Including 2112 etc. In addition to the illustrated example, fields for displaying items necessary for analyzing the accident, buttons for performing operations, etc. may also be included. Note that the password input field 2112 includes a determination button for determining the input password. Note that when 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. 19, which is due to the fear level setting information included in the video data. If the included setting values are not included in the operator's allowable setting values specified by the allowable setting value acquisition means, this corresponds to restricting the display of video data in analyzing the accident situation.

After step S14 in FIG. 18, the accident analysis device 10 determines whether the administrator has performed a release operation (step S15), and if it has been performed (step S15; Yes route), the accident analysis device 10 displays the image shown in FIG. The video data acquired in step S11 is displayed in the display field 2102 (step S16). In step S15, whether or not the administrator has performed a release operation is determined based on, for example, whether a valid password has been entered in the password input field 2112 shown in FIG. 19. If a valid password is entered, it may be determined that a release operation has been performed. Note that in this embodiment, an example is shown in which the administrator's release operation is performed when a valid password is input, but the invention is not limited to this. For example, the administrator may be able to change the fear level setting value. You can. 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 administrator After a valid password is input, the fear level setting value may be changed to "1". After the fear level setting value is changed by the administrator, the process may proceed to step S13. Note that the administrator's cancellation operation (more specifically, the operation of entering a valid password in the password input field 2112 shown in FIG. 19, or the operation of changing the fear level setting value by the administrator) requires specific authority. This corresponds to the fact that the restriction can be canceled by the user who owns it.

If the fear level set value is included in the allowable set value in step S13 (step S13; No route), or after executing the process of step S16, the accident analysis device 10 displays the image information acquired in step S11 in the video display column 2102. While displaying the video data, the accident situation is analyzed, a corresponding accident case is searched (step S17), and the process ends. On the other hand, in step S15, if the administrator's release operation is not performed or a proper password is not input (step S15; No route), the accident analysis device 10 displays the information acquired in step S11 in the video display field 2102. The situation of the accident is analyzed, the corresponding accident case is searched for (step S17), and the process is ended without displaying the video data. That is, when the fear level setting value exceeds the permissible setting value and the administrator does not perform a release operation, the display of the video data is restricted. The process in step S17 corresponds to an analysis means and an analysis step.

In step S17, a plurality of processes are performed. For example, by analyzing video data at the time of an accident frame by frame, one or more surrounding objects (other vehicles, people, signs, road structures, etc.), and further performs processing to identify the coordinates indicating the position of the identified surrounding object in the image. Then, based on the coordinates of the identified surrounding objects, a process is performed to estimate the relative positional relationship between the vehicle 1000 and surrounding objects existing around the vehicle 1000.

The accident analysis device 10 also 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 combines the estimated absolute position of the vehicle 1000 with the Based on the estimated relative positional relationship between the vehicle 1000 and the surrounding objects existing around the vehicle 1000, a process is performed to estimate the absolute position of the surrounding objects surrounding the vehicle 1000.

The accident analysis device 10 also generates images (including bird's-eye views and videos) showing the accident situation by mapping the calculated absolute positions of the vehicle 1000 and surrounding objects around the vehicle 1000 onto map data. The direction in which the vehicle 1000 collided with another vehicle or obstacle (for example, the front A process is performed to estimate the occurrence of a collision (such as a collision).

Next, the accident analysis device 10 obtains 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 surrounding objects existing around the vehicle 1000, and the estimated collision direction of the vehicle 1000. , map data, and performs a process of analyzing information indicating the situation of an accident caused by vehicle 1000. The information includes a plurality of items (which may also be referred to as tags), and the situation of the accident is identified by the combination of each item. Next, the accident analysis device 10 searches the accident case database using each item as a key, thereby performing a process of acquiring 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 there is no inconsistency in the processes.

According to the embodiment described above, the accident analysis device 10 is configured such that the fear level setting information associated with the acquired video data exceeds the permissible setting value of the operator of the terminal 20 accessing the accident analysis device 10. If so, restrict the display of video data. Therefore, it is possible to prevent the operator from viewing scary images that exceed the permissible range, and it is possible to reduce the mental burden on the operator.

In addition, if the fear level setting information exceeds the operator's allowable setting value, the accident analysis device 10 performs a cancellation operation by the administrator (more specifically, inputting a valid password into the password input field 2112 shown in FIG. 19). When the administrator performs a release operation (by inputting an input or changing the fear level setting value by the administrator), the video data is displayed. Therefore, the restriction can be canceled by the administrator's cancellation operation, and the administrator can perform accident situation analysis work while supporting the operator.

In addition, if the fear level setting information exceeds the operator's permissible setting value, the accident analysis device 10 sends a notification to the pre-registered administrator terminal that the fear level setting value exceeds the permissible setting value. message informing you that the display of video data will be restricted in analyzing the accident situation. Therefore, the administrator can quickly support the operator.

(Modified example)
Note that the present invention is not limited to the embodiments described above, and various modifications and applications are possible. For example, it is possible to omit or replace a part of the above embodiments, or add arbitrary configurations.

The cloud storage server may be a manufacturer's server that collects vehicle data and video data of the vehicle 1000. In this case, the comprehensive center server 30 and the accident analysis device 10 may acquire vehicle data and video data from the manufacturer's server.

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 do not have to have all the technical features shown in the above embodiment; The device may include some of the configurations described in the above embodiments so as to solve at least one technical problem. Furthermore, at least a portion of each of the following modified examples may be combined.

When a smartphone owned by the driver is used instead of the drive recorder 1100, external video data and internal video data may be photographed using cameras mounted on the back and front of the smartphone.

Further, in the above embodiment, an example in which the drive recorder 1100 is attached to the vehicle 1000 has been described, but it is also possible that the vehicle 1000 has all or part of the functions of the drive recorder 1100 (for example, the functional parts shown in FIG. 3). You may also do so. For example, the vehicle 1000 itself detects an impact (acceleration greater than a predetermined value), estimates the occurrence of an accident, automatically shoots images outside and inside the vehicle, Vehicle data and video data may be sent to a cloud storage server or the like. In this case, the in-vehicle equipment and device type of the vehicle 1000 may be an in-vehicle accident detection system, etc., and the accident information display field 3200, device type display 3210, and accident response procedure display field 3201 indicate the device type "in-vehicle accident detection system". It suffices if the display is made accordingly. Further, such an on-vehicle accident detection system and the communication terminal 40 may be configured in cooperation with each other, and, for example, information may be transmitted via the communication terminal 40.

Further, in the above embodiment, an example is shown in which the analysis processing section 318 is provided in the integrated center server 30, but for example, at least part of the functions of the analysis processing section 318 may be provided in the drive recorder 1100. For example, the analysis processing unit 318 may be provided in the drive recorder 1100 in order to automatically make a call only when it is determined that the level representing the probability of an accident is equal to or higher than a predetermined level. Alternatively, passenger information may be extracted in advance and such information may also be sent to the cloud storage server. Similarly, information indicating the need for repair may be extracted in advance and such information may also be sent to the cloud storage server.

Note that the drive recorder 1100 or the general center server 30 may determine whether or not the service can be provided, such as whether the contract period is still within the contract period.

Further, in the above embodiment, an example is shown in which it is determined in step S13 shown in FIG. 18 whether or not the fear level setting value of the acquired video data exceeds the operator's permissible range, but this is just an 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 image is a scary image, regardless of the operator's tolerance range. If the fear level setting information indicates that the video is a scary video, the process may proceed to step S14. According to this, when the fear level setting information associated with the video data received from the comprehensive center server 30 indicates that the video is a scary video, display of the video data is restricted in analyzing the accident situation. Therefore, it is possible to prevent the operator from visually recognizing the scary images, and it is possible to reduce the mental burden on the operator. In addition, it is determined whether the fear level setting value is "1" or more, that is, the fear level setting information indicates that the video is a scary video, and if it is determined that the video is a scary video, the video is not used in the analysis of the accident situation. Restricting the display of data corresponds to restricting the display of video data in analyzing the accident situation when the fear level setting information included in the video data indicates that the video is a scary video.

Further, in the above embodiment, if the administrator does not perform a release operation in step S15 shown in FIG. 18 or a proper password is not input (step S15; No route), in the process of step S17, An example has been shown in which the accident situation is analyzed and a corresponding accident case is searched for without displaying video data in the video display field 2102, but this is just one example. If the administrator does not perform a release operation in step S15 shown in FIG. 18 or a proper password is not input (step S15; No route), the process is terminated without executing the process in step S17. Good too. That is, when video data is not displayed, analysis of the accident situation and search for the corresponding accident case may not be performed.

The accident analysis system 1 can be realized using a normal computer without using a dedicated device. For example, the accident analysis system 1 that executes any of the above-described processes may be configured by installing a program for executing any of the above-described processes into a computer from a recording medium stored therein. Further, one accident analysis system 1 may be configured by a plurality of computers working together.

Furthermore, any method can be used to supply the program to the computer. For example, it may be supplied via a communication line, communication network, communication system, etc.

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

The embodiments described above are intended to facilitate understanding of the present invention, and are not intended to be interpreted as limiting the present invention. The flowcharts, sequences, and elements included in the embodiments, as well as their arrangement, materials, conditions, shapes, sizes, etc., described in the embodiments are not limited to those illustrated and can be changed as appropriate. Further, it is possible to partially replace or combine the structures shown in different embodiments.

DESCRIPTION OF SYMBOLS 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, 40... Communication terminal , 100... Storage section, 101... Acquisition section, 102... Analysis section, 103, 1200... Generation section, 104... Search section, 105... Output section, 301... Acquisition section, 302... Display control section, 311... Receiving section, 312 ...Vehicle extraction section, 313...Contractor database (DB), 314...Data acquisition section, 315, 1200...Data storage section, 316...Data output processing section, 317...Input processing section, 318...Analysis processing section, 319...External Notification processing section, 320... Countermeasure data storage section, 321... Call processing section, 322... Insurance company notification section, 401... First communication section, 402... Second communication section, 403... Positioning section, 404... Recording section, 405... Recording section, 406... Acceleration measurement section, 407... Automatic diagnosis data acquisition section, 408... Control section, Display section... 409, Operation section... 410, Drive recorder data acquisition section 411, 1000... Vehicle, 1100... Drive recorder, 1110... First communication section, 1120... Second communication section, 1130... Positioning section, 1140... Recording section, 1150... Recording section, 1160... Acceleration measurement section, 1170... Automatic diagnosis data acquisition section, 1180... Control section, 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...Call Back instruction button, 3111... Road service request button, 3112... Rescue request button, 3113... Response data input field, 3114... End button, 3115... Registration button, 3200... Accident information display field, 3201... Accident response procedure display field, 3210 …Equipment type display, ac…color bar

In order to achieve the above object, the accident information display device of the present invention includes:
an acquisition unit that acquires extracted data extracted from the accident vehicle;
a display control unit that displays accident information regarding an accident caused by the accident vehicle on a display device based on the extracted data acquired by the acquisition unit;
The display control section includes:
displaying the accident information on a display device according to the equipment type of the source of the extracted data ;
The device type of the source of the extracted data is displayed on a display device .

The display control unit may display an image corresponding to the device type of the source of the extracted data on the display device.

The display control unit may display the degree of certainty of the information according to the type of device that is the source of the extracted data.
Other accident information display devices of the present invention include:
an acquisition unit that acquires extracted data extracted from the accident vehicle;
a display control unit that displays accident information regarding an accident caused by the accident vehicle on a display device based on the extracted data acquired by the acquisition unit;
The display control unit displays the accident information on a display device according to the equipment type of the source of the extracted data,
The accident information includes information about the degree of certainty of the information,
The display control unit displays the degree of certainty of the information according to the device type of the source of the extracted data.

The display control unit may display video data of the accident as the accident information when the device type of the source of the extracted data includes a camera included in the accident vehicle.

In order to achieve the above object, the accident information display method of the present invention includes:
Obtain the extracted data extracted from the accident vehicle,
An accident information display method for displaying accident information regarding an accident caused by the accident vehicle on a display device based on the acquired extracted data, the method comprising:
displaying the accident information on a display device according to the equipment type of the source of the extracted data ;
The device type of the source of the extracted data is displayed on a display device .

In order to achieve the above object, the program of the present invention:
computer,
an acquisition unit that acquires extracted data extracted from the accident vehicle;
Functioning as a display control unit that displays accident information regarding an accident caused by the accident vehicle on a display device based on the extracted data acquired by the acquisition unit,
The display control section includes:
displaying the accident information on a display device according to the equipment type of the source of the extracted data ;
The device type of the source of the extracted data is displayed on a display device .

Claims (11)

an acquisition unit that acquires extracted data extracted from the accident vehicle;
a display control unit that displays accident information regarding an accident caused by the accident vehicle on a display device based on the extracted data acquired by the acquisition unit;
The accident information display device, wherein the display control unit displays the accident information on a display device according to a device that is a source of the extracted data. The accident information display device according to claim 1, wherein the display control unit displays the type of device that is the source of the extracted data on the display device. The accident information display device according to claim 2, wherein the display control unit displays an image corresponding to a type of device that is a transmission source of the extracted data on a display device. The accident information display device according to any one of claims 1 to 3, wherein the accident information includes information about the degree of certainty of the information. The accident information display device according to claim 4, wherein the display control unit displays the degree of certainty of the information according to a device that is a source of the extracted data. The accident information display device according to any one of claims 1 to 3, wherein the display control unit displays information regarding accident response procedures. The accident information display device according to any one of claims 1 to 3, wherein the accident information includes information regarding the possibility of communication with the accident vehicle. Any one of claims 1 to 3, wherein the display control unit displays video data of the accident as the accident information when the device that is the source of the extracted data includes a camera included in the accident vehicle. Accident information display device as described in Section. The accident information display device according to any one of claims 1 to 3, wherein the acquisition unit acquires the extracted data via a communication terminal that can communicate with in-vehicle equipment of the accident vehicle. Obtain the extracted data extracted from the accident vehicle,
An accident information display method for displaying accident information regarding an accident caused by the accident vehicle on a display device based on the acquired extracted data, the method comprising:
An accident information display method, characterized in that the accident information is displayed on a display device according to a device that is a source of the extracted data. computer,
an acquisition unit that acquires extracted data extracted from the accident vehicle;
Functioning as a display control unit that displays accident information regarding an accident caused by the accident vehicle on a display device based on the extracted data acquired by the acquisition unit,
A program characterized in that the display control unit displays the accident information on a display device according to a device that is a source of the extracted data.

Images