Vehicle accident history recording system

Abstract

To provide a vehicle accident history recording system capable of identifying a part damaged by a light collision.SOLUTION: A vehicle 200 comprises: a collision determination unit 12 that determines a collision when a signal indicating acceleration detected by one of a plurality of collision detection sensors 20 is equal to or larger than a prescribed collision determination threshold value; and a failure detection determination unit that determines failure detection of a plurality of components 30 to be failure-detected on the basis of the result of communication with the components mounted near the outer peripheral surface of the vehicle 200. A data server 150 determines, as a collision surface, the outer peripheral surface of the vehicle 200 near the disposing position of a collision detection sensor 20 which has detected acceleration and which has been collision-detected by the collision determination unit 12 of the vehicle 200, and identifies, as a collision part, a part on which the component 30 determined to be a failure by the failure detection determination unit 14 of the vehicle 200.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a vehicle accident history recording system that records the accident history of a vehicle as well as the location of damage to the vehicle caused by the accident. [Background technology]

[0002] When assessing a used car, the appraisal value will vary depending on whether or not the used car has an accident history. Even a minor collision (hereinafter referred to as a "minor collision") can cause damage to the vehicle that requires repair, so in order to assess the car accurately and efficiently, it is necessary to identify not only the accident history but also the damaged areas of the vehicle.

[0003] Patent Document 1 discloses an invention of a vehicle accident history recording device that identifies and records damaged areas caused by a collision by combining the results of collision determination by a collision detection sensor and the results of vehicle rotation determination by a yaw rate sensor. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2014-137733 Summary of the Invention [Problem to be solved by the invention]

[0005] However, in the invention described in Patent Document 1, the output of the yaw rate sensor is small in the case of a light collision, which may make it difficult to identify the collision site.

[0006] In consideration of the above, an object of the present invention is to provide a vehicle accident history recording system that can identify damaged areas caused by minor collisions. [Means for solving the problem]

[0007] According to the first aspectThe vehicle accident history recording system includes a collision determination unit that determines a collision when a signal indicating acceleration detected by any of a plurality of collision detection sensors provided in a vehicle is equal to or greater than a predetermined collision determination threshold; a failure detection determination unit that determines whether a failure has been detected in a plurality of failure detection target parts mounted near the outer peripheral surface of the vehicle based on the results of communication with the failure detection target parts; and a collision part determination unit that determines, as a collision surface, the outer peripheral surface of the vehicle near the location of the collision detection sensor that detected the acceleration that the collision determination unit determined to be a collision, and identifies, as a collision part, a part where the failure detection target part determined to be faulty by the failure detection determination unit is mounted. The failure detection determination unit determines that a failure detection target component that does not normally respond to the communication within a predetermined time period from when the signal becomes equal to or greater than the collision determination threshold has failed, and the collision determination unit determines that a collision has occurred when the failure detection determination unit does not determine that the failure detection target component has failed and when the signal is equal to or greater than a collision re-determination threshold that is greater than the collision determination threshold. .

[0008] First Aspect According to this, it is possible to identify the collision surface and collision location by detecting not only the collision detection sensor but also the state of the component subject to failure detection. Furthermore, by waiting a predetermined time before determining whether a component is faulty, it is possible to prevent a temporary interruption of communication between the fault detection / determination unit and the component being faulty from being erroneously determined as a component failure. Furthermore, when no determination of whether a component is faulty is involved, it is possible to distinguish between a vehicle wheel running over a curb or the like and a collision by determining that a collision has occurred when the signal output by the collision detection sensor is equal to or greater than a collision re-determination threshold that is greater than the collision determination threshold. [Effects of the Invention]

[0013] As described above, according to the present invention, it is possible to provide a vehicle accident history recording system that is capable of identifying damaged areas caused by minor collisions. [Brief explanation of the drawings]

