Cloud-based application platform for searching and retrieving evidence records related to vehicle events

Abstract

A cloud-based application platform for searching and retrieving evidence records related to vehicle events is provided. A method and system for collecting, matching, and reporting evidence related to a collision event captured on a first collision detection device associated with a vehicle transportation system. A first accident report of a collision event is communicated from a first collision detection device to a cloud-based application. The first accident report includes image data, location data, and time data of the collision event. A collision event database of the cloud-based application is searched to locate a second accident report of the collision event. And when the collision event of the first accident report is matched with the recorded collision event of the second accident report, the first accident report and the second accident report are assembled. A collision evidence report is generated based on the assembled first and second accident reports.

Description

Technical Field

[0001] The technical field generally relates to the collection of evidence of vehicle incidents, and more specifically to systems and methods for collecting, matching, and reporting evidence related to vehicle collision incidents captured on a first collision detection device associated with a vehicle transportation system. 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 these communication protocols 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 provides a method for collecting, matching, and reporting evidence related to a collision event involving a vehicle and an object captured on a first collision detection device associated with a vehicle transportation system. The method includes establishing a communication link between a cloud-based application and the first collision detection device. The first collision detection device registers with the cloud-based application to communicate with it. The method includes receiving a first accident report of a collision event communicated from the first collision detection device to the cloud-based application. The first accident report includes image data, location data, and time data of the collision event. The method includes searching a collision event database of the cloud-based application with multiple stored accident reports to locate a second accident report of the collision event. Each of the multiple stored accident reports includes image data, location data, and time data of the recorded collision event. The method includes compiling the first accident report and the second accident report when the collision event of the first accident report matches the recorded collision event of the second accident report, and generating a collision evidence report based on the compiled first and second accident reports.

[0006] In one form, the method includes storing the first accident report and collision evidence report into a collision event database.

[0007] In some forms, the first incident report is received from the equipment involved in the first collision event.

[0008] In at least one of the forms, the first accident report is received from an observation device located near the first collision event.

[0009] In another form, the first accident report is received from the vehicle adjacent to the first collision.

[0010] In some forms, the first accident report is received from infrastructure equipment associated with and adjacent to the vehicle transport system at the first collision event.

[0011] In another form, the method further includes: processing collision evidence reports to identify vehicles involved in a collision event, searching for cloud-based applications to determine whether the vehicle is registered to communicate with it, establishing a communication link with the vehicle if it is registered to communicate with the cloud-based application, and sending a collaboration evidence report to the vehicle.

[0012] In another embodiment, the method includes receiving a search query from a registered user on a cloud-based application. The search query includes geographic location and time window. The method also includes searching a collision event database based on the search query to identify collision events, and sending a collaborative evidence report to the registered user.

[0013] In one embodiment, the method further includes registering a user with a user device with the cloud-based application and granting the user permission to communicate with the cloud-based application via the user device. The cloud-based application receives time and location data from the user device. The method also includes setting user preferences for pushing notifications from the cloud-based application to the user-based application. User preferences include the device location range and device time window for pushing notifications. The method further includes generating a registration record for the user, including user and user device identifiers, permissions, and user preferences.

[0014] In another form, the method further includes: processing a first incident report to determine the time and location of the collision event, locating the user equipment based on time and location data received from the user equipment, and sending a notification for the collision event when the user equipment is near the collision event, based on the device location range and the device time window.

[0015] In another aspect, this disclosure provides a cloud-based application system for collecting, matching, and reporting evidence related to collision events within a vehicle transportation system. The cloud-based application is hosted on a remote server and includes a collision event database, a communication module, and an evidence matching module. The collision event database stores multiple accident reports. Each accident report is associated with a recorded collision event occurring between a vehicle and an object and includes image data, location data, and time data of the recorded collision event. The communication module establishes a communication link between the cloud-based application and a first collision detection device. The first collision detection device registers with the cloud-based application to communicate with it. The evidence matching module has a processing unit. This processing unit receives a first accident report of a first collision event communicated from the first collision detection device to the cloud-based application. The first accident report includes image data, location data, and time data of the first collision event. The processing unit also searches the collision event database to locate a second accident report for the first collision event; when the first collision event in the first accident report matches the recorded collision event in the second accident report, the first accident report and the second accident report are compiled; and a collision evidence report is generated based on the compiled first and second accident reports.

