Control system and control method

Abstract

This invention provides a control system and control method that can appropriately manage event files necessary for the user. [Solution] The control system 10 according to this disclosure is a control system for controlling a recording device that performs event recording processing associated with vehicle impact detection, and comprises a calculation unit 11 and a control unit 12. The calculation unit 11 calculates the impact object passage time, which indicates the time from the current time until the vehicle passes the impact object, based on an image that includes a stationary impact object present on the road surface that causes an impact on the vehicle. The control unit 12 controls the recording device to delete, after a predetermined time has elapsed since the vehicle passed the impact object, the event record from the event record of the recording device that corresponds to the impact object passage time and is the event record when the vehicle passed the impact object.

Description

Technical Field

[0001] The present disclosure relates to a control system and a control method.

Background Art

[0002] Patent Document 1 discloses an impact detection malfunction prevention device that can suppress the execution of the recording process of an event file when an impact not caused by an accident is detected. In the impact detection malfunction prevention device disclosed in Patent Document 1, a location where impact detection has been performed a predetermined number of times or more is registered as an impact detection malfunction location regardless of an accident, and in the impact detection malfunction location, the execution of the recording process of the event file is suppressed.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the impact detection malfunction prevention device disclosed in Patent Document 1 described above, if it is not registered in advance as an impact detection malfunction location, the execution of the recording process of an event file not related to an accident cannot be suppressed. Therefore, an event file not related to an accident is recorded, making it difficult for the user to find the event file necessary for the user.

[0005] The present disclosure has been made in view of such circumstances, and an object thereof is to provide a control system and a control method capable of appropriately managing an event file necessary for a user.

Means for Solving the Problems

[0006] The control system according to the present disclosure is A control system for controlling a recording device that performs event recording processing in response to vehicle impact detection, A calculation unit calculates the impact object passage time, which indicates the time from the current time until the vehicle passes the impact object, based on an image that includes an immovable impact object on the road surface that will cause the vehicle to impact the vehicle. A control unit controls the recording device to delete, from the event records of the recording device, the event record corresponding to the time the vehicle passed the impact object, after a predetermined time has elapsed since the vehicle passed the impact object. It is equipped with.

[0007] The control system described in this disclosure performs recording of event files unrelated to accidents, and these are initially recorded in a recording device. However, after a predetermined time has elapsed since the vehicle passed over the impacting object, the event files unrelated to the accident are deleted from the recording device. This configuration allows for the proper management of event files necessary for the user.

[0008] The control method relating to this disclosure is: A control method for controlling a recording device that performs event recording processing in response to vehicle impact detection, Based on an image of a stationary impactor present on the road surface that causes an impact on the vehicle, the impactor passage time, which indicates the time from the current point until the vehicle passes the impactor, is calculated. After a predetermined time has elapsed since the vehicle passed the impacting object, the recording device is controlled to delete from the event records of the recording device the event record corresponding to the time the vehicle passed the impacting object. The computer performs the process.

[0009] In the control method described herein, event files unrelated to an accident are recorded and initially stored in the recording device. However, after a predetermined time has elapsed since the vehicle passed the impacting object, the event files unrelated to the accident are deleted from the recording device. This configuration allows for the proper management of event files necessary for the user. [Effects of the Invention]

[0010] This disclosure provides a control system and control method that can appropriately manage event files necessary for the user. [Brief explanation of the drawing]

[0011] [Figure 1] This is a block diagram illustrating the control system according to Embodiment 1. [Figure 2] This diagram illustrates the state of a vehicle when passing over a step or curb. [Figure 3] This is a flowchart illustrating the driving assistance method according to Embodiment 1. [Figure 4] This is a block diagram illustrating the control system according to Embodiment 2. [Figure 5] This is a schematic diagram showing whether or not impact detection is performed based on vehicle speed and the height of the impacting object. [Figure 6] This is a block diagram illustrating the control system according to Embodiment 2. [Figure 7] This is a flowchart illustrating the driving assistance method according to Embodiment 2. [Figure 8] This is a block diagram illustrating the control system according to Embodiment 3. [Figure 9] This is a schematic diagram showing whether or not impact detection is performed according to vehicle speed and vehicle weight. [Figure 10] This is a block diagram illustrating the control system according to Embodiment 3. [Figure 11] This is a flowchart illustrating the driving assistance method according to Embodiment 3. [Modes for carrying out the invention]

[0012] Hereinafter, the present disclosure will be described through embodiments of the invention, but the invention according to the claims is not limited to the following embodiments. Also, not all of the configurations described in the embodiments are essential as means for solving the problems. For clarity of explanation, the following description and drawings have been appropriately omitted and simplified. In each drawing, the same reference numerals are assigned to the same elements, and redundant descriptions are omitted as necessary.

[0013] (Embodiment 1) <Control System> The control system according to Embodiment 1 will be described. FIG. 1 is a block diagram illustrating the control system according to Embodiment 1. As shown in FIG. 1, the control system 10 includes a calculation unit 11 and a control unit 12.