[0014] [Figure 1] (A) is a block diagram showing an example of the configuration of a vehicle accident history recording system according to this embodiment, (B) is a schematic diagram showing an example of the arrangement of collision detection sensors, and (C) is an explanatory diagram showing an example of a component that is the target of fault detection. [Figure 2] (A) is a schematic diagram showing the case where the collision site is on the front left side of the vehicle, and the upper part of (B) is an explanatory diagram showing the waveform of the signal corresponding to the G detected by the front sensor, and the lower part shows failure information of the failure detection target parts near the collision site. [Figure 3] (A) is a schematic diagram showing what happens when the rear wheels of a vehicle run over a curb, and the upper part of (B) is an explanatory diagram showing the waveform of the signal corresponding to the G detected by the floor sensor, and the lower part shows the failure information of the component subject to failure detection. [Figure 4](A) is a flowchart showing an example of a collision detection process in a vehicle, (B) is an explanatory diagram showing an example of a signal output by a front sensor or a floor sensor, (C) is an explanatory diagram showing an example of a signal output by either a right side sensor or a left side sensor, (D) is an explanatory diagram showing an example of a signal output by a floor sensor and a signal, and (E) is a flowchart showing an example of a process in a data server. [Figure 5] FIG. 10 is an explanatory diagram showing an example of a damaged portion determination result. [Figure 6] (A) is a flowchart showing an example of a process for improving rear collision detection in a modified example of this embodiment, (B) is an explanatory diagram showing an example of a signal output by a front sensor or a floor sensor, (C) is an explanatory diagram showing an example of a signal output by either a right side sensor or a left side sensor, and (D) is an explanatory diagram showing an example of a signal output by a floor sensor. DETAILED DESCRIPTION OF THE INVENTION

[0015] 1A, a vehicle accident history recording system 100 according to this embodiment is configured with a vehicle 200 and a data server 150.

[0016] Vehicle 200 is provided with a plurality of collision detection sensors (G sensors) 20, which are a type of acceleration sensor that detects collisions. Fig. 1(B) is a schematic diagram showing an example of the arrangement of collision detection sensors 20. Collision detection sensors 20 include a front sensor 20F installed on the front of vehicle 200 and detecting acceleration (G) in the longitudinal direction of vehicle 200 as indicated by the arrow, right side sensors 20R1 and 20R2 installed on the right side of vehicle 200 and detecting G in the lateral direction of vehicle 200 as indicated by the arrow, left side sensors 20L1 and 20L2 installed on the left side of vehicle 200 and detecting G in the lateral direction of vehicle 200, and floor sensor 20C installed on the floor of vehicle 200 and detecting G in the longitudinal direction and lateral direction of vehicle 200 as indicated by the arrow.

[0017] To accurately detect the location of a collision in the vehicle 200, it is ideal to provide a right front sensor 20RF, a left front sensor 20LF, a right C-pillar sensor 20RC, and a left C-pillar sensor 20LC in addition to the above-mentioned collision detection sensors 20 (20F, 20R1, 20R2, 20L1, 20L2, 20C). However, since increasing the number of collision detection sensors 20 increases costs, in this embodiment, the right front sensor 20RF, the left front sensor 20LF, the right C-pillar sensor 20RC, and the left C-pillar sensor 20LC are not implemented.

[0018] The signals from the collision detection sensors 20 are input to a collision determination section 12 of an ECU (Electronic Control Unit) 10 of the vehicle 200, which determines whether or not a collision has occurred.

[0019] The vehicle 200 has fault detection target parts 30 such as on-board radar or ultrasonic sensors mounted near the outer periphery of the vehicle 200, and each of the fault detection target parts 30 is electrically connected to the fault detection determination unit 14 of the ECU 10 of the vehicle 200. As will be described later, in this embodiment, the collision site of the vehicle 200 is identified by the fault detection target part 30 that outputs part fault information indicating that a failure occurred within a predetermined time from when the collision detection sensor 20 detected a collision.