[0016] In one embodiment, the processing unit of the evidence matching module stores the first accident report and the collision evidence report into the collision event database.

[0017] In another configuration, the communication module is also configured to receive a first incident report from the device involved in the first collision event.

[0018] In some configurations, the communication module receives the first incident report from an observation device located near the first collision event.

[0019] In at least one form, the communication module receives a first accident report from a vehicle adjacent to the first collision event.

[0020] In another form, the communication module receives the first accident report from infrastructure equipment associated with the vehicle transport system and located near the first collision event.

[0021] In another form, the processing unit of the evidence matching module processes the collision evidence report to identify the vehicle involved in the collision event, searches for cloud-based applications to determine whether the vehicle is registered to communicate with it, establishes a communication link with the vehicle if it is registered to communicate with the cloud-based application, and sends a collaborative evidence report to the vehicle.

[0022] In another form, the evidence matching module's processing unit receives search queries from registered users on a cloud-based application. The search queries include geographic location and time window. In this form, the evidence matching module's processing unit also searches a collision event database based on the search queries to identify collision events and sends collaborative evidence reports to registered users.

[0023] In some forms, the evidence matching module's processing unit registers users with user devices with the cloud-based application and grants those users permission to communicate with the cloud-based application via their devices. The cloud-based application receives time and location data from the user devices. The evidence matching module's processing unit also sets user preferences for pushing notifications from the cloud-based application to the user-based application. User preferences include the device location range and device time window used for pushing notifications. The evidence matching module's processing unit also generates registration records for users, including user and user device identifiers, permissions, and user preferences.

[0024] In some forms, the processing unit of the evidence matching module processes the first incident report to determine the collision time and location for the collision event, locates the user equipment based on time and location data received from the user equipment, and sends a notification for the collision event when the user equipment is near the collision event based on the equipment location range and the equipment time window. Attached Figure Description

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

[0026] Figure 1 This is an illustrative diagram showing the context of a system according to this disclosure;

[0027] Figure 2 This is a block diagram of a remote server hosted for the collection, matching, and reporting of evidence related to collision events within a vehicle transportation system, as disclosed herein; and

[0028] Figure 3 The diagram illustrates the implementation. Figure 2 A flowchart outlining the application methods;

[0029] Figure 4 This is a flowchart illustrating a method for collecting, matching, and reporting evidence related to collision events within a vehicle transportation system; and

[0030] Figure 5 This is a flowchart illustrating a method for searching, matching, and reporting evidence related to collision events within a vehicle transportation system. 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-at-Law No. P108567-PRI-NP-US01); Information Gathering and Sharing From a Collision Event (Attorney-at-Law No. P108928-PRI-NP-US01); and Cloud-Based Collision Detection and Information Exchange (Attorney-at-Law No. P108929-PRI-NP-US01). The entire disclosure of each of the foregoing applications is incorporated herein by reference.

[0033] refer to Figure 1 This disclosure discloses a vehicle transportation system environment including a system 100 for collecting, searching, matching, and / or reporting collision-related evidence. The system includes an evidence collection application 102 stored on a remote server 104 communicating with a user terminal 106 and multiple collision detection devices 108 located around an intersection 112 of a road 110. While the environment of the collision detection devices 108 is located near or around the intersection 112, the environment of the collision detection devices 108 can include any location where a collision event occurs between multiple objects such as vehicles 108-1, 108-2. The collision detection devices 108 can be located within vehicles, mobile computing devices, vehicle roadside infrastructure equipment, traffic camera equipment, etc. When evidence collected in accident reports 124 matches a collision event, the evidence collection application 102 compiles one or more accident reports 124 received from the collision detection devices 108 and generates a collision evidence report 126 based on the evidence from the matched accident reports 124.

