JP7342384B2 - Traffic accident recording system and method of providing traffic accident information - Google Patents

Description

The present embodiment relates to a traffic accident recording system and a method for providing traffic accident information.

2. Description of the Related Art A device described in Patent Document 1, for example, is known as a traffic accident situation recording device that records an image when a traffic accident occurs and is used in verification work performed after the accident occurs. The recording device disclosed in Patent Document 1 detects the collision sound and brake sound that occur when an accident occurs, determines that a traffic accident has occurred based on these sounds, and then captures the image using a camera installed at an intersection, for example. It is disclosed that the image recorded in the image is recorded.

Japanese Patent Application Publication No. 2016-192072

However, in the above-mentioned conventional example, although it is described that images at the time of a traffic accident are stored, it is later mentioned that the images will be used as records when an insurance company investigates the circumstances at the time of the accident. It has not been.

The present embodiment has been developed to solve such conventional problems, and its purpose is to easily obtain information on a desired traffic accident case among the many traffic accidents that have occurred in the past. The object of the present invention is to provide a retrievable traffic accident recording system and a method for providing traffic accident information.

In order to achieve the above object, a traffic accident recording system according to one aspect is a traffic accident recording system that records the situation at the time of the traffic accident when the traffic accident occurs, and is installed around the driving route. , a sensor that detects moving objects including pedestrians, two-wheeled vehicles, and vehicles existing on the travel route, and movement that is data including the position and speed of the moving object based on sensor data detected by the sensor. a moving body analysis unit that detects body data; a database that stores the moving body data detected by the moving body analysis unit; and when a user specifies at least one of the time or location of a traffic accident, Reading the moving body data corresponding to the time or position of the traffic accident stored in the database, and based on at least one of the position and speed of the moving body included in the read moving body data. determining whether or not a traffic accident has occurred in the mobile object, and when it is determined that a traffic accident has occurred, creating a traffic accident list that is a list including mobile object data regarding the mobile object; A traffic accident recording system characterized by comprising an accident determination/search section.

A method for providing traffic accident information according to one embodiment is a method for providing traffic accident information that, when a traffic accident occurs, records the situation at the time of the traffic accident and provides the recorded traffic accident information to a user. , a moving object analysis unit collects moving object data including the positions and speeds of moving objects including pedestrians, motorcycles, and vehicles existing on the driving path, which are detected by sensors installed around the driving path. a step in which the moving object analysis unit stores the moving object data in a database; and a step in which the moving object analysis unit stores the moving object data in a database; and when the user specifies at least one of the time of occurrence or the location of the traffic accident, determining and searching for a traffic accident. the unit reads out moving body data corresponding to the time or position of occurrence of the traffic accident stored in the database, and at least one of the position and speed of the moving body included in the read moving body data. It is determined whether a traffic accident has occurred in the mobile object based on the above, and if it is determined that a traffic accident has occurred, a traffic accident list that is a list containing mobile object data regarding this mobile object is generated. the output unit presents the created traffic accident list to the user; and the billing unit charges the user for providing the traffic accident list. It is characterized by:

According to this embodiment, it is possible to easily retrieve information on a desired traffic accident case from among a large number of traffic accidents that have occurred in the past.

FIG. 1 is a block diagram showing the configuration of a traffic accident recording system according to the first embodiment. FIG. 2 is an explanatory diagram showing an image created by the image creation unit at time t1 when a traffic accident occurs. FIG. 3 is an explanatory diagram showing an image created by the image creation unit at time t2 when the traffic accident occurs. FIG. 4 is an explanatory diagram showing an image created by the image creation unit at time t3 when the traffic accident occurs. FIG. 5 is a flowchart showing the processing procedure of the traffic accident recording system according to the first embodiment. FIG. 6 is a flowchart showing the processing procedure by the user interface of the traffic accident recording system according to the first embodiment. FIG. 7 is an explanatory diagram showing an example of a traffic accident list created by the traffic accident determination/search unit. FIG. 8 is a block diagram showing the configuration of a traffic accident recording system according to a modification of the first embodiment. FIG. 9 is a block diagram showing the configuration of a traffic accident recording system according to the second embodiment. FIG. 10 is a flowchart showing the processing procedure of the traffic accident recording system according to the second embodiment. FIG. 11 is a flowchart showing the processing procedure by the user interface of the traffic accident recording system according to the second embodiment. FIG. 12 is a block diagram showing the configuration of a traffic accident recording system according to the third embodiment. FIG. 13 is a flowchart showing the processing procedure by the user interface of the traffic accident recording system according to the third embodiment. FIG. 14 is a flowchart showing the processing procedure by the administrator server of the traffic accident recording system according to the third embodiment.

Hereinafter, embodiments will be described based on the drawings.
[Description of the first embodiment]
FIG. 1 is a block diagram showing the configuration of a traffic accident recording system according to the first embodiment. As shown in FIG. 1, a traffic accident recording system 101 according to the first embodiment records the situation when a traffic accident occurs, and includes a sensor 1, a control device 2, and a user interface 3. .

