System and method for recording vehicle events

Abstract

Systems and methods for recording vehicle events are provided. Methods and apparatus are provided for matching vehicles related to a collision event involving a first vehicle and a second vehicle. A first collision message having data relating to a first collision event detected by a first vehicle with a first unknown vehicle is received by a collision matching application. The collision matching application determines whether a second collision message has been received, the second collision message having data relating to a second collision event detected by a second vehicle with a second unknown vehicle. The first and second collision messages are compared to determine whether the first collision event is the same as the second collision 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.

Description

Technical Field

[0001] The technical field generally relates to the collection and recording of data associated with vehicle collision events, and more specifically to systems and methods for generating collision reports for multi-vehicle collision events. Background Technology

[0002] In recent years, advancements in vehicle safety technology have increasingly focused on improving vehicles' ability to prevent and mitigate collisions. A key 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 imminent threats. A primary use case for vehicle communication is transmitting vehicle data to cloud-based applications hosted on remote servers.

[0003] In the case of a minor collision, drivers of the vehicles involved in a multi-vehicle collision may feel it is inadvisable to pull over and share information about the collision. For various reasons, drivers may perceive the environment associated with the collision as unsafe. Similarly, drivers may not perceive the minor collision as serious enough to warrant stopping and providing information about the incident.

[0004] This disclosure addresses the aforementioned issues and more. Summary of the Invention

[0005] In one aspect, this disclosure includes a cloud-based application hosted on a remote server for recording vehicle collision events. The cloud-based application includes a communication module, a collision matching module, and a collision database.

[0006] The communication module communicates with multiple vehicles. A 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 the 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 is received, the processing unit also compares the first collision message with the second collision message to confirm that a multi-vehicle collision event involving both the first and second vehicles has occurred, and generates a collision event record to document the multi-vehicle collision event. The collision event record includes a first insurance record for the driver of the first vehicle and a second insurance record for the driver of the second vehicle. A collision database communicates with the collision matching module to store the first and second collision messages and the collision event record.

[0007] In one embodiment, the processing unit generates a first collision report, including a second insurance record, for transmission from the communication module to the first vehicle.

[0008] In another configuration, the processing unit generates a second collision report, including the first insurance record, for transmission from the communication module to the second vehicle.

[0009] In another form, the processing unit: (a) generates a list of target vehicles within a predetermined range of the first vehicle, (b) searches a collision database for a target collision message from one of the target vehicles, (c) compares the target collision message with a first collision message, and (d) determines whether the first vehicle and the second vehicle are involved in the same collision event based on the comparison between the target collision message and the first collision message.

[0010] In another form, the vehicle data includes collision metrics, and the processing unit prompts the user of the first vehicle, the second vehicle, or the first and second vehicles to confirm whether the first and second vehicles were involved in the same collision event, and receives a response from the user confirming that the first and second vehicles were involved in the same collision event.

[0011] In one embodiment, the processing unit generates a first request, including the vehicle brand, model, and color of the second vehicle, to confirm that the second vehicle is involved in a multi-vehicle collision event. This request is sent from the communication module to the first vehicle.

[0012] In another configuration, the processing unit generates a second request, including the vehicle brand, model, and color of the first vehicle, to confirm that the first vehicle was involved in a multi-vehicle collision. This request is then sent from the communication module to the second vehicle.

[0013] In another form, the first collision message includes vehicle data selected from a group consisting of: vehicle location, vehicle brand, vehicle model, vehicle color, impact force, impact direction, or a combination thereof for the first vehicle.

[0014] In another form, the processing unit processes the first collision message to confirm that the vehicle position for the second vehicle is within a predetermined distance of the vehicle position for the first vehicle.

[0015] In one embodiment, the processing unit processes the first collision message and the second collision message respectively to confirm that the impact force and direction against the second vehicle are consistent with the impact force and direction against the first vehicle.

[0016] In another aspect, this disclosure provides a method for logging vehicle collision events on a cloud-based application hosted on a remote server. The method includes receiving a first collision message reporting a collision event involving a first vehicle from a first vehicle. The first collision message includes image data and vehicle data captured by the first vehicle during the collision event. The method also includes determining whether a second collision message reporting a collision event involving a second vehicle has been received from a second vehicle. The second collision message includes image data and vehicle data captured by the second vehicle during the collision event. The method further includes: comparing the first collision message with the second collision message upon receipt of the second collision message to determine a matching collision event indicating that the first vehicle and the second vehicle were involved in the same collision event; and generating a collision event record for the matching collision event. The collision event record includes a first insurance record for the driver of the first vehicle and a second insurance record for the driver of the second vehicle. The method includes storing the first and second collision messages and the collision event record in a collision database.