[0034] Each collision detection device 108 can capture collision events between involved objects (such as vehicles 108-1, 108-2). In one form, each collision detection device 108 is registered as a member of the evidence collection application 102. As a member associated with the evidence collection application 102, the collision detection device 108 is granted permission to communicate with the evidence collection application 102 to upload an accident report 124 generated based on evidence collected during the collision event detected by the collision detection device 108. The accident report 124 includes the location of the collision event, the time frame or time window of the collision event, image data capturing the collision event, and identification information related to the collision event. Each collision detection device 108 is enabled to broadcast messages to the evidence collection application 102 and other collision detection devices 108 within a predetermined range. The collision detection device 108 uses 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, and Vehicle-to-Everything (V2X). Using this communication broadcast protocol, each collision detection device 108 can send with low latency, ensuring that the evidence collection application 102 and other collision detection devices 108 within range can quickly receive and process data broadcast from the collision detection device 108 with low latency. The collision detection device 108 also manages incoming and outgoing data transmissions for its respective communication network and employs asymmetric encryption to protect broadcast messages sent or exchanged between the respective collision detection device 108 and the evidence collection application 102.

[0035] The collision detection device 108 initiates an input request to the user of the corresponding collision detection device 108 to determine whether the transmission of the corresponding accident report 124 is desired. When the user preference is set to "Yes" indicating that the transmission of the corresponding accident report is desired, the collision detection device 108 determines whether to send the accident report 124. If the user preference is set to "No" indicating that the transmission of the corresponding accident report 124 is not desired, the collision detection device 108 determines not to send the accident report 124.

[0036] Each collision detection 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 detection 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 detection device 108, such as the longitude and latitude coordinates of the collision detection device. Using the longitude and latitude coordinates, each collision detection device 108 determines the location associated with a collision event between the vehicles 114-1 and 114-2 involved, as observed using the respective collision detection device 108.

[0037] The collision detection device 108 can be implemented as a mobile device (not shown) associated with a vehicle (such as vehicles 108-1, 108-2 involved in the collision). Alternatively, each collision detection device 108 can be implemented as a mobile observer device associated with a vehicle (such as vehicle 108-3 not involved in the collision). Each collision detection device 108 can also be implemented as a fixed device 108-4 associated with roadside infrastructure equipment (such as traffic camera equipment, connected vehicle roadside equipment (not shown)). Figure 1 As shown, regardless of whether the device is a mobile or fixed device, it is located around the intersection 112 of road 110. Each collision detection device 108 is configured to acquire data on a collision event between a first vehicle 108-1 and a second vehicle 108-2, and send an accident report 124 containing that data to an evidence collection application 102.

[0038] Multiple collision detection devices 108 can detect collision events along road 110 individually and collectively. For example, a first vehicle 108-1 can detect a first collision event with a second vehicle 108-2, generate a first accident report 124-1 based on the detected first collision event, and send the first accident report 124-2 to the evidence collection application 102. Similarly, the second vehicle 108-2 can detect a second collision event with the first vehicle 108-1, generate a second accident report 124-2 based on the detected second collision event, and send the second accident report 124-2 to the evidence collection application.

[0039] The first vehicle 108-1 and the second vehicle 108-2 may be conventional, autonomous, or semi-autonomous vehicles communicating with the evidence-gathering application 102. In some embodiments, the first vehicle 108-1 and the second vehicle 108-2 may include a car, a motorcycle, or a truck. In this example, the first vehicle 108-1 is a passenger car. The first vehicle 108-1 and the second vehicle 108-2 include multiple components and subsystems distributed within the respective vehicles 108-1 and 108-2, designed to work together to perform one or more functions to achieve specific objectives related to the operation, safety, comfort, and / or efficiency of the respective vehicles 108-1 and 108-2. These systems may be mechanical, electrical, electronic, hydraulic, or a combination thereof, and are designed to ensure that the first vehicle 108-1 operates and performs effectively under one or more conditions. Each of the first vehicle 108-1 and the second vehicle 108-2 may detect collision events individually and / or jointly and generate an accident report based on the detection of a collision event.

[0040] Mobile observation device 108-3 and fixed observation device 108-4, not involved in the collision event, detect the collision event and subsequently generate and send an accident report 124 to the evidence collection application. Mobile observation device 108-3 may be a conventional, autonomous, or semi-autonomous vehicle communicating with the evidence collection application 102. In some embodiments, mobile observation device 108-3 may include a car, motorcycle, or truck. In this example, mobile observation device 108-3 is a passenger vehicle and includes multiple components and subsystems distributed throughout the third-party vehicle 108-3 to work together to perform one or more functions to achieve specific objectives related to the operation, safety, comfort, and / or efficiency of the third-party vehicle 108-3. These systems may be mechanical, electrical, electronic, hydraulic, or a combination thereof, and are designed to ensure that the third-party vehicle 108-3 operates and performs effectively under one or more conditions.