In addition, in each of the above-mentioned components, it is sufficient that only the sensor 1 is provided around the running route, and the control device 2 may be installed at a base station or the like that can communicate with the sensor 1 by wire or wirelessly. . Further, the user interface 3 is provided at a location where it can communicate with the control device 2 by wire or wirelessly. Furthermore, it is also possible to configure the control device 2 to be provided on a virtual server in a network cloud. The control device 2 can also be configured as an integrated computer comprising a central processing unit (CPU) and storage means such as RAM, ROM, and hard disk.

The sensor 1 is installed around a road on which vehicles and pedestrians travel, and detects moving objects such as vehicles, bicycles, and pedestrians present on the road. The travel road includes roads on which moving objects travel, and intersections such as crossroads, T-junctions, and three-way intersections. Further, sensor data, which is data detected by the sensor 1, is output to a moving object analysis section 21, which will be described later. The sensor 1 is, for example, a laser radar, and detects objects in the surroundings by emitting laser light toward the surroundings and receiving reflected light from objects in the surroundings. The term "mobile object" is a concept that includes vehicles, motorcycles, light vehicles, and pedestrians.

Therefore, as will be described later, it is possible to recognize the shape and size of the moving object on the travel path based on the sensor data detected by the sensor 1. Furthermore, the type of moving object, that is, the type of vehicle, two-wheeled vehicle (bicycle or motorcycle), pedestrian, etc. can be determined. Furthermore, the position and moving speed of the moving object can be recognized. In this embodiment, an example in which a laser radar is used as the sensor 1 will be described, but the sensor 1 is not limited to this, and it is also possible to use a lidar, a visible camera, an RGBD camera, an infrared camera, etc.

Further, it is also possible to install a microphone attached to the sensor 1 to detect sounds around the traveling route. Furthermore, the sensor 1 is not limited to one sensor; for example, two laser radars may be installed at one monitoring point, or different types of sensors, such as a laser radar and a visible camera, may be used together. .

The control device 2 includes a moving object analysis section 21, a database 23, a traffic accident determination/search section 24, and an image creation section 25.

The moving object analysis unit 21 identifies the type of moving object based on the sensor data detected by the sensor 1. Specifically, based on the horizontal length or vertical length of the reflected pulse reflected by a moving object and detected by a laser radar, for example, the horizontal length is a preset constant length. If this is the case, it is determined that the moving object is a vehicle. Furthermore, if the length in the lateral direction is longer than the vehicle described above, it is determined that the vehicle is a large vehicle (such as a truck).

Furthermore, based on the above sensor data, the positions (including the directions of the moving bodies) and velocities (including the directions of the speeds) of all moving bodies (including the sensor data) are calculated from moment to moment. The speed of a moving object can be calculated based on the amount of change in the position of the same moving object detected by sensor data obtained at different timings among sensor data obtained in time series. Note that hereinafter, data on the type, position, and speed of a moving object will be collectively referred to as "moving object data."

Then, the calculated mobile object data is output to the database 23. Further, when a moving object is present at an intersection, a preset intersection ID is added to the above moving object data and output. Furthermore, if the sensor 1 is equipped with a microphone, the voice data detected by the microphone is added to the mobile object data and output to the database 23.

That is, the moving object analysis unit 21 has a function of detecting moving object data, which is data including the position and speed of the moving object, based on the sensor data detected by the sensor 1.

The database 23 stores various types of moving object data output from the moving object analysis section 21. That is, when a moving object is detected based on sensor data detected by each sensor 1 installed at a plurality of detection points, the moving object data (data such as type, position, speed, etc.) of this moving object is stored in the database 23. is memorized. Then, as will be described later, when a search request for a traffic accident is input, mobile object data that matches this search request is read out from the database 23, and based on the read mobile object data, the following operation is performed. A list of traffic accidents is created.

The traffic accident determination/search unit 24 determines whether a traffic accident has occurred based on data on the type, position, and speed of the moving body detected by the moving body analysis unit 21 and stored in the database 23. As a method for determining the occurrence of a traffic accident, for example, the methods shown in (a), (b), and (c) below can be adopted.

(a) Obtain information on the positions of two moving bodies detected by the moving body analysis unit 21, and if the positions of the two moving bodies overlap at the same time, the two moving bodies have collided, It is determined that a traffic accident has occurred.

(b) Calculate the time to collision (TTC) between the two moving bodies, and if the moving bodies are not decelerated even after the collision time of the two moving bodies has passed, the two moving bodies will collide. It is determined that a traffic accident has occurred.

(c) Communication (road-to-vehicle communication) is performed with a vehicle (mobile object) traveling on the road, and when the airbag of the vehicle is activated, this activation signal is acquired. If the positions of the two moving objects overlap and the airbag of at least one of the moving objects is activated, it is determined that a traffic accident has occurred in this vehicle.
Note that the method for detecting the occurrence of a traffic accident is not limited to the above method, and various methods can be used.

That is, the traffic accident determination/search unit 24 has a function of determining whether a traffic accident has occurred in a moving object based on at least one of the position and speed of the moving object.

Furthermore, when a user inputs a search request for traffic accident cases through the user interface 3 (details will be described later), the traffic accident determination/search unit 24 searches mobile object data that meets the search request conditions. is read from the database 23, and based on the read mobile object data, it is determined whether a traffic accident has occurred using the method described above. If it is determined that a traffic accident has occurred, a traffic accident list is created that includes moving body data regarding this traffic accident case. A traffic accident list is created and output to the user interface 3.