[0020] FIG. 1(C) is an explanatory diagram showing an example of fault detection target parts 30. The fault detection target parts 30 are provided on the left, center, and right sides of the front of the vehicle. Furthermore, the fault detection target parts 30 are provided on the left / front, left / center, left / rear, right / front, right / center, and right / rear sides of the vehicle sides. Furthermore, the fault detection target parts 30 are provided on the left, center, and right sides of the rear of the vehicle. The fault detection determination unit 14 determines which fault detection target part 30 has failed based on the part failure information from these fault detection target parts 30.

[0021] The signals output from the collision determination unit 12 and the failure detection / determination unit 14 of the ECU 10 are remotely communicated 120 to a data server 150 by an in-vehicle communication device 40. The remote communication 120 is, for example, V2X (Vehicle-to-Everything) communication.

[0022] The data server 150 is a type of computer that includes a collision surface / site determination unit 152 that determines each of the collision surfaces and collision sites of the vehicle 200, and a collision surface / site recording unit 154 that records each of the collision surfaces and collision sites of the vehicle 200. The data server 150 includes a CPU, a ROM, a RAM, a hard disk (HDD), and an input / output port.

[0023] Fig. 2(A) is a schematic diagram showing a case where the collision site 210 is on the front left side of the vehicle 200. Due to the collision, the front sensor 20F detects G in the direction of the arrow. The upper part of Fig. 2(B) is an explanatory diagram showing the waveform of the signal 230 corresponding to the G detected by the front sensor 20F, and the lower part shows failure information (left front component failure information) of the failure detection target component 30 near the collision site 210.

[0024] 2A, when vehicle 200 collides, signal 230 indicating G at the time of collision is equal to or greater than predetermined collision determination threshold 220 at time t1, and collision determination unit 12 performs a frontal collision determination. In this embodiment, the collision determination threshold varies depending on the specifications, sensitivity, and mounting state of collision detection sensor 20, and is therefore estimated, for example, by simulation using CAE (Computer-Aided Engineering), and is then determined through experiments using an actual vehicle.

[0025] In the event of a collision, the failure detection / determination unit 14 collects failure information such as component failure, communication disruption, or sensitivity deviation of each of the failure detection target components 30. For example, a failure detection target component 30 that does not normally respond to a clock signal from the ECU 10 can be regarded as a failed component. The location where the failure detection target component 30 that is thought to have failed is then designated as the collision site 210.

[0026] In this embodiment, the front / left side determination is delayed from time t1 when the front collision determination is made until time t2, when the predetermined time (fault diagnosis determination time + α) as shown in Figure 2(B) has elapsed. This is to avoid erroneously determining that a temporary communication interruption between the ECU 10 and the fault detection target component 30 is a component fault. In this embodiment, the predetermined time varies depending on the specifications, sensitivity, and mounting state of the fault detection target component 30, so it is estimated, for example, by CAE simulation and then determined through experiments using an actual vehicle.

[0027] 3(A) is a schematic diagram showing a case where the rear wheels of vehicle 200 run over curbstone 212. When the rear wheels run over curbstone 212, G in the direction of arrow 214 occurs in vehicle 200. Floor sensor 20C then detects G in the direction of arrow 216.

[0028] The upper part of FIG. 3B is an explanatory diagram showing waveforms of signals 250A, 250B, and 250C corresponding to G detected by floor sensor 20C, and the lower part shows failure information of failure detection target component 30.

[0029] 3A shows a collision determination threshold 240A used to determine whether or not a collision has occurred, and a collision determination threshold 240B that is lower than the collision determination threshold 240A. Since the G detected by the floor sensor 20C when running over a curb may be erroneously determined as a minor collision, in this embodiment, it is determined that a collision or running over a curb has occurred when the signals 250A, 250B, and 250C are equal to or higher than the collision determination threshold 240B that is lower than the collision determination threshold 240A.