[0014] The control system 10 controls a recording device that executes event recording processing associated with impact detection of a vehicle. The event recording processing is a process of recording a camera video file and sensor values at the time of impact detection as a short-time event file separately from normal recording when the vehicle detects an impact while traveling and the impact value exceeds a set sensor threshold. The recording destination is a storage unit (not shown) inside and outside the control system 10. The event file is stored, for example, in the event folder of the storage unit. Although details will be described below, the control system 10 calculates the passing time of the impact object from the image, and after a predetermined time has elapsed since the vehicle passed the impact object, controls the recording device 13 to delete the event recording at the time when the vehicle passed the impact object and the event recording for the passing time of the impact object.

[0015] The control system 10 is configured to be able to communicate with the recording device 13. The recording device 13 executes event recording processing. The recording device 13 is, for example, a drive recorder. However, as shown in the block diagram of FIG. 1, the control system 10 and the recording device 13 are not limited to a configuration in which they can communicate with each other, and a configuration in which the calculation unit 11 and the control unit 12 of the control system 10 are included in the recording device 13 may also be used.

[0016] Alternatively, the recording device 13 may include a part of the control system 10 (either the calculation unit 11 or the control unit 12), and the server (not shown) may include a part of the control system 10 (the other part of the calculation unit 11 or the control unit 12) to perform distributed processing. Below, the calculation unit 11 and the control unit 12 shown in Figure 1 will be described in detail. The control system 10 will be described as controlling a drive recorder.

[0017] <Calculation of the time it takes for an impacting object to pass through> First, the calculation unit 11 will be described. Based on an image containing an impact object that will hit the vehicle, the calculation unit 11 calculates the impact object passage time, which indicates the time from the current time until the vehicle passes over the impact object. An impact object typically refers to a stationary impact object that is installed, fixed, or formed on the road surface, but is not limited to this and may also include a road surface with irregularities, and may include any object that can cause an impact when a vehicle passes over it, such as speed bumps, stones, or uneven road surfaces.

[0018] Referring to Figure 2, the method for calculating the time it takes for an impact object to pass will be explained. Figure 2 shows the state when a vehicle passes over a step. As shown in Figure 2, vehicle C1 is about to pass over a step IP1 located in front of it. Step IP1 is an example of an impact object. The calculation unit 11 calculates the distance from point S1 to point S2 and the distance from point S2 to point S3 by analyzing the image including step IP1. Point S1 indicates the current position of vehicle C1, point S2 indicates the position of the step closest to point S1, and point S3 indicates the position of the step furthest from point S2. Note that the current position of vehicle C1 refers to the point where vehicle C1 is located when the process of calculating the time it takes for an impact object to pass is started.

[0019] Here, vehicle C1 can obtain information about its speed from location information such as GPS. The calculation unit 11 (control system 10) then obtains the information about the vehicle speed from vehicle C1. The calculation unit 11 can calculate the time it takes to travel a certain distance by dividing the distance by the vehicle speed. In the example shown in Figure 2, the calculation unit 11 calculates 3 seconds by dividing the distance from point S1 to point S2 by the vehicle speed. Also in the example shown in Figure 2, the calculation unit 11 calculates 1 second by dividing the distance from point S2 to point S3 by the vehicle speed. In this way, the calculation unit 11 can calculate the time it takes for vehicle C1 to pass over the step IP1 as 4 seconds.

[0020] Furthermore, the calculation unit 11 may improve the accuracy of distance calculation by comparing the distance from point S1 to point S2 and the distance from point S2 to point S3 obtained from the image with values ​​obtained from a distance sensor mounted on the vehicle C1.

[0021] <Controlling the dashcam> Next, the control unit 12 will be described. The control unit 12 controls the drive recorder so that, after a predetermined time has passed since the vehicle passed the impacting object, it deletes the event record from the drive recorder's event record that corresponds to the time the vehicle passed the impacting object. Note that the event record is a so-called overwrite-protected record.

[0022] The control of the drive recorder by the control unit 12 will be explained with reference to Figure 2. In Figure 2, the drive recorder performs event recording processing for the 4 seconds it takes for the impact object to pass, in other words, when vehicle C1 passes through the section from point S1 to point S3. As a result, the event recording for the 4 seconds it takes for the impact object to pass is recorded in the storage unit (not shown in Figure 1) as an event record of when the vehicle passed the impact object. The control unit 12 then controls the system to delete the event recording for the 4 seconds it takes for the impact object to pass after a predetermined time has elapsed since the vehicle passed the impact object. This predetermined time could be, for example, 2 seconds after the impact object has passed, and can be set arbitrarily. In this way, the drive recorder performs event file recording processing unrelated to the accident and records it in the drive recorder, but after a predetermined time has elapsed since the vehicle passed the impact object, the event files unrelated to the accident are deleted from the drive recorder.

