Accident evaluation system

Abstract

An accident assessment system for a vehicle accident includes a first imager configured to capture image data corresponding to a first vehicle, and a first vehicle processor communicatively coupled to the first imager and configured to receive the captured image data. The first vehicle processor is configured to generate a first vehicle report in response to an accident captured in the image data, and includes a first vehicle profile including at least one of first vehicle insurance details, driver details, and pre-accident image data. The accident assessment system also includes a server communicatively coupled to the first vehicle processor and configured to receive the first vehicle report. The server is configured to evaluate the captured image data to generate an accident report.

Description

[0001] introduction

[0002] The information provided in this section is for the purpose of generally presenting the context of the present disclosure. The work of the presently named inventors, to the extent it is described in this section and in aspects of the description that may not qualify as prior art at the time of filing, is neither explicitly nor implicitly admitted to be prior art against the present disclosure. Technical Field

[0003] The present disclosure relates generally to incident assessment systems. Background Art

[0004] Vehicles typically travel along a road system beside or near other vehicles. Traffic and weather patterns may affect the driving patterns of some vehicles so that sudden delays in traffic flow may result in sudden disruptions. In some cases, vehicles may collide due to sudden changes in driving patterns. In common practice, the drivers of the vehicles direct the respective vehicles to a safe stopping point and leave the vehicles to exchange information. Often, the drivers contact police personnel for support and observation of post-collision events.

[0005] After a collision, a driver may have an elevated level of stress and may forget to obtain certain documents that may be useful for insurance purposes. Additionally, the driver may disagree about who is at fault, and face-to-face interactions may result in increased stress levels. In other cases, a collision event may result in a situation where the driver or other passengers may seek medical assistance, such that exiting the vehicle may prove difficult. Typically, police officers interview surrounding witnesses while preparing a police report. However, witnesses often leave the scene of a collision event before an interview can occur. Summary of the invention

[0006] In some aspects, a vehicle accident assessment system includes at least one imager configured to capture image data and a first vehicle processor storing a first vehicle profile and configured to receive the captured image data of the first vehicle from the imager. The first vehicle processor is configured to generate a first vehicle report including the first vehicle profile and the captured image data in response to a collision event. The second vehicle processor stores a second vehicle profile and is configured to generate a second vehicle report including the second vehicle profile in response to the collision event. A server is communicatively coupled to each of the first vehicle processor and the second vehicle processor and includes a server processor configured to receive each of the first vehicle report and the second vehicle report. The server processor is configured to generate an accident report and determine a collision direction based on a comparison of the first vehicle report and the second vehicle report.

[0007] In some examples, the at least one imager may include a first imager coupled to the first vehicle and a second imager coupled to the second vehicle. The first vehicle processor may be configured to receive image data from the first imager, and the second vehicle processor may be configured to receive image data from the second imager. The server processor may be configured to compare the image data from the first imager with the image data from the second imager to determine the direction of the collision. Optionally, the first vehicle profile may include first vehicle insurance details, and the second vehicle profile may include second vehicle insurance details. The server processor may be configured to receive the first vehicle insurance details and the second vehicle insurance details, and may be configured to exchange the first vehicle insurance details with the driver of the second vehicle via the second vehicle processor, and exchange the second vehicle insurance details with the driver of the first vehicle via the first vehicle processor. In other examples, at least one imager may be disposed in an interior cabin of one of the first vehicle and the second vehicle. The first vehicle processor and the second vehicle processor may each be configured to collect data from one or more user devices in the interior cabin of the first vehicle and the interior cabin of the second vehicle, respectively.

[0008] In another aspect, an accident assessment system for a vehicle accident includes a first imager and a first vehicle processor, the first imager being configured to capture image data corresponding to a first vehicle, the first vehicle processor being communicatively coupled to the first imager and being configured to receive the captured image data. The first vehicle processor is configured to generate a first vehicle report in response to an accident captured in the image data and includes a first vehicle profile including at least one of first vehicle insurance details, driver details, and pre-accident image data. The accident assessment system also includes a server communicatively coupled to the first vehicle processor and configured to receive the first vehicle report. The server is configured to assess the captured image data to generate an accident report.

[0009] In some configurations, the accident assessment system may also include a second vehicle processor that may be communicatively coupled to the server and may include a second vehicle profile. The second vehicle processor may be configured to generate a second vehicle report in response to the accident. The second imager is configured to capture image data corresponding to the second vehicle. The server is configured to compare the image data from the second vehicle processor with the image data from the first vehicle processor to identify the direction of the collision. The server may be configured to query a third-party device for third-party data related to the accident. In another example, the server may be configured to compare the third-party data with the first vehicle report and the second vehicle report to determine the direction of the collision. The server may be configured to receive a plurality of collision reports in addition to the first vehicle report, and may be configured to identify the parties involved for each corresponding collision report including the first vehicle report. Optionally, the server may include an accident log that is configured to store accident reports and track future accident reports corresponding to vehicle profiles including the first vehicle profile.