[0041] Evidence collection application 102 is a cloud-based application that provides cloud services via a network such as the Internet or a cellular network. The cloud-based application may be hosted by one or more remote servers or computers to process information exchanged between evidence collection application 102 and collision detection device 108 off-site, away from the collision detection device 108.

[0042] Refer again Figure 2 The evidence collection application 102 includes a registration module 128, an evidence matching module 130, a communication module 132, and a collision event database 134. The registration module 128 prompts the user via a user terminal 106 to enter registration information to associate the collision detection device 108 with the evidence collection application 102. The registration information includes a username, address, and mobile phone number. Depending on the collision detection device 108 being registered, the registration information may include other types of information.

[0043] In one embodiment, if the collision detection device 108 is a vehicle 108-1, 108-2, or 108-3, the registration information may include the username, vehicle information, insurance policy records, and driver's license information associated with the vehicle being registered. Vehicle information may also include data related to the VIN number, vehicle brand, vehicle type, and vehicle color. Insurance policy records include the policy name, policy number, and driver's insurance name. 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 detection device 108 is infrastructure equipment 108-4, the registration information includes the equipment identification number and equipment location.

[0044] Registration module 128 prompts the user to enter one or more user preferences to customize the user's experience with the evidence collection application 102. Registration module 128 prompts the user to enter a first user preference via user terminal 106, indicating whether the user wants an accident report automatically uploaded after the collision detection 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 collisions recorded near the collision detection device 108. "Near" includes a predetermined range adjacent to the collision detection device 108. Registration module 128 prompts the user to enter a third user preference via user terminal 106, indicating whether the evidence collection application can track the location of the collision detection device 108. Based on the registration information and user preferences, registration module 128 creates a user record 136 associated with the user and the collision detection device 108 being registered and stores it in the collision event database 134.

[0045] The evidence matching module 130 receives an accident report from the corresponding collision detection device 108 and stores the accident report in the collision event database 134. The evidence matching module 130 determines whether the collision detection device 108 that issued the accident report 124 has registered with the evidence collection application 102.

[0046] The evidence matching module 130 also determines whether either of the vehicles 108-1 or 108-2 involved in providing accident report 124 is registered as a member of the evidence collection application 102. In one example, based on registration information stored in the collision event database 134, the evidence matching module 130 determines that the affected vehicle has registered with the evidence collection application. The evidence matching module 130 sends a notification to the vehicles 108-1 or 108-2 that are registered as members of the evidence collection application 102, or to the user terminal 106 associated with a registered member. This notification prompts the user to assess a collision reported by vehicles 108-1 or 108-2 that is adjacent to the collision. In one form, the evidence matching module 130 determines the location of the collision event and broadcasts a notification to all collision detection devices of users with user records associated with the evidence collection application 102 who are located within a predetermined range of the collision event and the location of the corresponding evidence collection application.

[0047] In one embodiment, the evidence matching module 130 determines that the collision detection device 108 that issued the accident report 124 is not registered with the evidence collection application 102. The evidence matching module 130 prompts the user via a human-machine interface (not shown) associated with the corresponding evidence matching module 130 to determine whether the user wishes to register the vehicles 108-1 and 108-2 involved with the evidence collection application 102. In this example, if the user wishes to register the collision detection device 108, then, as described above, the evidence collection application 102 registers the corresponding collision detection device 108. In some embodiments, if the user does not wish to register with the evidence collection application 102, the evidence matching module 130 stores the accident report 124 in the collision event database 134. In another example, the evidence matching module 130 ignores the accident report 124.

[0048] In one embodiment, the evidence matching module 130 analyzes the image data of the accident report 124 to determine whether the current size, color, and / or format of the image data conforms to a predetermined image model. The evidence matching module 130 processes the image data of the accident report 124 to conform the image data to the desired size, color, format, or a combination thereof of the predetermined image model. For example, the evidence matching module 130 performs formatting, compression, cropping, white balance, or a combination thereof to manipulate the image data to the desired size, color, and / or format for storage in the collision event database 134.