[0023] Let's explain the control of the drive recorder by the control unit 12 using another example. Although not shown in Figure 2, let's assume that before reaching point S1, vehicle C1 made contact with another vehicle and continued to drive in that state. Then, let's assume that it passed over the step IP1 shown in Figure 2. In this case, the drive recorder performs event recording processing for the event file when vehicle C1 made contact with the other vehicle and for the event file when it passed over the step IP1. In other words, the drive recorder has recorded an event file when vehicle C1 made contact with the other vehicle and an event file when it passed over the step IP1. The former is an event file related to the accident. The latter is an event file unrelated to the accident. The control unit 12 controls the drive recorder to delete the latter event file after a predetermined time has elapsed since vehicle C1 passed over the step IP1. As a result, after a predetermined time has elapsed since vehicle C1 passed over the step IP1, the drive recorder will still have the event file from when vehicle C1 made contact with the other vehicle.

[0024] If event files unrelated to the accident are recorded and not deleted, it will strain the capacity of the event folder in the storage unit (not shown in Figure 1). Generally, since the event folder is not overwritten, the user needs to organize files when the free space runs out. However, in the control system 10 according to Embodiment 1, even if event files unrelated to the accident are stored in the event folder, they are deleted after a predetermined time has elapsed since the vehicle passed over the impact object, so it does not strain the capacity. Furthermore, the user can easily find the necessary event files, such as event files related to the accident.

[0025] The timing at which the control unit 12 deletes the event recording from the drive recorder can be anytime the vehicle has passed over an impact object. In the example shown in Figure 2, after the vehicle C1 has passed point S3, the event recording that occurred when it passed over the step IP1, specifically the 4-second period during which the vehicle passed over the impact object, should be deleted at any point.

[0026] Furthermore, the drive recorder may record not only the 4 seconds of time the impacting object passed, but also the start time of the impacting object's passage (for example, 10:30:30 on July 16th) and the end time of the impacting object's passage (for example, 10:30:34 on July 16th). In this case, the control unit 12 performs the following processing, for example, at 10:30:30 on July 17th, 24 hours after the start time of the impacting object's passage (10:30:30 on July 16th). The control unit 12 controls the drive recorder to delete the event file for the 4 seconds from the start time of the impacting object's passage (10:30:30 on July 16th) to the end time of the impacting object's passage (10:30:34 on July 16th).

[0027] Furthermore, the control unit 12 uses the impact object passage time calculated in real time by the calculation unit 11 to control the deletion of event records from the drive recorder. Therefore, unlike conventional technology, there is no need for historical information that records whether past event records were executed or not. Thus, the control system 10 can accurately identify event files unrelated to the accident. And, because event files unrelated to the accident are deleted, the control system 10 can properly manage necessary event files, as necessary event files for the user, such as event files related to the accident, remain in the event folder.

[0028] Here, an example was described in which the control unit 12 controls the drive recorder to delete event recordings for the 4-second period during which the impact object passes. However, the control unit 12 is not limited to this, and may control the drive recorder to delete event recordings for the extended or shortened period during which the impact object passes. With this configuration, when the calculation unit 11 calculates the impact object passage time, it identifies the current location S1, the location S2 of the impact object including the step IP1 in front of the vehicle, and the location S3 after the impact based on the image, but can also handle cases where the clarity of the image is reduced. In addition, since the calculation unit 11 receives vehicle speed information of vehicle C1 from GPS location information, it can also handle situations where precise time calculation becomes difficult due to poor reception conditions.

[0029] Thus, the control unit 12 can be configured to control the drive recorder to delete event records from when the vehicle passed the impacting object, specifically those recorded during the time the vehicle passed the impacting object or during a period that was extended or shortened, after a predetermined time has elapsed since the vehicle passed the impacting object.

[0030] Furthermore, if the control system 10 (control unit 12) acquires information from the vehicle's environmental sensors about the surrounding environment where accidents are likely to occur, such as traffic lights, pedestrian crossings, and intersections, it may control the drive recorder so that event recordings are not deleted after a predetermined time has elapsed since the vehicle passed over an impact object. With this configuration, the control system 10 can leave event files in the event folder if there is a risk of an accident.

[0031] Furthermore, the control system 10 (control unit 12) may perform the following control if, within a predetermined time elapsed after the vehicle has passed an impacting object, the image includes the vehicle in a stopped state or a person or object in contact with the vehicle. The control system 10 (control unit 12) may control the drive recorder so that the event record is not deleted after the predetermined time has elapsed. That is, the control system 10 determines that there is a possibility that the event file is necessary for the user and leaves the event file in the event folder without deleting it from the drive recorder.

[0032] <Control Method> Next, the control method according to Embodiment 1 will be described. Figure 3 is a flowchart illustrating the driving support method according to Embodiment 1.