[0010] In yet another aspect, an accident assessment system includes a first vehicle processor that stores a first vehicle profile including insurance details of a first vehicle and is configured to collect first vehicle collision data in response to a first collision event. The first vehicle processor is also configured to generate a first vehicle report including the first vehicle profile and the first vehicle collision data in response to the first collision event. The second vehicle processor stores a second vehicle profile and is configured to generate a second vehicle report including the second vehicle profile in response to the first collision event or a second collision event different from the first collision event. A server is communicatively coupled to each of the first vehicle processor and the second vehicle processor and is configured to receive each of the first vehicle report and the second vehicle report. The server is configured to generate an accident report and determine a collision direction based on a comparison of the first vehicle report and the second vehicle report.

[0011] In some examples, the first vehicle collision data may include image data from a first imager coupled to one of the front and rear of the first vehicle. The second vehicle processor may be configured to collect the second vehicle collision data from a second imager coupled to one of the front and rear of the second vehicle. The server may be configured to compare the first vehicle collision data with the second vehicle collision data to determine a collision direction. The server may be configured to determine whether the first vehicle report and the second vehicle report include a first collision event. Optionally, the server may be configured to query a third-party device for third-party data related to the collision event. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The drawings described herein are for illustrative purposes only of selected configurations and are not intended to limit the scope of the present disclosure.

[0013] Figure 1 is a schematic diagram of an accident involving a first vehicle and a second vehicle;

[0014] Figure 2 is a schematic diagram of an incident involving a first vehicle and a second vehicle in communication with a server and a third-party device according to the present disclosure;

[0015] Figure 3 is a functional block diagram of an example accident assessment system according to the present disclosure;

[0016] Figure 4 is an enlarged partial perspective view of an interior cabin of a vehicle according to the present disclosure with a driver and passengers;

[0017] Figure 5 is a functional block diagram of an example accident assessment system according to the present disclosure;

[0018] Figure 6 is an example flow chart of an incident assessment system according to the present disclosure; and

[0019] Figure 7 is an example flow chart of an accident assessment system according to the present disclosure.

[0020] Corresponding reference characters indicate corresponding parts throughout the several views of the drawings. DETAILED DESCRIPTION

[0021] Example configurations will now be described more fully with reference to the accompanying drawings. Example configurations are provided so that the present disclosure will be thorough and will fully convey the scope of the present disclosure to those of ordinary skill in the art. Specific details, such as examples of specific components, devices, and methods, are set forth to provide a thorough understanding of the configurations of the present disclosure. It will be apparent to those of ordinary skill in the art that specific details need not be employed, that example configurations may be embodied in many different forms, and that the specific details and example configurations should not be construed as limiting the scope of the present disclosure.

[0022] The terms used herein are only used for the purpose of describing specific exemplary configurations and are not intended to be limiting. As used herein, the singular articles "a", "an" and "the" may also be intended to include plural forms unless the context clearly states otherwise. The terms "comprises", "comprising", "including" and "having" are inclusive and therefore specify the presence of features, steps, operations, elements and / or parts, but do not exclude the presence or addition of one or more other features, steps, operations, elements, parts and / or groups thereof. The method steps, processes and operations described herein should not be interpreted as necessarily requiring them to be performed in the specific order discussed or shown, unless specifically identified as an execution order. Additional or alternative steps may be adopted.

[0023] When an element or layer is referred to as being "on another element or layer," "engaged to," "connected to," "attached to," or "coupled to" another element or layer, it may be directly on, directly engaged with, connected to, attached to, or coupled to another element or layer, or there may be intermediate elements or layers. Conversely, when an element is referred to as being "directly on another element or layer," "directly engaged to," "directly connected to," "directly attached to," or "directly coupled to" another element or layer, there may be no intermediate elements or layers. Other words used to describe the relationship between elements should be interpreted in a similar manner (e.g., "between" versus "directly between," "adjacent" versus "directly adjacent," etc.). As used herein, the term "and / or" includes any and all combinations of one or more associated listed items.

[0024] The terms first, second, third, etc. can be used in this article to describe various elements, components, regions, layers and / or parts. These elements, components, regions, layers and / or parts should not be limited by these terms. These terms can only be used to distinguish an element, component, region, layer or part from another region, layer or part. Unless the context clearly indicates, terms such as "first", "second" and other numerical terms do not imply order or sequence. Therefore, without departing from the teaching of the example configuration, the first element, component, region, layer or part discussed below can be referred to as the second element, component, region, layer or part.