[0030] Focusing on signal 250B, signal 250B exceeds collision determination threshold 240B at time t1. At this time t1, it is determined that a collision or curb-running has occurred. Furthermore, it is determined that a collision has occurred at the location where fault detection target component 30, for which fault information has been received, is located, between time t1 and time t2, when the predetermined time (fault diagnosis determination time + α) as shown in FIG. 3(B) has elapsed.

[0031] When signals 250A and 250C are detected, unlike when signal 250B is detected, this is the case when no failure information is obtained within a predetermined time after each of signals 250A and 250C becomes equal to or greater than collision determination threshold 240B. In such a case, each of signals 250A and 250C is compared with collision determination threshold 240A, which is a collision re-determination threshold.

[0032] 3B, signal 250C is less than collision determination threshold 240A, so it can be determined that the cause is not a collision but the rear wheel running over a curb, etc. However, signal 250A is greater than or equal to collision determination threshold 240A, so it can be determined that the cause is a collision.

[0033] 4A is a flowchart showing an example of a process for detecting a collision in the vehicle 200. In step S100, one of the collision detection sensors 20 detects a collision G.

[0034] In step S102, it is determined whether or not either of the signals output from the front sensor 20F and the floor sensor 20C used as front collision determination sensors is equal to or greater than the collision determination threshold value 260A.

[0035] 4(B) is an explanatory diagram showing an example of signal 270A output by front sensor 20F or floor sensor 20C. Since signal 270A is equal to or greater than collision determination threshold 260A, in such a case, it is assumed that collision G has been detected in step S102, and the procedure proceeds to step S104. If signal 270A is less than collision determination threshold 260A in step S102, the procedure proceeds to step S112.

[0036] In step S104, a timer is set and starts counting a predetermined time for determining whether or not there is fault information about the fault detection target component 30.

[0037] In step S106, it is determined whether or not part failure information of the failure detection target part 30 has been obtained within a predetermined time from the detection of the collision G. In step S106, if part failure information has been obtained within the predetermined time, the procedure proceeds to step S108, and if part failure information has not been obtained, the procedure proceeds to step S110.

[0038] In step S108, the process ends by transmitting collision G information and component failure information as the accident history to the data server 150. In step S110, the process ends by transmitting collision G information as the accident history to the data server 150.

[0039] In step S112, it is determined whether any one of the signals output from the right side sensors 20R1, 20R2 and the left side sensors 20L1, 20L2 used as side collision determination sensors is equal to or greater than the collision determination threshold value 260B.

[0040] 4(C) is an explanatory diagram showing an example of signal 270B output by either right side sensors 20R1, 20R2 or left side sensors 20L1, 20L2. Since signal 270B is equal to or greater than collision determination threshold 260B, in this case, it is determined in step S112 that a collision G has been detected, and the procedure proceeds to step S104. If signal 270B is less than collision determination threshold 260B in step S112, the procedure proceeds to step S114. In step S114, it is determined whether the signal output by floor sensor 20C, which is used as a rear-end collision determination sensor, is equal to or greater than collision determination threshold 260C.

[0041] 4(D) is an explanatory diagram showing an example of signals 270C and 270D output by floor sensor 20C. Since signal 270C is equal to or greater than collision determination threshold 260C, in such a case, it is determined that a collision G has been detected in step S114, and the procedure proceeds to step S104. On the other hand, if the signal is less than collision determination threshold 260C, as in signal 270D, it is not determined that a collision G has been detected in step S114, and the procedure proceeds to step S116. Then, in step S116, it is determined that no collision has been determined, and the process ends.

[0042] 4(E) is a flowchart showing an example of processing in data server 150. In step S200, data is received from vehicle 200, and in step S202, it is determined whether the received data contains only collision G or includes part failure information. In step S202, if the received data contains only collision G, the procedure proceeds to step S210, and if the received data includes part failure information, the procedure proceeds to steps S204 and S206.

