Control system and control method

By calculating the time it takes for a vehicle to pass an impact object and deleting irrelevant event records after a specified time, the problem of managing event files during vehicle operation is solved, achieving the retention of necessary files and optimization of storage space.

CN122228532APending Publication Date: 2026-06-16JVC KENWOOD CORP

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
JVC KENWOOD CORP
Filing Date
2024-12-05
Publication Date
2026-06-16

AI Technical Summary

Technical Problem

In the existing technology, event files unrelated to accidents during vehicle operation cannot be properly managed, resulting in excessive storage space usage and difficulty for users to find necessary files.

Method used

The event recording processing of the dashcam is controlled by the computing and control units by calculating the time it takes for the vehicle to pass the impact object and deleting event records unrelated to the accident after a specified time.

🎯Benefits of technology

Effective management of event files ensures that necessary event files are retained, reduces storage space usage, and makes it easier for users to find files related to incidents.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122228532A_ABST
    Figure CN122228532A_ABST
Patent Text Reader

Abstract

Provided is a control system and control method capable of appropriately managing event files necessary for a user. A control system (10) of the present disclosure includes a calculation section (11) that calculates a time to pass through an immobile impact object present on a road surface on which an impact is applied to a vehicle, based on an image containing the impact object, and a control section (12) that controls a recording device such that, based on the time to pass through the impact object, an event record for the time to pass through the impact object is deleted after passing through the impact object or an event record process is not performed before passing through the impact object.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to control systems and control methods. Background Technology

[0002] Patent Document 1 discloses an impact detection malfunction prevention device that can suppress the recording and processing of event files when an impact not caused by an accident is detected. In the impact detection malfunction prevention device disclosed in Patent Document 1, locations where impact detection has been performed more than a predetermined number of times and are unrelated to an accident are registered as impact detection malfunction locations, and the recording and processing of event files is suppressed at the impact detection malfunction locations.

[0003] Existing technical documents Patent documents Patent document 1: Japanese Patent Application Publication No. 2022-134910. Summary of the Invention

[0004] In the impact detection malfunction prevention device disclosed in Patent Document 1, if the impact detection malfunction location is not pre-registered, it is impossible to suppress the recording and processing of event files unrelated to the accident. Therefore, event files unrelated to the accident will be recorded, making it difficult to find the event files necessary for the user.

[0005] This disclosure was made in view of the above circumstances, and its purpose is to provide a control system and control method that can properly manage event files necessary for users.

[0006] The control system in this embodiment controls the recording device that performs event recording processing for impact detection of accompanying vehicles. The control system includes: The computing unit calculates the time to pass the impact object based on an image containing a stationary impactor on the road surface that impacted the vehicle, the time to pass the impact object representing the time from the current moment until the vehicle passes the impact object; and The control unit controls the recording device based on the time of passing the impactor, so as to delete the event record of the time period of passing the impactor after passing the impactor or not perform the event recording process before passing the impactor.

[0007] The control method of this embodiment controls the recording device that performs event recording processing for impact detection of accompanying vehicles. The computer performs the following processing: Based on an image containing a stationary impact object present on the road surface that impacted the vehicle, the time to pass the impact object is calculated, where passing the impact object represents the time from the current moment until the vehicle passes the impact object; and The recording device is controlled based on the time of impact to delete the event record for the time period of impact after the impact has passed, or to not perform the event recording process before the impact has passed.

[0008] This disclosure provides a control system and control method that can properly manage event files necessary for users. Attached Figure Description

[0009] Figure 1 This is a block diagram illustrating the control system of Implementation Method 1; Figure 2 It is a diagram showing the state of a vehicle as it goes over a step; Figure 3 This is a flowchart illustrating the driving assistance method of embodiment 1; Figure 4 This is a block diagram illustrating the control system of embodiment 2; Figure 5 This is a schematic diagram showing whether 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 of embodiment 2; Figure 7 This is a flowchart illustrating the driving assistance method of embodiment 2; Figure 8 This is a block diagram illustrating the control system of embodiment 3; Figure 9 This is a schematic diagram illustrating whether there is an impact detection based on vehicle speed and weight; Figure 10 This is a block diagram illustrating the control system of embodiment 3; Figure 11 This is a flowchart illustrating the driving assistance method of embodiment 3; Figure 12 This is a flowchart illustrating the driving assistance method of embodiment 4; Figure 13 It is a diagram showing the state of a vehicle as it goes over a step; Figure 14 This is a schematic diagram showing whether impact detection is performed based on vehicle speed and the height of the impacting object; Figure 15 This is a flowchart illustrating the driving assistance method of embodiment 5; Figure 16 This is a schematic diagram illustrating whether there is an impact detection based on vehicle speed and weight; Figure 17 This is a flowchart illustrating the driving assistance method of embodiment 6. Detailed Implementation

[0010] The present disclosure will now be described through embodiments of the invention, but the invention covered by the claims is not limited to these embodiments. Furthermore, not all structures described in the embodiments are means for solving the problem. For clarity, the following descriptions and drawings will be appropriately omitted and simplified. In the drawings, the same reference numerals will be used for the same elements, and repeated descriptions will be omitted as necessary.

[0011] (Implementation Method 1) <Control System> The control system of Implementation Method 1 will be described. Figure 1 This is a block diagram illustrating the control system of Embodiment 1. For example... Figure 1 As shown, the control system 10 includes a computing unit 11 and a control unit 12.

[0012] The control system 10 controls the recording device that performs event recording processing associated with vehicle impact detection. Event recording processing refers to the following process: when an impact is detected while the vehicle is in motion, if the impact value exceeds a set sensor threshold, the camera image file showing the impact detection and the sensor value are recorded separately from the normal recording as a short-duration event file. The recording location is a storage unit (not shown) inside or outside the control system 10. The event file is stored, for example, in an event folder within the storage unit. As will be explained in detail below, the control system 10 calculates the time of passage through the impact object based on the image and controls the recording device 13 to delete the event record of the time the vehicle passed the impact object and the event record of the time period during which the vehicle passed the impact object after a predetermined time has elapsed since the impact.

[0013] The control system 10 is a structure capable of communicating with the recording device 13. The recording device 13 performs event recording processing. The recording device 13 is, for example, a vehicle recorder. However, it is not limited to such devices. Figure 1 The structure shown in the block diagram allows the control system 10 and the recording device 13 to communicate with each other. Alternatively, the recording device 13 may include a calculation unit 11 and a control unit 12 of the control system 10.

[0014] Alternatively, a distributed processing configuration can be performed by including a portion of the control system 10 (one of the computing unit 11 and the control unit 12) in the recording device 13 and a portion of the control system 10 (the other of the computing unit 11 and the control unit 12) in the server (not shown). The following will describe this configuration in detail. Figure 1 The calculation unit 11 and control unit 12 are shown. Furthermore, the system 10 is described as controlling the vehicle recorder.

[0015] <Calculation of time to pass through impact object> First, the calculation unit 11 will be described. Based on an image containing an impact object that impacts the vehicle, the calculation unit 11 calculates the time it takes for the vehicle to pass the impact object, representing the time from the current moment until it passes the impact object. The impact object typically refers to a stationary impact object that is set, fixed, or formed on the road surface, but it can also include uneven road surfaces, and is not limited to this. It can also include objects that may exert impact when a vehicle passes over them, such as speed bumps, stones, or road surfaces with steps.

[0016] Reference Figure 2 The method for calculating the time it takes to pass through an impact object is explained. Figure 2 This is a diagram showing the state of a vehicle as it passes over a step. (Example) Figure 2 As shown, vehicle C1 is about to pass step IP1 located ahead. Step IP1 is an example of an impact object. The calculation unit 11 analyzes the image containing step IP1, thereby calculating the distance from point S1 to point S2 and the distance from point S2 to point S3. Point S1 represents the current position of vehicle C1, point S2 represents the position of the step closest to point S1, and point S3 represents the position of the step farthest from point S2. Furthermore, the current position of vehicle C1 represents the location of vehicle C1 at the start of the process of calculating the time of passing the impact object.