[0025] In this application, including the definitions below, the term module may be replaced by the term circuit. The term module may refer to, be part of, or include: an application specific integrated circuit (ASIC); a digital, analog, or mixed analog / digital discrete circuit; a digital, analog, or mixed analog / digital integrated circuit; a combinational logic circuit; a field programmable gate array (FPGA); a processor (shared, dedicated, or group) that executes code; a processor (shared, dedicated, or group) that stores code executed by a memory; other suitable hardware components that provide the described functionality; or a combination of some or all of the above, such as in a system on a chip.

[0026] The term code as used above may include software, firmware and / or microcode, and may refer to a program, a routine, a function, a class and / or an object. The term shared processor includes a single processor that executes some or all codes from multiple modules. The term processor group includes a processor that executes some or all codes from one or more modules in combination with an additional processor. The term shared memory includes a single memory that stores some or all codes from multiple modules. The term memory group includes a memory that stores some or all codes from one or more modules in combination with an additional memory. The term memory may be a subset of the term computer-readable medium. The term computer-readable medium does not include transient electrical signals and electromagnetic signals propagated through the medium, and therefore can be considered to be tangible and non-transitory memory. Non-limiting examples of non-transitory memory include tangible computer-readable media, which include non-volatile memory, magnetic storage, and optical storage.

[0027] The apparatus and methods described in this application may be implemented in part or in whole by one or more computer programs executed by one or more processors. The computer program includes processor executable instructions stored on at least one non-transitory tangible computer readable medium. The computer program may also include and / or rely on stored data.

[0028] A software application (i.e., software resource) may refer to computer software that enables a computing device to perform tasks. In some examples, a software application may be referred to as an "application," "application," or "program." Example applications include, but are not limited to, system diagnostic applications, system management applications, system maintenance applications, word processing applications, spreadsheet applications, messaging applications, media streaming applications, social networking applications, and gaming applications.

[0029] Non-transitory memory can be a physical device used to temporarily or permanently store programs (e.g., sequences of instructions) or data (e.g., program state information) for use by a computing device. Non-transitory memory can be volatile and / or non-volatile addressable semiconductor memory. Examples of non-volatile memory include, but are not limited to, flash memory and read-only memory (ROM) / programmable read-only memory (PROM) / erasable programmable read-only memory (EPROM) / electrically erasable programmable read-only memory (EEPROM) (e.g., commonly used for firmware, such as bootloaders). Examples of volatile memory include, but are not limited to, random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), phase change memory (PCM), and disk or tape.

[0030] These computer programs (also referred to as programs, software, software applications, or code) include machine instructions for a programmable processor and may be implemented in high-level procedural and / or object-oriented programming languages ​​and / or assembly / machine languages. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, non-transitory computer-readable medium, apparatus, and / or device (e.g., disks, optical disks, memory, programmable logic devices (PLDs)) for providing machine instructions and / or data to a programmable processor, including machine-readable media that receive machine instructions as machine-readable signals. The term "machine-readable signal" refers to any signal for providing machine instructions and / or data to a programmable processor.

[0031] Various implementations of the systems and techniques described herein can be realized in digital electronic and / or optical circuits, integrated circuits, specially designed ASICs (application specific integrated circuits), computer hardware, firmware, software, and / or combinations thereof. These various implementations may include implementations in one or more computer programs executable and / or interpretable on a programmable system that includes at least one programmable processor, which may be special purpose or general purpose, coupled to receive data and instructions from a storage system, at least one input device, and at least one output device, and to send data and instructions to the storage system, at least one input device, and at least one output device.

[0032] The processes and logic flows described in this specification can be performed by one or more programmable processors (also referred to as data processing hardware), which execute one or more computer programs to perform functions by operating on input data and generating outputs. The processes and logic flows can also be performed by special logic circuits (e.g., FPGA (field programmable gate array) or ASIC (application-specific integrated circuit)). As an example, processors suitable for executing computer programs include both general-purpose and special-purpose microprocessors, and any one or more processors of any type of digital computer. Typically, the processor will receive instructions and data from a read-only memory or a random access memory or both. The basic elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Typically, a computer will also include one or more mass storage devices (e.g., magnetic disks, magneto-optical disks, or optical disks) for storing data, or be operably coupled to receive data from it or transmit data to it or both. However, a computer does not need to have such a device. Computer-readable media suitable for storing computer program instructions and data include all forms of nonvolatile memory, media, and memory devices, including, for example, semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD ROM and DVD-ROM disks. The processor and memory may be supplemented by, or incorporated in, special purpose logic circuitry.

[0033] To provide interaction with a user, one or more aspects of the present disclosure may be implemented on a computer having a display device (e.g., a CRT (cathode ray tube), LCD (liquid crystal display) monitor, or touch screen) for displaying information to the user and optionally a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other kinds of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; and input from the user may be received in any form, including sound, voice, or tactile input. In addition, the computer may interact with the user by sending documents to and receiving documents from a device used by the user; for example, by sending a web page to a web browser on a user's client device in response to a request received from the web browser.