[0017] In one form, the method includes generating a first collision report that includes a second insurance record, and sending the first collision report to a first vehicle.

[0018] In another form, the method includes generating a second collision report that includes the first insurance record, and sending the second collision report to a second vehicle.

[0019] In another form, the step of receiving a second collision message for reporting a collision event involving a second vehicle further includes: (a) generating a list of target vehicles within a predetermined range of the first vehicle, (b) searching a 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, based on the comparison of the target collision message with the first collision message, whether the first vehicle and the second vehicle were involved in the same collision event.

[0020] In another form, the vehicle data includes a collision metric, and step (d) further includes: (d-1) determining whether the first collision metric associated with the first collision message matches a second collision metric associated with the target collision message, and (d-2) confirming that the first and second vehicles were involved in the same collision event when the first collision metric matches the second collision metric.

[0021] In one form, the method includes: generating a first request that includes the vehicle brand, vehicle model, and vehicle color of a second vehicle to confirm that the second vehicle is involved in a multi-vehicle collision event; and sending the request to the first vehicle.

[0022] In some forms, the method includes: generating a second request that includes the vehicle brand, vehicle model, and vehicle color of a first vehicle to confirm that the first vehicle is involved in a multi-vehicle collision event; and sending the request to a second vehicle.

[0023] In another form, the first collision message includes vehicle data selected from a group consisting of: vehicle location for the first vehicle, vehicle brand, vehicle model, vehicle color, impact force, impact direction, or a combination thereof.

[0024] In another form, the method includes processing a first collision message and a second collision message respectively to confirm that the vehicle position for the second vehicle is within a predetermined distance of the vehicle position for the first vehicle.

[0025] In another aspect, this disclosure includes a method for logging vehicle collision events on a cloud-based application hosted on a remote server. The method includes receiving 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 the collision event. The method includes: 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 target collision messages from one of the target vehicles; comparing the first collision message with target collision messages in the list of target vehicles to confirm that the impact force and impact direction of the vehicle data associated with the first collision message match the impact force and impact direction of the vehicle data in one of the target collision messages; confirming, based on the comparison between the target collision message and the first collision message, whether the first vehicle and a second vehicle were involved in the same collision event; and generating a collision event record for the same collision event. The collision event record includes a first insurance record for the driver of the first vehicle and a second insurance record for the driver of the second vehicle. Attached Figure Description

[0026] Exemplary embodiments will now be described in conjunction with the following figures, wherein the same numerals denote the same elements, and wherein:

[0027] Figure 1 This is an illustrative diagram of a collision event sharing (CES) system according to an embodiment;

[0028] Figure 2 This is a block diagram of a cloud-based collision matching application hosted on a remote server according to an embodiment;

[0029] Figure 3 Utilization according to the embodiments Figure 2 The functional flowchart of the collision matching application method; and

[0030] Figure 4Utilization according to the embodiments Figure 2 The functional flowchart of the collision matching application method. Detailed Implementation

[0031] The following detailed description is merely exemplary in nature and is not intended to limit application and use. Furthermore, it is not intended to be bound by any express or implied theory presented in the foregoing technical field, background art, summary of the invention, or the following detailed description. As used herein, the term module refers to an application-specific integrated circuit (ASIC), electronic circuitry, a processor (shared, dedicated, or grouped) and memory executing one or more software or firmware programs, combinational logic circuitry, and / or other suitable components providing the described functionality.

