CN-121999545-A - System and method for recording vehicle events

CN121999545ACN 121999545 ACN121999545 ACN 121999545ACN-121999545-A

Abstract

Systems and methods for documenting vehicle events are provided. Methods and apparatus for matching vehicles associated with a crash event involving a first vehicle and a second vehicle are provided. A first collision message is received by the collision matching application, the first collision message having data related to a first collision event detected by the first vehicle with the first unknown vehicle. The collision matching application determines whether a second collision message has been received, the second collision message having data related to a second collision event detected by a second vehicle with a second unknown vehicle. The first and second crash messages are compared to determine whether the first crash event is the same as the second crash event. After determining that the first collision event is the same as the second collision event, a first collision report is sent to the first vehicle and a second collision report is sent to the second vehicle.

Inventors

M. Nasiren
D.Xie
U. Seni
P. G.G. Diguinio

Assignees

通用汽车环球科技运作有限责任公司

Dates

Publication Date: 20260508
Application Date: 20250103
Priority Date: 20241107

Claims (10)

1. A cloud-based application hosted on a remote server for documenting a vehicle collision event, the cloud-based application comprising: a communication module configured to communicate with a plurality of vehicles; A collision matching module operatively coupled to the communication module and having a processing unit configured to: receiving a first collision message reporting a collision event involving a first vehicle, wherein the first collision message includes image data and vehicle data captured by the first vehicle during the collision event; Determining whether a second collision message reporting a collision event involving a second vehicle has been received, wherein the second collision message includes image data and vehicle data captured by the second vehicle during the collision event; Comparing the first collision message with the second collision message when the second collision message has been received for confirming occurrence of a multiple vehicle collision event involving the first vehicle and the second vehicle, and Generating a crash event record to document the multi-vehicle crash event, wherein the crash event record includes a first insurance record for a driver of the first vehicle and a second insurance record for a driver of the second vehicle, and A collision database in communication with the collision matching module for storing the first and second collision messages and the collision event record.
2. The cloud-based application of claim 1, wherein the processing unit is further configured to generate a first collision report comprising the second insurance record for transmission from the communication module to the first vehicle.
3. The cloud-based application of claim 2, wherein the processing unit is further configured to generate a second collision report comprising the first insurance record for transmission from the communication module to the second vehicle.
4. The cloud-based application of claim 1, wherein the processing unit is further configured to: (a) Generating a list of target vehicles within a predetermined range of the first vehicle; (b) Searching the collision database for a target collision message from one of the target vehicles; (c) Comparing the target collision message with the first collision message, and (D) Determining whether the first vehicle and the second vehicle are involved in the same collision event based on the comparison of the target collision message and the first collision message.
5. The cloud-based application of claim 4, wherein the vehicle data comprises a collision metric, and the processing unit is further configured to: prompting a user of the first vehicle, the second vehicle, or the first and second vehicles to confirm whether the first and second vehicles are involved in the same collision event, and A response is received from the user confirming that the first vehicle and the second vehicle are in the same collision event.
6. The cloud-based application of claim 1, wherein the processing unit is further configured to: generating a first request including a vehicle brand, a vehicle model, and a vehicle color of the second vehicle for confirming that the second vehicle is involved in the multi-vehicle collision event, wherein the request is sent from the communication module to the first vehicle, and A second request including a vehicle brand, a vehicle model, and a vehicle color of the first vehicle is generated for confirming that the first vehicle is involved in the multi-vehicle collision event, wherein the request is sent from the communication module to the second vehicle.
7. The cloud-based application of claim 1, wherein the first collision message comprises vehicle data selected from the group consisting of a vehicle location, a vehicle brand, a vehicle model, a vehicle color, an impact force, an impact direction, or a combination thereof for the first vehicle.
8. The cloud-based application of claim 7, wherein the processing unit is further configured to process the first collision message for confirming that the vehicle location for the second vehicle is within a predetermined distance of the vehicle location for the first vehicle.
9. The cloud-based application of claim 7, wherein the processing unit is further configured to process the first and second collision messages, respectively, for confirming that the impact force and the impact direction for the second vehicle coincide with the impact force and the impact direction for the first vehicle.
10. A method for documenting a vehicle crash event on a cloud-based application hosted on a remote server, the method comprising: receiving a first collision message from a first vehicle reporting a collision event involving the first vehicle, wherein the first collision message includes image data and vehicle data captured by the first vehicle during the collision event; Storing the first collision message in a collision database; generating a list of target vehicles within a predetermined range of the first vehicle; searching the collision database for a target collision message from one of the target vehicles; comparing the first collision message with the target collision messages for the target vehicle list to confirm that the impact force and impact direction of the vehicle data associated with the first collision message matches the impact force and impact direction of the vehicle data of one of the target collision messages; confirming whether the first and second vehicles are involved in the same collision event based on the comparison of the target collision message and the first collision message, and A crash event record for the same crash event is generated, wherein the crash event record includes a first insurance record for a driver of the first vehicle and a second insurance record for a driver of the second vehicle.