For example, from the user interface 3, the intersection ID (including the location information of the intersection) where the traffic accident to be searched occurred, and the date and time (including the date and time interval such as time zone) when the traffic accident occurred are input. In this case, moving object data at the intersection corresponding to the input intersection ID is read out. If a traffic accident has occurred, this traffic accident case is searched and a traffic accident list is created. If there are multiple traffic accident cases that meet the conditions, a traffic accident list of all traffic accident cases is created and output.

In addition, if only the intersection ID where a traffic accident occurred is input, the occurrence of a traffic accident is detected based on the data of moving objects detected in the past at this intersection, and when a traffic accident occurs, this Create and output a traffic accident list for traffic accident cases. Note that "traffic accidents that occurred in the past" are, for example, accidents that occurred a predetermined period T (for example, from several weeks to several months, more specifically, for example, one month) from the time when the search request was input by the user. It can be a traffic accident that occurred during the period.

FIG. 7 is a diagram showing an example of a display of a traffic accident list. For example, various information such as the date, time, location, type of moving object, speed at the time of the accident, etc., of the traffic accident may be displayed on the printed matter output from the printer. mobile data is described.

That is, when the user specifies at least one of the time of occurrence (including date and time interval) or location of occurrence (or intersection ID (including sensor detection area)) of the traffic accident, the traffic accident determination/search unit 24 detects Then, the moving body data corresponding to the time or position of the traffic accident stored in the database 23 is read out, and based on at least one of the position and speed of the moving body included in the read moving body data. A function that determines whether or not a traffic accident has occurred with a moving object, and if it is determined that a traffic accident has occurred, creates a traffic accident list that is a list containing moving object data related to this moving object. We are prepared.

When the user inputs an image output request through the user interface 3, the image creation unit 25 stores the mobile object data regarding the traffic accident case searched by the traffic accident determination/search unit 24 in the database 23. Based on the read mobile object data, a CG image (for example, a CG video) of the time when the traffic accident occurred for the traffic accident case is created and output to the user interface 3 (see FIGS. 2 to 4). ). Note that templates for the shapes of various moving objects are stored in the database 23.

For example, when a desired traffic accident case is selected by the user interface 3 from the traffic accident list searched by the traffic accident determination/search unit 24, the movement included in the moving body data of the selected traffic accident case is Based on the position and speed of the body, a moving image of the moving body during the time period when the traffic accident occurred is created using CG (computer graphics) or the like and output to the user interface 3.

Further, if the sensor 1 is equipped with a microphone and the microphone detects audio, a moving image including audio data is created.
That is, when the user specifies at least one of the time of occurrence or the location of the traffic accident, the image creation unit 25 generates a moving body corresponding to the time of occurrence or location of the traffic accident stored in the database 23. It has the ability to read data and create images (still images, videos) related to traffic accidents based on the read mobile object data.

2 to 4 are explanatory diagrams showing examples of moving images created by the image creation unit 25 at a certain intersection. FIG. 2 is an image at time t1, FIG. 3 is an image at time t2, and FIG. 4 is an image at time t3. It shows images, that is, time-series images. As shown in FIG. 2, at time t1, vehicles V1 and V2 are traveling with a constant inter-vehicle distance. At time t2 (FIG. 3) after a certain period of time has elapsed, the inter-vehicle distance between vehicles V1 and V2 becomes shorter, and at time t3 (FIG. 4) at which a further certain period of time has elapsed, vehicles V1 and V2 have collided. In other words, a traffic accident has occurred.

The image creation unit 25 creates images from times t1 to t3 as moving images, as shown in FIGS. 2 to 4, and outputs them to the user interface 3. At this time, the speeds of vehicles V1 and V2 are displayed. For example, "○○km/h" is displayed. Further, although not shown, the speeds of the vehicles V1 and V2 may be displayed by the length of the arrow. Specifically, the faster the speed, the longer the arrow is displayed.

In this embodiment, an example in which the image creation unit 25 creates a moving image will be described, but the present invention is not limited to this, and one or more still images may be created. Further, although FIGS. 2 to 4 show an example in which a bird's-eye view image of the location where the traffic accident occurred is displayed, the image may be displayed from the perspective of the occupant of the moving object that caused the accident.

Returning to FIG. 1, the user interface 3 includes an input section 31 that can be operated by the user, and an output section 32 that presents various information to the user, and allows access to the control device 2 to determine the desired traffic accident information. An operation is performed to obtain a traffic accident list (traffic accident information) related to the case, or a video or still image during the time period in which the traffic accident occurred.

The input unit 31 is a keyboard, a mouse, a touch pen, or the like. The output unit 32 is a display, printer, or the like that outputs the traffic accident list. Further, when an image is output from the image creation section 25, the image is displayed on the display. Furthermore, it can also include a speaker that outputs the sound detected by the microphone.

Then, when the user inputs, for example, an intersection ID and the date and time of occurrence of a traffic accident as a traffic accident search request in the input unit 31, a traffic accident list of traffic accident cases matching these input data is obtained and output. The information is output from the unit 32 (for example, a printer).