[0034] refer to Figure 1-7 The accident assessment system 10 is configured to receive data regarding an accident 12 between one or more vehicles. For example, Figure 11 and 2, wherein the accident 12 is depicted as a rear-end collision. Each of the first vehicle 100 and the second vehicle 200 is equipped with a vehicle processor 102, 202, each of which is configured to generate a vehicle report 104, 204 in response to the accident 12. Each of the vehicle reports 104, 204 is transmitted to a server 300 to ultimately generate an accident report 302 for insurance companies and police personnel. Although the description herein is generally directed to an accident 12 involving the first vehicle 100 and the second vehicle 200, it is contemplated that the accident 12 may involve more than two vehicles. Additionally or alternatively, the accident 12 may involve a single vehicle and a non-vehicle object. The accident assessment system 10 may collectively define the vehicle processors 102, 202 and the server 300, which work together to generate the accident report 302. It is also contemplated that the incident assessment system 10 may also receive third-party data 400 , which may be captured or otherwise collected by one or more third-party devices 402 independent of the incident 10 , as described in further detail below.

[0035] Specific reference Figures 1 to 4 , the first vehicle 100 and the second vehicle 200 are each equipped with a respective vehicle processor 102, 202. Each vehicle processor 102, 202 includes a vehicle profile 106, 206, which includes vehicle information 108, 208. The vehicle information 108, 208 may include, but is not limited to, the model year, make, color, and trim of the respective vehicle 100, 200. The vehicle profile 106, 206 also includes insurance details 110, 210 and passenger information 112, 212 of one or more passengers 14 of the vehicle 100, 200. The vehicle profile 106, 206 may be manually input and updated by the owner-passenger 14 of the vehicle 100, 200. In some aspects, the vehicle processor 102, 202 may query the passenger information 112, 212 from the user device 404 within the respective vehicle 100, 200.

[0036] For example, the passenger information 112, 212 stored in the vehicle profile 106, 206 may also include passenger details 112a, 212a and driver details 112b, 212b. The passenger details 112a, 212a may be queried from the user device 404 in the vehicle 100, 200. The driver details 112b, 212b may also be queried from the user device 404 of the driver 14a. Additionally or alternatively, the driver 14a may manually input the driver details 112b, 212b. In some examples, the driver 14a may have a preprogrammed driver profile 114, 214, in which the driver details 112b, 212b may be stored. Considering the possibility that the passenger 14b of the vehicle 100, 200 may change compared to the driver 14a, the vehicle processor 102, 202 may query the passenger details 112a, 212a. However, in some examples, the vehicle processor 102, 202 may include one or more passenger profiles 116, 216 as part of the passenger information 112, 212. The passenger information 112, 212 may include identification information, such as the name, height, and eye color of the passenger. In some examples, the passenger information 112, 212 may include a license associated with each respective passenger, wherein the license of the driver 14a is stored in the driver profile 114, 214.

[0037] Each vehicle 100, 200 may also include a monitoring system 120, 220 in communication with the vehicle processor 102, 202. The monitoring system 120, 220 may include at least one imager 122, 222 disposed within an interior cabin 124, 224 of the vehicle 100, 200. Figure 4 As shown, a plurality of imagers 122, 222 are disposed within the interior cabin 124, 224. In addition, at least one imager 122, 222 may be used to collectively refer to and include a first imager 122 of the first vehicle 100 and a second imager 222 of the second vehicle 200. The imagers 122, 222 may be disposed within the interior cabin 124, 224 of the vehicles 100, 200 to capture in-cabin image data 126, 226. The image data 126, 226 may include the location of the passengers 14 within the vehicles 100, 200. For example, the imagers 122, 222 may capture the location of the driver 14a and any passengers 14b within the vehicles 100, 200.

[0038] The vehicle processor 102, 202 may match the in-cabin image data 126, 226 with the driver details 112, 212. The vehicle processor 102, 202 may identify whether the in-cabin image data 126, 226 of the driver 14a corresponds to the driver details 112, 212 stored in the vehicle processor 102, 202. In some examples, the vehicle processor 102, 202 may include any detected inconsistencies between the in-cabin image data 126, 226 and the driver details 112, 212 in the vehicle report 104, 204. The vehicle processor 102, 202 may also utilize the in-cabin image data 126, 226 to evaluate possible in-cabin events that may be related to the accident 12 or have preceded the accident 12. If the vehicle processor 102, 202 determines that the in-cabin event may be related to the accident 12, then the vehicle processor 102, 202 may include the in-cabin event in the vehicle report 104, 204.