[0033] First, the control system 10 determines whether or not the drive recorder image contains an impact object (step ST1). If the drive recorder image contains an impact object (step ST1YES), the control system 10 (calculation unit 11) calculates the impact object passage time, which indicates the time it takes for the vehicle to pass over the impact object, based on the image containing the impact object that caused the vehicle to hit the object (step ST2). On the other hand, if the drive recorder image does not contain an impact object (step ST1NO), the process in step ST1 is repeated.

[0034] Following step ST2, the recording device 13 performs event recording processing related to the detection of a vehicle impact (step ST3). The event file recorded by the recording device 13 is stored in the event folder of the storage unit (not shown in Figure 1).

[0035] Next, the control unit 12 controls the recording device 13 to delete the event record of the vehicle passing over the impact object, specifically the event record corresponding to the time the impact object passed, after a predetermined time has elapsed since the vehicle passed over the impact object (step ST4).

[0036] Thus, in the control method according to Embodiment 1, in step ST3, the recording process for event files unrelated to the accident is performed and temporarily recorded in the drive recorder. Then, in step ST4, after a predetermined time has elapsed since the vehicle passed over the impacting object, the event files unrelated to the accident are deleted from the drive recorder. Therefore, in the control method according to Embodiment 1, after a predetermined time has elapsed since the vehicle passed over the impacting object, the drive recorder remains with the necessary event files, such as event files related to the accident. This allows the user to easily find the necessary event files.

[0037] (Embodiment 2) <Height of impact object> A control system according to Embodiment 2 will now be described. Figure 4 is a block diagram illustrating the control system according to Embodiment 2. As shown in Figure 4, the control system 20 includes an analysis unit 14, a calculation unit 11, and a control unit 12. The control system 20 is configured to communicate with the recording device 13, similar to the control system 10 according to Embodiment 1. The calculation unit 11 and the recording device 13 are the same as in Embodiment 1, so their description will be omitted. Here, the analysis unit 14 and the control unit 12 will be described. In Embodiment 2, as in Embodiment 1, the recording device 13 will be described as a drive recorder.

[0038] The analysis unit 14 analyzes information regarding the height of the impacting object from the image. The control unit 12 then controls the drive recorder to delete the event record corresponding to the time the vehicle passed the impacting object, after a predetermined time has elapsed since the vehicle passed the impacting object, if the height of the impacting object determined by the analysis unit 14 is less than a predetermined value and greater than or equal to a predetermined value. Here, the height of the impacting object less than a predetermined value may be, for example, the minimum ground clearance of the vehicle (also called the road clearance). The height of the impacting object greater than or equal to a predetermined value determined by the analysis unit 14 may be, for example, a height of the impacting object that can be arbitrarily set by the user, or a recommended value that does not result in a large impact (i.e., is not related to an accident) based on past impact records and statistics. Furthermore, it is preferable that the control unit 12 controls the drive recorder to delete the event record corresponding to the time the vehicle passed the impact object, after a predetermined time has elapsed since the vehicle passed the impact object, when the height of the impact object determined by the analysis unit 14 is below a predetermined value and within a predetermined range. For example, suppose the minimum ground clearance of the vehicle is 15 centimeters and the height of the impact object is 14 centimeters. In this case, since there is a possibility that the event file will be related to an accident such as a vehicle malfunction, the control unit 12 controls the drive recorder not to delete the event record when the height of the impact object determined by the analysis unit 14 is below a predetermined value and the height of the impact object is between 10 centimeters and 15 centimeters. Also, the control unit 12 controls the drive recorder to delete the event record when the height of the impact object determined by the analysis unit 14 is below a predetermined value and within a predetermined range such that the height of the impact object is less than 10 centimeters.

[0039] <Drive recorder control based on the height of the impacting object> Referring to Figure 5, an example of how the control unit 12 controls the drive recorder based on the height information of the impacting object will be described. Figure 5 is a schematic diagram showing whether or not impact detection occurs depending on the vehicle speed and the height of the impacting object. Generally, the faster the vehicle speed, the more impact the vehicle will experience even if the height of the impacting object is low. Figure 5 shows the boundary at which the drive recorder detects impact. In Figure 5, if the point plotted with the vehicle speed and the height of the impacting object is within region R1, the drive recorder will not detect an impact even if the vehicle is hit by an impacting object. On the other hand, if the point plotted with the vehicle speed and the impacting object is within region R2, the drive recorder will detect an impact if the vehicle is hit by an impacting object.

[0040] In other words, if the point plotted with respect to vehicle speed and the height of the impacting object falls within region R1, the drive recorder does not detect an impact and therefore does not perform event recording processing. For this reason, the control unit 12 does not control the drive recorder. On the other hand, if the point plotted with respect to vehicle speed and the height of the impacting object falls within region R2, the drive recorder detects an impact. For this reason, the control unit 12 controls the drive recorder to delete the event recording that occurred when the vehicle passed the impacting object, specifically the event recording corresponding to the time the impacting object passed, after a predetermined time has elapsed since the vehicle passed the impacting object.