As an example of the input operation, an image for inputting or selecting an intersection ID, date, and time zone is displayed on the display, and the input operation can be performed using this display screen. Note that the user interface 3 may be accessed locally on the server machine, or may be configured to be accessed via a network.

[Operation description of the first embodiment]
Next, the processing procedure of the traffic accident recording system 101 according to the first embodiment configured as described above will be explained with reference to the flowchart shown in FIG. 5.

First, in step S11, the sensor 1 detects moving objects existing around the travel path. Sensor data detected by the sensor 1 is output to the mobile object analysis section 21. For example, when the sensor 1 is a laser radar, the sensor data indicates received light data (for example, point group data) of reflected light reflected by an object from a laser emitted from the laser radar. In addition, when the sensor 1 is provided with a microphone, audio data detected by the microphone is added to the sensor data and output to the mobile object analysis section 21.

In step S12, the moving object analysis unit 21 identifies the type of each moving object, that is, whether it is a vehicle, a two-wheeled vehicle, or a pedestrian, based on the sensor data about each moving object detected by the sensor 1. Furthermore, the position and speed of each moving object are calculated based on the sensor data. Furthermore, if the detected moving object is present at an intersection (T-junction, crossroads, etc.), the intersection ID of this intersection is specified in step S13. The intersection ID is intersection-specific information that is set in advance. Data such as the type, position, speed, and intersection ID of the moving object (moving object data) are output to the database 23.

In step S14, the moving object analysis unit 21 stores the moving object data (type, position, speed data) and intersection ID of each moving object in the database 23.

In step S15, the traffic accident determination/search unit 24 determines whether a traffic accident search request has been issued from the user interface 3. If a search request for a traffic accident has not occurred (S15; NO), this process ends.

On the other hand, if a search request for a traffic accident has occurred (S15; YES), the traffic accident determination/search unit 24 detects the occurrence of a traffic accident in step S16. For example, a search request for a traffic accident includes the intersection ID (or intersection area information) where the traffic accident occurred and the date and time (or date and time interval) at which the traffic accident occurred. Then, the traffic accident determination/search unit 24 reads mobile object data that meets the above conditions (intersection ID (or intersection area information) and date and time (or date and time interval)) from the database 23, and based on the read mobile object data. Then, the occurrence of a traffic accident is detected using the method described above. In step S17, it is determined whether a traffic accident has occurred, and if the occurrence of a traffic accident is not detected (S17; NO), the process ends.

On the other hand, if the occurrence of a traffic accident is detected (S17; YES), in step S18, the traffic accident determination/search unit 24 creates a traffic accident list based on the mobile object data stored in the database 23. and output to the user interface 3. As a result, a traffic accident list as shown in FIG. 7 mentioned above is created, for example.

In step S19, the image creation unit 25 determines whether an image display request has been issued from the user interface 3. If an image display request has not occurred (S19; NO), this process ends.

On the other hand, if an image display request has been made (S19; YES), the image creation unit 25 creates and outputs an image (for example, a video) of the traffic accident case to be searched for in step S20.

Specifically, when an image display request is input, the image creation unit 25 generates an image based on the position and speed of the moving object from the moving object data regarding the traffic accident searched in the process of step S18. , create an image of the time period when the traffic accident occurred. For example, the videos shown in FIGS. 2 to 4 described above are created. Furthermore, the created moving image is output to the user interface 3. After that, this process ends.

Next, the processing procedure by the user interface 3 will be explained with reference to the flowchart shown in FIG. First, in step S31, the user interface 3 accepts a search request for traffic accidents (area of accident occurrence and time zone or time interval or date and time interval) from the user.

Next, in step S32, the user interface 3 determines whether a search request for a traffic accident has been input. If no search request has been input (S32; NO), this process ends.

On the other hand, if a search request has been input (S32; YES), in step S33, the user interface 3 outputs the search request to the traffic accident determination/search unit 24, and the traffic accident determination/search unit 24 Get a list of traffic accidents. As described above, the traffic accident search request includes information such as the intersection where the traffic accident occurred and the time period during which the traffic accident occurred. Further, the traffic accident list is created in the process of step S18 in FIG. 5 described above.

In step S34, the user interface 3 presents the traffic accident list to the output unit 32. For example, if the output unit 32 is a display, a traffic accident list is displayed on the display. Therefore, by looking at the display, the user can recognize moving object data (type, position, speed, etc.) regarding the traffic accident case to be searched.

Further, when the output unit 32 is a printer, it outputs a printed matter on which the traffic accident list is printed (see FIG. 7). Therefore, by looking at the printed matter, the user can recognize the mobile object data related to the traffic accident case that is the search target.

In step S35, the user interface 3 accepts the display of an image of a traffic accident, and further in step S36, the user interface 3 determines whether a request to display an image (for example, a video) of a traffic accident has been input. to decide. If an image display request has not been input (S36; NO), this process ends.

On the other hand, if an image display request has been input (S36; YES), in step S37, the user interface 3 outputs an image display request to the image creation section 25, and the image creation section 25 Obtain images at the time of a traffic accident. As described above, the image is created in the process of step S20 in FIG.