[0043] Steps S204 and S206 are processed in parallel. In step S204, the collision surface is determined from the position of the collision detection sensor 20 where the collision G exceeded the collision determination threshold and the direction of the acceleration detected by the collision detection sensor 20. In step S206, the collision site is determined from the part failure information. Then, in step S208, the collision surface and collision site are recorded and the process ends. Note that if there is no part failure information related to a part near the collision surface, the process may proceed to step S212, where only the collision surface is recorded and the process ends.

[0044] In step S210, the collision surface is determined from the position of the collision detection sensor 20 where the collision G exceeds the collision determination threshold and the direction of acceleration detected by the collision detection sensor 20. Then, in step S212, only the collision surface is recorded and the process ends.

[0045] FIG. 5 is an explanatory diagram showing an example of the damage location determination result. When the collision detection sensors 20 are arranged as shown in FIG. 1B, the collision surface can be determined as the front (near the front sensor 20F), the left side (near the left side sensors 20L1 and 20L2), the right side (near the right side sensors 20R1 and 20R2), and the rear (near the floor sensor 20C). When the fault detection target components 30 are arranged as shown in FIG. 1C, the relationship between the collision surface and the collision location is as follows: When the front sensor 20F detects a collision G, the collision location is detected by the fault detection target components 30 arranged on either the front / left side, the front / center, or the front / right side. When the left side sensors 20L1 and 20L2 detect a collision G, the collision location is detected by the fault detection target components 30 arranged on either the left side / front, the left side / center, or the left side / rear. When the right side sensors 20R1, 20R2 detect a collision G, the part of the collision is detected by the failure detection target part 30 located at the front of the right side, the center of the right side, or the rear of the right side. When the floor sensor 20C detects a collision G, the part of the collision is detected by the failure detection target part 30 located at the left rear, the center of the rear, or the right rear.

[0046] Fig. 6(A) is a flowchart showing an example of processing for improving rear collision detection performance in a modified example of this embodiment. In Fig. 6(A), the collision G and malfunction information are detected taking into consideration the curb-running described with reference to Fig. 3. In step S300, one of the collision detection sensors 20 detects the collision G.

[0047] In step S302, it is determined whether or not either of the signals output from the front sensor 20F and the floor sensor 20C used as front collision determination sensors is equal to or greater than the collision determination threshold value 280A.

[0048] 6(B) is an explanatory diagram showing an example of signal 290A output by front sensor 20F or floor sensor 20C. Since signal 290A is equal to or greater than collision determination threshold 280A, in such a case, it is determined that collision G has been detected in step S302, and the procedure proceeds to step S304. If signal 290A is less than collision determination threshold 280A in step S302, the procedure proceeds to step S312.

[0049] In step S304, a timer is set and starts counting down to a predetermined time for determining whether or not there is failure information for the failure detection target component 30. In step S306, it is determined whether or not component failure information for the failure detection target component 30 has been obtained within a predetermined time from the detection of the collision G. If component failure information has been obtained within the predetermined time in step S306, the procedure proceeds to step S308, and if component failure information has not been obtained, the procedure proceeds to step S310.

[0050] In step S308, the process ends by transmitting collision G information and part failure information as the accident history to the data server 150. In step S310, the process ends by transmitting collision G information as the accident history to the data server 150.

[0051] In step S312, it is determined whether any one of the signals output from the right side sensors 20R1, 20R2 and the left side sensors 20L1, 20L2 used as side collision determination sensors is equal to or greater than the collision determination threshold value 280B.

[0052] 6(C) is an explanatory diagram showing an example of signal 290B output by either right side sensors 20R1, 20R2 or left side sensors 20L1, 20L2. Since signal 290B is equal to or greater than collision determination threshold 280B, in this case, it is determined in step S312 that a collision G has been detected, and the procedure proceeds to step S304. If signal 290B is less than collision determination threshold 280B in step S312, the procedure proceeds to step S314. In step S314, it is determined whether the signal output by floor sensor 20C, which is used as a rear-end collision determination sensor, is equal to or greater than collision determination threshold 280B.