[0041] The control system 20 acquires information about the vehicle speed from the vehicle. For example, at a speed of 60 km / h, the control unit 12 determines from Figure 5 that the height of the impacting object that controls the drive recorder is 10 mm or more. Then, based on the information about the height of the impacting object from the analysis unit 14, if the height of the impacting object is 10 mm or more, it is included in region R2, so the control unit 12 controls the drive recorder to delete the event recording for the duration of the impacting object's passage after a predetermined time has elapsed since the vehicle passed the impacting object. For example, at a speed of 80 km / h, even if the height of the impacting object is 10 mm, the control unit 12 determines from Figure 5 that it is included in the R2 region where impact is detected based on the plot of vehicle speed and impacting object height, and initially records the event, but controls the drive recorder to delete the event recording for the duration of the impacting object's passage after a predetermined time has elapsed since the vehicle passed the impacting object.

[0042] Here, the control unit 12 may control the drive recorder based on information about the height of the impacting object stored in the memory unit that stores whether or not event recording processing has been performed. Figure 6 is a block diagram illustrating a control system according to Embodiment 2. As shown in Figure 6, the control system 21 includes a memory unit 15, an analysis unit 14, a calculation unit 11, and a control unit 12. The configurations other than the memory unit 15 and the control unit 12 shown in Figure 6 are the same as in Figure 4, so their explanation will be omitted. Here, the memory unit 15 and the control unit 12 will be explained in detail.

[0043] The memory unit 15 stores whether or not event recording processing is performed according to the height of the impacting object. This will be explained in more detail with reference to Table 1. Table 1 is an example of a list of information regarding the height of impacting objects stored in the memory unit 15. It is intended to explain whether or not event recording processing is performed depending on the height and shape of the impacting object, and the height and shape are not limited.

[0044] [Table 1]

[0045] As shown in Table 1, the memory unit 15 stores whether or not event recording processing is performed according to the height of the impacting object. In addition, in the example shown in Table 1, the memory unit 15 also stores the shape of the impacting object in relation to its height. For example, in Table 1, it is shown that event recording processing was performed when the height of the impacting object is 5 mm and the shape of the impacting object is flat. Also in Table 1, it is shown that event recording processing was not performed when the height of the impacting object is 3 mm and the shape of the impacting object is flat. The minimum ground clearance of the vehicle that is below a predetermined value for the height of the impacting object is also stored in the memory unit 15, but the minimum ground clearance of the vehicle may also be stored in the analysis unit 14.

[0046] The control unit 12 controls the drive recorder as follows, based on the height of the impact object determined by the analysis unit 14 and the information in Table 1 that is stored in the storage unit 15. If the height of the impact object determined by the analysis unit 14 is less than a predetermined height at which event recording processing is performed in the storage unit 15, but greater than or equal to the height of the impact object, the control unit 12 performs the following control: The control unit 12 controls the drive recorder to delete the event record for the duration of the impact object's passage, which is the event record when the vehicle passes over the impact object.

[0047] For example, if the height of the impact object determined by the analysis unit 14 is 4 mm, then, as shown in Table 1, the impact object event detection process has been executed. Therefore, the control unit 12 controls the system to delete the event record corresponding to the time the vehicle passed the impact object, after a predetermined time has elapsed since the vehicle passed the impact object. As a result, the control system 21 deletes event files unrelated to the accident, leaving only the necessary event files, such as those related to the accident, in the event folder. Therefore, the control system 21 can properly manage the necessary event files. In addition, the user can easily find the necessary event files.

[0048] Furthermore, if the height of an impact object determined by the analysis unit 14 is stored in the storage unit 15, the control unit 12 may identify a shape identical or similar to the shape of the impact object included in the image from the storage unit and control the drive recorder. For example, if the height of the impact object determined by the analysis unit 14 is 3 mm, in the example shown in Table 1, two event recording processes with a height of 3 mm are stored in the storage unit. In this case, the control unit 12 obtains information about the shape of the impact object included in the image from the analysis unit 14. The control unit 12 then determines whether or not an event recording process has been executed for an impact object having a shape identical or similar to the shape obtained from the analysis unit 14. For example, if the shape obtained from the analysis unit 14 is an uneven shape, Table 1 shows that an event detection process has been executed for an impact object with a height of 3 mm and an uneven shape. Therefore, the control unit 12 controls the drive recorder to delete the event recording for the duration of the impact object's passage, after a predetermined time has elapsed since the vehicle passed the impact object.

[0049] Furthermore, if the height of the impacted object determined by the analysis unit 14 is not stored in the storage unit 15, the control unit 12 may control the drive recorder based on whether or not to perform event recording processing corresponding to the height value closest to the height of the impacted object determined by the analysis unit 14.