[0017] Here, vehicle C1 can obtain speed-related information via GPS or other location information. Then, the calculation unit 11 (control system 10) obtains the speed-related information from vehicle C1. The calculation unit 11 calculates the travel time for that distance by dividing the distance by the vehicle speed. Figure 2 In the example shown, the calculation unit 11 divides the distance from location S1 to location S2 by the vehicle speed to calculate 3 seconds. Additionally, in Figure 2 In the example shown, the calculation unit 11 divides the distance from location S2 to location S3 by the vehicle speed to calculate 1 second. In this way, the calculation unit 11 can calculate that the time to pass through the impact, which represents the time until vehicle C1 passes through step IP1, is 4 seconds.

[0018] In addition, the calculation unit 11 can compare the distances from location S1 to location S2 and from location S2 to location S3 obtained from the image with the values ​​obtained from the distance sensor mounted on the vehicle C1 to improve the accuracy of distance calculation.

[0019] <Controlling the dashcam> Next, the control unit 12 will be explained. The control unit 12 controls the dashcam to delete the event record of the vehicle passing the impact object and the event record of the time period of passing the impact object from the event record of the dashcam after a predetermined time from the time the vehicle passes the impact object. In addition, the event record is a so-called overwrite-prohibited record.

[0020] Reference Figure 2 The control unit 12's control over the vehicle recorder is explained. Figure 2 In the process, the dashcam performs event recording processing during the 4-second period when the vehicle C1 passes through the impact object, specifically during the interval from point S1 to point S3. Therefore, the event recording during this 4-second period is stored in the storage unit as the event record of the vehicle passing through the impact object. Figure 1 (Not shown in the diagram). Then, the control unit 12 controls the deletion of event records for the period of 4 seconds following the vehicle's passage over the impact object. The specified time can be, for example, 2 seconds after passing the impact object, or can be arbitrarily set. Thus, while recording and temporarily storing accident-independent event files in the dashcam, the accident-independent event files are deleted from the dashcam after the specified time has elapsed since the vehicle passed the impact object.

[0021] Let's take another example to illustrate the control unit 12's control over the dashcam. Although in Figure 2 Not illustrated, but it is assumed that vehicle C1 makes contact with other vehicles before reaching location S1 and continues driving. Afterwards, it is assumed that... Figure 2 The step IP1 is shown. At this time, the dashcam will perform event recording processing on the event files of vehicle C1 when it comes into contact with other vehicles and on the event files of vehicle C1 when it passes through step IP1. In other words, the dashcam records the event files of vehicle C1 when it comes into contact with other vehicles and on the event files of vehicle C1 when it passes through 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 dashcam to delete the latter event file after a predetermined time has elapsed since vehicle C1 passed through step IP1. Thus, after a predetermined time has elapsed since vehicle C1 passed through step IP1, the dashcam retains the event files of vehicle C1 when it comes into contact with other vehicles.

[0022] If event files unrelated to the incident are logged and not deleted, they will occupy storage space. Figure 1 The event folder (not shown) has a capacity. Normally, the event folder cannot be overwritten; therefore, if available space is exhausted, the user needs to organize the files. However, in the control system 10 of 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 the impact point, thus not occupying space. Furthermore, the user can more easily find necessary event files, such as those related to the accident.

[0023] Furthermore, the timing for the control unit 12 to delete the event records from the dashcam can be arbitrary, as long as the vehicle passes over the impact object. Figure 2 In the example shown, it is sufficient to delete the event record of the vehicle passing through step IP1 and the event record of the period when the vehicle passes through the impact object for 4 seconds at any time after the vehicle C1 passes through point S3.

[0024] In addition to recording the 4 seconds of time it takes for the vehicle to pass the impact object, the dashcam can also record the start time of the impact (e.g., 10:30:30 AM on July 16th) and the end time of the impact (e.g., 10:30:34 AM on July 16th). In this case, the control unit 12 performs the following processing at 10:30:30 AM on July 17th, 24 hours after the start time of the impact (10:30:30 AM on July 16th): The control unit 12 controls the dashcam to delete the event file for the 4 seconds from the start time of the impact (10:30:30 AM on July 16th) to the end time (10:30:34 AM on July 16th).

[0025] Furthermore, the control unit 12 performs control and uses the time to pass the impact object, calculated in real time by the calculation unit 11, to delete the event records from the dashcam. Therefore, unlike existing technologies, it is not necessary to record historical information about whether past events have occurred. Thus, the control system 10 can accurately identify event files unrelated to the accident. Moreover, by deleting event files unrelated to the event, the control unit 10 retains necessary event files, such as those related to the accident, in the event folder, thereby enabling proper management of essential event files.

[0026] Here, we will use the example of the control unit 12 controlling the dashcam to delete event recordings during a period of 4 seconds when passing through an impact object. However, it is not limited to this; the control unit 12 can also control the dashcam to delete event recordings with extended or shortened time periods after passing through an impact object. With this structure, when the calculation unit 11 calculates the time of passing through an impact object, although it determines the current location S1 of the calculation starting point, the location S2 of the impact object including the step IP1 in front of the vehicle, and the location S3 after passing through the impact object based on the image, it can also cope with the situation where the image clarity decreases. In addition, the calculation unit 11 receives the vehicle speed information of the vehicle C1 from the GPS location information, so it can also cope with the situation where the time cannot be calculated more accurately due to the deterioration of the reception.

[0027] Thus, the control unit 12 only needs to have the following structure: control the driving recorder to delete the event record of the vehicle passing the impact object after a specified time has elapsed since the vehicle passed the impact object, and the event record of the time after passing the impact object or the time after extending or shortening the time after passing the impact object.

[0028] Furthermore, the control system 10 (control unit 12) can also control the dashcam so that, when information about the surrounding environment, such as traffic lights, pedestrian crossings, and intersections, which are close to accident-prone situations, is obtained from the vehicle's environmental sensors, the event recordings after a predetermined time has elapsed since the vehicle passed the impact object are not deleted. With this structure, the control system 10 can retain event files in an event folder when there is an accident risk.

[0029] Furthermore, if the control system 10 (control unit 12) performs the following control if, before a predetermined time has elapsed since the vehicle passed the impact object, the image contains a stopped state of the vehicle or a person or object in contact with the vehicle, the control system 10 (control unit 12) controls the dashcam not to delete event recordings after the predetermined time has elapsed. That is, if the control system 10 determines that there is a possibility that an event file is necessary for the user, it will not delete the event file from the dashcam but will retain it in the event folder.

[0030] <Control Methods> Next, the control method of Implementation Method 1 will be described. Figure 3 This is a flowchart illustrating the driving assistance method of Implementation Method 1.

[0031] First, the control system 10 determines whether the image from the dashcam contains an impact object (step ST1). If the image from the dashcam contains an impact object (step ST1 is "Yes"), the control system 10 (calculation unit 11) calculates the time to pass the impact object, representing the time until the vehicle passes the impact object, based on the image containing the impact object that impacted the vehicle (step ST2). On the other hand, if the image from the dashcam does not contain an impact object (step ST1 is "No"), the process of step ST1 is repeated.