[0049] In another example, the evidence matching module 130 analyzes image data to determine whether the image data includes metadata based on a metadata model. The metadata model identifies a list of collision-related data identifiers for each piece of image data stored in the collision event database 134. For example, the list of collision-related data identifiers includes the collision event, the location of the collision event, the time window of the collision event, and the identification of the vehicles involved, 108-1, 108-2, etc. When analyzing the image data, the evidence matching module 130 utilizes any number of image processing techniques known to those skilled in the art for identifying and extracting metadata associated with image data to search the image data and locate the metadata associated with it. In one form, the evidence matching module 130 determines, based on the metadata model, that the image data in the accident report includes metadata and stores the image data and the accident report. The evidence matching module 130 determines, based on the metadata model, that the image data omits some or all of the metadata and generates image metadata based on the metadata model and the accident report. Once generated, the evidence matching module 130 inserts the image metadata into the image data of the accident report, thereby creating processed image data, and stores the processed image data together with the accident report in the collision event database 134.

[0050] The evidence matching module 130 determines whether any other accident reports 124 related to the same collision event associated with accident report 124 have been received from other collision detection devices 108. Other accident reports 124 may have been previously stored in the collision event database 134. In one example, the evidence matching module 130 searches the collision event database 134 to locate previously stored accident reports 124 based on the time window and location of the collision event associated with the received accident report. When a previously stored accident report is identified as having the collision event, the evidence collection module compiles the received accident report 124 with the previously stored accident report 124 and generates a collision evidence report. The collision evidence report 126 includes the number of vehicles identified in the collision event, the identification of the collision detection device 108 that sent the accident report, the location of the detected collision event, the number of vehicles detected, descriptive data for each involved vehicle 108-1, 108-2, image data associated with the collision event from each received accident report 124, etc. The collision evidence report 126 may also include insurance policy records, driver's license information, vehicle registration information, or combinations thereof for the first vehicle 108-1 and the second vehicle 108-2. This information may be extracted from accident reports originating from the vehicles involved 108-1 and 108-2, or may be retrieved from the registration records of registered users in the evidence collection application 102. In one embodiment, the evidence matching module 130 receives a search query for the collision evidence report 126 associated with predetermined search criteria from the user terminal 106 or the collision detection device 108. The search criteria include search terms, such as words or phrases entered into the search engine (not shown) of the evidence collection application 102. For example, the search criteria include the location of the collision event, the time window of the collision event, the travel history within a predetermined time frame of the time window of the collision event, and image data capturing the collision event.

[0051] In one form, based on the association of the search query with a collision detection device 108 registered with the evidence collection application 102, the evidence matching module 130 determines whether to restrict access to data related to the collision evidence report 126 requested via the search query. In one example, the evidence matching module 130 determines that the search query is associated with a collision detection device 108 registered with the evidence collection application 102 and allows full access to the collision evidence report 126 requested by the search query. In one form, the evidence matching module 130 allows all collision detection devices 108 registered with the evidence collection application 102 to access the stored collision evidence report 126. In another example, when the search query is not associated with a collision detection device 108 registered with the evidence collection application 102, the evidence matching module 130 restricts or prohibits partial or complete access to the collision evidence report 126 requested by the search query. In one form, based on the association of the search query with an unregistered collision detection device 108, the evidence matching module 130 prohibits access to all stored collision evidence reports 126. In other words, the evidence matching module 130 can restrict access to the data in the requested collision evidence report 126 to the public or non-members of the evidence collection application 102 (i.e., less than full access). The limited access data in the collision evidence report 126 includes, but is not limited to, the location and time of the detected collision event, the number of vehicles detected in the collision event, and / or descriptive data associated with each of the vehicles involved 114-1, 114-2.

[0052] In addition to restricting access to collision evidence report 126, in one form, the evidence matching module 130 also prompts the user via user terminal 106 to register the collision detection device 108 associated with the search query. The evidence matching module 130 determines whether the user has already registered the collision detection device 108 with the evidence collection application 102 in response to the prompt to register the collision detection device 108 for the search query. The evidence matching module determines that the collision detection device 108 has been registered with the evidence collection application 102 and retrieves and displays the collision evidence report 126 requested based on the search query. The evidence matching module 130 determines that the user refuses to register the collision detection device 108 and, in response, restricts some or all access to the requested collision evidence report 126. For example, the evidence matching module 130 displays limited data from the collision evidence report 126, such as the collision event and its location, instead of displaying all collision evidence reports to the user via user terminal 106.