[0050] Furthermore, the control unit 12 does not control the drive recorder if the height of the impact object detected by the analysis unit 14 is less than or equal to the height of an impact object for which event recording processing has not been performed in the memory unit. This is because the drive recorder does not perform event recording processing if the height of the impact object is less than or equal to the height of an impact object for which event recording processing has not been performed in the memory unit.

[0051] Thus, the control systems 20 and 21 according to Embodiment 2 control the system to delete the event record corresponding to the time the vehicle passed the impact object, after a predetermined time has elapsed since the vehicle passed the impact object, when the height of the impact object determined by the analysis unit 14 is less than a predetermined value and greater than or equal to a predetermined value.

[0052] Furthermore, the control systems 20 and 21 set predetermined criteria as shown in Figure 6 or Table 1 and control the drive recorder based on the height information of the impacting object provided by the analysis unit 14. In conventional technology, even if an impact detection malfunction location is registered, if the road surface shape changes due to construction or disaster, impact detection is performed and event recording processing is executed, putting pressure on the capacity of the event folder in the storage unit (not shown in Figure 6). However, once predetermined criteria are set in the control systems 20 and 21, even if an event file unrelated to an accident is stored, the event file unrelated to the accident is deleted based on the predetermined criteria. In other words, even if an event file unrelated to an accident is stored in the event folder, it is deleted after a predetermined time has elapsed since the vehicle passed over the impacting object, so it does not put pressure on the capacity. Moreover, the user can easily find the necessary event files, for example, event files related to the accident. Furthermore, the control systems 20 and 21 may acquire the magnitude of the impact when the impacting object passes and store information linking the height of the impacting object with the magnitude of the impact. The control systems 20 and 21 may also be configured to delete event records corresponding to the time the impacting object passed after a predetermined time has elapsed relative to the height of the detected impacting object, if the impact value is below a predetermined value.

[0053] The control system 21 may also be configured to store the position information, shape, and height of the impacting object in the storage unit 15. By using such a configuration, the control system 21 can further improve the accuracy of the predetermined criteria. Furthermore, the control system 21 may use the drive recorder's front camera to record before the impacting object passes and the drive recorder's rear camera to record after the impacting object passes. This allows the control system 21 to more accurately recognize the height, shape, etc., of the impacting object and store it in the storage unit 15, thereby further improving the accuracy of the predetermined criteria. The control system 21 may be entirely or partially composed of a server (not shown).

[0054] <Control Method> Next, the control method according to Embodiment 2 will be described. Figure 7 is a flowchart illustrating the driving support method according to Embodiment 2. The flowchart in Figure 7 differs from the flowchart in Figure 3 in that steps ST11 and ST12 are executed. The other processes are the same as in Figure 3, so their explanation will be omitted.

[0055] Following step ST1, the control system 20(21) analyzes information regarding the height of the impacting object from the image (step ST11). Here, the height of the impacting object below a predetermined height, for example, below the minimum ground clearance of the vehicle, is the target of analysis. The control system 20(21) then determines whether the analyzed height of the impacting object is above a predetermined value (step ST12).

[0056] If the control system 20(21) determines that the height of the impacting object it has analyzed is greater than or equal to a predetermined value (step ST12YES), the control system 20(21) executes the processing from step ST2 onward. That is, the control system 20(21) controls the drive recorder to delete the event record of the vehicle passing the impacting object, specifically the event record corresponding to the time the vehicle passed the impacting object, after a predetermined time has elapsed since the vehicle passed the impacting object.

[0057] On the other hand, if the control system 20(21) does not determine that the height of the impacted object it has analyzed is greater than or equal to a predetermined value (step ST12NO), the control system 20(21) repeatedly executes the process from step ST1. In other words, the control system 20(21) does not control the drive recorder.

[0058] (Embodiment 3) <Vehicle Information> A control system according to Embodiment 3 will now be described. Figure 8 is a block diagram illustrating the control system according to Embodiment 3. As shown in Figure 8, the control system 30 includes a vehicle information acquisition unit 16, a calculation unit 11, and a control unit 12. The control system 30 is configured to communicate with the recording device 13, similar to Embodiments 1 and 2. The calculation unit 11 and the recording device 13 are the same as in Embodiments 1 and 2, so their description will be omitted. Here, the vehicle information acquisition unit 16 and the control unit 12 will be described. In Embodiment 3, as in Embodiments 1 and 2, the recording device 13 will be described as a drive recorder. In addition, all or part of the control system 30 may be configured as a server (not shown).

[0059] The vehicle information acquisition unit 16 acquires vehicle information about the vehicle. This vehicle information includes, for example, information about the vehicle class and vehicle weight. For example, the vehicle information may be "1500kg passenger car" or "13-ton dump truck". Based on the vehicle information, the control unit 12 controls the system to delete the event record that occurred when the vehicle passed over an impact object, specifically the event record corresponding to the time the impact object passed.