[0032] Following step ST2, the recording device 13 performs event recording processing associated with the vehicle impact detection (step ST3). The event files recorded by the recording device 13 are stored in the storage unit ( Figure 1 (Not shown in the image) in the event folder.

[0033] Next, the control unit 12 controls the recording device 13 to delete the event record of the time when the vehicle passed the impact object and the event record of the time period when the vehicle passed the impact object after a predetermined time has elapsed (step ST4).

[0034] Thus, in the control method of Embodiment 1, in step ST3, recording of event files unrelated to the accident is performed and temporarily recorded in the dashcam. Then, in step ST4, after a predetermined time has elapsed since the vehicle passed the impact object, the event files unrelated to the accident are deleted from the dashcam. Therefore, in the control method of Embodiment 1, after a predetermined time has elapsed since the vehicle passed the impact object, the dashcam retains necessary event files, such as those related to the accident. This allows the user to easily find the necessary event files.

[0035] (Implementation Method 2) <Height of the impacting object> The control system of Implementation Method 2 will be described. Figure 4 This is a block diagram illustrating the control system of Embodiment 2. For example... Figure 4 As shown, the control system 20 includes an analysis unit 14, a calculation unit 11, and a control unit 12. The control system 20 is the same as the control system 10 in Embodiment 1, and is a structure capable of communicating with the recording device 13. The calculation unit 11 and the recording device 13 are the same as in Embodiment 1, so their description is omitted. Here, the analysis unit 14 and the control unit 12 will be described. In Embodiment 2, also as in Embodiment 1, the recording device 13 is assumed to be a vehicle recorder.

[0036] The analysis unit 14 analyzes information related to the height of the impact object based on the image. Then, if the height of the impact object analyzed by the analysis unit 14 is less than or greater than a specified value, the control unit 12 controls the dashcam to delete the event record of the vehicle passing the impact object and the event record of the time period of passing the impact object after a specified time has elapsed since the vehicle passed the impact object. Here, the height of the impact object being less than the specified value can be, for example, the vehicle's minimum ground clearance (also known as road clearance). The height of the impact object analyzed by the analysis unit 14 being greater than or greater than the specified value can be, for example, a height of the impact object that can be arbitrarily set by the user, or a recommended value based on past impact records and statistics indicating that the impact is not significant (unrelated to the accident).

[0037] Furthermore, preferably, when the height of the impacting object analyzed by the analysis unit 14 is less than a predetermined value and within a predetermined range, the control unit 12 controls the dashcam to delete the event record of the time the vehicle passed the impacting object and the event record of the time period during which the vehicle passed the impacting object after a predetermined time has elapsed. For example, suppose the minimum ground clearance of the vehicle is 15 cm and the height of the impacting object is 14 cm. In this case, event files related to accidents such as vehicle malfunctions may be generated. Therefore, when the height of the impacting object analyzed by the analysis unit 14 is less than the predetermined value and the height of the impacting object is between 10 cm and 15 cm, the control unit 12 controls not to delete the event record. Alternatively, when the height of the impacting object analyzed by the analysis unit 14 is less than the predetermined value and the height of the impacting object is less than 10 cm, the control unit 12 controls the dashcam to delete the event record.

[0038] Control of dashcam based on the height of the impacting object. Reference Figure 5 An example of how the control unit 12 controls the dashcam based on the height information of the impacting object will be explained. Figure 5 This diagram illustrates whether impact detection is performed based on vehicle speed and the height of the impacting object. Generally, the faster the vehicle speed, the more impact will be exerted on the vehicle even if the height of the impacting object is relatively low. Figure 5 The image shows the boundary for impact detection by the dashcam. Figure 5 In the case where the points plotting vehicle speed and the height of the impact object are contained within region R1, the dashcam will not perform impact detection even if the vehicle is impacted by the impact object. On the other hand, if the points plotting vehicle speed and the height of the impact object are contained within region R2, the dashcam will perform impact detection when the vehicle is impacted by the impact object.

[0039] That is, if the point for plotting the vehicle speed and the height of the impact object is contained within region R1, the dashcam does not perform impact detection and therefore does not perform event recording processing. Therefore, the control unit 12 does not control the dashcam. On the other hand, if the point for plotting the vehicle speed and the height of the impact object is contained within region R2, the dashcam performs impact detection. Therefore, the control unit 12 controls the dashcam to delete the event recording of the time the vehicle passed the impact object and the event recording of the time period during which the vehicle passed the impact object after a predetermined time has elapsed since the incident.

[0040] The control system 20 acquires information related to vehicle speed from the vehicle. For example, at a speed of 60 km / h, the control unit 12... Figure 5The height of the impacting object is determined to be 10mm or more. Then, if the control unit 12 determines that the height of the impacting object is 10mm or more based on information related to the height of the impacting object analyzed by the analysis unit 14, and since it is included within region R2, the control unit 12 controls the dashcam to delete the event recording for the time period from when the vehicle passes the impacting object after a predetermined time has elapsed. For example, at a speed of 80km / h... Figure 5 It is known that even if the height of the impacting object is 10mm, the curve of vehicle speed and the height of the impacting object is included in the R2 area for detecting the impact. In this case, the control unit 12 controls the driving recorder to temporarily record the event, but deletes the event record for the time period of passing the impacting object after a specified time has elapsed since the vehicle passed the impacting object.

[0041] Here, the control unit 12 can also control the dashcam based on information about the height of the impacting object stored in the storage unit that stores whether or not event recording processing has been performed. Figure 6 This is a block diagram illustrating the control system of Embodiment 2. For example... Figure 6 As shown, the control system 21 includes a storage unit 15, an analysis unit 14, a calculation unit 11, and a control unit 12. Figure 6 The structure other than the storage unit 15 and the control unit 12 shown is similar to Figure 4 Since they are the same, the description is omitted. Here, the storage unit 15 and the control unit 12 will be described in detail.

[0042] Storage unit 15 stores whether event recording processing corresponding to the height of the impacting object has been performed. See Table 1 for a more detailed explanation. Table 1 is an example of a list of information related to the height of the impacting object stored in storage unit 15. It is used to illustrate whether event recording processing is performed based on the height and shape of the impacting object; height and shape are not limited.

[0043] [Table 1] As shown in Table 1, the storage unit 15 stores whether event recording processing corresponding to the height of the impact object has been performed. Furthermore, in the example shown in Table 1, the storage unit 15 also stores the shape of the impact object in association with its height. For example, Table 1 shows that event recording processing was performed when the impact object height was 5 mm and the impact object shape was flat. Additionally, Table 1 shows that event recording processing was not performed when the impact object height was 3 mm and the impact object shape was flat. Moreover, the minimum ground clearance of the vehicle when the impact object height is set to less than a predetermined value is also stored in the storage unit 15, but the minimum ground clearance of the vehicle can also be stored in the analysis unit 14.

[0044] Based on the height of the impacting object analyzed by the analysis unit 14 and the information in Table 1 pre-stored in the storage unit 15, the control unit 12 controls the dashcam as follows. If the height of the impacting object analyzed by the analysis unit 14 is less than the height specified in the storage unit 15 for event recording processing, but is greater than or equal to the height of the impacting object, the control unit 12 performs the following control: The control unit 12 controls the dashcam to delete the event recording of the vehicle passing over the impacting object, specifically the event recording for the period of time during which the vehicle passed over the impacting object.

[0045] For example, if the height of the impact object analyzed by the analysis unit 14 is 4mm, it can be seen from Table 1 that impact object event detection processing has been performed. Therefore, the control unit 12 performs control to delete the event record of the time the vehicle passed the impact object and the event record of the time period during which the vehicle passed the impact object after a predetermined time has elapsed. Thus, the control system 21 deletes event files unrelated to the accident and retains necessary event files, such as those related to the accident, in the event folder. Therefore, the control system 21 can appropriately manage necessary event files. Furthermore, the user can easily find the necessary event files.

[0046] Furthermore, if the storage unit 15 stores the heights of multiple impact objects analyzed by the analysis unit 14, the control unit 12 can also determine from the storage unit a shape that is the same as or similar to the shape of the impact object contained in the image, and control the dashcam. For example, if the height of the impact object analyzed by the analysis unit 14 is 3mm, in the example shown in Table 1, two event recording processes with a height of 3mm are stored in the storage unit. In this case, the control unit 12 obtains information related to the shape of the impact object contained in the image from the analysis unit 14. Then, the control unit 12 determines whether event recording processing has been performed on an impact object with a shape that is the same as the shape obtained from the analysis unit 14. For example, if the shape obtained from the analysis unit 14 is a concave-convex shape, as shown in Table 1, event detection processing has been performed on an impact object with a height of 3mm and a concave-convex shape. Therefore, the control unit 12 controls the dashcam so that, after a predetermined time has elapsed since the vehicle passed the impact object, the event recording of the time when the vehicle passed the impact object and the event recording of the time period during which the vehicle passed the impact object are deleted.

[0047] In addition, if the height of the impactor analyzed by the analysis unit 14 is not stored in the storage unit 15, the control unit 12 can control the dashcam based on whether or not event recording processing is performed on the height corresponding to the height closest to the height of the impactor analyzed by the analysis unit 14.

[0048] Furthermore, if the height of the impacting object analyzed by the analysis unit 14 is lower than the height of the impacting object in the storage unit that has not undergone event recording processing, the control unit 12 will not control the dashcam. This is because, if the height of the impacting object in the storage unit is lower than the height of the impacting object that has not undergone event recording processing, event recording processing will not be performed in the dashcam.

[0049] Thus, if the height of the impacting object analyzed by the analysis unit 14 is less than or greater than a specified value, the control systems 20 and 21 of Embodiment 2 control the vehicle to delete the event record of the time when the vehicle passed the impacting object and the event record of the time period during which the vehicle passed the impacting object after a specified time has elapsed.

[0050] In addition, control systems 20 and 21 are set Figure 6 Alternatively, based on the reference specified in Table 1, the dashcam is controlled according to the height information of the impacting object analyzed by the analysis unit 14. In the prior art, even if an impact detection malfunction is registered, impact detection and event recording are performed even when the road surface shape has changed due to construction, disasters, etc., occupying storage space ( Figure 6 The event folder (not shown in the diagram) has a capacity. However, once the control systems 20 and 21 set the prescribed baseline, even if event files unrelated to the accident are temporarily stored, these unrelated event files will be deleted based on the prescribed baseline. That is, even if event files unrelated to the accident are stored in the event folder, they will be deleted after a prescribed time has elapsed since the vehicle passed the impact object, thus not occupying any space. Consequently, users can easily find the necessary event files, such as those related to the accident.

[0051] Additionally, control systems 20 and 21 can also acquire the magnitude of the impact when passing over an impacting object and store information relating the height of the impacting object to the magnitude of the impact. Furthermore, control systems 20 and 21 can also be configured to delete the event record for the time period of passing over the impacting object after a predetermined time has elapsed, provided that the impact value is below a specified value.

[0052] Furthermore, the control system 21 can also be configured to store the position information, shape, and height of the impacting object in the storage unit 15. With this configuration, the control system 21 can further improve the accuracy of the specified reference. Additionally, the control system 21 can also use the front-facing camera of a dashcam to capture images before passing the impacting object, and the rear-facing camera of the dashcam to capture images after passing the impacting object. Thus, the control system 21 can more accurately identify the height, shape, etc., of the impacting object and store them in the storage unit 15, thereby further improving the accuracy of the specified reference. Furthermore, a server (not shown) can constitute all or part of the control system 21.

[0053] <Control Methods> Next, the control method of Implementation Method 2 will be described. Figure 7 This is a flowchart illustrating the driving assistance method of Embodiment 2. Figure 7 In the flowchart shown, with Figure 3 The difference between the flowchart shown and the actual flowchart lies in the execution of steps ST11 and ST12. All other processing is the same. Figure 3 Since they are the same, the explanation is omitted.

[0054] Following step ST1, the control system 20 (21) analyzes information related to the height of the impacting object based on the image (step ST11). Here, the height of the impacting object that is less than a specified height, for example, less than the minimum ground clearance of the vehicle, becomes the object of analysis. Then, the control system 20 (21) determines whether the height of the analyzed impacting object is above a specified value (step ST12).

[0055] If the control system 20 (21) determines that the height of the analyzed impact object is above a specified value (step ST12 is "Yes"), the control system 20 (21) executes the processing after step ST2. That is, the control system 20 (21) controls the vehicle recorder to delete the event record of the time when the vehicle passed the impact object and the event record of the time when the vehicle passed the impact object after a specified time has elapsed since the vehicle passed the impact object.

[0056] On the other hand, if the control system 20 (21) does not determine that the height of the analyzed impact object is above the specified value (step ST12 is "No"), the control system 20 (21) repeatedly executes the processing from step ST1. That is, the control system 20 (21) does not control the vehicle recorder.

[0057] (Implementation Method 3) <Vehicle Information> The control system of Implementation Method 3 will be described. Figure 8 This is a block diagram illustrating the control system of embodiment 3. For example... Figure 8 As shown, 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 the same as in Embodiments 1 and 2, and has a structure capable of communicating with the recording device 13. The calculation unit 11 and the recording device 13 are the same as in Embodiments 1 and 2, so their description is omitted. Here, the vehicle information acquisition unit 16 and the control unit 12 will be described. In Embodiment 3, the same as in Embodiments 1 and 2, the recording device 13 is described as a dashcam. Alternatively, a server (not shown) may constitute all or part of the control system 30.

[0058] The vehicle information acquisition unit 16 acquires vehicle information related to the vehicle. This vehicle information includes, for example, information related to vehicle specifications and weight. Examples of vehicle information include "1500kg ordinary car" and "13-ton dump truck." The control unit 12 performs control based on the vehicle information to delete the event record of the vehicle passing over the impact object, specifically the event record for the time period during which the vehicle passed over the impact object.

[0059] Control of dashcams based on vehicle information Reference Figure 9 An example of how the control unit 12 controls the dashcam based on vehicle information will be explained. Figure 9 This diagram illustrates the impact detection based on vehicle speed and weight. Generally, the faster the vehicle travels, the more impact it will have, even if the vehicle is relatively lightweight. Figure 9 This shows the boundary where the dashcam performs impact detection. Figure 9 In the case where the points plotting vehicle speed and weight are contained within region R3, the dashcam will not perform impact detection even if the vehicle is impacted by an object. On the other hand, if the points plotting vehicle speed and weight are contained within region R4, the dashcam will perform impact detection when the vehicle is impacted by an object.

[0060] That is, if the points for plotting vehicle speed and weight are contained within region R3, the dashcam does not perform impact detection and therefore does not perform event recording processing; therefore, the control unit 12 does not control the dashcam. On the other hand, if the points for plotting vehicle speed and weight are contained within region R4, the dashcam performs impact detection; therefore, the control unit 12 controls the dashcam to delete the event recording of the time the vehicle passed the impact object and the event recording of the time period during which the vehicle passed the impact object after a predetermined time has elapsed since the incident.

[0061] The control system 30 acquires information related to vehicle speed from the vehicle. For example, at a speed of 60 km / h, the control unit 12 obtains information from the vehicle. Figure 9 The vehicle weight controlled by the dashcam is determined to be 1200 kg or more. Furthermore, if the vehicle weight-related information acquired by the vehicle information acquisition unit 16 is 1500 kg, since it is included in area R4, the control unit 12 controls the dashcam to delete the event record of the time when the vehicle passed the impact object and the event record of the time period when the vehicle passed the impact object after a predetermined time has elapsed.

[0062] Here, the control unit 12 can also control the event recording process based on the vehicle-related information stored in the storage unit that stores whether or not the event recording process has been performed. Figure 10 This is a block diagram illustrating the control system of embodiment 3. For example... Figure 10As shown, the control system 31 includes a storage unit 17, a vehicle information acquisition unit 16, a computing unit 11, and a control unit 12. Figure 10 The structure other than the storage unit 17 and the control unit 12 shown is similar to Figure 8 Since they are the same, the description is omitted. Here, the storage unit 17 and the control unit 12 will be described in detail.

[0063] Storage unit 17 stores whether or not event recording processing corresponding to vehicle-related information has been performed. See Table 2 for a more detailed explanation. Table 2 is an example of a list of vehicle-related information stored in storage unit 17.

[0064] [Table 2] As shown in Table 2, the storage unit 17 stores whether event recording processing corresponding to the vehicle weight has been performed. In the example shown in Table 2, the storage unit 17 also stores the vehicle shape and speed in association with the vehicle weight. Additionally, the storage unit 17 may also store the minimum ground clearance. For example, Table 2 shows that event recording processing was performed when the vehicle weight was 13 tons, the vehicle shape was a dump truck, and the speed was 50 km / h.

[0065] The control unit 12 controls the dashcam based on vehicle weight-related information acquired by the vehicle information acquisition unit 16 and vehicle speed-related information acquired by the control system 31. For example, the control unit 12 acquires vehicle weight-related information such as "13 tons" and vehicle speed-related information such as "50 km / h". In this case, the control unit 12 performs event recording processing as shown in Table 2. Therefore, the control unit 12 controls the dashcam to delete the event record of the time the vehicle passed the impact object and the event record of the time period of passing the impact object after a specified time has elapsed since the incident. As a result, the control system 31 deletes event files unrelated to the accident and retains necessary event files, such as those related to the accident, in the event folder. Therefore, the control system 31 can properly manage necessary event files. In addition, the user can easily find necessary event files, such as those related to the accident.

[0066] In addition, if the vehicle weight-related information obtained by the vehicle information acquisition unit 16 is not stored in the storage unit 17, the control unit 12 can control the dashcam based on whether or not the event recording process corresponding to the vehicle weight closest to the acquired vehicle weight has been performed.

[0067] Furthermore, if the vehicle weight-related information acquired by the vehicle information acquisition unit 16 and the vehicle speed-related information acquired by the control system 31 are the vehicle weight and vehicle speed stored in the storage unit 17 without event recording processing, the control unit 12 will not control the dashcam. This is because, in this case, event recording processing is not performed in the dashcam.

[0068] Thus, the control systems 30 and 31 of Embodiment 3 control the dashcam based on vehicle information to achieve a period without recording. Even with the same impact object, the impact on the vehicle varies depending on vehicle specifications, load, and speed. Therefore, the control systems 30 and 31 can more reliably delete event files unrelated to the accident. Consequently, event files associated with the accident are retained in the event folder, thus enabling proper management of accident-related event files. Furthermore, users can easily find necessary event files, such as those related to the accident.

[0069] In addition, the control systems 30 and 31 may also include the aforementioned analysis unit 14, which performs control based on information related to the height of the impacting object and vehicle information to delete the event records of the time period during which the vehicle passed the impacting object from the dashcam.

[0070] <Control Methods> Next, the control method of Implementation Method 3 will be described. Figure 11 This is a flowchart illustrating the driving assistance method of embodiment 3. Figure 11 In the flowchart shown, with Figure 3 The difference between the flowchart shown and the one presented is that steps ST111 and ST112 are executed. Other than this, the processing is the same. Figure 3 The same applies, therefore the explanation is omitted. Furthermore, as stated above, the explanation is based on the premise of obtaining information related to vehicle speed from the vehicle.

[0071] Following step ST1, the control system 30 (31) acquires information related to vehicle weight (step ST111). Then, the control system 30 (31) acquires a threshold of vehicle weight as a reference for controlling the dashcam based on the vehicle speed (step ST112). Then, the control system 30 (31) determines whether the vehicle weight is above the threshold of step ST112 (step ST113).

[0072] If the control system 30 (31) determines that the vehicle weight is above the threshold of step ST112 (step ST113 is "Yes"), the control system 30 (31) executes the processing after step ST2. That is, the control system 30 (31) controls the driving recorder to delete the event record of the vehicle passing the impact object and the event record of the time period of passing the impact object after a specified time has elapsed since the vehicle passed the impact object.

[0073] On the other hand, if the control system 30 (31) does not determine that the vehicle weight is above the threshold of step ST112 (step ST113 is "No"), the control system 30 (31) repeatedly executes the processing from step ST1. That is, the control system 30 (31) does not control the driving recorder.

[0074] In the control systems of embodiments 1 to 3, event files unrelated to the accident are recorded and temporarily stored in a recording device. However, after a predetermined time has elapsed since the vehicle passed the impact object, the event files unrelated to the accident are deleted from the recording device. By configuring the system in this way, event files necessary for the user can be properly managed.

[0075] (Implementation Method 4) <Control System> The control system of Embodiment 4 will be described. The control system of Embodiment 4 is related to... Figure 1 The control system shown in Embodiment 1 is the same, including a calculation unit 11 and a control unit 12. Hereinafter, the control system of Embodiment 4 will be referred to as control system 40.

[0076] Control system 40 is a control system that controls event recording processing associated with vehicle impact detection. Event recording processing is performed as follows: when an impact is detected while the vehicle is in motion, if the impact value exceeds a set sensor threshold, the camera image at the time of impact detection and the sensor value are recorded separately as a short-duration event file from the normal recording. The recording location is a storage unit (not shown) inside or outside control system 40. The event file is stored, for example, in an event folder within the storage unit. Control system 40 calculates the time to impact based on the image and controls event recording processing based on this time to create a no-recording period where event recording processing is not performed.

[0077] The control system 40 is a structure capable of communicating with the recording device 13. The recording device 13 performs event recording processing. The recording device 13 is, for example, a dashcam, and the control system 40 controls the event recording processing of the dashcam. However, it is not limited to such devices. Figure 1 The control system 40 and the recording device 13, as shown in the block diagram, can communicate with each other. Alternatively, the recording device 13 can include a calculation unit 11 and a control unit 12 of the control system 40.

[0078] Alternatively, a distributed processing configuration can be achieved by including a portion of the control system 40 (one of the computing unit 11 and the control unit 12) in the recording device 13 and a portion of the control system 40 (the other of the computing unit 11 and the control unit 12) in the server (not shown). Hereinafter, the control system 40... Figure 1The calculation unit 11 and control unit 12 shown will be described in detail. Furthermore, the event recording processing of the vehicle recorder controlled by the control system 40 will be explained.

[0079] <Calculation of time through impact> First, the calculation unit 11 will be described. The calculation unit 11 calculates the time it takes for the vehicle to pass the impact object, representing the time from the current moment until it passes the impact object, based on an image containing an impact object that impacts the vehicle. The impact object typically refers to a stationary impact object that is set, fixed, or formed on the road surface, but it can also be a road surface with uneven surfaces, and is not limited to this, including objects that may exert impact when a vehicle passes over them, such as speed bumps, stones, or road surfaces with steps.

[0080] Regarding the method for calculating the time of impact, it is consistent with that in Implementation 1. Figure 2 The method described in the previous section is the same, so it is omitted.

[0081] <Control of Event Logging> Next, the control unit 12 will be described. The control unit 12 controls the event recording process, creating a no-recording period based on the time of impact before the vehicle passes the impact object, during which event recording processing is not performed. During this no-recording period, event recording processing is not performed, but impact detection can still be performed. Furthermore, the event record is a so-called overwrite-prohibited record.

[0082] In other words, the no-recording period is the period during which impact detection is performed when the vehicle is impacted by an object, but no event recording is executed. Additionally, during the no-recording period, no event recording is performed, but normal recording (so-called overwriteable normal recording) is conducted. Therefore, even if an accident occurs during the no-recording period, the user can still review the moving images from the normal recording.

[0083] The method for controlling event logging and processing is explained. Figure 2 In this configuration, the control unit 12, for example, performs control to set a 4-second period during which the time of passing the impact object is a no-recording period during which the dashcam's event processing is not performed. This suppresses the recording processing of event files unrelated to the accident.

[0084] If recording of event files unrelated to the incident is performed, it will consume storage space ( Figure 1 The event folder (not shown) has a capacity. Normally, since the event folder cannot be overwritten, users need to organize the files when the available capacity is exhausted. However, in the control system 40 of Embodiment 1, event files unrelated to the accident are not stored in the event folder and therefore do not occupy capacity. Furthermore, users can easily find necessary event files, such as those related to the accident.

[0085] Furthermore, the control unit 12 uses the time to pass the impacting object calculated in real time by the calculation unit 11 to control the vehicle recorder not to perform event recording processing. Therefore, it does not need to record historical information on whether or not past events were recorded, as is the case with existing technologies. As a result, the control system 40 can more reliably suppress the recording processing of event files unrelated to the accident.

[0086] Here, an example is described where the control unit 12 controls the process to set a 4-second period of passing over the impact object as a no-recording period during which the dashcam's event processing is not performed. However, this is not a limitation; the control unit 12 may also control the process to set the period after extending or shortening the time of passing over the impact object as a no-recording period during which the dashcam's event processing is not performed. Thus, when the calculation unit 11 calculates the time of passing over the impact object, it determines the current location S1 of the calculation starting point, the location S2 of the impact object including the step IP1 in front of the vehicle, and the location S3 after passing over the impact object based on the image. However, it can also cope with situations where it is difficult to calculate the time more accurately due to reduced image clarity or reduced reception of vehicle speed information received from GPS location information.

[0087] Thus, the control unit 12 only needs to control the event recording processing of the dashcam before the vehicle passes the impact object, and configure it to set the period of extended or shortened passage time or the time after passage time as a no-recording period. The method by which the control unit 12 controls the dashcam to re-execute the event recording processing of the dashcam will be described later using a flowchart.

[0088] Furthermore, the control system 40 can also, when it obtains information about the surrounding environment, such as traffic lights, pedestrian crossings, and intersections, which are likely to be accident-prone conditions, from the vehicle's environmental sensors, refrain from controlling the dashcam to not perform event recording processing during a no-recording period. With this configuration, the control system 40 can record event files in situations where an accident may occur.

[0089] <Control Methods> Next, the control method of Implementation Method 4 will be described. Figure 12 This is a flowchart illustrating the driving assistance method of embodiment 4.

[0090] First, the control system 40 determines whether the image from the dashcam contains an impact object (step ST1). If the image from the dashcam contains an impact object (step ST1 is "Yes"), the control system 40 (calculation unit 11) calculates the time to pass the impact object, representing the time until the vehicle passes the impact object, based on the image containing the impact object that impacted the vehicle (step ST2). On the other hand, if the image from the dashcam does not contain an impact object (step ST1 is "No"), the process of step ST1 is repeated.

[0091] Following step ST2, before the vehicle passes the impact object, the control unit 12 controls the event recording processing of the driving recorder based on the time of passing the impact object, so as to create a no-recording period during which event recording processing is not performed (step ST3).

[0092] Next, the control unit 12 determines whether the vehicle has detected an impact (step ST4). If the vehicle has detected an impact (step ST4 is "yes"), the control unit 12 controls the event recording processing of the dashcam to execute the event recording processing of the dashcam again (step ST6).

[0093] On the other hand, if no impact is detected in the vehicle (step ST4 is "No"), the control unit 12 determines whether the time for passing the impact object has elapsed (step ST5). If the time for passing the impact object has elapsed (step ST5 is "Yes"), the control unit 12 executes the processing in step ST6. When step ST5 is "Yes", although no impact was detected, the time for passing the impact object has elapsed, therefore the control unit 12 determines that the impact object contained in the image is a false recognition and executes the processing in step ST6.

[0094] On the other hand, if the time for passing the impact object has not elapsed (step ST5 is "No"), the control unit 12 repeatedly executes the processing starting from step ST4.

[0095] Thus, in the control method of Embodiment 4, during the period from controlling event recording processing in step ST3 to achieve a no-recording period to controlling event recording processing in step ST6, event file recording processing is not performed. Furthermore, the vehicle passes an impact object during this period. Therefore, the control method of Embodiment 4 can more reliably suppress the execution of event file recording processing unrelated to the accident.

[0096] exist Figure 12 In the control method shown, in step ST4, the control unit 12 determines whether the vehicle has detected an impact. However, in the control method of embodiment 4, step ST4 can also be omitted. That is, the control unit 12 can also control the event recording processing of the dashcam to perform the processing in step ST6 based on whether the step passage time has elapsed (step ST5).

[0097] Here, refer to Figure 13 Explain the effects of executing step ST4. Figure 13 This is a diagram showing the state of a vehicle as it passes over a step. Figure 13 In the middle, regarding steps IP1 and locations S1~S3, and... Figure 2 The structures shown are the same. Figure 13 The next paragraph and Figure 13 Compared to the previous section, this indicates that vehicle C1 changes to twice the speed and passes through step IP1.

[0098] exist Figure 13 In the preceding section, vehicle C1 passes step IP1 4 seconds after passing point S1. Furthermore, control unit 12 controls the event recording processing of the dashcam to execute the event processing again 4 seconds after passing point S1.

[0099] exist Figure 13 The next section, and Figure 13 Compared to the previous section, vehicle C1's speed is twice as fast, therefore vehicle C1 passes step IP1 2 seconds after leaving point S1. Furthermore, in Figure 13 In the next section, 2 seconds after passing from point S3 (4 seconds after passing from point S1), vehicle C1 is located away from step IP1.

[0100] exist Figure 13 In the case of the next paragraph, with Figure 13 Similar to the previous paragraph, if the event recording processing of the dashcam is controlled to be executed again after 4 seconds from location S1 (after 2 seconds), then the event data for the 2 seconds starting from location S3 will not be recorded. That is, in Figure 13 The next section passes step IP1 2 seconds after passing point S1. Therefore, it is preferable that the control unit 12 controls the event recording processing of the dashcam to execute the event processing of the dashcam again 2 seconds after passing point S1.

[0101] Two seconds after vehicle C1 passes point S1, it is impacted by step IP1. Therefore, control unit 12 can control the event recording processing of the dashcam by determining whether the vehicle has detected an impact, so as to re-execute the event processing of the dashcam at a more appropriate time.

[0102] (Implementation Method 5) <Height of the impacting object> The control system of Embodiment 5 will be described. The control system of Embodiment 5 is related to... Figure 4The control system shown in Embodiment 2 is the same, including an analysis unit 14, a calculation unit 11, and a control unit 12. Hereinafter, the control system of Embodiment 5 will be referred to as control system 50. Control system 50 is the same as control system 40 in Embodiment 4, and is a structure capable of communicating with recording device 13. The calculation unit 11 and recording device 13 are the same as in Embodiment 4, so their description is omitted. Here, the analysis unit 14 and control unit 12 will be described. In Embodiment 5, also as in Embodiment 4, the recording device 13 will be described as a vehicle recorder.

[0103] The analysis unit 14 analyzes information related to the height of the impacting object based on the image analysis. Then, if the height of the impacting object analyzed by the analysis unit 14 is less than or greater than a specified value, the control unit 12 controls the event recording processing of the dashcam to enter a no-recording period. Here, the height of the impacting object being less than the specified value can be, for example, the vehicle's minimum ground clearance (also known as road clearance).

[0104] Control of event logging and processing based on the height of the impact object. Reference Figure 14 An example of how the control unit 12 controls the event recording process based on the height information of the impacting object will be explained. Figure 14 This diagram illustrates whether impact detection is performed based on vehicle speed and the height of the impacting object. Generally, the faster the vehicle speed, the more impact will be exerted on the vehicle even if the height of the impacting object is relatively low. Figure 14 If the points plotting vehicle speed and the height of the impact object are contained within region R1, the dashcam will not perform impact detection even if the vehicle is impacted by the impact object. On the other hand, if the points plotting vehicle speed and the height of the impact object are contained within region R2, the dashcam will perform impact detection when the vehicle is impacted by the impact object.

[0105] That is, if the points for plotting vehicle speed and impact are included in region R1, the dashcam does not perform impact detection, and therefore does not perform event recording processing. Consequently, the control unit 12 does not control the event recording processing of the dashcam to become a no-recording period. On the other hand, if the points for plotting vehicle speed and impact are included in region R2, the dashcam performs impact detection, and therefore the control unit 12 controls the event recording processing of the dashcam to become a no-recording period.

[0106] The control system 50 acquires information related to vehicle speed from the vehicle. For example, at a speed of 60 km / h, the control unit 12 obtains information from... Figure 14The height of the impact object is determined to be 10 mm or more. Then, if the control unit 12 determines that the height of the impact object is 10 mm or more based on information related to the height of the impact object analyzed by the analysis unit 14, and since it is contained in region R2, the control unit 12 controls the event recording processing of the dashcam to become a no-recording period.

[0107] Here, the control unit 12 can also control the event recording process based on information about the height of the impactor stored in a storage unit that stores whether or not event recording processing has been performed. For example, the control system of Embodiment 5 and Figure 6 The control system 21 shown in Embodiment 2 is the same, including a storage unit 15, an analysis unit 14, a calculation unit 11, and a control unit 12. This control system is designated as control system 51. The structure of control system 51, except for the storage unit 15 and the control unit 12, is the same as... Figure 6 The control system 21 shown in Embodiment 2 is the same, so its description is omitted. Here, the storage unit 15 and the control unit 12 will be described in detail.

[0108] The storage unit 15 stores whether or not event recording processing corresponding to the height of the impact object has been performed. This will be explained in more detail with reference to Table 1 shown in Embodiment 2.

[0109] Based on the height of the impacting object analyzed by the analysis unit 14 and the information in Table 1 pre-stored in the storage unit 15, the control unit 12 controls the event recording processing of the dashcam as follows: If the height of the impacting object analyzed by the analysis unit 14 is less than or equal to the height specified in the storage unit 15 for event recording processing, the control unit 12 controls the event recording processing of the dashcam to enter a no-recording period. For example, if the height of the impacting object analyzed by the analysis unit 14 is 4mm, it can be seen from Table 1 that impacting object event detection processing has been performed; therefore, the control unit 12 controls the event recording processing to enter a no-recording period. Thus, the control system 51 can suppress the recording processing of event files unrelated to the accident.

[0110] Furthermore, if the storage unit 15 stores multiple heights of impact objects analyzed by the analysis unit 14, the control unit 12 can determine from the storage unit a shape that is the same as or similar to the shape of the impact object contained in the image, and control the event recording processing of the dashcam. For example, if the height of the impact object analyzed by the analysis unit 14 is 3mm, in the example shown in Table 1, two event recording processes with a height of 3mm are stored in the storage unit. In this case, the control unit 12 obtains information related to the shape of the impact object contained in the image from the analysis unit 14. Then, the control unit 12 determines whether event recording processing has been performed on an impact object with a shape that is the same as the shape obtained from the analysis unit 14. For example, if the shape obtained from the analysis unit 14 is a concave-convex shape, as shown in Table 1, event detection processing has been performed on an impact object with a height of 3mm and a concave-convex shape. Therefore, the control unit 12 controls the event recording processing of the dashcam to become a no-recording period.

[0111] In addition, if the height of the impacting object analyzed by the analysis unit 14 is not stored in the storage unit 15, the control unit 12 can control the event recording processing of the dashcam based on whether or not event recording processing corresponding to the height closest to the height of the impacting object analyzed by the analysis unit 14 is performed.

[0112] Furthermore, if the height of the impactor analyzed by the analysis unit 14 is below the height of the impactor in the storage unit that has not undergone event recording processing, the control unit 12 will not control the event recording process to become a no-recording period. This is because even if the control unit 12 does not control the event recording process to become a no-recording period, it will not perform event recording processing.

[0113] Thus, in Embodiment 5, if the height of the impacting object analyzed by the analysis unit 14 is less than or greater than a predetermined value, the control system 50 and 51 control the event recording process of the vehicle recorder to become a period without recording.

[0114] In addition, control systems 50 and 51 are configured as follows: Figure 14 Alternatively, based on the specified references shown in Table 1, the event recording process is controlled according to the height information of the impacting object analyzed by the analysis unit 14. In the prior art, even if an impact detection malfunction is registered, impact detection and event recording may still be performed if the road surface shape changes due to construction, disasters, etc. However, once the control systems 50 and 51 set the specified references, they can control the event recording process. Therefore, the control systems 50 and 51 can more reliably suppress the recording of event files unrelated to the accident.

[0115] In addition, control systems 50 and 51 can also acquire the magnitude of the impact when passing an impactor, store information that correlates the height of the impactor with the magnitude of the impact, and set a no-recording period for the height of the detected impactor when the impact value is below a specified value.

[0116] Furthermore, the control system 51 can also be configured to store the position information, shape, and height of the impacting object in the storage unit 15. With this configuration, the control system 51 can further improve the accuracy of the specified reference. Additionally, the control system 51 can also use the front-facing camera of the dashcam to take pictures before passing the impacting object, and the rear-facing camera of the dashcam to take pictures after passing the impacting object. Thus, the control system 51 can more accurately identify the height, shape, etc., of the impacting object and store them in the storage unit 15, thereby further improving the accuracy of the specified reference. Furthermore, a server (not shown) can constitute all or part of the control system 51.

[0117] <Control Methods> Next, the control method of Implementation Method 5 will be described. Figure 15 This is a flowchart illustrating the driving assistance method of embodiment 5. Figure 15 In the flowchart shown, with Figure 12 The difference between the flowchart shown and the one presented is that steps ST11 and ST12 are executed. Other than these, the processing is the same. Figure 12 Since they are the same, the explanation is omitted.

[0118] Following step ST1, the control system 50 (51) analyzes information related to the height of the impacting object based on the image (step ST11). Here, the height of the impacting object that is less than a specified height, for example, less than the minimum ground clearance of the vehicle, becomes the object of analysis. Then, the control system 50 (51) determines whether the analyzed height of the impacting object is above a specified value (step ST12).

[0119] If the control system 50 (51) determines that the height of the analyzed impact object is above a specified value (step ST12 is "Yes"), the control system 50 (51) executes the processing after step ST2. That is, the control system 50 (51) controls the event recording processing of the vehicle recorder to become a no-recording period.

[0120] On the other hand, if the control system 50 (51) does not determine that the height of the analyzed impact object is above the specified value (step ST12 is "No"), the control system 50 (51) repeatedly executes the processing from step ST1. That is, the control system 50 (51) does not control the event recording processing of the dashcam, so as to become a period of no recording.

[0121] (Implementation Method 6) <Vehicle Information> The control system of Embodiment 6 will be described. The control system of Embodiment 6 is related to... Figure 8 The control system shown in Embodiment 3 is the same as that in Embodiment 6, including a vehicle information acquisition unit 16, a calculation unit 11, and a control unit 12. Hereinafter, the control system of Embodiment 6 will be referred to as control system 60. Control system 60 is the same as in Embodiments 4 and 5, and is a structure capable of communicating with the recording device 13. The calculation unit 11 and the recording device 13 are the same as in Embodiments 4 and 5, and therefore their description is omitted. Here, the vehicle information acquisition unit 16 and the control unit 12 will be described. In Embodiment 6, as in Embodiments 4 and 5, the recording device 13 will be described as a dashcam. Furthermore, all or part of the control system 60 may also be configured as a server (not shown). This allows information related to the height of the impact object and periods without recording, stored in the storage unit 15, to be shared with other vehicles.

[0122] The vehicle information acquisition unit 16 acquires vehicle information related to the vehicle. This vehicle information includes, for example, information related to vehicle specifications and weight. Examples of vehicle information include "a 1500kg ordinary car" or "a 13-ton dump truck." Based on the vehicle information, the control unit 12 controls the event recording processing of the driving recorder to create a no-recording period.

[0123] <Control of event logging and processing based on vehicle information> Reference Figure 16 An example of how the control unit 12 controls event recording processing based on vehicle information will be explained. Figure 16 This diagram illustrates the impact detection based on vehicle speed and weight. Generally, the faster the vehicle travels, the more impact it will experience, even if the vehicle is relatively lightweight. Figure 16 In the case where the points for plotting vehicle speed and weight are included in region R3, the dashcam will not perform impact detection even if the vehicle is impacted by an object. On the other hand, if the points for plotting vehicle speed and weight are included in region R4, the dashcam will perform impact detection when the vehicle is impacted by an object.

[0124] That is, when the points for plotting vehicle speed and weight are contained within region R3, the dashcam does not perform impact detection, and therefore does not perform event recording processing. Consequently, the control unit 12 does not control the event recording processing of the dashcam to become a no-recording period. On the other hand, when the points for plotting vehicle speed and weight are contained within region R4, the dashcam performs impact detection, and therefore the control unit 12 controls the event recording processing of the dashcam to become a no-recording period.

[0125] The control system 60 acquires information related to vehicle speed from the vehicle. For example, at a speed of 60 km / h, the control unit 12 obtains information from the vehicle's speed. Figure 16 The vehicle weight for which event recording processing is controlled is determined to be 1200 kg or more. Furthermore, if the vehicle weight information related to the vehicle information acquisition unit 16 is 1500 kg, since it is included in area R4, the control unit 12 controls the event recording processing of the dashcam to become a no-recording period.

[0126] Here, the control unit 12 can also control the event recording process based on vehicle-related information stored in a storage unit that stores whether or not event recording processing has been performed. For example, the control system of Embodiment 6 and Figure 10 The control system 31 shown in Embodiment 3 is the same as that in the control system 31, including a storage unit 17, a vehicle information acquisition unit 16, a computing unit 11, and a control unit 12. This control system is designated as control system 61. The configuration of control system 61, except for the storage unit 17 and the control unit 12, is the same as... Figure 10 The control system 31 of Embodiment 3 shown is the same, so its description is omitted. Here, the storage unit 17 and the control unit 12 will be described in detail.

[0127] The storage unit 17 stores whether or not event recording processing corresponding to vehicle-related information has been performed. This will be explained in more detail with reference to Table 2 shown in Embodiment 3.

[0128] The control unit 12 controls the event recording processing of the dashcam based on vehicle weight-related information acquired by the vehicle information acquisition unit 16 and vehicle speed-related information acquired by the control system 61. For example, the control unit 12 acquires vehicle weight-related information such as "13 tons" and vehicle speed-related information such as "50 km / h". In this case, since event recording processing has been performed as shown in Table 2, the control unit 12 controls the event recording processing of the dashcam to be in a no-recording period. As a result, the control system 61 can suppress the execution of recording processing of event files unrelated to the accident.

[0129] In addition, if the vehicle weight-related information acquired by the vehicle information acquisition unit 16 is not stored in the storage unit 17, the control unit 12 can control the event recording processing of the dashcam based on whether or not the event recording processing corresponding to the vehicle weight closest to the acquired vehicle weight has been performed.

[0130] Furthermore, if the vehicle weight-related information acquired by the vehicle information acquisition unit 16 and the vehicle speed-related information acquired by the control system 61 are the vehicle weight and vehicle speed stored in the storage unit 17, where event recording processing has not been performed, the control unit 12 will not control event recording processing to make it a no-recording period. This is because even if the control unit 12 does not control event recording processing to make it a no-recording period, event recording processing will not be performed.

[0131] Thus, the control systems 60 and 61 of Embodiment 6 control the event recording processing of the dashcam based on vehicle information to create a period without recording. Even with the same impact object, the impact on the vehicle will be different depending on the vehicle specifications, load, and speed. Therefore, the control systems 60 and 61 can more reliably suppress the recording processing of event files unrelated to the accident.

[0132] In addition, the control systems 60 and 61 may also include the aforementioned analysis unit 14, which controls the event recording processing of the dashcam to become a period without recording based on information highly correlated with the impacting object and vehicle information.

[0133] <Control Methods> Next, the control method of Implementation Method 6 will be described. Figure 17 This is a flowchart illustrating the driving assistance method of embodiment 6. Figure 17 In the flowchart shown, with Figure 12 The difference between the flowchart shown and the one presented is that steps ST111 and ST112 are executed. Other than this, the processing is the same. Figure 3 Since they are the same, the explanation is omitted.

[0134] Following step ST1, the control system 60 (61) acquires information related to vehicle weight (step ST111). Then, the control system 60 (61) determines whether the vehicle weight is above a specified value (step ST112).

[0135] If the control system 60 (61) determines that the acquired vehicle weight is above a specified value (step ST112 is "Yes"), the control system 60 (61) executes the processing after step ST2. That is, the control system 60 (61) controls the event recording processing of the driving recorder to become a no-recording period.

[0136] On the other hand, if the control system 60 (61) does not determine that the acquired vehicle weight is above the specified value (step ST112 is "No"), the control system 60 (61) repeatedly executes the processing from step ST1. That is, the control system 60 (61) does not control the event recording processing of the dashcam to become a period without recording.

[0137] The above describes implementation methods 1 to 6.

[0138] In the control systems of embodiments 1 to 3, event files unrelated to the accident are recorded and temporarily stored in a recording device. However, after a predetermined time has elapsed since the vehicle passed the impact point, the event files unrelated to the accident are deleted from the recording device. By configuring the system in this way, event files necessary for the user can be properly managed.

[0139] Furthermore, the control systems in embodiments 4-6 calculate the time it takes for the object to pass through the image, and based on this time, control the event recording process to create a no-recording period during which event recording processing is not performed. By configuring the system in this way, it is possible to more reliably suppress the recording of event files unrelated to the accident.

[0140] In other words, in the control systems of embodiments 1 to 6, the control unit performs the following processing. The control unit controls the recording device based on the time of impact, to delete event records for the period of impact after the impact or to set event recording processing to not be performed before the impact, thus creating a no-recording period. By configuring it in this way, the recording processing of event files unrelated to the accident can be more reliably suppressed.

[0141] Some or all of the processes in the control systems and control methods described in embodiments 1 to 6 above can be implemented as computer programs. Such programs can be stored in various types of non-transitory computer-readable media and provided to a computer. Non-transitory computer-readable media include various types of tangible recording media. Examples of non-transitory computer-readable media include magnetic recording media (e.g., floppy disks, magnetic tapes, hard disk drives), optical-magnetic recording media (e.g., optical disks), CD-ROMs (Read Only Memory), CD-Rs, CD-R / Ws, semiconductor memories (e.g., mask ROMs, PROMs (Programmable ROMs), EPROMs (Erasable PROMs), flash memory ROMs, and RAMs (Random Access Memory). Alternatively, programs can also be provided to a computer via various types of transient computer-readable media. Examples of transient computer-readable media include electrical signals, optical signals, and electromagnetic waves. Transient computer-readable media can provide programs to a computer via wired communication paths such as wires and optical fibers, or via wireless communication paths.

[0142] The present disclosure has been described above in conjunction with the above embodiments, but the present disclosure is not limited to the structure of the above embodiments, and naturally includes various modifications, alterations and combinations that can be made by those skilled in the art within the scope of the claims of this application.

[0143] This application claims priority based on Japanese Patent Application No. 2023-219071 filed on December 26, 2023 and Japanese Patent Application No. 2024-160731 filed on September 18, 2024, the entire contents of which are incorporated herein by reference.

[0144] Industrial applicability This invention can be used in recording devices, such as dashcams.

[0145] Explanation of reference numerals in the attached figures: 10, 20, 21, 30, 31, 40, 50, 51, 60, 61: Control system; 11: Calculation unit; 12: Control unit; 13: Recording device; 14: Analysis unit; 15, 17: Storage unit; 16: Vehicle information acquisition unit; C1: Vehicle; IP1: Step; R1, R2, R3, R4: Area; S1, S2, S3: Location.

Claims

1. A control system for controlling a recording device, the recording device performing event recording processing associated with impact detection of a vehicle, the control system comprising: The computing unit calculates the time to pass the impact object based on an image containing a stationary impact object that exists on the road surface and will impact the vehicle. The time to pass the impact object represents the time from the current moment until the vehicle passes the impact object. as well as The control unit controls the recording device to either delete the event record for the time period of passing the impact object after passing the impact object, or not perform the event recording process before passing the impact object, based on the time of passing the impact object.

2. The control system according to claim 1, wherein, The control unit controls the recording device to delete, after a predetermined time has elapsed since the vehicle passed the impact object, the event record of the vehicle passing the impact object and the event record of the time period of passing the impact object from the event record of the recording device.

3. The control system according to claim 2, wherein, If, before a predetermined time has elapsed since the vehicle passed the impact object, the image contains a stopped state of the vehicle or a person or object in contact with the vehicle, the control unit controls the recording device to prevent the deletion of the event record after the predetermined time has elapsed since the vehicle passed the impact object.

4. The control system according to claim 2, wherein, The control system further includes an analysis unit that analyzes information related to the height of the impactor from the image. If the height of the impactor, as determined by the analysis unit, is less than or equal to a specified height of the vehicle, but is above a specified value. The control unit controls the recording device to delete the event record for the time period of the impact.

5. The control system according to claim 4, wherein, The control system also includes a storage unit that stores whether event recording processing corresponding to the height of the impactor has been performed. When the height of the impactor analyzed by the analysis unit is the same as the height of the impactor for which the event recording process in the storage unit was performed, the control unit controls the recording device to delete the event record for the time period during which the impactor passed.

6. The control system according to claim 1, wherein, The control unit controls the event recording process such that, before the vehicle passes the impact object, the recording device forms a no-recording period based on the time of passing the impact object, during which the event recording process is not performed.

7. The control system according to claim 6, wherein, The control system further includes an analysis unit that analyzes information related to the height of the impactor from the image. When the height of the impacting object analyzed by the analysis unit is less than the specified height of the vehicle but greater than the specified value, the control unit controls the event recording process so that the recording device forms the no-recording period.

8. The control system according to claim 7, wherein, The control system also includes a storage unit that stores whether event recording processing corresponding to the height of the impactor has been performed. When the height of the impactor analyzed by the analysis unit is greater than or equal to the height of the impactor to which the event recording process in the storage unit is executed, the control unit controls the event recording process to cause the recording device to form the no-recording period.

9. The control system according to claim 8, wherein, The control system further includes a vehicle information acquisition unit, which acquires vehicle information related to the vehicle. The storage unit stores whether event recording processing corresponding to vehicle information has been performed. When the vehicle information acquired by the vehicle information acquisition unit is vehicle information for which the event recording process in the storage unit has been executed, the control unit controls the event recording process to cause the recording device to form the no-recording period.

10. A control method for controlling a recording device that performs event recording processing associated with impact detection of a vehicle, the control method causing a computer to perform the following processing: Based on an image containing a stationary impact object on the road surface that could cause an impact to the vehicle, the time to pass the impact object is calculated, whereby the time to pass the impact object represents the time from the current moment until the vehicle passes the impact object; and The recording device is controlled to delete the event record for the time period of passing the impact object after passing the impact object, or not to perform the event recording process before passing the impact object, based on the time of passing the impact object.

11. The control method according to claim 10, wherein, The recording device is controlled to delete, after a predetermined time has elapsed since the vehicle passed the impact object, the event record of the vehicle passing the impact object and the event record of the time period of passing the impact object from the event record of the recording device.

12. The control method according to claim 10, wherein, Prior to the vehicle passing the impact object, the event recording process is controlled based on the time of passing the impact object, so that the recording device forms a no-recording period in which the event recording process is not performed.