[0039] The imagers 122, 222 may additionally or alternatively be disposed on the exterior of the vehicle 100, 200 at the front 128, 228 and / or rear 130, 230 of the vehicle 100, 200. The imagers 122, 222 on the exterior of the vehicle 100, 200 are configured to capture exterior image data 132, 232. It is contemplated that the exterior image data 132, 232 may include video data. Video data may be collected during operation of the vehicle 100, 200 and / or when the vehicle 100, 200 is stationary or otherwise not in current operation. For example, when the vehicle 100, 200 is turned off or otherwise idle, the exterior imagers 122, 222 may capture exterior image data 132, 232. Additionally, the exterior imagers 122, 222 may help capture surrounding traffic patterns, including potential accidents that may or may not involve the vehicle 100, 200.

[0040] Further references Figures 1 to 4 , the imagers 122, 222 within the interior cabin 124, 224 are configured to capture pre-accident image data 134, 234, which may be incorporated as part of the vehicle profile 106, 206. The pre-accident image data 134, 234 may also include exterior images of the vehicle 100, 200, which may be uploaded or otherwise provided by the owner of the vehicle 100, 200 prior to the accident 12 as a reference point for the vehicle 100, 200. The pre-event image data 134, 234 may be used by the server 300 to evaluate the event 12, as described below, and any potential damage to the vehicle 100, 200.

[0041] In some examples, the vehicle processor 102, 202 can communicate with nearby vehicle processors to exchange vehicle profiles 106, 206 in response to the incident 12. For example, the first vehicle processor 102 can send the first vehicle profile 106 to the second vehicle processor 202 in response to the incident 12. In some examples, the vehicle processor 102, 202 can query all vehicles within a predetermined radius 16 of the incident 12. The predetermined radius 16 can be stored in the vehicle processor 102, 202 and can be defined around the perimeter of the vehicle 100, 200. It is contemplated that while the predetermined radius 16 captures nearby vehicles, the predetermined radius 16 is designed to minimize the number of vehicle profiles evaluated by the vehicle processor 102, 202 to help detect one or more vehicles involved in the incident 12.

[0042] As described above, the vehicle processor 102, 202 may also query a user device 404 within the interior cabin 124, 224 of the vehicle 100, 200. For example, the user device 404 may have captured image data related to the accident 12 and / or may provide the vehicle processor 102, 202 with context of passenger behavior before, during, and / or after the accident 12. The data 406 collected from the user device 404 may be compiled along with the pre-accident image data 134, 234 and the vehicle profile 106, 206 as part of a vehicle report 104, 204 generated by the vehicle processor 102, 202.

[0043] Further references Figure 1-4 , the monitoring system 120 may also include a sensor array 140, 240 including at least one of a proximity sensor 142, 242 and a capacitive sensor 144, 244. The proximity sensor 142, 242 is configured to detect an object, such as a surrounding vehicle near or in proximity to the vehicle 100, 200. It is contemplated that the proximity sensor 142, 242 is configured with a detection range 146, 246 such that when an object (i.e., a vehicle) is within the detection range 146, 246, the proximity sensor 142, 242 records proximity data.

[0044] The capacitive sensors 144 , 244 are configured to detect contact between the vehicle 100 , 200 and an object. Figure 1The illustrated example of depicts a collision event 18 between a first vehicle 100 and a second vehicle 200. One or both of the vehicles 100, 200 may be equipped with a capacitive sensor 144, 244 to detect the collision event 18. It is contemplated that the vehicle processor 102, 202 may record a timestamp 150, 250 associated with the collision event 18 detected by the capacitive sensor 144, 244. The data corresponding to the collision event 18 collected by the vehicle processor 102, 202 from the sensor array 140, 240 may be referred to as collision data 152, 252.

[0045] refer to Figures 2 to 5 The vehicle processor 102, 202 is configured to generate a vehicle report 104, 204 in response to an incident I2 that may be detected by the monitoring system 120, 220. The vehicle report 104, 204 is generated by the vehicle processor 102, 202 that collects the collision data 152, 252 from the monitoring system 120, 220. Although the collision data 152, 252 is described above with respect to the sensor array 140, 240, it is also contemplated that the collision data 152, 252 may include in-cabin image data 126, 226 in addition to the external image data 132, 232.

[0046] according to Figure 1 , the external image data 132 of the first vehicle 100 may depict the front portion 228 of the second vehicle 200 contacting the rear portion 130 of the first vehicle 100. The first vehicle processor 102 may collect the external image data 132 depicting the contact between the first vehicle 100 and the second vehicle 200 and include the external image data 132 as part of the first vehicle report 104. It is also contemplated that a series of images of the external image data 132 may be utilized together by the vehicle processors 102, 202 to depict a series of events associated with the accident 12.