[0060] <Control of the drive recorder based on vehicle information> Referring to Figure 9, an example of how the control unit 12 controls the drive recorder based on vehicle information will be described. Figure 9 is a schematic diagram showing whether or not impact detection occurs according to vehicle speed and vehicle weight. Generally, the faster the vehicle speed, the more impact the vehicle will experience, even if the vehicle is light. Figure 9 shows the boundary at which the drive recorder detects impact. In Figure 9, if the points plotted for vehicle speed and vehicle weight are within region R3, the drive recorder will not detect an impact even if the vehicle is hit by an object. On the other hand, if the points plotted for vehicle speed and vehicle weight are within region R4, the drive recorder will detect an impact if the vehicle is hit by an object.

[0061] In other words, if the point plotted with vehicle speed and vehicle weight falls within region R3, the drive recorder does not detect an impact and therefore does not perform event recording processing, so the control unit 12 does not control the drive recorder. On the other hand, if the point plotted with vehicle speed and vehicle weight falls within region R4, the drive recorder does detect an impact, so the control unit 12 controls the drive recorder to delete the event recording that occurred when the vehicle passed the impact object, specifically the event recording corresponding to the time the impact object passed, after a predetermined time has elapsed since the vehicle passed the impact object.

[0062] The control system 30 acquires information about the vehicle speed from the vehicle. For example, at a speed of 60 km / h, the control unit 12 determines from Figure 9 that the vehicle weight controlling the drive recorder is 1200 kg or more. Then, if the vehicle weight information from the vehicle information acquisition unit 16 is 1500 kg, the control unit 12 controls the drive recorder to delete the event record for the duration of the vehicle passing the impact object after a predetermined time has elapsed since the vehicle passed the impact object.

[0063] Here, the control unit 12 may control the event recording process based on information about the vehicle stored in the storage unit that stores whether or not the event recording process is executed. Figure 10 is a block diagram illustrating a control system according to Embodiment 3. As shown in Figure 10, the control system 31 includes a storage unit 17, a vehicle information acquisition unit 16, a calculation unit 11, and a control unit 12. The configurations other than the storage unit 17 and the control unit 12 shown in Figure 10 are the same as in Figure 8, so their explanation will be omitted. Here, the storage unit 17 and the control unit 12 will be explained in detail.

[0064] The memory unit 17 stores whether or not event recording processing corresponding to vehicle information has been executed. This will be explained in more detail with reference to Table 2. Table 2 is an example of a list of vehicle information stored in the memory unit 17.

[0065] [Table 2]

[0066] As shown in Table 2, the memory unit 17 stores whether or not event recording processing was performed according to the vehicle weight. In the example shown in Table 2, the memory unit 17 also stores the vehicle shape and vehicle speed in association with the vehicle weight. The memory unit 17 may also store the minimum ground clearance. For example, Table 2 indicates that event recording processing was performed when the vehicle weight is 13 tons, the vehicle shape is a dump truck, and the vehicle speed is 50 km / h.

[0067] The control unit 12 controls the drive recorder based on the vehicle weight information acquired by the vehicle information acquisition unit 16 and the vehicle speed information acquired by the control system 31. For example, suppose the control unit 12 acquires vehicle weight information such as "13 tons" and vehicle speed information such as "50 km / h". In this case, since the event recording process is executed according to Table 2, the control unit 12 controls the drive recorder to delete the event record for the duration of the impact after a predetermined time has elapsed since the vehicle passed the impact object. As a result, the control system 31 deletes event files unrelated to the accident, leaving only the necessary event files, such as event files related to the accident, in the event folder. Therefore, the control system 31 can properly manage the necessary event files. In addition, the user can easily find the necessary event files, such as event files related to the accident.

[0068] Furthermore, if the vehicle weight information acquired by the vehicle information acquisition unit 16 is not stored in the storage unit 17, the control unit 12 may control the drive recorder based on whether or not to execute an event recording process corresponding to the vehicle weight closest to the acquired vehicle weight.

[0069] Furthermore, the control unit 12 will not control the drive recorder if the vehicle weight information acquired by the vehicle information acquisition unit 16 and the vehicle speed information acquired by the control system 31 are vehicle weight and vehicle speed for which event recording processing has not been performed in the storage unit 17. This is because in this case, event recording processing will not be performed in the drive recorder.

[0070] As described above, the control systems 30 and 31 according to Embodiment 3 control the drive recorder based on vehicle information to ensure a period of no recording. Even with the same impact object, the impact on the vehicle differs depending on the vehicle class, load, and speed. Therefore, the control systems 30 and 31 can more reliably delete event files unrelated to the accident. As a result, event files related to the accident remain in the event folder, allowing for proper management of event files related to the accident. Furthermore, the user can easily find the necessary event files, such as event files related to the accident.

[0071] Naturally, the control systems 30 and 31 may further include the aforementioned analysis unit 14 and control the drive recorder to delete event recordings corresponding to the time the impacting object passed, based on information regarding the height of the impacting object and vehicle information.