In step S38, the user interface 3 displays an image at the time of the traffic accident on the output unit 32. For example, when the output unit 32 is a display, an image at the time of a traffic accident is displayed on the display. Therefore, by looking at the display, the user can visually recognize images related to traffic accident cases that are search targets. Note that providing the image to the user is not limited to displaying it on the user interface 3, but may also provide a download link.

[Description of effects of the first embodiment]
In this way, in the traffic accident recording system 101 according to the first embodiment, the sensor 1 is installed around the running road on which the vehicle travels, detects moving objects existing on the running road, and furthermore detects the detected moving objects. The type, position, and speed of the vehicle are calculated and stored in the database 23. When a search request for a traffic accident is input from the user interface 3, the mobile object data matching the conditions included in the search request, such as the intersection ID where the traffic accident occurred and the date and time when the traffic accident occurred. is read from the database 23 to determine whether a traffic accident has occurred.
If it is determined that a traffic accident has occurred, a traffic accident list including moving body data related to this traffic accident is created and presented to the user.

Therefore, the user can easily search for a desired traffic accident case, obtain moving object data, that is, various data such as the type of moving object that caused the traffic accident, the position, speed, and intersection ID of the moving object, and can be recognized. Furthermore, when the sensor 1 is equipped with a microphone and the output section 32 is equipped with a speaker, it is possible to recognize the voice at the time of a traffic accident, and the situation at the time of a traffic accident can be recognized with higher accuracy.

Furthermore, when a request for outputting an image (for example, a video) is input through the user interface 3, images before and after the time of occurrence of the traffic accident that match this output request are created and sent to the output unit 32 of the user interface 3. will be displayed at Therefore, the user can visually recognize the situation of a desired traffic accident case by viewing the image, and can know the situation at the time of the traffic accident in more detail.

Therefore, for example, when an insurance company investigator wants to know the situation at the time of a traffic accident, he or she can easily obtain mobile data related to the desired traffic accident case and images at the time of the traffic accident. It becomes possible to easily recognize the situation when an accident occurs. Furthermore, since an image showing the desired traffic accident situation is provided, an insurance company investigator can use it to determine the percentage of fault.

Furthermore, since the speed of the moving object is superimposed on the video as an icon such as an arrow or as a numerical value, it is possible to easily recognize at what speed the traffic accident occurred.

In this embodiment, a vehicle is used as an example of a moving object, and a traffic accident in which vehicles collided with each other has been explained. However, a traffic accident between a vehicle and a motorcycle, a traffic accident between a vehicle and a pedestrian, a motorcycle Similarly, a list of traffic accidents and images of traffic accidents between two vehicles and between two-wheeled vehicles and pedestrians can be provided to the user.
Note that in this embodiment, sensor data at intersections and the like can be retained for a long period of time, from several weeks to several months. Therefore, it is possible to detect not only accidents at the intersection, but also so-called near-miss incidents.

[Description of modification of the first embodiment]
Next, a modification of the first embodiment described above will be described. FIG. 8 is a block diagram showing the configuration of a traffic accident recording system 101a according to the second embodiment. In this modification, a communication unit 26 is provided that performs communication (also referred to as road-to-vehicle communication) between the control device 2a and each vehicle. The communication section 26 is connected to the traffic accident determination/search section 24 . The communication unit 26 receives an airbag activation signal indicating that the airbag of the vehicle has activated by communicating with the vehicle.

Then, as a moving object detected by the moving object analysis unit 21, when the positional relationship of two vehicles approaches or overlaps, and an airbag activation signal is output from one of the two vehicles, , it is determined that this vehicle has collided with another vehicle and a traffic accident has occurred. That is, the occurrence of a traffic accident is detected based on the activation signal of the airbag.

In this way, the traffic accident recording system 101a according to the modified example receives the airbag activation signal output from the vehicle and determines whether a traffic accident has occurred based on the airbag activation signal, so it can achieve higher accuracy. It becomes possible to detect the occurrence of traffic accidents.

[Description of second embodiment]
Next, a second embodiment will be described. FIG. 9 is a block diagram showing the configuration of a traffic accident recording system 102 according to the second embodiment. The second embodiment differs from the first embodiment described above in that it includes a sensor data storage unit 27 that continuously stores sensor data detected by the sensor 1, and that the sensor The mobile object data is created using the sensor data stored in the data storage unit 27, and a traffic accident list is created and provided to the user. The difference is that an image related to the image is created and provided to the user. This will be explained in detail below.

As shown in FIG. 9, the control device 2b is different from FIG. 1 described above in that it includes a sensor data storage section 27 that stores sensor data detected by the sensor 1. The rest of the configuration is the same as that of the control device 2 shown in FIG. 1, so the same reference numerals are given and the description of the configuration will be omitted.

The sensor data stored in the sensor data storage section 27 is output to the traffic accident determination/search section 24 and the image creation section 25.

Further, the sensor data storage unit 27 and the database 23 described above each have a storage period set for storing data. The period during which the sensor data storage section 27 stores sensor data is set longer than the period during which the database 23 stores mobile object data and mobile object data.