[0053] In another example, based on the user profile associated with the vehicle in question or the travel history of the corresponding collision detection device 108, the evidence matching module 130 determines whether full or limited access to the data in the collision evidence report 126 is permitted. In one form, the evidence matching module 130 determines whether the user profile initiating the search query is associated with the collision detection device 108 that is the vehicle in question 108-1, 108-2. For example, the evidence matching module identifies the vehicle in question 108-1, 108-2 based on the collision evidence report 126 retrieved according to the search query. The evidence matching module compares the vehicle in question 108-1, 108-2 with the collision detection device 108 associated with the search query. The evidence matching module 130 determines that the collision detection device 108 associated with the search query matches the vehicle in question 108-1, 108-2, and in response, retrieves and displays the collision evidence report 126 requested via the search query. The evidence matching module 130 determines that the collision detection device 108 associated with the search query does not match the vehicles 108-1 and 108-2 involved, and in response, limits a portion or all of the requested collision evidence report 126. In one form, the limited portion of the collision evidence report 126 may include, but is not limited to, the location and time of the detected collision event, the number of vehicles detected, and descriptive data for each of the affected vehicles 108.

[0054] In another form, based on the travel history associated with the corresponding collision detection device 108 registered by the user, the evidence matching module 130 determines whether to restrict access to the corresponding collision evidence report 126 requested in response to a search query initiated by the user. In one example, the evidence matching module 130 determines whether the location of the collision detection device 108 is within a predetermined range of the collision event. The evidence matching module 130 receives the travel history of the collision detection device 108 associated with the search query. The evidence matching module 130 analyzes the collision evidence report to determine the location and time window of the collision event. The evidence matching module 130 determines the location of the collision detection device 108 during the time frame of the collision event based on the time window of the collision event. The evidence matching module 130 determines whether the location of the collision detection device 108 is within a predetermined range of the location of the collision event and within the time window of the collision event.

[0055] When the location of the corresponding collision detection device 108 is not within the predetermined range and time window of the collision event associated with the requested corresponding collision evidence report 126, the evidence matching module 130 determines to restrict access to the corresponding collision evidence report 126. When the location of the corresponding collision detection device 108 is within the predetermined range and time window of the collision event associated with the requested corresponding collision evidence report 126, the evidence matching module 130 determines to grant full access to the corresponding collision evidence report 126.

[0056] Communication module 132 receives a request for a communication link from the requesting collision detection device 108. Once the communication link is established, communication module 132 receives an accident report 124 from collision detection device 108. Communication module 132 establishes communication with collision detection device 108 and user terminal 106 via any communication method (such as, for example, 4G / 5G cellular communication, Bluetooth, etc.) to exchange messages (e.g., data packets containing messages or data). Communication module 132 can also use dedicated communication protocols (such as Dedicated Short Range Communication (DSRC), Cellular Vehicle-to-Everything (C-V2X), Vehicle-to-Infrastructure (V2I), Vehicle-to-Person (V2P), etc.) to send messages. Communication module 132 employs asymmetric encryption to protect messages received, sent, or exchanged between collision detection devices 108.

[0057] The collision event database 134 stores and registers data related to the collision detection device 108 and collects incident reports 124 sent by the collision detection device 108. The collision event database 134 stores a public key 138, a private key 140, user records 136, received incident reports 124, and collision evidence reports 126. The public key 138 is used to securely encrypt the collision evidence reports 126 to be sent to the requesting collision detection device 108 or user terminal 106. The private key 140 is kept secret by the evidence collection application 102 and is used to decrypt the received incident reports 124 sent from the collision detection device 108.