[0072] <Control Method> Next, the control method according to Embodiment 3 will be described. Figure 11 is a flowchart illustrating the driving assistance method according to Embodiment 3. The flowchart in Figure 11 differs from the flowchart in Figure 3 in that steps ST111 and ST112 are executed. The other processes are the same as in Figure 3, so their explanation will be omitted. Note that, as mentioned above, this explanation assumes that information regarding vehicle speed is obtained from the vehicle.

[0073] Following step ST1, the control system 30(31) acquires information regarding the vehicle weight (step ST111). The control system 30(31) then acquires a threshold for the vehicle weight that serves as a reference for controlling the drive recorder based on the vehicle speed (step ST112). The control system 30(31) then determines whether the vehicle weight is greater than or equal to the threshold in step ST112 (step ST113).

[0074] If the control system 30(31) determines that the vehicle weight is greater than or equal to the threshold in step ST112 (step ST113YES), the control system 30(31) executes the processing from step ST2 onward. That is, the control system 30(31) controls the drive recorder to delete the event record of the vehicle passing the impact object, specifically the event record corresponding to the time the impact object passed, after a predetermined time has elapsed since the vehicle passed the impact object.

[0075] On the other hand, if the control system 30(31) does not determine that the vehicle weight is greater than or equal to the threshold in step ST112 (step ST113NO), the control system 30(31) repeatedly executes the process from step ST1. In other words, the control system 30(31) does not control the drive recorder.

[0076] Some or all of the processing in the control systems and control methods according to the above-described embodiments 1 to 3 can be implemented as computer programs. Such programs can be stored using various types of non-temporary computer-readable media and supplied to a computer. Non-temporary computer-readable media include various types of tangible recording media. Examples of non-temporary computer-readable media include magnetic recording media (e.g., flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (e.g., magneto-optical disks), CD-ROMs (Read Only Memory), CD-Rs, CD-R / Ws, and semiconductor memories (e.g., mask ROMs, PROMs (Programmable ROMs), EPROMs (Erasable PROMs), flash ROMs, and RAMs (Random Access Memory)). Programs may also be supplied to a computer using various types of temporary computer-readable media. Examples of temporary computer-readable media include electrical signals, optical signals, and electromagnetic waves. Temporary computer-readable media can be supplied to a computer via wired communication channels such as electric wires and optical fibers, or via wireless communication channels.

[0077] Although the present disclosure has been described in accordance with the above embodiments, the present disclosure is not limited to the configuration of the above embodiments, and of course includes various modifications, alterations, and combinations that a person skilled in the art could make within the scope of the claims of the present patent application. [Explanation of Symbols]

[0078] 10, 20, 21, 30, 31 Control Systems 11 Calculation Section 12 Control Unit 13 Recording device 14 Analysis Department 15, 17 Storage section 16. Vehicle Information Acquisition Unit C1 Vehicle IP1 Step R1, R2, R3, R4 area S1, S2, S3 points

Claims

1. A control system for controlling a recording device that performs event recording processing in response to vehicle impact detection, A calculation unit calculates the impact object passage time, which indicates the time from the current time until the vehicle passes the impact object, based on an image that includes an immovable impact object on the road surface that will cause the vehicle to impact the vehicle. A control unit controls the recording device to delete, from the event records of the recording device, the event record corresponding to the time the vehicle passed the impact object, after a predetermined time has elapsed since the vehicle passed the impact object. A control system equipped with this system.

2. The control unit, If, within a predetermined time elapsed after the vehicle has passed the impacting object, the image includes the vehicle in a stationary state or a person or object in contact with the vehicle, The recording device is controlled so that the event record is not deleted after a predetermined time has elapsed since the vehicle passed over the impacting object. The control system according to claim 1.

3. The system further includes an analysis unit that analyzes information regarding the height of the impacting object from the aforementioned image, The control unit, If the height of the impacting object determined by the analysis unit is less than a predetermined height of the vehicle and greater than or equal to a predetermined value, The recording device is controlled to delete the event record corresponding to the time the impacting object passed through. The control system according to claim 1.

4. The system further includes a storage unit that stores whether or not an event recording process was executed according to the height of the impacting object. The control unit, If the height of the impact object determined by the analysis unit is greater than or equal to the height of the impact object for which event recording processing is being performed in the storage unit, The recording device is controlled to delete the event record corresponding to the time the impacting object passed through. The control system according to claim 3.

5. A control method for controlling a recording device that performs event recording processing in response to vehicle impact detection, Based on an image of a stationary impactor present on the road surface that causes an impact on the vehicle, the impactor passage time, which indicates the time from the current point until the vehicle passes the impactor, is calculated. After a predetermined time has elapsed since the vehicle passed the impacting object, the recording device is controlled to delete from the event records of the recording device the event record corresponding to the time the vehicle passed the impacting object. The computer performs the process. Control method.

Images