[0047] The second vehicle processor 202 is also configured to collect second vehicle collision data 252 from the perspective of the second vehicle 200. As described in detail below, it is contemplated that the server 300 is configured to identify whether the first collision data 152 matches the second vehicle collision data 252. If the first vehicle collision data 152 is inconsistent with the second vehicle collision data 252, the server 300 may determine that the collision event 18 of the first vehicle 100 is different from the collision event 18 of the second vehicle 200. Inconsistent collision data 152, 252 may occur when multiple accidents 12 occur in a local area and / or within a predetermined radius 16, such that multiple vehicle reports 104, 204 are sent to the server 300 even when the collision event 18 is the result of a separate accident 12. The server 300 is configured to identify and separate unrelated accidents 12, and generate an accident report 302 in response to the determination of the parties involved.

[0048] In some examples, the vehicle processor 102, 202 can utilize the collision data 152, 252 to identify a collision direction 154, 254. As described below, the collision direction 154, 254 determined by each of the vehicle processors 102, 202 can be evaluated by the server 300 to determine the collision direction 20 used in the accident report 302. Although both the vehicle processors 102, 202 can identify the collision direction 154, 254, it is contemplated that if the collision events 18 of the vehicles 100, 200 are unrelated, the identified collision directions 154, 254 may be inconsistent. Therefore, the server processor 304 discussed below is configured to identify whether the collision event 18 of the first vehicle 100 matches the collision event 18 of the second vehicle 200 by at least partially comparing the identified collision directions 154, 254.

[0049] Further references Figure 2-5 , the server 300 is equipped with a server processor 304 and is configured as a cloud-based data system. The server 300 communicates with the vehicles 100, 200 via wireless communications, including but not limited to Bluetooth, ultra-wideband, cellular networks, or any other feasible wireless communication network. It is also contemplated that the first vehicle processor 102 and the second vehicle processor 202 can use similar wireless communications to transmit the corresponding vehicle profiles 106, 206. The server 300 is configured to receive and send data between the vehicle processors 102, 202 and the third-party processor 408 of the third-party device 402. For example, the first vehicle profile 106 and the second vehicle profile 206 are shared with the server 300 via wireless communications. Although it is expected that the vehicle processors 102, 202 can directly exchange the corresponding vehicle profiles 106, 206, it is also expected that the server 300 can be used to exchange vehicle profiles 106, 206.

[0050] As described above, the server 300 receives the vehicle reports 104, 204 from the corresponding vehicle processors 102, 202, and generates the accident report 302 via the server processor 304, as described below. As described herein, the server processor 304 performs operations on the server 300, so that the operations described as being performed by the server 300 can be understood to be performed by the server processor 304 at the same time, and vice versa. The accident report 302 generated by the server 300 can be used by official personnel to evaluate the accident 12 independently of the passengers involved. For example, once the server processor 304 generates the accident report 302, the accident report 302 is sent to the relevant insurance companies and police personnel for reporting. The server processor 304 may also include an accident log 306, which is configured to track and monitor the reported accidents 12 and store the accident reports 302 and track future accident reports 302 corresponding to the vehicle profile. For example, after the server processor 304 generates the accident report 302, the vehicles 100, 200 involved can be recorded in the accident log 306 stored on the server processor 304. If one or both of the vehicles 100 , 200 are already registered on the accident log 306 , the accident event 308 will be added to the accident log 306 associated with the respective vehicle 100 , 200 .

[0051] The accident log 306 may additionally or alternatively be configured to record the location 310 of the accident 12. By recording the accident location 310, the server 300 may determine or otherwise identify the location 310 where the accident 12 may occur frequently. Thus, the accident assessment system 10 may advantageously assist officials in assessing locations with high accident rates. The data compiled from the accident log 306 may help determine various adjustments and / or potential revisions to minimize future accidents at the identified locations.

[0052] Still reference Figure 2-5 And as described above, the server 300 may also query one or more third-party devices 402 to collect third-party data 400 stored in a corresponding third-party processor 408. In some examples, the third party or third-party device 402 may include nearby vehicles, buildings, and other public or private monitoring systems. In some aspects, the third-party device 402 receives a notification from the server 300 indicating that the accident 12 occurred nearby and requests the third-party data 400 from the corresponding third-party processor 408. As described below, the server 300 can utilize the collected third-party data 400 in conjunction with the vehicle report 104, 204 from the corresponding vehicle processor 102, 202 to generate an accident report 302.

[0053] For example, the server 300 may first compare the first vehicle report 104 with the second vehicle report 204 and identify whether the first vehicle 100 and the second vehicle 200 were involved in the same accident 12. The server 300 may evaluate the timestamps 150, 250 of the accident 12 recorded by each of the vehicle processors 102, 202. The server 300 also evaluates whether the location 310 of the accident 12 matches between the first vehicle report 104 and the second vehicle report 204. In addition, the server 300 evaluates the collision data 152, 252 included in the two vehicle reports 104, 204. The server 300 may determine the collision direction 20 based on the collision data 152, 252. Although the server processor 304 is configured to compare the identified collision directions 154, 254 from each of the vehicle processors 102, 202, it is contemplated that the server processor 304 may independently determine the collision direction 20 based on the collision data 152, 252. The collision direction 20 is defined as the transfer of momentum from one vehicle 200 to another vehicle 100. For example, Figure 2 The collision direction 20 shown in FIG. 1 is from the second vehicle 200 to the first vehicle 100. Once the server processor 304 has evaluated the collision data 152, 252 and determined the collision direction 20, the server processor 304 may compare the collision direction 20 to the identified collision directions 154, 254.