[Operation description of second embodiment]
Next, the processing procedure of the traffic accident recording system 102 according to the second embodiment will be explained with reference to the flowchart shown in FIG.
First, in step S51, the sensor 1 detects moving objects existing around the travel path. Sensor data detected by the sensor 1 is output to the mobile object analysis section 21 and the sensor data storage section 27. Note that if the sensor 1 is equipped with a microphone, audio data detected by the microphone is added to the sensor data and output to the mobile object analysis section 21 and the sensor data storage section 27.

In step S52, the sensor data detected by the sensor 1 is stored in the sensor data storage section 27.

In step S53, the moving object analysis unit 21 identifies the type of each moving object, that is, whether it is a vehicle, a two-wheeled vehicle, or a pedestrian, based on the sensor data about each moving object detected by the sensor 1. Furthermore, the position and speed of each moving object are detected based on the sensor data. Furthermore, if the detected moving object is present at an intersection (such as a T-junction or crossroads), the intersection ID of this intersection is specified in step S54. Data such as the type, position, speed, and intersection ID of the moving object (moving object data) are output to the database 23.

In step S55, the moving object analysis unit 21 stores the moving object data (type, position, speed data) and intersection ID of each moving object in the database 23.

In step S56, the traffic accident determination/search unit 24 determines whether a traffic accident search request has been issued from the user interface 3. If a traffic accident search request has not occurred (S56; NO), this process ends.

On the other hand, if a search request for a traffic accident has occurred (S56; YES), the traffic accident determination/search unit 24 detects the occurrence of a traffic accident in step S57. For example, a search request for a traffic accident includes the intersection ID where the traffic accident occurred and the date and time when the traffic accident occurred. Then, the traffic accident determination/search unit 24 reads out the moving object data that meets the above conditions (intersection ID and date and time) from the database 23, and uses the method described above to determine the traffic accident based on the read moving object data. The occurrence is detected (step S58). If the occurrence of a traffic accident is not detected (S58; NO), this process ends.

On the other hand, if the occurrence of a traffic accident is detected (S58; YES), in step S59, the traffic accident determination/search unit 24 creates a traffic accident list based on the mobile object data stored in the database 23. and output to the user interface 3. As a result, a traffic accident list as shown in FIG. 7, for example, is output.

In step S60, the traffic accident determination/search unit 24 determines whether a detailed search request, which is a search request for a more detailed traffic accident, has been generated from the user interface 3. For example, in the traffic accident list created in step S59, if there is a risk of data tampering, the user inputs a detailed search request.

Alternatively, if mobile data for a period longer than the storage period in which the database 23 stores mobile data is required, the user inputs a detailed search request. If a detailed search request has occurred (S60; YES), the process moves to step S61. If a detailed search request has not occurred (S60; NO), the process moves to step S62.

In step S61, the traffic accident determination/search unit 24 calculates moving body data based on the sensor data stored in the sensor data storage unit 27, and further creates a traffic accident list and outputs it to the user interface 3. do. Therefore, a traffic accident list based on the sensor data detected by the sensor 1 (original data that is free from falsification) can be presented to the user. Alternatively, a traffic accident list that includes moving object data for a longer period than the storage period in the database 23 can be presented to the user.

In step S62, the image creation unit 25 determines whether or not an image output request has been generated from the user interface 3. If an image output request has not occurred (S62; NO), this process ends.

On the other hand, if an image output request has occurred (S62; YES), the image creation unit 25 creates and outputs an image (for example, a video) of the traffic accident case to be searched for in step S63.

Specifically, when an image output request is input, the image creation unit 25 generates moving object data regarding the traffic accident case searched in step S59, that is, data on the position and speed of the moving object. An image of the traffic accident is created based on the following. For example, the images (videos) shown in FIGS. 2 and 3 described above are created. Furthermore, the created moving image is output to the user interface 3.

In step S64, the image creation unit 25 determines whether a detailed display request, which is a request to display a more detailed moving image, has been issued from the user interface 3. For example, if the video created in step S63 is displayed for a short period of time, or if there is a concern that the data may be tampered with, the user inputs a request to display details of the video.

If a video detail display request has been made (S64; YES), in step S65, the image creation unit 25 generates images before and after the traffic accident occurrence time based on the sensor data stored in the sensor data storage unit 27. An image is created for a predetermined period of time (a period longer than the video created in S63), and the created image is output to the user interface 3. Therefore, images over a longer period of time based on sensor data detected by the sensor 1 (original data that is free from falsification) can be presented to the user. After that, this process ends.

Next, the processing procedure of the user interface 3 will be explained with reference to the flowchart shown in FIG. First, in step S71, the user interface 3 receives a search input for traffic accidents from the user.

Next, in step S72, the user interface 3 determines whether a search request for a traffic accident has been input. If no search request has been input (S72; NO), this process ends.

On the other hand, if a search request has been input (S72; YES), in step S73, the user interface 3 outputs the search request to the traffic accident determination/search unit 24, and the traffic accident determination/search unit 24 Get a list of traffic accidents.

In step S74, the user interface 3 presents the traffic accident list to the output unit 32. For example, if the output unit 32 is a display, a traffic accident list is displayed on the display. Therefore, by looking at the display, the user can recognize moving object data related to traffic accident cases to be searched. Further, when the output unit 32 is a printer, it outputs a printed matter on which the traffic accident list is printed. Therefore, by looking at the printed matter, the user can recognize the mobile object data related to the traffic accident case that is the search target.