[0053] 6(D) is an explanatory diagram showing an example of signals 290C, 290D, and 290E output by floor sensor 20C. Since signals 290C, 290D, and 290E are equal to or greater than collision determination threshold 280D, in such cases, it is determined that a collision G has been detected in step S314, and the procedure proceeds to step S316. On the other hand, if the signals are less than collision determination threshold 280D, it is not determined that a collision G has been detected in step S314, and the procedure proceeds to step S326. Then, in step S326, it is determined that no collision has been determined, and the process ends.

[0054] In step S316, a timer is set and starts counting down to a predetermined time for determining whether or not there is failure information for the failure detection target component 30. In step S318, it is determined whether or not component failure information for the failure detection target component 30 has been obtained within a predetermined time from the detection of the collision G. If component failure information has been obtained within the predetermined time in step S318, the procedure proceeds to step S320, and if component failure information has not been obtained, the procedure proceeds to step S322.

[0055] In step S320, the process ends by transmitting collision G information and component failure information as accident history to the data server 150. In step S322, it is determined whether the signal output from the floor sensor 20C used as a rear collision determination sensor is equal to or greater than the collision determination threshold value 280C.

[0056] In step S322, it is determined whether the signal output by floor sensor 20C used as a rear collision determination sensor is equal to or greater than collision determination threshold 280C, which is greater than collision determination threshold 280D. If in step S322 the signal output by floor sensor 20C is equal to or greater than collision determination threshold 280C, the procedure proceeds to step S324, and if the signal output by floor sensor 20C is not equal to or greater than collision determination threshold 280C, which is greater than collision determination threshold 280D, the procedure proceeds to step S326. Then, in step S324, collision G information is sent to data server 150 as an accident history, and the process ends.

[0057] After this, the process proceeds to the data server 150. The data server 150 performs, for example, the process shown in Fig. 4(E) described above, and determines the collision surface and collision portion according to Fig. 5.

[0058] As described above, this embodiment can detect minor collisions and identify the collision surface and collision site by detecting the collision site of the vehicle 200 not only using the collision detection sensor 20 but also by detecting the state of the failure detection target component 30. Also, it is possible to reduce the number of collision detection sensors 20 mounted, thereby reducing vehicle production costs. Furthermore, by recording the identified collision surface and collision site, detailed accident history information can be created, which can contribute to appropriate used car appraisals based on that information.

[0059] In this embodiment, the collision site is identified by the data server 150, but this is not limiting. The vehicle 200 may identify the collision surface and collision site, transmit information on the identified collision surface and collision site to the data server 150, and record the information in the data server 150. [Explanation of symbols]

[0060] 12 Collision determination section 14 Fault detection and judgment unit 20 Collision detection sensor 30 Parts subject to fault detection 100 Vehicle Accident History Recording System 152 Collision surface / part determination section 154 Collision surface / area recording unit 200 vehicles 220 Collision detection threshold 230 signal 240A, 240B Collision detection threshold 250A, 250B, 250C signal

Claims

[Claim 1] a collision determination unit that determines that a collision has occurred when a signal indicating acceleration detected by any of a plurality of collision detection sensors provided in the vehicle is equal to or greater than a predetermined collision determination threshold; a fault detection determination unit that determines whether a fault has been detected in a plurality of fault detection target components mounted near an outer periphery of the vehicle based on the results of communication with the fault detection target components; a collision part determination unit that determines, as a collision surface, an outer peripheral surface of the vehicle near an arrangement position of a collision detection sensor that detected acceleration that the collision determination unit determined to be a collision, and that identifies, as a collision part, a part on which the failure detection target part that the failure detection determination unit determined to be faulty is mounted; Including, the failure detection determination unit determines that a failure detection target component that does not normally respond to the communication within a predetermined time period from when the signal becomes equal to or greater than the collision determination threshold has failed; The collision determination unit determines that a collision has occurred when the signal is equal to or greater than a collision re-determination threshold that is greater than the collision determination threshold if the failure detection determination unit does not determine that the component subject to failure detection has failed.

Images