[0054] If the server 300 determines that the collision direction 20 is consistent with the identified collision direction 154, 254, the server 300 can compare the external image data 132, 232. In some cases, the server processor 304 compares the image data 132 from the first imager 122 with the image data 232 from the second imager 222 to determine the collision direction 20. All data collected by the server 300 from the vehicle processor 102, 202 can be compared with the third party data 400 to further evaluate the accident 12.

[0055] Ultimately, the server 300 may determine that the vehicles 100, 200 were involved in the same accident 12, and the corresponding vehicle profiles 106, 206 may be exchanged between the vehicle processors 102, 202. If the server 300 determines that the vehicles 100, 200 are involved, the server 300 may generate an accident report 302 for and including both vehicle profiles 106, 206. In some examples, the server processor 304 is configured to receive the first vehicle insurance details 110 and the second vehicle insurance details 210, and is configured to exchange the first vehicle insurance details 110 with the driver 14a of the second vehicle 200 via the second vehicle processor 202. The server processor 304 may also exchange the second vehicle insurance details 210 with the driver 14a of the first vehicle 100 via the first vehicle processor 102. Alternatively, as described above, the vehicle profiles 106, 206 may be exchanged directly between the vehicle processors 102, 202 prior to being determined by the server 300.

[0056] In either aspect, the passengers 14 of the first vehicle 100 and the second vehicle 200 may obtain the vehicle profile 106, 206 of the other of the first vehicle 100 and the second vehicle 200 without face-to-face interaction. For example, the vehicle profile 106, 206 may be displayed on an infotainment device of the vehicle 100, 200 and / or may be sent by the respective receiving vehicle processor 102, 202 to the user device 404 of the driver 14a. In some accidents 12, it may be advantageous to minimize the interaction between the passengers 14 and / or the movement of the passengers 14 after the accident 12. Wireless communication of the vehicle profile 106, 206 facilitates the transfer of vehicle insurance details 110, 210 and passenger information 112, 212 with minimal interaction between the passengers 14.

[0057] Further references Figure 2-5, the collision event 18 is included as part of the accident report 302 generated by the server processor 304. As described above, the accident report 302 may also include external image data 132, 232, in-cabin image data 126, 226, and pre-accident image data 134, 234 from each of the vehicle reports 104, 204. The server processor 304 is configured to analyze the external image data 132, 232 in determining the collision direction 20, and may also identify the collision time. The server processor 304 may also compare the first collision data 152 collected from the first sensor array 140 with the second collision data 252 collected from the second sensor array 240 to determine, for example, when the second vehicle 200 is approaching the first vehicle 100 and is within the range of the first proximity sensor 142. The collision data 152, 252 associated with the capacitive sensors 144, 244 is used to determine the collision time 24. In some examples, the server processor 304 may compare the timestamps 150 , 250 recorded by each of the vehicle processors 102 , 202 to the determined collision time 24 and record any differences as part of the accident report 302 .

[0058] The server processor 304 may also receive a plurality of collision reports 410 from third-party devices 402 to assess the accident 12 and determine the involvement of each of the first vehicle 100 and the second vehicle 200. In addition to determining the collision direction 20, the server processor 304 may also determine a party at fault based in part on the third-party data 400. The server processor 304 may compare the respective collision data 152, 252 from each of the first vehicle processor 102 and the second vehicle processor 202 with the third-party data 400 to confirm the collision direction 20 and assess the circumstances surrounding the accident 12.

[0059] Reference now Figure 6 and Figure 7 , sets forth an example flow chart of the operation of the vehicle accident assessment system 10. At 500, one or more vehicles 100, 200 may be in transit, and at 502, the vehicle processor 102, 202 monitors whether an accident 12 has occurred. The vehicle processor 102, 202 continues to monitor the vehicle 100, 200 during transit until an accident 12 is detected. At 504, the vehicle processor 102, 202 may transmit the vehicle profile 106, 206 to another vehicle processor 102, 202, and at 506, the vehicle processor 102, 202 queries surrounding third-party devices 402 within a predetermined radius 16 for a corresponding vehicle profile. At 508, the vehicle processor 102, 202 may also query all user devices 404 within the corresponding vehicle 100, 200.