[0032] Additional information relating to the subject matter described and claimed herein is provided in the following related applications filed by the applicant on the same date: System and Method for Collision Matching and Information Exchange (Attorney's File No. P108567-PRI-NP-US01); Information Gathering and Sharing From a Collision Event (Attorney's File No. P108928-PRI-NP-US01); and Cloud-Based Application Platform To Search and Retrieve Evidence Records Related to Vehicular Events (Attorney's File No. P108926-PRI-NP-US01). The entire disclosure of each of the foregoing applications is incorporated herein by reference.

[0033] refer to Figure 1 This disclosure provides a collision detection and recording system 100, which includes a collision matching application 102 stored on a remote server 104 communicating with a user terminal 106, and multiple collision reporting devices 108 located around an intersection 110 of a road 112. While the environment of the collision reporting devices 108 is located near or around the intersection 110, the environment of the collision reporting devices 108 can include any location where a collision event occurs between multiple vehicles 114. The collision reporting devices 108 can be embodied in vehicles, infrastructure (e.g., traffic cameras, road signs, light poles, traffic signals, etc.), or mobile devices (e.g., smartphones) of people near the collision event.

[0034] The collision matching application 102 is geographically located away from the collision reporting device 108 and is used to receive multiple collision messages 124 from the collision reporting device 108 (e.g., first vehicle 114-1 and second vehicle 114-2), compare the collision messages 124 to confirm a multi-vehicle collision event involving first vehicle 114-1 and second vehicle 114-2, and generate a collision event record 138. The collision matching application 102 can also generate a collision report based on the collision event record 138 for transmission to first vehicle 114-1, second vehicle 114-2, or both. Collision messages 124 may include image data, geographic data, and / or time data. In the case of an onboard collision reporting device, the collision message may also include vehicle data related to the corresponding vehicle at or near the time window of the corresponding collision event. Image data may be (multiple) still images, (multiple) video images, or a combination thereof. Vehicle data may include the collision event, vehicle location data, vehicle brand, vehicle model, vehicle color, vehicle speed, acceleration, collision measurement, or a combination thereof. Collision metrics may include steering wheel angle, yaw rate, braking status, airbag deployment, hard braking, stability control, path history, headlight status, vehicle size, turn signal status, impact direction, and impact force. Collision message 124 may also include driver's license information, vehicle registration information, and insurance policy records, or a combination thereof, related to the driver of the vehicle that sent the collision message 124.

[0035] Each collision reporting device 108 includes a location system (not shown), such as a Global Positioning System (GPS), a Global Navigation System, or a similar satellite navigation system. The location system can be configured to generate location data for the collision reporting device 108, such as via a transceiver communicating with one or more satellites orbiting the Earth. The location data may include the current geographic location of each collision reporting device 108, such as the longitude and latitude or GPS coordinates of the collision detection device. Using the current geographic location, each collision reporting device 108 can estimate the location associated with the collision event between the vehicles 114-1 and 114-2 involved, as observed using the respective collision reporting device 108.

[0036] Each collision reporting device 108 includes a communication system (not shown) that enables the broadcasting of messages within a predetermined range around the respective collision reporting device 108. The collision reporting device 108 may use a dedicated communication protocol to send or broadcast messages (e.g., data packets containing messages or data), such as Dedicated Short Range Communication (DSRC), Vehicle-to-Vehicle (V2V) communication systems, Cellular Vehicle-to-Everything (C-V2X), Vehicle-to-Infrastructure (V2I), Vehicle-to-Person (V2P), 5G LTE cellular communication, etc. Using this communication broadcasting protocol, each collision reporting device 108 is able to send messages with low latency, ensuring that messages are sent and received quickly. Each collision reporting device 108 also manages incoming and outgoing data transmissions for its respective communication network and may employ asymmetric encryption to protect broadcast messages sent or exchanged with the collision matching application 102. Each collision reporting device 108 initiates an input request to the user of the respective vehicle to determine whether it expects the transmission of the corresponding collision message 124. When a user preference is set to indicate that the transmission of the corresponding collision message 124 is expected, each collision reporting device 108 determines whether to send the collision message 124. If a user preference is set to indicate that the transmission of the corresponding collision message 124 is not expected, each collision reporting device 108 determines not to send the collision message 124.

[0037] In one embodiment, collision reporting devices 108 are registered as members of collision matching application 102. As registered members, each collision reporting device 108 is granted permission to send and receive communication messages with collision matching application 102. Each collision reporting device 108 detects collision events with unknown vehicles individually and / or jointly. For example, a first collision reporting device 108-1 may detect a first collision event. A second collision reporting device 108-2 may detect a second collision event. Based on the detection of the corresponding collision event, the first collision reporting device 108-1 and the second collision reporting device 108-2 respectively send their corresponding collision messages to collision matching application 102. In response to the detection of a collision event, the first collision reporting device 108-1 broadcasts the first collision message, and the second collision reporting device 108-2 broadcasts the second collision message 124-1, which are received by collision matching application 102. The first collision message 124-1 and the second collision message 124-2 may also be received by other collision reporting devices 108.

[0038] In one example, the collision reporting device 108 includes a first vehicle 114-1, a second vehicle 114-2, a third vehicle 114-3, a fourth vehicle 114-4, etc. (collectively referred to as vehicles 114). For the purposes of system 100, the first vehicle 114-1, the second vehicle 114-2, the third vehicle 114-3, and the fourth vehicle 114-4 are similar in structure and function. The first vehicle 114-1 and the second vehicle 114-2 may be collectively referred to as the vehicles involved. Vehicles 114 may be conventional, autonomous, or semi-autonomous vehicles that communicate separately with the collision matching application 102. Vehicles 114 may include motor vehicles such as automobiles, motorcycles, or trucks, with multiple components and subsystems distributed within the vehicle to work together to perform one or more functions, thereby achieving specific objectives related to vehicle operation, safety, comfort, and / or efficiency. These systems may be mechanical, electrical, electronic, hydraulic, or a combination thereof, and are designed to ensure that vehicles 114 operate and perform effectively under one or more conditions.

[0039] In another example, some collision reporting devices 108 may be smartphones or similar mobile devices (not shown) associated with people near the collision event. In yet another example, collision reporting devices 108 may be embodied as fixed devices associated with infrastructure equipment (such as traffic cameras). Figure 1 As shown, regardless of whether the device is a mobile or fixed device, it is located around the intersection 110 of road 112. Each collision reporting device 108 is configured to acquire data on a collision event between a first vehicle 114-1 and a second vehicle 114-2, and send a collision message 124 containing that data to a collision matching application 102.

[0040] The collision matching application 102 is a cloud-based application that provides cloud services via a network such as the Internet or a cellular network. The collision matching application 102 may be hosted by one or more remote servers or computers to process the information exchanged between the vehicle involved 114 and the collision matching application 102 located remotely from the vehicle involved 114.

[0041] Refer again Figure 2The collision matching application 102 includes a registration module 128, a collision matching module 130, a communication module 132, and a collision database 134. The registration module 128 prompts a user via a user terminal 106 to enter registration information for associating the collision reporting device 108 with the collision matching application 102. In one embodiment, the collision reporting device is a vehicle. In this embodiment, the registration information includes a username, address, and mobile phone number. The registration information may also include a username, vehicle information, insurance policy records, and driver's license information associated with the vehicle and driver being registered. Vehicle information includes data related to the vehicle identification number (VIN), vehicle brand, vehicle model, and vehicle color. Insurance policy records include the identity of the insurance company, policy number, insured vehicles under the policy, and (multiple) insured drivers. Driver's license information includes the driver's name, address, license number, and license validity date. In another embodiment, the collision reporting device 108 may be an infrastructure device. In this embodiment, the registration information includes a device identification number and device location; however, vehicle information, insurance policy records, or driver's license information will not be present.

[0042] Registration module 128 prompts the user to enter one or more user preferences to customize the user's experience with the collision matching application 102. Registration module 128 prompts the user to enter a first user preference via user terminal 106, indicating whether the user wants to automatically broadcast collision messages after the collision reporting device 108 detects a collision event. Registration module 128 prompts the user to enter a second user preference via user terminal 106, indicating whether to notify the user via user terminal notification to view collision event records identified near the collision reporting device 108. "Near" of the collision reporting device 108 includes a predetermined range adjacent to the collision reporting device 108. Registration module 128 prompts the user to enter a third user preference via user terminal 106, indicating whether the collision matching application 102 can track the location of the vehicle being registered. Based on the registration information and user preferences, registration module 128 creates a user record 136 associated with the vehicle being registered and stores it in the collision database 134.

[0043] In one embodiment, if the collision reporting device 108 is a vehicle 114-1, 114-2, 114-3, or 114-4, the registration information may include the username, vehicle information, insurance policy records, and driver's license information associated with the vehicle 108-1, 108-2, or 108-3 that is being registered. The vehicle information may also include data related to the VIN number, vehicle brand, vehicle type, and vehicle color. The insurance policy records include the policy name, policy number, and driver's insurance name. The driver's license information includes the driver's name, driver's address, driver's license number, and driver's license expiry date. In another embodiment, if the collision reporting device 108 is infrastructure equipment 108-4, the registration information includes the equipment identification number and equipment location.

[0044] The collision matching module 130 receives a communication request from the collision reporting device 108 (such as the vehicle involved, 114). The collision matching module 130 determines whether the collision reporting device 108 is a registered member of the collision matching application 102. The collision matching module 130 requests registration of any vehicle that is not currently a registered member of the collision matching application 102 and requests communication.

[0045] The collision matching module 130 receives a first collision message 124-1 from the first involved vehicle 114-1. The first collision message 124-1 indicates that the first involved vehicle 114-1 was involved in a first collision event and includes image data and vehicle data captured by the first involved vehicle 114-1 during the first collision event. The collision matching module 130 then collects a list of target vehicles within a predetermined range of the first involved vehicle 114-1 based on collision reporting devices 108 registered with the collision matching application 102. The collision matching module 130 receives location data from each collision reporting device 108 registered with the registration module 128. Using the location data from the collision reporting devices 108, the collision matching module 130 obtains a list of target vehicles in the vicinity 119 of the involved vehicle 114-1 and determines the total number of target vehicles based on the obtained list. The vicinity 119 of the first involved vehicle 114-1 includes a predetermined range adjacent to the first involved vehicle 114-1. The collision matching module 130 identifies vehicles located within the vicinity 119 of the first involved vehicle 114-1. This target vehicle list is a list of vehicles used to determine whether there are any other vehicles 114 affected or involved in the same collision event as the first involved vehicle 114-1.

[0046] The collision matching module 130 identifies a second involved vehicle based on a target vehicle list. The collision matching module 130 processes collision messages 124 sequentially for each target vehicle in the target vehicle list to determine if the target vehicle is another involved vehicle. In this regard, the collision matching module 130 receives and processes second (or subsequent) collision messages from the second (or subsequent) vehicles 114-2. The second collision message 124-2 indicates that the second vehicle is involved in a second collision event and includes image data and vehicle data captured by the collision reporting device 108 during the second collision event. The collision matching module 130 stores the second collision message 124-2 in the collision database 134. The collision matching module 130 processes the second collision message to determine the vehicle identifier of the second vehicle.

[0047] The collision matching module 130 compares the vehicle identifier of the second vehicle with the vehicle identifiers for each of the target vehicles i. When the vehicle identifier of the second vehicle matches the vehicle identifier of the target vehicle, the collision matching module 130 determines that one of the target vehicles is the second vehicle. When the vehicle identifier of the second vehicle does not match the vehicle identifier of the target vehicle, the collision matching module 130 determines that the target vehicle is not the second vehicle. Next, the collision matching module 130 verifies that the target vehicle i is the second involved vehicle 114-2.

[0048] In one example, a user query based on the users in the involved vehicles is validated. The collision matching module 130 activates the human-machine interface (HMI) (not shown) of one or both of the involved vehicles 114-1 and 114-2. The collision matching module 130 displays a first vehicle identifier to the user of the second involved vehicle 114-2 and displays second vehicle information to the user of the first involved vehicle 114-1 to confirm that the two vehicles were involved in the same collision event. The collision matching module 130 prompts the users of the corresponding vehicles via the HMI to confirm that the collision matching module 130 has correctly identified the target vehicle as the second involved vehicle 114-2. The collision matching module 130 determines that the target vehicle is the second involved vehicle 114-2 based on the "yes" or "no" response to the prompt.

[0049] In another example, verification is based on information from first and second collision messages 124-1 and 124-2. The collision matching module 130 compares the collision metric from the first collision message 124-1 with the collision metric from the second collision message 124-2. The collision matching module 130 determines whether the first involved vehicle 114-1 and the target vehicle are involved in the same collision event based on the matched impact force and impact direction. The collision matching module 130 obtains the first impact force and first impact direction from the first collision message 124-1 associated with the first involved vehicle 114-1. The collision matching module 130 also obtains the second impact force and second impact direction from the corresponding collision message 124-2 sent by the corresponding target vehicle. The collision matching module 130 determines whether the first impact force and first impact direction match the second impact force and second impact direction, respectively. When the second impact force and second impact direction are complementary to the first impact force and first impact direction, the collision matching module 130 verifies that the target vehicle is the second involved vehicle. When the second impact force and the second impact direction are not complementary to each other, the collision matching module 130 does not confirm that the target vehicle i is the second involved vehicle 114-2.

[0050] Once the collision matching module 130 verifies that a multi-vehicle collision event involving the first vehicle 114-1 and the second vehicle 114-2 has occurred, a collision event record 138 is generated by the collision matching module 130 and stored in the collision database 134. The collision event record 138 may include vehicle registration data, driver's license information, and insurance policy records extracted from the first and second collision messages 124-1 and 124-2. The collision event record may also include image data, vehicle location, vehicle telemetry (e.g., speed, vehicle direction, force applied to the brakes, force applied to the accelerator pedal), airbag status, seatbelt status, advanced driver assistance system status (e.g., ADAS feature enabled / disabled), number of occupants, date and time, and button status for vehicle SaaS applications (Software as a Service applications) (e.g., whether the OnStar button is active or inactive).

[0051] The collision matching module 130 generates collision reports for the first and second vehicles involved. The first collision report 126-1 includes vehicle registration data, driver's license information, and / or insurance policy records related to the driver of the second vehicle 114-2. The second collision report 126-2 includes vehicle registration data, driver's license information, and / or insurance policy records related to the driver of the first vehicle 114-1.

[0052] Once collision reports 126-1 and 126-2 are generated, the collision matching module 130 determines whether to send the first collision report 126-1 to the first vehicle 114-1 and the second collision report to the second vehicle 114-2. In one example, the collision matching module 130 sends a user response prompt to the first vehicle 114-1 and / or the second vehicle 114-2 to determine whether each driver of the involved vehicles 114 expects the transmission of the corresponding collision report. When an affirmative response is received, the collision matching module 130 sends the first collision reports 126-1 and 126-2 to the first and second involved vehicles. In some embodiments, the collision matching module 130 stores the collision reports 126-1 and 126-2 in the collision database 134.

[0053] The collision database 134 stores and registers data related to the collision reporting device 108 and collects data related to collision messages 124 issued by the collision reporting device 108, including collision messages 124-1, 124-2, collision reports 126-1, 126-2, and / or collision event records 138. The collision database 134 also stores a public key 140, a private key 142, and a user record 136. The public key 140 is used by the collision matching application 102 to securely encrypt the collision report 126 before sending it to the corresponding first vehicle 114-1, second vehicle 114-2, or a combination thereof. The private key 142 is kept secret by the collision matching application 102 and is used to decrypt the received collision messages 124 issued by the collision reporting device 108.

[0054] User terminal 106 is a human-machine interface used by a user to register a specific collision reporting device 108 with the collision matching application 102. User terminal 106 may include a laptop computer, desktop computer, tablet terminal, personal digital assistant, smartphone, wearable device such as an eyeglass or watch-type information processing terminal, etc. In one example, user terminal 106 is integrated into collision reporting device 108. User terminal 106 sends data to collision matching application 102 to register the corresponding collision reporting device 108. This data is used to register collision reporting device 108 as a member of collision matching application 102. As a registered member, collision reporting device 108 is granted one or more licenses to exchange data communication with collision matching application 102. User terminal 106 allows the user to input data associated with collision reporting device 108 related to one or more user preferences. User terminal 106 receives input from the user for search criteria used to request a search and retrieve collision report 126. Search criteria include a search query based on a time window associated with the collision event, the location of the collision event, and vehicle description data. The time window includes the date and time associated with the collision event. Vehicle description data includes the vehicle brand, model, and color. The vehicle description may also include the license plate number.

[0055] refer to Figure 3 The collision matching application 102 uses example method 300 to generate a collision report for the vehicles 114-1 and 114-2 involved in the multi-vehicle collision event. At step 302, the collision matching application 102 starts method 300 and proceeds to step 304.

[0056] At step 304, the collision matching application 102 receives a first collision message 124 reporting a first collision event from the collision reporting device 108 of the first involved vehicle 114-1, and proceeds to step 306.

[0057] At step 306, the collision matching application 102 generates a target vehicle list within a certain range of the first involved vehicle 114-1. The target vehicle list is used to identify other involved vehicles 114 associated with the first collision event. The collision matching application retrieves location data for each registered collision reporting device 108 within the collision database 134. Using the location data of each of the registered collision reporting devices 108, the collision matching application 102 determines whether each collision reporting device 108 is within a predetermined range of the involved vehicles. If the corresponding collision reporting device 108 is within the predetermined range of the first involved vehicle 114-1, the collision matching application 102 adds the corresponding collision reporting device 108 to the target vehicle list. Therefore, the target vehicle list includes involved vehicles 114-2 located near the first involved vehicle 114-1 and uninvolved vehicles 114-3 and 114-4. After compiling the target vehicle list, the collision matching application 102 calculates the total number of target vehicles and proceeds to step 308.

[0058] At step 308, the collision matching application 102 determines whether each vehicle 114-2, 114-3, and 114-4 in the target vehicle list has been evaluated. The collision matching application 102 uses the total number of target vehicles to determine whether all target vehicles 114-2, 114-3, and 114-4 have been processed. The collision matching application 102 determines whether the target vehicle is the last target vehicle in the target vehicle list based on the total number of target vehicles. If the collision matching application 102 determines "yes," proceed to step 310. Otherwise, the collision matching application 102 determines "no" and proceeds to step 314.

[0059] At step 314, the collision matching application 102 obtains target vehicle i from the target vehicle list and proceeds to step 316. Initially, i is set to 1 to allow the collision matching application 102 to retrieve the first target vehicle from the target vehicle list. After processing target vehicle i to determine whether it is the involved vehicle, the collision matching application increments i by a predetermined value, such as 1. Incrementing i allows the collision matching application to retrieve subsequent target vehicles for later processing.

[0060] At step 316, the collision matching application 102 determines whether a collision message 124 has been received from the target vehicle i. For example, if the collision matching application 102 determines "no" and returns to step 308, or if the collision matching application 102 determines "yes" and proceeds to step 318, the collision matching application 102 determines "yes" and proceeds to step 318.

[0061] At step 318, the collision matching application 102 determines whether the corresponding target vehicle i is the second involved vehicle 114-2. When determining whether the corresponding target vehicle i is the second involved vehicle 114-2, the collision matching application 102 proceeds to step 320.

[0062] At step 320, the collision matching application 102 determines whether a first impact force associated with a collision event involving the first involved vehicle 114-1 matches a second impact force associated with a collision event involving the corresponding target vehicle i. The collision matching application 102 obtains the first impact force from a first collision message 124-1 emitted by the first involved vehicle 114-1. Similarly, the collision matching application 102 obtains the second impact force from a corresponding collision message 124-2 emitted by the target vehicle i. The collision matching application compares the first impact force with the second impact force to determine if a match exists. If the collision matching application 102 determines "no," it returns to step 308 to evaluate the next target vehicle. Otherwise, the collision matching application 102 determines "yes," and proceeds to step 322.

[0063] At step 322, the collision matching application 102 determines whether the first impact direction associated with the first collision message 124-1 received from the first involved vehicle 114-1 matches the second impact direction associated with the second collision message 124-2 received from the corresponding target vehicle i. The collision matching application 102 compares the first impact direction with the second impact direction to determine whether there is a match in the impact directions. If the collision matching application 102 determines "no", it returns to step 308 to evaluate the next target vehicle. Otherwise, the collision matching application 102 determines "yes" and proceeds to step 324, and the target vehicle i becomes the second or another involved vehicle.

[0064] At step 324, the collision matching application 102 generates a collision report 126 for the first involved vehicle 114-1 and the second or subsequent involved vehicle 114-2, and proceeds to step 308 to evaluate the next target vehicle.

[0065] Once all target vehicles have been evaluated, in step 310, the collision matching application 102 sends the generated collision report to the corresponding involved vehicle 114 and proceeds to the end.

[0066] refer to Figure 4 The collision matching application 102 uses another example method 400 to generate a collision report for the vehicles involved in the collision event. At step 402, the collision matching application 102 starts method 400 and proceeds to step 404.

[0067] At step 404, the collision matching application 102 receives a first collision detection message reporting a first collision event from the collision reporting device 108 of the first involved vehicle 114-1, and proceeds to step 406.

[0068] At step 406, the collision matching application 102 generates a target vehicle list within a certain range of the first involved vehicle 114-1. This target vehicle list is used to identify other involved vehicles associated with the first collision event. The collision matching application 102 retrieves location data for each registered collision reporting device 108 within the collision database 134. Using the location data of each of the registered collision reporting devices 108, the collision matching application 102 identifies each collision reporting device 108 within a predetermined range of the first involved vehicle 114-1. If a corresponding collision reporting device 108 associated with vehicle 114 is within the predetermined range of the first involved vehicle 114-1, the collision matching application 102 adds the corresponding collision reporting device 108 to the target vehicle list. Upon completion of evaluating each collision reporting device, the collision matching application 102 calculates the total number of target vehicles and proceeds to step 408.

[0069] At step 408, the collision matching application 102 determines whether all target vehicles have been evaluated. If the collision matching application 102 determines "yes", proceed to step 410. Otherwise, the collision matching application 102 determines "no" and proceeds to step 414 to evaluate the next target vehicle.

[0070] At step 414, the collision matching application 102 obtains the target vehicles from the target vehicle list and proceeds to step 416.

[0071] At step 416, the collision matching application 102 determines whether a collision detection message has been received from the target vehicle. If the collision matching application 102 determines "no," the method returns to step 408 to check whether all target vehicles have been evaluated. Otherwise, the collision matching application 102 determines "yes" and proceeds to step 418. At step 418, the collision matching application 102 activates the target vehicle's HMI and proceeds to step 420.

[0072] At step 420, the collision matching application 102 determines whether the target vehicle is involved in the collision event of the first involved vehicle, and therefore is the second involved vehicle 114-2. Upon determining whether the target vehicle is the second involved vehicle, the collision matching application 102 proceeds to step 422.

[0073] At step 422, the collision matching application 102 prompts the user of the target vehicle via the HMI to confirm whether his or her vehicle was involved in the collision event with the first involved vehicle. The collision matching application 102 retrieves image data associated with the first collision message received from the first involved vehicle 114-1. The collision matching application 102 displays the image data to the user associated with the target vehicle and prompts the user to confirm whether the target vehicle was involved in the collision event. If the response from the user is "no", the collision matching application 102 determines to return to step 408. If the response from the user is "yes", the collision matching application 102 verifies that the target vehicle is the second (or subsequent) involved vehicle and proceeds to step 424.

[0074] At step 424, the collision matching application determines whether the user of the first involved vehicle 114-1 or the second or subsequent involved vehicle 114-2 wishes to exchange driver, vehicle, and insurance information. If the collision matching application 102 determines "no," then method 400 returns to step 408 to check whether all target vehicles have been evaluated. If the collision matching application 102 determines "yes," then method 400 proceeds to step 426.

[0075] At step 426, the collision matching application 102 generates a collision report for the first involved vehicle 114-1 and the second (or subsequent) involved vehicle 114-2, and proceeds to step 408 to see if all target vehicles have been evaluated.

[0076] Once all target vehicles have been evaluated, method 400 proceeds to step 410, and the collision matching application 102 sends the collision report generated in step 426 to the corresponding involved vehicle 114, and proceeds to the end at step 412.

[0077] While at least one exemplary embodiment has been presented in the foregoing detailed description, it should be understood that numerous variations exist. It should also be understood that the exemplary embodiments or multiple exemplary embodiments are merely examples and are not intended to limit the scope, applicability, or configuration of this disclosure in any way. Rather, the foregoing detailed description will provide those skilled in the art with a convenient roadmap for implementing the exemplary embodiments or multiple exemplary embodiments. It should be understood that various changes can be made to the function and arrangement of the elements without departing from the scope of this disclosure as set forth in the appended claims and their legal equivalents.

Claims

1. A cloud-based application hosted on a remote server for recording vehicle collision events, the cloud-based application comprising: A communication module configured to communicate with multiple vehicles; A collision matching module, operably coupled to the communication module and having a processing unit, the processing unit being configured to: Receive 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; Determine 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; When the second collision message has been received, the first collision message is compared with the second collision message to confirm that a multi-vehicle collision event involving the first vehicle and the second vehicle has occurred; as well as A collision event log is generated to record the multi-vehicle collision events, wherein the collision event log includes a first insurance record for the driver of the first vehicle and a second insurance record for the driver of the second vehicle; and A collision database, which communicates with the collision matching module, is used to store the first collision message, the second collision message, 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 including 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 including the first insurance record for transmission from the communication module to the second vehicle.

4. The cloud-based application according to claim 1, wherein the processing unit is further configured to: (a) Generate a list of target vehicles within a predetermined range of the first vehicle; (b) Search the collision database for a target collision message from one of the target vehicles; (c) Compare the target collision message with the first collision message; and (d) Determine whether the first vehicle and the second vehicle were involved in the same collision event based on the comparison between the target collision message and the first collision message.

5. The cloud-based application according to claim 4, wherein the vehicle data includes collision metrics, and the processing unit is further configured to: The user of the first vehicle, the second vehicle, or both the first and second vehicles is prompted to confirm whether the first and second vehicles were involved in the same collision event; and The user receives confirmation of the responses of the first vehicle and the second vehicle in the same collision event.

6. The cloud-based application according to claim 1, wherein the processing unit is further configured to: A first request is generated, including the vehicle brand, model, and color of the second vehicle, to confirm 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 is generated, including the vehicle brand, vehicle model, and vehicle color of the first vehicle, to confirm that the first vehicle was 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 includes vehicle data selected from the group consisting of: vehicle location, vehicle brand, vehicle model, vehicle color, impact force, 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 to confirm that the vehicle position for the second vehicle is within a predetermined distance of the vehicle position for the first vehicle.

9. The cloud-based application of claim 7, wherein the processing unit is further configured to process the first collision message and the second collision message respectively to confirm that the impact force and the impact direction against the second vehicle are consistent with the impact force and the impact direction against the first vehicle.

10. A method for logging vehicle collision events on a cloud-based application hosted on a remote server, the method comprising: Receive a first collision message from the 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; Store the first collision message in the collision database; Generate a list of target vehicles within a predetermined range of the first vehicle; Search the collision database for target collision messages from one of the target vehicles; The first collision message is compared 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 are consistent with the impact force and impact direction of the vehicle data in one of the target collision messages. The comparison between the target collision message and the first collision message is used to determine whether the first vehicle and the second vehicle were involved in the same collision event. as well as Generate a collision event record for the same collision event, wherein the collision event record includes a first insurance record for the driver of the first vehicle and a second insurance record for the driver of the second vehicle.

Images