Description

System and method for recording vehicle events Technical Field The technical field relates generally to collecting and documenting data associated with vehicle crash events, and more particularly to systems and methods for generating crash reports for multiple vehicle crash events. Background In recent years, advances in vehicle safety technology have been increasingly focused on improving the ability of vehicles to prevent and mitigate collisions. One important area of development is vehicle communication protocols, which allow vehicles to exchange critical information in real time. These systems are designed to enhance situational awareness, enabling vehicles to react to potential hazards before they become an impending threat. The primary use case for vehicle communications is to transmit vehicle data to a cloud-based application hosted on a remote server. In the case of a light crash event, drivers of vehicles involved in a multiple vehicle crash event may consider it undesirable to park alongside and share crash event information. For various reasons, the driver may feel the environment associated with the collision event unsafe. Also, the driver may not consider the light collision to be severe enough to stop and provide information about the collision event. The present disclosure addresses the above-described problems and others. Disclosure of Invention In one aspect, the present disclosure includes a cloud-based application hosted on a remote server for documenting a vehicle crash event. Cloud-based applications include a communication module, a collision matching module, and a collision database. The communication module communicates with a plurality of vehicles. The collision matching module is operatively coupled to the communication module and has a processing unit. The processing unit receives a first collision message reporting a collision event involving a first vehicle. The first collision message includes image data and vehicle data captured by the first vehicle during a collision event. The processing unit also determines whether a second collision message reporting a collision event involving a second vehicle has been received. The second collision message includes image data and vehicle data captured by the second vehicle during the collision event. When the second collision message has been received, the processing unit also compares the first collision message with the second collision message for confirming occurrence of a multi-vehicle collision event involving the first and second vehicles, and generates a collision event record to document the multi-vehicle collision event. The crash event record includes a first insurance record for a driver of the first vehicle and a second insurance record for a driver of the second vehicle. The crash database communicates with the crash matching module for storing the first and second crash messages and the crash event records. In one form, the processing unit generates a first crash report including the second insurance record for transmission from the communication module to the first vehicle. In another form, the processing unit generates a second crash report including the first insurance record for transmission from the communication module to the second vehicle. In yet another form, the processing unit (a) generates a list of target vehicles within a predetermined range of the first vehicle, (b) searches the collision database for a target collision message from one of the target vehicles, (c) compares the target collision message to the first collision message, and (d) confirms whether the first vehicle and the second vehicle are involved in the same collision event based on the comparison of the target collision message to the first collision message. In yet another form, the vehicle data includes a collision metric and the processing unit prompts the first vehicle, the second vehicle, or a user of the first and second vehicles to confirm whether the first vehicle and the second vehicle are involved in the same collision event and receives a response from the user confirming that the first and second vehicles are in the same collision event. In one form, the processing unit generates a first request including a vehicle brand, a vehicle model, and a vehicle color of the second vehicle for confirming that the second vehicle is involved in the multi-vehicle collision event. The request is sent from the communication module to the first vehicle. In another form, the processing unit generates a second request including a vehicle brand, a vehicle model, and a vehicle color of the first vehicle for confirming that the first vehicle is involved in the multi-vehicle crash event. The request is sent from the communication module to the second vehicle. In yet another form the first crash message includes vehicle data selected from the group consisting of a vehicle location for the first vehicle, a vehicle brand, a vehicle model, a vehicle color,