[0060] As mentioned above, the vehicle profile 106, 206 may include the pre-accident image data 134, 234. At 710, the vehicle processor 102, 202 stores the pre-accident image data 134, 234 and may include the pre-accident image data 134, 234 in the vehicle report 104, 204. The vehicle processor 102, 202 then generates the vehicle report 104, 204 at 512 and uploads the vehicle report 104, 204 to the server 300 at 514. At 600, the server 300 receives the vehicle reports 104, 204 from the first vehicle processor 102 and the second vehicle processor 202, respectively. The server processor 304 evaluates the vehicle reports 104, 204 and determines at 602 whether the collision time 24 included in the first vehicle report 104 and the second vehicle report 204 matches the other of the first vehicle report 104 and the second vehicle report 204. If the collision time 24 in the first vehicle report 104 does not match and / or is not within the predetermined time range, the server processor 304 determines that the first vehicle report 104 and the second vehicle report 204 are not related.

[0061] If the collision times 24 of the two vehicle reports 104, 204 are consistent, then the server processor 304 evaluates the proximity of the reported incident 12 at 604. For example, the server processor 304 compares the location of the incident in the first vehicle report 104 with the location of the incident in the second vehicle report 204. If the reported incident 12 is not within the detection range 146, 246, then the server processor 304 determines that the reported incident 12 is not relevant. If the reported incident 12 is within the detection range 146, 246, then the server processor 304 determines at 606 whether the reported collision direction 154, 254 of the first vehicle report 104 and the second vehicle report 204 matches the other of the first vehicle report 104 and the second vehicle report 204. If the reported collision directions 154, 254 are inconsistent, then the server processor 304 determines that the reported incident 12 is not relevant.

[0062] If the reported collision directions 154, 254 are consistent between the vehicle reports 104, 204, the server processor 304 compares the external image data 132, 232 from each of the vehicle reports 104, 204 at 608. At 610, the server processor 304 may also compare the collision data 152, 252 from the vehicle reports 104, 204 to determine whether the collision data 152, 252 supports the collision event 18 of the accident 12. If the collision data 152, 252 is consistent and supports the collision event 18, at 612, the server 300 may combine the vehicle reports 104, 204 into a single accident report 302.

[0063] Many embodiments have been described. However, it should be understood that various modifications can be made without departing from the spirit and scope of the present disclosure. Therefore, other embodiments are within the scope of the appended claims.

[0064] The foregoing description is provided for the purpose of illustration and description. It is not intended to be exhaustive or to limit the present disclosure. The individual elements or features of a particular configuration are generally not limited to that particular configuration, but are interchangeable where applicable and can be used in a selected configuration, even if not specifically shown or described. It can also be varied in many ways. Such variations should not be considered as departing from the present disclosure, and all such modifications are intended to be included within the scope of the present disclosure.

Claims

1. An accident assessment system for a vehicle accident, the accident assessment system comprising: a first imager configured to capture image data corresponding to a first vehicle; a first vehicle processor communicatively coupled to the first imager and configured to receive the captured image data and generate a first vehicle report in response to an accident captured in the image data, the first vehicle processor comprising a first vehicle profile including at least one of first vehicle insurance details, driver details, and pre-accident image data; as well as A server is communicatively coupled to the first vehicle processor and is configured to receive the first vehicle report and evaluate the captured image data to generate an accident report.

2. The accident assessment system of claim 1, further comprising a second vehicle processor communicatively coupled to the server and comprising a second vehicle profile, the second vehicle processor being configured to generate a second vehicle report in response to the accident. 3 . The accident assessment system of claim 2 , further comprising a second imager configured to capture image data corresponding to a second vehicle.

4. The accident assessment system according to claim 3, wherein: The server is configured to compare image data from the first imager with image data from the second imager to determine a collision direction.

5. The accident assessment system according to claim 2, wherein: The server is configured to query a third-party device for third-party data related to the accident.

6. The accident assessment system according to claim 5, wherein: The server is configured to compare the third party data with the first vehicle report and the second vehicle report to determine a collision direction.

7. The accident assessment system according to claim 3, wherein: The first vehicle profile includes first vehicle insurance details and the second vehicle profile includes second vehicle insurance details.

8. The accident assessment system according to claim 7, wherein: The server is configured to receive the first vehicle insurance details and the second vehicle insurance details and to exchange the first vehicle insurance details with a driver of a second vehicle via the second vehicle processor and to exchange the second vehicle insurance details with the driver of the first vehicle via the first vehicle processor.

9. The accident assessment system according to claim 1, wherein: The server is configured to receive a plurality of collision reports in addition to the first vehicle report and is configured to identify involved parties for each respective collision report including the first vehicle report.

10. The accident assessment system according to claim 1, wherein: The server includes an accident log configured to store the accident report and track future accident reports corresponding to vehicle profiles including the first vehicle profile.

Images