In step S75, the user interface 3 determines whether a detailed search request has been input. If it has not been input (S75; NO), the process moves to step S78. If it has been input (S75; YES), a detailed search request is output to the traffic accident determination/search unit 24.

In step S76, the user interface 3 obtains the detailed traffic accident list output from the traffic accident determination/search unit 24.

In step S77, the user interface 3 presents the acquired detailed traffic accident list to the user via the output unit 32 such as a display or printer.

In step S78, the user interface 3 accepts a request to display an image of a traffic accident. In step S79, it is determined whether or not an image display request has been input, and if it has not been input (S79; NO), the process ends.

On the other hand, if an image display request has been input (S79; YES), in step S80, the user interface 3 outputs an image display request to the image creation section 25, and the image creation section 25 Obtain an image (for example, a video) at the time of a traffic accident.

In step S81, the user interface 3 displays an image at the time of the traffic accident on the output unit 32. For example, when the output unit 32 is a display, an image at the time of a traffic accident is displayed on the display. Therefore, by looking at the display, the user can visually recognize images related to traffic accident cases that are search targets.

In step S82, the user interface 3 determines whether a request for displaying image details has been input. If a request for displaying detailed images has not been input (S82; NO), this process ends. If an image detail display request has been input (S82; YES), the process moves to step S83.

In step S83, the user interface 3 acquires the detailed image output from the image creation section 25.

In step S84, the user interface 3 displays the acquired detailed image on the display. After that, this process ends.

[Description of effects of second embodiment]
In this way, the traffic accident recording system 102 according to the second embodiment includes the sensor data storage section 27 that stores sensor data detected by the sensor 1. At this time, the period for storing sensor data in the sensor data storage section 27 is set longer than the period for storing moving object data in the database 23. When the user inputs a search request for detailed moving object data (detailed search request), moving object data is calculated based on the sensor data stored in the sensor data storage unit 27, and the Create an accident list. Therefore, the user can obtain a traffic accident list that is free from data falsification, which is extremely useful, for example, when making insurance calculations by referring to the traffic accident list.

In addition, since the image at the time of the traffic accident is created based on the sensor data stored in the sensor data storage unit 27, the image can be created not only during the time period when the traffic accident occurred, but also over a longer period of time before and after the accident. For example, it becomes possible to more reliably investigate the causes of traffic accidents.

[Description of third embodiment]
Next, a third embodiment will be described. FIG. 12 is a block diagram showing the configuration of a traffic accident recording system according to the third embodiment.
As shown in FIG. 12, a traffic accident recording system 103 according to the third embodiment differs from that in FIG. 1 described above in that an administrator server 4 is provided. The rest of the configuration is the same as that in FIG. 1, so the same reference numerals are given and the explanation of the configuration will be omitted. The detailed configuration of the administrator server 4 will be described below.

The administrator server 4 includes a usage record aggregation section 41, a billing section 42, and an administrator interface 43. The administrator server 4 is connected to the user interface 3 by wire or wirelessly.

The usage record aggregation unit 41 aggregates and stores the number of times the user performed a search on the user interface 3, the number of times an image was displayed, and the search time required for the search (hereinafter referred to as "usage record data"). . For example, if user P1 enters a search request for a target traffic accident on the user interface 3 in order to search for traffic accident cases and obtains a traffic accident list, the number of times the search request was executed in this process is , the number of times the image was displayed, and the time required for the search are stored as usage record data of the user P1.

The billing unit 42 calculates the amount to be charged to each user based on usage record data for each user. For example, the amount of money is set depending on the number of times the search is performed, the time required for the search request, the number of times the traffic accident list is provided, and so on. At this time, a user ID, which is information for identifying each user, may be set for each user, and the amount to be charged may be determined for each user ID according to the number of times the traffic accident list is provided. It is possible.

The administrator interface 43 has a function operated by an administrator who manages the traffic accident recording system 103, and performs processing such as creating a bill according to the amount set by the billing section 42.

[Operation description of third embodiment]
Next, a processing procedure of the traffic accident recording system 103 according to the third embodiment will be explained. The processing by the sensor 1 and the control device 2 is the same as the flowchart shown in FIG. 5 described above, so the explanation will be omitted.

The processing procedure in the user interface 3 will be described below with reference to the flowchart shown in FIG. The processing in steps S91 to S98 shown in FIG. 13 is similar to the processing in steps S31 to S38 shown in FIG. 6 described above. Therefore, the processing after step S99 shown in FIG. 13 will be explained.

In step S99 of FIG. 13, the user interface 3 calculates usage record data including the time or number of times the user performed a traffic accident search and displaying an image of a traffic accident, and uses the calculated usage record data as a user interface. The information is stored in a storage unit (not shown) provided in the interface 3.

In step S100, the user interface 3 outputs the stored usage record data to the administrator server shown in FIG. 12 at regular intervals (regularly).

Next, the processing procedure in the administrator server 4 will be explained with reference to the flowchart shown in FIG.
First, in step S111, the usage record aggregation unit 41 aggregates the usage record data output from the user interface 3 for each user. That is, the usage history aggregation unit 41 stores usage history data for each user.