[0058] User terminal 106 is a human-machine interface used by a user to register a specific collision detection device 108 with the evidence collection application 102. User terminal 106 may include a laptop computer, desktop computer, tablet terminal, personal digital assistant, smartphone, wearable device such as glasses or watch-type information processing terminals, etc. In one example, user terminal 106 is integrated into collision detection device 108. User terminal 106 sends data to evidence collection application 102 to register the corresponding collision detection device 108. This data is used to register the collision detection device as a member of the evidence collection application. As a registered member, collision detection device 108 is provided with one or more granted licenses to exchange data with evidence collection application 102. User terminal 106 allows the user to input data associated with collision detection device 108 related to one or more user preferences. User terminal 106 receives input from the user for search criteria used to request the search and retrieval of collision evidence 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.

[0059] refer to Figure 3 Evidence collection application 102 uses example method 300 to register the collision detection device as a member with one or more granted permissions to communicate with evidence collection application 102. At step 302, evidence collection application 102 starts method 300 and proceeds to step 304.

[0060] At step 304, the evidence collection application 102 collects registration information for multiple collision detection devices 108 to register each of the multiple collision detection devices as a member associated with the cloud-based application. The registration information is collected using user terminal 106. Each member of the evidence collection application 102 is granted permission to exchange communication with the cloud-based application. After registering the multiple collision detection devices, the evidence collection application 102 proceeds to step 306.

[0061] At step 306, the evidence collection application 102 sets user preferences for each member, which are used to automatically notify the corresponding collision detection devices near the collision event and within a predetermined time window associated with the detected nearby collision event, and proceeds to step 308. At step 308, the evidence collection application 102 generates user records for registration information and user preferences associated with each of the multiple collision detection devices, and proceeds to step 310. At step 310, the evidence collection application 102 stores the user records in the collision event database, and the process ends.

[0062] refer to Figure 4The evidence collection application 102 executes exemplary method 400 to automatically search and aggregate accident reports related to the same detected collision event. At step 402, the evidence collection application 102 begins method 400 and proceeds to step 404. At step 404, the evidence collection application 102 establishes a communication link with the collision detection device and proceeds to step 406. At step 406, the evidence collection application 102 receives a first accident report. This accident report includes a report generated based on collision information and vehicle insurance-related data. The collision information relates to a collision event detected between a first vehicle 108-1 and a second vehicle 108-2, and the vehicle insurance-related data was exchanged between the first and second vehicles or collected from the first vehicle after the collision event was detected. The collision-related information is generated based on sensing data detected within a time window of the collision event. The collision information includes the location of the collision event, the time window of the collision event, image data capturing the collision event between the first and second vehicles, and may also include collision measurement data. The vehicle insurance-related data includes driver's license information, related insurance policy records, and vehicle registration information related to at least one driver of the first and / or second vehicles. After receiving the incident report, the evidence collection application 102 proceeds to step 408.

[0063] At step 408, the evidence collection application 102 determines whether the received incident report is related to another previously stored incident report. For example, if the evidence collection application 102 determines "yes," the application proceeds to step 410. At step 410, the evidence collection application 102 compiles the received incident report with the previously stored incident report and proceeds to step 414. At step 414, the evidence collection application 102 generates a collision evidence report based on the received incident report and the previously stored incident report and proceeds to step 416. According to step 408, if the determination is "no," the evidence collection application 102 may also store the evidence report as a collision evidence report and proceed to step 416.

[0064] At step 416, the evidence collection application 102 broadcasts a notification to registered members associated with it, informing them of a collision event near their respective collision detection devices, and proceeds to step 418. This notification includes user request input to determine whether to send image data associated with the collision evidence report to the requesting collision detection device. At 418, the evidence collection application 102 sends the image data associated with the collision evidence report to the requesting collision detection device based on the user request input, and the process ends.

[0065] refer to Figure 5Evidence collection application 102 utilizes exemplary method 500 to automatically search and aggregate accident reports related to the same detected collision events. At step 502, evidence collection application 102 begins method 500 and proceeds to step 504. At step 504, evidence collection application 102 establishes a communication link with at least one of a user terminal or a registered collision detection device and proceeds to step 506. At step 506, evidence collection application 102 receives a request from the user terminal or a registered collision detection device to search for collision accident reports based on input search criteria and proceeds to step 508. The input search criteria may specify data definitions related to a given collision event, including a time window and location associated with a specific collision event. At step 508, evidence collection application 102 determines whether a search result has been found. If no search result is found, evidence collection application 102 proceeds to step 510. At step 510, evidence collection application 102 sends a notification indicating that no search result was found and the process ends.