In step S112, the charging unit 42 calculates the billing amount to be charged to each user based on the usage history data of each user.

In step S113, the administrator interface 43 outputs the billed amount for each user. By transmitting the output billed amount to each user, it is possible to collect compensation for performing the traffic accident search.

[Description of effects of third embodiment]
In this way, in the traffic accident recording system 103 according to the third embodiment, when each user inputs a search request for traffic accidents and acquires a traffic accident list or acquires an image, these operations are performed. Calculate the billing amount by charging the consideration according to the amount. Then, the calculated billing amount is billed to the user. Therefore, the administrator of the traffic accident recording system 103 can obtain compensation according to the frequency (number of times and time) each user uses the system.

In addition, by paying the necessary price, users can obtain a list of traffic accidents or images (still images, videos) of their desired traffic accident case, and can learn about the situation at the time of the traffic accident. Become.

Although the embodiments have been described above, the statements and drawings that form part of this disclosure should not be understood as limiting the present invention. Various alternative embodiments, implementations, and operational techniques will be apparent to those skilled in the art from this disclosure.

1 Sensors 2, 2a, 2b Control device 3 User interface 4 Administrator server 21 Mobile object analysis section 23 Database 24 Traffic accident determination/search section 25 Image creation section 26 Communication section 27 Sensor data storage section 31 Input section 32 Output section 41 Usage record aggregation unit 42 Billing unit 43 Administrator interface 101, 101a, 102, 103 Traffic accident recording system P1 User V1, V2 Vehicle

Claims (8)

A traffic accident recording system that records the situation at the time of the traffic accident when the traffic accident occurs,
A sensor installed around a running road to detect moving objects including pedestrians, motorcycles, and vehicles present on the running road;
a moving object analysis unit that detects moving object data that is data including the position and speed of the moving object based on sensor data detected by the sensor;
a database that stores moving object data detected by the moving object analysis section;
When the user specifies at least one of the time of occurrence or the location of the traffic accident, the mobile object data corresponding to the time of occurrence or location of the traffic accident stored in the database is read out, and the read movement is performed. determining whether or not a traffic accident has occurred in the mobile body based on at least one of the position and speed of the mobile body included in the body data, and when it is determined that a traffic accident has occurred; a traffic accident determination/search unit that creates a traffic accident list that is a list containing mobile object data regarding this mobile object;
A traffic accident recording system characterized by being equipped with. When the user specifies at least one of the time or location of a traffic accident,
The mobile object data of the mobile object that corresponds to the time or location of the occurrence of the traffic accident and that has been determined by the traffic accident determination/search unit to have been involved in a traffic accident is read out from the database. The traffic accident recording system according to claim 1, further comprising an image creation unit that creates an image related to a traffic accident based on moving body data. The sensor acquires audio emitted from the mobile object,
The traffic accident recording system according to claim 2, wherein the image creation unit adds the audio to the image related to the traffic accident. further comprising a sensor data storage unit that continuously records sensor data detected by the sensor,
The sensor data storage section and the database each have a storage period for storing data, and the period during which the sensor data storage section stores sensor data is the same as when the database stores the mobile object data. is set longer than the period to
The image creation unit creates an image based on sensor data stored in the sensor data storage unit when the user requests continuous provision of images of the moving body. The traffic accident recording system according to claim 2. The traffic accident according to claim 2, wherein the image related to the traffic accident is a moving image, and the image creation unit displays the speed of the moving object superimposed on the moving image using an icon or a numerical value indicating the speed. Accident recording system. When a traffic accident occurs, a method for providing traffic accident information includes recording the situation at the time of the traffic accident and providing the recorded traffic accident information to a user, the method comprising:
The moving object analysis unit acquires moving object data including the position and speed of moving objects including pedestrians, motorcycles, and vehicles existing on the driving path, which are detected by sensors installed around the driving path. the step of
the moving object analysis unit storing the moving object data in a database;
When the user specifies at least one of the time of occurrence or location of a traffic accident, the traffic accident determination/search unit determines the movement corresponding to the time of occurrence or location of the traffic accident stored in the database. read the body data, determine whether a traffic accident has occurred in the mobile body based on at least one of the position and speed of the mobile body included in the read mobile body data, and determine whether a traffic accident has occurred. If it is determined that the mobile object is a traffic accident, the step of creating a traffic accident list that is a list including mobile object data regarding the mobile object;
an output unit presenting the created traffic accident list to the user;
a charging unit charging the user a fee for providing the traffic accident list;
A method for providing traffic accident information, comprising: the billing unit sets a user ID, which is information for identifying each user, for the user;
7. The method of providing traffic accident information according to claim 6 , wherein the step of charging the consideration determines the amount to be charged according to the number of times the traffic accident list is provided for each user ID. When the user specifies at least one of the time of occurrence or the location of the traffic accident, the image creation unit reads the moving object data in the time period of the traffic accident from the database, and based on the read moving object data. further comprising the step of creating an image related to a traffic accident,
8. The method for providing traffic accident information according to claim 6 , wherein the step of charging the fee includes charging a fee for the image provided to the user in addition to the traffic accident list.

Images