[0066] If the search matches (multiple) previously stored incident reports with the search criteria, the evidence collection application 102 proceeds to step 512. At step 512, the evidence collection application 102 sends a notification of the search results to the user terminal or a registered collision detection device and proceeds to step 514. The search results include a list of matches against the requested search criteria, based on a percentage of the number of matching criteria associated with the collision evidence report.

[0067] At step 514, based on the user prompt input associated with the search result notification, the evidence collection application 102 determines whether to send the selected collision evidence report. If so, the evidence collection application 102 proceeds to step 516. At step 516, the evidence collection application 102 sends the collision evidence report to the user terminal or a registered collision detection device, and the process ends.

[0068] 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 method for collecting, matching, and reporting evidence relating to a collision event involving a vehicle and an object, captured on a first collision detection device associated with a vehicle transportation system, the method comprising: A communication link is established between a cloud-based application and a first collision detection device, wherein the first collision detection device registers with the cloud-based application to communicate with it. Receive a first incident report of the collision event from the first collision detection device and communicate it to the cloud-based application, wherein the first incident report includes image data, location data, and time data of the collision event; Search the cloud-based application's collision event database, which contains multiple stored incident reports, to locate a second incident report of the collision event, wherein each of the multiple stored incident reports includes image data, location data, and time data of the recorded collision event; When the collision event in the first accident report matches the recorded collision event in the second accident report, the first accident report and the second accident report are compiled together; as well as A collision evidence report is generated based on the compiled first and second accident reports.

2. The method according to claim 1, further comprising: Process the collision evidence report to determine the location and time window of the collision event; Analyze the image data in the collision evidence report to determine whether the image data includes metadata identifying the location and time window of the collision event; The image data is processed to include metadata that identifies the location and time window of the collision event, in order to create updated image data; as well as The collision evidence report containing the updated image data is stored.

3. The method of claim 1, wherein the first accident report is received from the device involved in the first collision event.

4. The method of claim 1, wherein the first accident report is received from an observation device adjacent to the first collision event, and wherein the observation device is at least one of a vehicle or infrastructure device.

5. The method according to claim 1, further comprising: Process the collision evidence report to identify the vehicle involved in the collision event; The cloud-based application is searched to determine whether the vehicle is registered for communication with it. When registered for communication with the cloud-based application, a communication link is established with the vehicle; as well as Send a cooperation evidence report to the vehicle.

6. The method according to claim 1, further comprising: The cloud-based application receives a search query from the user for the collision evidence report, wherein the search query includes geographic location and time window; The collision event database is searched based on the search query to identify the collision event; as well as Send a collaboration evidence report to the user.

7. The method according to claim 6, further comprising: Process the collision evidence report to identify the devices involved in the collision event; Determine whether the user is associated with the device involved in the collision; Whether to restrict access to the collision evidence report is determined based on whether the user is associated with the device involved in the collision event; as well as When the user is associated with the device involved in the collision event, the user is given access to the collision evidence report.

8. The method according to claim 6, further comprising: Process the collision evidence report to determine the location and time window of the collision event; The location of the user device is determined based on the trip history of the user device associated with the user, and whether the location is within the time window and the predetermined range of the location of the collision event. Whether to restrict access to the collision evidence report is determined based on whether the location of the user equipment is within the time window of the collision event and the predetermined range of the location; as well as When the user equipment is within the predetermined range and time window of the collision event, it provides registered users with access to the collision evidence report.

9. The method according to claim 1, further comprising: Register users with user devices with the cloud-based application; Granting the user permission to communicate with the cloud-based application via the user device, wherein the cloud-based application receives time and location data from the user device; Configure user preferences for pushing notifications from the cloud-based application to the user-based application, wherein the user preferences include a device location range and a device time window for pushing notifications; and A registration record is generated for the user, including the identifiers of the user and the user device, the permissions, and the user preferences.

10. The method of claim 9, further comprising: The first accident report is processed to determine the time and location of the collision event; The user equipment is located based on the time and location data received from the user equipment; as well as Based on the device location range and the device time window, a notification for the collision event is sent when the user device is near the collision event.

Images