Method and system for optimizing vehicle event processes

Abstract

In various embodiments, methods and systems for processing data related to a vehicle event of a vehicle are provided. According to an example embodiment, vehicle sensor data is obtained from one or more vehicle sensors associated with the vehicle event. Also in example embodiments, based on the vehicle sensor data, an assessment of the vehicle event is determined via a processor, including regarding a fault or severity or both associated with the vehicle event.

Description

Technical Field

[0001] This technical field generally relates to vehicles, and more particularly to methods and systems for optimizing vehicle-related processes. Background Technology

[0002] Today, various procedures can be implemented when a vehicle incident occurs, such as assessing vehicle damage, occupant injuries, and insurance claims. However, this existing technology may not always provide the optimal handling, for example, in terms of the time required.

[0003] Therefore, it may be necessary to provide improved methods and systems for handling vehicle-related incidents, such as assessing vehicle damage, occupant needs, and insurance claims. Summary of the Invention

[0004] According to an exemplary embodiment, a method is provided for processing data related to vehicle events, including: obtaining vehicle sensor data from one or more vehicle sensors related to the vehicle event; and determining an assessment of the vehicle event via a processor based on the vehicle sensor data, including a fault or severity associated with the vehicle event, or both.

[0005] In another exemplary embodiment, the method further includes obtaining a database of previous vehicle events from a computer memory; wherein the step of determining an assessment of a vehicle event includes determining an assessment of a vehicle event based on vehicle sensor data combined with the database of previous vehicle events.

[0006] In another exemplary embodiment, the method further includes generating a database of previous vehicle events via machine learning through one or more computer processors.

[0007] In another exemplary embodiment, the method further includes taking vehicle control actions based on an assessment of vehicle events, via instructions provided by the processor.

[0008] In another exemplary embodiment, the step of obtaining vehicle sensor data includes obtaining vehicle sensor data from one or more vehicle sensors built into the vehicle; and the step of determining an evaluation includes determining the evaluation via a processor using the vehicle sensor data from the one or more vehicle sensors built into the vehicle.

[0009] In another exemplary embodiment, the method further includes notifying an insurance provider of a vehicle event and an assessment of the vehicle event via instructions provided by the processor.

[0010] In another exemplary embodiment, the step of obtaining vehicle sensor data includes: obtaining first sensor data from one or more vehicle sensors before a vehicle event; obtaining second sensor data from one or more vehicle sensors during a vehicle event; and obtaining third sensor data from one or more vehicle sensors after a vehicle event; and the step of determining an assessment of the vehicle event includes determining an assessment of the vehicle event via a processor using each of the first sensor data, the second sensor data, and the third sensor data.

[0011] In another exemplary embodiment, the step of determining the assessment of a vehicle event includes determining the cause of the vehicle event via a processor based on vehicle sensor data.

[0012] In another exemplary embodiment, the step of obtaining vehicle sensor data includes obtaining at least some of the vehicle sensor data prior to the vehicle event; and the step of determining the cause of the vehicle event is performed by the processor based on the driving behavior of the vehicle driver and based on at least some of the vehicle sensor data obtained prior to the vehicle event.

[0013] In another exemplary embodiment, the step of determining the assessment of a vehicle event includes determining an assessment of vehicle damage via a processor based on vehicle sensor data.

[0014] In another exemplary embodiment, the step of obtaining vehicle sensor data includes obtaining at least some vehicle sensor data during a vehicle incident; and, based on the impact on the vehicle, including the severity and location of the impact, the processor performs an assessment of the damage to the vehicle based on the at least some vehicle sensor data obtained during the vehicle incident.

[0015] In another exemplary embodiment, the step of determining the assessment of a vehicle incident includes determining, via a processor, an assessment of injury to one or more vehicle occupants based on vehicle sensor data.

[0016] In another exemplary embodiment, the step of obtaining vehicle sensor data includes obtaining at least some vehicle sensor data during a vehicle incident; and, based on the impact on the vehicle, including the severity and location of the impact, the processor performs an assessment of damage based on the at least some vehicle sensor data obtained during the vehicle incident.

[0017] In another exemplary embodiment, a system is provided for processing data related to vehicle events, the system including one or more vehicle sensors and a processor. The one or more vehicle sensors are configured to generate vehicle sensor data related to vehicle events. The processor is coupled to the one or more vehicle sensors and configured to at least facilitate an assessment of the vehicle event based on the vehicle sensor data, including a fault or severity associated with the vehicle event, or both.

[0018] In another exemplary embodiment, the processor is further configured to at least facilitate: obtaining a database of previous vehicle events generated via machine learning from computer memory; and determining an assessment of the vehicle events based on vehicle sensor data combined with the database of previous vehicle events.

[0019] In another exemplary embodiment, the processor is further configured to, based on an assessment of a vehicle event, at least facilitate vehicle control actions via instructions provided by the processor.

[0020] In another exemplary embodiment, the processor is further configured to at least facilitate the notification of vehicle events and assessments of vehicle events to the insurance provider via instructions provided by the processor.

[0021] In another exemplary embodiment, one or more vehicle sensors are configured to generate: first sensor data prior to a vehicle event; second sensor data during a vehicle event; and third sensor data after a vehicle event; and the processor is configured to at least facilitate the determination of an assessment of the vehicle event using each of the first sensor data, the second sensor data, and the third sensor data.

[0022] In another exemplary embodiment, the processor is configured to at least facilitate the determination of the cause of the malfunction from the vehicle event, the damage to the vehicle, and the injury to one or more occupants of the vehicle based on each of the first sensor data, the second sensor data, and the third sensor data.

[0023] In another exemplary embodiment, a vehicle is provided, including a vehicle body, one or more vehicle sensors, and a processor. The one or more vehicle sensors are integrated into the vehicle body and configured to generate vehicle sensor data relating to vehicle events. The processor is coupled to the one or more vehicle sensors and configured to at least facilitate: determining an assessment of a vehicle event based on the vehicle sensor data, including a fault or severity associated with the vehicle event, or both; and automatically taking vehicle control actions based on the assessment of the vehicle event. Attached Figure Description

[0024] The present disclosure will now be described in conjunction with the following accompanying drawings, wherein like reference numerals denote like elements, in which:

[0025] Figure 1 The present invention is a functional block diagram of a communication system according to an exemplary embodiment, the communication system including a vehicle having a control system configured to provide processing related to vehicle events, such as vehicle damage, occupant needs and insurance claims;

[0026] Figure 2 To illustrate according to an exemplary embodiment Figure 1 A flowchart illustrating the implementation process of the control and communication systems;

[0027] Figure 3 For compatibility according to exemplary embodiments Figure 1 A process diagram illustrating a method for handling vehicle-related events, such as vehicle damage, occupant needs, and insurance claims, implemented in conjunction with a control system and a communication system; and

[0028] Figure 4 To explain Figure 3 A logical block diagram illustrating the implementation of the method, which can be combined with exemplary embodiments. Figure 1 The implementation of control and communication systems. Detailed Implementation

[0029] The following detailed description is exemplary in nature and is not intended to limit this disclosure or its application and use. Furthermore, it is not intended to be bound by the foregoing background information or any theories set forth in the following detailed description.

[0030] Figure 1 This is a functional block diagram of a communication system 10 according to an exemplary embodiment. As described in further detail below, according to an exemplary embodiment, the communication system 10 includes a vehicle 12 (also referred to herein as the "main vehicle"), the vehicle 12 including a control system 11 configured to provide processing of vehicle events, such as vehicle damage, occupant needs, and insurance claims. As further described below, in various embodiments, the control system 11 includes a processor 38, a computer memory 40, sensors 72, and one or more transceivers 74 and a display component 67. In some embodiments, the control system may also include a satellite-based positioning system component (e.g., GPS) 42, and various other components.

[0031] In various embodiments, vehicle 12 includes an internal combustion engine vehicle, an electric vehicle, or a hybrid electric vehicle, and operates using a motor 17 (such as an internal combustion engine, an electric motor, and / or other motors). In some embodiments, vehicle 12 may also include one or more rechargeable energy storage systems (RESS), as well as other components.

[0032] like Figure 1 As shown, in some embodiments, user 13 also has device 15, such as a smartphone, computer and / or other electronic device 15, which can communicate with user 13 and vehicle 12, for example.

[0033] like Figure 1The depicted communication system 10 typically includes a vehicle 12, one or more wireless carrier systems 14, one or more terrestrial networks 16, and one or more remote servers 18. It should be understood that the overall architecture, setup, and operation of the illustrated system, as well as the individual components, are merely exemplary, and examples of communication systems with different configurations may be used to implement the methods disclosed herein. Therefore, the following paragraphs, which provide a brief overview of the illustrated communication system 10, are not intended to be limiting.

[0034] Vehicle 12 can be any type of mobile vehicle, such as a car, motorcycle, sedan, truck, recreational vehicle (RV), boat, airplane, agricultural equipment, etc., and is equipped with suitable hardware and software that enable it to communicate through communication system 10. For example... Figure 1 As shown, in various embodiments, vehicle hardware 20 is disposed within the body 19 of vehicle 12 and includes a telematics unit 24, a microphone 26, a speaker 28, and buttons and / or controls 30 connected to the telematics unit 24. A network connection or vehicle bus 32 is operatively coupled to the telematics unit 24. Examples of suitable network connections include Controller Area Network (CAN), System Transmission for Media (MOST), Local Interconnect Network (LIN), Ethernet, and other suitable connections, such as those conforming to known ISO (International Organization for Standardization), SAE (Institute of Automotive Engineers), and / or IEEE (Institute of Electrical and Electronics Engineers) standards and specifications, to name just a few.

[0035] The telematics unit 24 is an in-vehicle device that provides various services through its communication with a remote server 18. It typically includes an electronic processing device (processor) 38, one or more types of electronic storage 40, a cellular chipset / component 34, a wireless modem 36, a dual-mode antenna 70, and a navigation unit containing a GPS chipset / component 42. In one example, the wireless modem 36 includes computer programs and / or a set of software routines suitable for execution within the electronic processing device 38.

[0036] In various embodiments, the telematics unit 24 may be embedded / installed within the vehicle 12 during manufacturing, or may be an aftermarket accessory unit installed after the vehicle 12 is manufactured. In various embodiments, the telematics unit 24 is capable of voice and / or data communication via one or more wireless networks (e.g., wireless carrier system 14) and / or via a wireless network, thereby allowing communication with a remote server 18 and / or other vehicles and / or systems.

[0037] In various embodiments, the telematics unit 24 may establish voice and / or data channels using radio transmission and wireless carrier system 14, thereby enabling the transmission and reception of voice and data transmissions via these channels. Vehicle communication is achieved via a cellular chipset / component 34 for voice communication and a wireless modem 36 for data transmission. Any suitable encoding or modulation technique may be used in this example, including digital transmission techniques such as TDMA (Time Division Multiple Access), CDMA (Code Division Multiple Access), W-CDMA (Wideband CDMA), FDMA (Frequency Division Multiple Access), OFDMA (Orthogonal Frequency Division Multiple Access), etc. In one embodiment, a dual-mode antenna 70 serves both the GPS chipset / component 42 and the cellular chipset / component 34. In various embodiments, the telematics unit 24 utilizes cellular communications according to industry standards, such as LTE, 5G, etc. Also in various embodiments, the telematics unit 24 performs wireless networking between the vehicle 12 and one or more other network devices, for example using one or more wireless protocols, such as one or more IEEE 802.11 protocols, WiMAX, or Bluetooth.

[0038] The telematics unit 24 can provide various services to users of vehicle 12, including detecting the time of a vehicle event (including processing related to vehicle damage, occupant injury and / or needs, insurance claims, and / or other matters). In various embodiments, a vehicle "event" includes, but is not limited to, the occurrence of vehicle 12 coming into contact with or being contacted by another vehicle or object, and / or the possibility of damage to vehicle 12, the potential injury and / or need for attention of one or more occupants, and / or the potential need for one or more insurance claims. In various embodiments, the telematics unit 24, according to... Figure 3 Process 300 and Figure 2 and Figure 4 The implementation provides processing for assessing, determining, and predicting vehicle repair needs, occupant needs, and insurance claims related to vehicle incidents, as described in more detail below with reference to exemplary embodiments.

[0039] In some embodiments, the telematics unit 24 may also provide connectivity to the electronic device 15. In various embodiments, by way of example, the electronic device may include various consumer electronics / mobile devices, such as smartphones, laptops, smart wearable devices, tablets, network computers, and / or one or more other electronic devices and / or combinations thereof.

[0040] In various embodiments, one or more Short Range Wireless Connectivity (SRWC) protocols (e.g., Bluetooth / Bluetooth Low Energy or Wi-Fi) may be utilized. In various embodiments, once SRWC is established, electronic device 15 can be bound and / or identified as a network participant of telematics unit 24, for example, for current and future use. For example, in some embodiments, when electronic device 15 is subsequently within wireless range of telematics unit 24 after initial pairing, telematics unit 24 (and / or remote server 18) can confirm that electronic device 15 has been identified as having been paired or established as a network participant for communicating with and receiving services from telematics unit 24.

[0041] In various embodiments, the telematics unit 24 may also provide other services, such as, for example: turn-by-turn navigation and other navigation-related services provided with the GPS chipset / component 42; emergency assistance services; information requests from users of vehicle 12 (e.g., points of interest along the route of vehicle 12); and / or infotainment-related services, such as music, internet web pages, movies, television programs, video games, and / or other content downloaded by infotainment center 46, which may be part of the telematics unit 24 and / or operatively connected to the telematics unit 24 via vehicle bus 32 and audio bus 22; and various other types of possible services.

[0042] Regarding other electronic components used in conjunction with the telematics unit 24, the microphone 26 provides a means for the driver or other vehicle occupants to input verbal or other auditory commands and may be equipped with an embedded voice processing unit utilizing human-machine interface (HMI) technologies known in the art. Conversely, the speaker 28 provides auditory output for the vehicle occupants and may be a separate speaker specifically for the telematics unit 24 or part of the vehicle audio component 64. In either case, the microphone 26 and speaker 28 enable the vehicle hardware 20 and the remote server 18 to communicate with the occupants via audible voice. The vehicle hardware also includes one or more buttons and / or controls 30 for enabling the vehicle occupants to activate or engage one or more of the vehicle hardware 20. For example, one of the buttons and / or controls 30 may be an electronic button for initiating voice communication with the remote server 18 (whether it is a person such as advisor 58 or an automated call response system). In another example, one of the buttons and / or controls 30 may be used to activate emergency services.

[0043] Audio component 64 is operatively connected to vehicle bus 32 and audio bus 22. Audio component 64 receives analog information via audio bus 22 and presents it as sound. It also receives digital information via vehicle bus 32. Audio component 64 provides AM and FM radio, CD, DVD, and multimedia functions independent of infotainment center 46. Audio component 64 may include a speaker system, or may utilize speaker 28 via arbitration on vehicle bus 32 and / or audio bus 22. In various embodiments, audio component 64 includes radio system 65 (in some embodiments, it also includes antenna 70, amplifiers, speakers, etc.).

[0044] In various embodiments, display component 67 provides a visual display to driver 13 of vehicle 12. In various embodiments, display component 67 provides driver 13 with a visual display of various driver alerts, warnings, and / or notifications, as well as other information. For example, in some embodiments, display component 67 may include one or more visual display systems, such as a visual display screen for a vehicle navigation system, a head-up display (HUD), and / or other visual displays and / or visual projections, such as on the windshield of vehicle 12, etc. In some embodiments, this information may also be provided via an audio system, such as audio component 64.

[0045] Vehicle sensors 72, connected to various sensor interface modules 44, are operatively connected to vehicle bus 32. In various embodiments, vehicle sensors 72 are integrated within vehicle 12. In other embodiments, vehicle sensors 72 are coupled to processor 38 and provide sensor information thereto.

[0046] In various embodiments, vehicle sensor 72 includes various sensors for processing vehicle events, which are then processed by processor 38. Figure 3 Process 300 and Figure 2 and Figure 4 The sensor 72 is used in various embodiments, for example, as described in more detail below. In various embodiments, among other possible sensors, the sensor 72 includes one or more cameras, lidar sensors, radar sensors, impact sensors, speed sensors, accelerometers, weight or mass sensors, tire sensors, biosensors, voltage sensors, and input sensors.

[0047] In various embodiments, one or more cameras are used to acquire camera sensor data monitoring the driver of vehicle 12, as well as information about the environment surrounding vehicle 12 and any visual indications and / or relevant information about vehicle events. Also in various embodiments, one or more other lidar sensors, radar sensors, and / or other distance sensors are used to acquire sensor data including information about the environment surrounding vehicle 12 and any visual indications and / or information about vehicle events. In some embodiments, similar cameras, lidar sensors, radar sensors, and / or other distance sensors from other vehicles (e.g., in the vicinity of the vehicle) are also used to generate such sensor data. In some embodiments, these sensors (e.g., cameras, lidar sensors, radar sensors, and / or other distance sensors from vehicle 12 and / or one or more other vehicles in its vicinity) generate data from before the vehicle event until the vehicle event (and in some embodiments, also during and / or after the vehicle event).

[0048] In various embodiments, one or more impact sensors are configured to detect vehicle events. In various embodiments, one or more speed sensors (e.g., one or more wheel speed sensors) are configured to detect the vehicle's speed or rate and / or information for calculating speed or rate. In some embodiments, one or more accelerometers are configured to detect the acceleration of vehicle 12, including its deceleration during a vehicle event. In various embodiments, one or more weight or mass sensors are configured to detect information related to the vehicle event, such as the seating position of the occupants of vehicle 12. In various embodiments, tire sensors are configured to detect tire pressure and / or other data related to the vehicle tires, including pressure changes during a vehicle event. In some embodiments, these sensors (e.g., vehicle 12 speed sensors, accelerometers, weight or mass sensors, and / or tire sensors) generate data during a vehicle event.

[0049] In various embodiments, biosensors acquire biosensor data about the health or condition of occupants in vehicle 12, including sound detection, respiration, heart rate, etc. In various embodiments, voltage sensors are configured to measure voltage and voltage changes, including for vehicle rechargeable energy storage systems (RESS), engine control units (ECUs), and / or other vehicle systems and components, including following vehicle events. In various embodiments, input sensors are configured to receive user input from one or more occupants of vehicle 12 (e.g., in response to vehicle notifications on a touchscreen, etc.). In some embodiments, these sensors (e.g., biosensors, voltage sensors, and input sensors) generate data after a vehicle event.

[0050] In various embodiments, vehicle sensor 72 may also include any number of additional sensors, including, by way of example, gyroscopes, magnetometers, emissions detection and / or control sensors, etc. In various embodiments, exemplary sensor interface module 44 includes powertrain control, climate control, and body control, to name just a few.

[0051] In various embodiments, processor 38 controls vehicle 12, including processing vehicle events. In also various embodiments, vehicle sensor 72 obtains sensor data and additional data (e.g., from one or more other vehicles, systems, and / or entities) and uses this data to determine and take appropriate actions regarding vehicle events, such as in conjunction with exemplary embodiments. Figure 3 Process 300 and Figure 2 and Figure 4 The implementation method is described in more detail.

[0052] In various embodiments, one or more transceivers 74 are configured to send and receive information between vehicle 12 and remote server 18 and / or one or more other entities (such as information providers, repair shops, emergency service providers, insurance providers, etc.), for example using wireless system 14.

[0053] In various embodiments, the wireless carrier system 14 may be any number of cellular phone systems, satellite-based wireless systems, and / or any other suitable wireless system, such as a system for transmitting signals between vehicle hardware 20 and terrestrial network 16 (and / or, in some embodiments, a system for communicating directly with vehicle 12 and / or remote server 18). According to some examples, the wireless carrier system 14 may include and / or be coupled to one or more cellular towers 48, satellites 49, base stations, and / or mobile switching centers (MSCs) 50, as well as any other networking components required to connect the wireless carrier system 14 to the terrestrial network 16. As those skilled in the art will understand, various cellular tower / base station / MSC arrangements are possible and can be used with the wireless carrier system 14.

[0054] The terrestrial network 16 may be a conventional terrestrial telecommunications network that connects to one or more terrestrial telephones and connects the wireless carrier system 14 to a remote server 18. For example, the terrestrial network 16 may include a Public Switched Telephone Network (PSTN) and / or an Internet Protocol (IP) network, as understood by those skilled in the art. Of course, one or more segments of the terrestrial network 16 may be implemented as a standard wired network, fiber optic or other optical network, cable network, other wireless networks (such as a wireless local area network (WLAN) or a network providing broadband wireless access (BWA)), or any combination thereof.

[0055] The remote server 18 is designed to provide various system backend functions to the vehicle hardware 20, which, according to the example shown here, typically include one or more switches 52, a server 54, a database 56, a processor (and / or computer) 57, an advisor 58, and various other telecommunications / computer equipment 60. These different call center components are appropriately interconnected via a network connection or bus 62, such as the network connection or bus described above in conjunction with the vehicle hardware 20. The switch 52, which may be a dedicated small exchange (PBX) switch, routes the input signals such that voice transmissions are typically sent to the advisor 58 or an automated response system, while data transmissions are passed to a modem or other telecommunications / computer equipment 60 for demodulation and further signal processing.

[0056] As explained above, modem or other telecommunications / computer equipment 60 may include an encoder and may be connected to various devices, such as server 54 and database 56. For example, database 56 may be designed to store subscriber profile records, subscriber behavior patterns, or any other relevant subscriber information. Although the example shown has been described as being used in conjunction with a manned remote server 18, it should be understood that remote server 18 may be any central or remote facility, manned or unmanned, mobile or fixed.

[0057] Figure 2 The description based on the exemplary embodiments represents Figure 1 A process diagram illustrating the implementation process 200 of the control system 11 and communication system 10. (See reference...) Figure 2 In an exemplary embodiment, vehicle sensor data relating to vehicle events of vehicle 12 is obtained from vehicle sensors (including sensors built into the vehicle), including from vehicle 12 and one or more other vehicles 202 in its vicinity. In various embodiments, the associated data and / or determinations are provided to a remote server 18, which performs service aggregation 204 related to vehicle events.

[0058] Continue to refer to Figure 2 In various embodiments, one or more processors 57 of the remote server and / or processor 38 of the vehicle 12 are configured according to the following description. Figure 3 The process described further in 300 and Figure 2 and Figure 4 The illustrated implementation identifies vehicle events and provides an action including a service set 204 that includes various services associated with them.

[0059] like Figure 2As shown, in various embodiments, service set 204 includes management information 206 for vehicle manager 208. In various embodiments, management information 206 includes the vehicle manager's maintenance, claims, and booking status (e.g., bookings for vehicle maintenance appointments and / or car rentals).

[0060] For example Figure 2 As shown, in various embodiments, service set 204 also includes government and / or emergency information 210 from one or more government and / or emergency entities 214. In various embodiments, government and / or emergency information 210 includes information for police and / or ambulance services, as well as information on the location and context of vehicle incidents related to such emergency services. Also in various embodiments, the location and context of vehicle incidents are provided to transportation departments and / or other government and / or similar entities for purposes such as improving road design, maintaining one or more vehicle incident databases, etc.

[0061] For example Figure 2 As shown, in various embodiments, the service set 204 also includes vehicle repair information 216 from one or more repair entities 214. In various embodiments, the vehicle repair information 216 includes information about damage that the vehicle 12 may have suffered due to a vehicle incident, and information about the necessary repairs and / or replacement parts associated with it. Also in various embodiments, this information is provided to one or more vehicle details, service stations, body shops, and / or other repair entities 214 for parts and service planning, such as to facilitate streamlined and faster, more efficient repairs.

[0062] For example Figure 2 As shown, in various embodiments, service aggregation 204 also includes claims-related information 220 from one or more insurance providers 222. In various embodiments, claims information 220 includes information about faults, damages, and value estimates, for use by insurance providers 222 in assessing faults and resolving and paying claims related to vehicle incidents.

[0063] For example Figure 2 As shown, in various embodiments, the service set 204 also includes rental information 224 from one or more rental providers 226. In various embodiments, the rental information 224 includes information about the owner or user of vehicle 12 or the user's rental requirements, preferences, and / or bookings, relating to vehicle events (e.g., rentals used when vehicle 12 is being repaired, etc.).

[0064] As described above, in various embodiments, Figure 2 process 200 combination Figure 3 The process 300 is implemented as follows.

[0065] Figure 3This is a process diagram of a method or process 300 for processing vehicle-related events, such as vehicle damage, occupant needs, and insurance claims, according to an exemplary embodiment. In various embodiments, process 300 may be combined with... Figure 1 This can be implemented using the control system 11 and communication system 10, or it can be combined with the above process 200 and further described below. Figure 4 The implementation method is as follows.

[0066] like Figure 3 As shown, in various embodiments, process 300 begins at step 302. In some embodiments, when Figure 1 When the control system 11 is activated, process 300 begins. For example, in some embodiments, process 300 begins when one or more users of vehicle 12 (e.g., drivers) approach or enter vehicle 12, or turn on vehicle 12 and / or its ignition system (e.g., by turning a key, engaging a smart key, or pressing a start button, etc.), and / or when driving begins or starts. In some embodiments, when the control system 11 is activated, the steps of process 300 are executed sequentially.

[0067] In various embodiments, pre-event data is obtained (steps 304 and 305). In various embodiments, prior to the vehicle event, via... Figure 1 12 vehicles Figure 1 Various vehicle sensors 72 acquire pre-event data (step 304) (e.g., they are built into vehicle 12), and in some embodiments, also from one or more other vehicles nearby (e.g., Figure 2 Vehicle 202 (step 305) obtains pre-event data. In some embodiments, the pre-event data in steps 304 and 305 includes sensor data from one or more cameras, lidar, radar, and / or other data from vehicle 12 (step 304) and other nearby vehicles 202 (step 305), such as as described above regarding Figure 1 As described above. In various embodiments, the pre-event data in steps 304 and 305 relates to the position and operation of vehicle 12, as well as the environmental and road conditions in which vehicle 12 was operating before and until the vehicle event.

[0068] In various embodiments, event data is also obtained during a vehicle event (step 306). In various embodiments, the event data in step 306 includes data from various vehicle sensors 72 (e.g., those built into vehicle 12) of vehicle 12. For example, in some embodiments, the event data in step 306 includes sensor data from one or more impact sensors, speed sensors, accelerometers, weight or mass sensors, and tire sensors of vehicle 12 during a vehicle event, such as those combined with the above. Figure 1As described. In various embodiments, the event data in step 306 includes data related to vehicle events, including the state and needs of vehicle 12 and its occupants, including impacts to vehicle 12, vehicle 12's speed, rate and acceleration and their changes, occupant seating positions, tire pressure changes, etc. In some embodiments, this data is provided to remote server 108 via transceiver 74 according to instructions provided by processor 38.

[0069] In various embodiments, post-event data may also be obtained during a vehicle event (step 307). In various embodiments, the post-event data in step 308 includes data from various vehicle sensors 72 (e.g., those built into vehicle 12) of vehicle 12. For example, in some embodiments, the post-event data in step 307 includes sensor data from one or more biosensors, voltage sensors, and input sensors of vehicle 12 after the vehicle event, such as those combined with the above. Figure 1 As described. In various embodiments, the post-event data of step 307 includes data related to the impact of the vehicle event, including the health or condition of the occupants of vehicle 12 (e.g., including voice detection, breathing, heart rate, etc.) and voltage and voltage changes of the vehicle's rechargeable energy storage system (RESS), engine control unit (ECU), and / or other vehicle systems and components following the vehicle event. In some embodiments, this data is provided to remote server 108 via transceiver 74 according to instructions provided by processor 38.

[0070] In various embodiments, determinations are made regarding road rules and driver behavior (step 308). In various embodiments, based on the pre-event sensors obtained in steps 304 and 305, by... Figure 1 Processors 38 and / or 57 (e.g., from Figure 1 These determinations are made by the vehicle 12 and / or the remote server 108. In various embodiments, during step 308, traffic state 310 and driver / operation state 312 are determined. In various embodiments, the determination of traffic state 310 includes determination of traffic signal status, any stop / yield signs, any speed limits, etc. Also in various embodiments, the determination of driver / operation state 312 includes determination of the driver's state (including their attention), any driver responses (e.g., braking, steering, etc.), lane following status (e.g., whether vehicle 12 remains within and / or follows its lane on the road it is driving on), turn signal status of vehicle 12, etc. In some embodiments, this data is provided to the remote server 108 via transceiver 74 according to instructions provided by processor 38.

[0071] In some embodiments, road rules and driver behavior are provided to the fault model (step 314). In various embodiments, during step 314, Figure 1 The processor 57 of the remote server 108 determines one or more fault measurements of vehicle events and / or related information. Also in various embodiments, based on pre-event data from other vehicles from step 305, cross-validation regarding road rules and driver behavior from step 308 is provided in step 316. For example, in some embodiments, the fault model of step 314 may include driver behavior such as whether the driver is attentive, whether the driver complies with speed limits, traffic laws, stop or yield signs, traffic signals (e.g., traffic lights), etc. In some embodiments, Figure 1 The processor 38 of vehicle 12 may also perform one or more determinations of steps 314 and / or 316.

[0072] In various embodiments, the driving environment is determined (step 318). In various embodiments, this is based on the pre-event sensors obtained in step 304, by... Figure 1 Processors 38 and / or 57 (e.g., from Figure 1 These determinations are made by vehicle 12 and / or remote server 108. In various embodiments, during step 318, determinations are made regarding road category 319, vehicle state 320, road straightness / curvature state 322, number of vehicles 324, event type 326, and condition 328. In various embodiments, road category 319 includes the type of road, such as highway versus non-highway, paved versus unpaved, number of lanes, etc. Also in various embodiments, vehicle state 320 includes vehicle speed, vehicle mass (including mass at different occupant seats), tire pressure, etc. Also in various embodiments, straightness / curvature state 322 relates to the amount and / or degree of curvature of the road traveled by vehicle 12. Also in various embodiments, number of vehicles 324 relates to the number of vehicles involved in a vehicle event. Also in various embodiments, event type 326 relates to the type of vehicle event. In some embodiments, this data is provided to remote server 108 via transceiver 74 according to instructions provided by processor 38.

[0073] In various embodiments, the determination of the driving environment (and its related data) in step 318 is... Figure 3 This is referred to as "D1". In various embodiments, the driving context and associated data (i.e., D1) are provided to the damage model 330, which will be described in further detail below. In some embodiments, this data is provided to a remote server 108 via a transceiver 74 according to instructions provided by the processor 38.

[0074] In various embodiments, the determination of impact data is also performed (step 334). In various embodiments, based on the event sensor data obtained in step 306, by... Figure 1 Processors 38 and / or 57 (e.g., from Figure 1 These determinations are made by the vehicle 12 and / or the remote server 108. In various embodiments, during step 334, the maximum incremental velocity 335, final orientation 336, acceleration time series 338, severity estimate 340, and impact location 342 are determined. In various embodiments, the maximum incremental velocity 335 is determined as the maximum velocity change of the vehicle 12 during or as a result of the vehicle event. In various embodiments, the final orientation 336 is determined as the final orientation (including the direction the vehicle 12 is facing) after the vehicle event. In various embodiments, the acceleration time series 338 relates to the acceleration change of the vehicle 12 as a result of the vehicle event. In various embodiments, the severity estimate 340 relates to the severity of the vehicle event, such as the amount of impact and / or potential damage as a result of the vehicle event (e.g., it may be determined based on whether airbags for the driver occupant, left, right, and / or curtains deployed or nearly deployed, and / or whether, for example, pretensioners deployed for seat belts, and / or whether a vehicle rollover occurred, etc.). In various embodiments, the impact location 342 relates to one or more specific locations (e.g., front, rear, and / or side) on the vehicle 12 where an impact occurred. In some embodiments, this data is provided to a remote server 108 via transceiver 74 according to instructions provided by processor 38.

[0075] In various embodiments, the impact data in step 334 is... Figure 3 This is referred to as "D2". In various embodiments, the impact data (i.e., D2) is provided to the damage model 330, which will be described in further detail below. In some embodiments, this data is provided to a remote server 108 via a transceiver 74 according to instructions provided by the processor 38.

[0076] In various embodiments, the health status of the vehicle and occupants is determined (step 346). In various embodiments, these determinations are made by... Figure 1 Processors 38 and / or 57 (e.g., from Figure 1The vehicle 12 and / or remote server 108) make decisions based on the post-event sensors obtained in step 307. In various embodiments, during step 346, determinations are made regarding battery voltage 347, ECU voltage 348, bus activity 350, sensor health and readings 352, biometrics 352, and user input 354. In various embodiments, battery voltage 347 relates to the voltage (or changes thereof) of the energy storage system (e.g., battery) of vehicle 12 after the vehicle event. In various embodiments, ECU voltage 348 relates to the voltage (or changes thereof) of the engine control unit (ECU) of vehicle 12 after the vehicle event. In various embodiments, bus activity 350 relates to communication bus activity (e.g., including CAN / LIN / ETH bus, and including short-circuit and impedance data) after the vehicle event. In various embodiments, sensor health and readings 352 relate to the voltage (or changes thereof) of the engine control unit (ECU) of vehicle 12 after the vehicle event. Figure 1 The sensor data values ​​of sensor 72 are related to health (e.g., sensor malfunction, etc.). In various embodiments, biometrics 352 are related to biometric data (e.g., respiration, heart rate, etc.) of the occupants of vehicle 12 following a vehicle incident, and / or other internal health sensing (e.g., VOCs). In various embodiments, user input 354 includes any input provided by the driver of vehicle 12 or other users (e.g., pressing the emergency button, initiating an emergency call, etc.). In some embodiments, this data is provided to remote server 108 via transceiver 74 according to instructions provided by processor 38.

[0077] In various embodiments, the vehicle and occupant health data in step 346 are... Figure 3 This is referred to as "D3". In various embodiments, vehicle and occupant health data (i.e., D3) is provided to the damage model 330, which will be described in more detail below. In some embodiments, this data is provided to a remote server 108 via transceiver 74 according to instructions provided by processor 38.

[0078] In various embodiments, a vehicle event database is obtained (step 329). In various embodiments, the vehicle event database is stored in computer memory (e.g., ...). Figure 1 The data is stored in the memory of the remote server 108 and includes data based on previous vehicle events, including vehicle 12 and / or various other vehicles. In various embodiments, machine learning techniques are used to generate different data (e.g., including pre-event data, event data, and post-event data) from various previous vehicle events of vehicle 12 and / or any number of other vehicles for analyzing vehicle events, including the damage model for step 330.

[0079] In various embodiments, during step 330, one or more damage models are used to determine estimates of damage and / or injury to vehicle 12, other vehicles, and / or occupants caused by the vehicle incident. In various embodiments, during step 330, Figure 1 The processor of the remote server 108 determines an estimate of the damage and / or injury to vehicle 12, other vehicles, and / or occupants caused by the vehicle event based on the driving environment data (i.e., D1) from step 318, the impact data (i.e., D2) from step 334, the vehicle and occupant health data (i.e., D3) from step 346, and data from the vehicle event database from step 329. For example, in some embodiments, the damage model in step 330 takes into account the nature and severity of the impact, the location where the impact is concentrated on vehicle 12 (e.g., for the purpose of vehicle damage and to determine which occupants may be injured, etc.), various sensor readings from sensors 72 built into vehicle 12, etc. In some embodiments, Figure 1 The processor 38 of vehicle 12 can also perform one or more determinations in step 330.

[0080] In various embodiments, various vehicle actions are performed (step 359). Specifically, in various embodiments, during step 359, Figure 1 The remote server 108 performs various vehicle actions based on the fault model of step 314 and the damage model of step 330. In some embodiments, Figure 1 The processor 38 of vehicle 12 may also perform one or more actions of step 359. In some embodiments, the actions of step 359 include one or more vehicle control actions and / or other actions for processing and / or assisting with vehicle events.

[0081] like Figure 3As shown, the actions of step 359 may include one or more emergency response calls 360. In various embodiments, these may include one or more of the following, particularly: (i) notifying one or more first responders, such as police officers; (ii) notifying one or more other first responders, such as medical personnel, ambulances, and / or firefighters; (iii) notifying other legal authorities; (iv) notifying towing providers; (v) notifying one or more vehicle dealerships, service stations, repair shops, etc.; (vi) prioritizing repairs; (vii) establishing a single point of contact for the owner of vehicle 12; (viii) requesting a replacement and / or rental vehicle, etc. Also in various embodiments, the actions of step 359 may include providing one or more value estimates 362. For example, in some embodiments, the value estimate may be based on the vehicle suspension (e.g., roughness), powertrain (e.g., revolutions per minute and / or accelerator pedal engagement), and the environment surrounding vehicle 12 (e.g., weather conditions), etc. For example, in some embodiments, suspension wear (S w The International Roughness Index (IRI) with trajectory data is used to determine and estimate suspension wear caused by driving on rough roads. In some embodiments, powertrain wear (P) is determined using changes in revolutions per minute (i.e., incremental rpm) along with engine torque, pedal data, etc. w This is used to determine vehicle usage and wear on the powertrain and braking systems. In some embodiments, wiper and humidity data are also used to determine environmental wear (E). w This is used to estimate the vehicle's operating environment. In some embodiments, these variables are also used to construct a depreciation factor ("f") that can be applied to the "maximum condition" price, based on the following equation:

[0082] f = w1S w +w2P w +w3E w (Equation 1), and

[0083] Vehicle value = $_highest condition * f (Equation 2)

[0084] In some embodiments, if the damage to the vehicle (including parts plus labor costs) exceeds the value of the vehicle, the vehicle is declared a total loss.

[0085] In some embodiments, a value estimate 362 may be provided to the owner of vehicle 12 and / or government and / or legal entities, insurance companies, etc.

[0086] In various embodiments, step 359 may also include sending vehicle data and video 363. In some embodiments, the vehicle data and video may be provided to the owner of vehicle 12, and / or government and / or legal institutions, insurance companies, etc.

[0087] In various embodiments, step 359 may also include sending the driving environment data (i.e., D1) from step 318. In some embodiments, the driving environment data may be provided to the owner of vehicle 12, and / or government and / or legal institutions, insurance companies, etc.

[0088] In various embodiments, step 359 may also include sending the impact data from step 334 (i.e., D2). In some embodiments, the impact data may be provided to the owner of vehicle 12, and / or government and / or legal authorities, insurance companies, etc.

[0089] In various embodiments, step 359 may also include sending the vehicle health data from step 346 (i.e., D3). In some embodiments, the vehicle health data may be provided to the owner of vehicle 12, and / or government and / or legal institutions, insurance companies, etc.

[0090] In various embodiments, step 359 may also include providing one or more estimates 372 of the costs of parts and repairs to the vehicle as a result of the vehicle incident. In some embodiments, the estimates of parts and repair costs may be provided to the owner of vehicle 12, and / or government and / or legal entities, insurance companies, etc.

[0091] In various embodiments, step 359 may also include providing a parts list 374 for the vehicle as a result of the vehicle incident. In some embodiments, the parts list may be provided to the owner of vehicle 12, and / or government and / or legal authorities, insurance companies, etc.

[0092] In various embodiments, step 359 may also include reviewing and approving the parts list 376. In some embodiments, the review and approval are provided by an insurance company or other payer and then relayed to the owner, repair shop, and / or other entity performing the repair, etc.

[0093] In various embodiments, the process terminates at step 380.

[0094] Figure 4 According to the exemplary embodiments Figure 3 A logic block diagram of an implementation of process 300, said process may be combined with an exemplary embodiment. Figure 1 The control system 11 and communication system 10 are implemented.

[0095] like Figure 4 As shown, the event-preceding data 401 (for example, corresponding to...) Figure 3Steps 304 and 305) are used to determine the speed 402 and trajectory 403 of vehicle 12, as well as data regarding one or more targets 404(1), 404(2), ... 404(n), such as other vehicles and / or objects near vehicle 12. Similarly, Figure 4 As shown, using event data 411 (for example, corresponding to...) Figure 3 Step 306) determines the acceleration values ​​412(1), 412(2), ... 412(n) at different time points during the vehicle event. Similarly, ... Figure 4 As shown, using post-event data 421 (for example, corresponding to...) Figure 3 Step 307) determines the battery voltage value 442, vehicle sensor data 423 (e.g., biometric data, sensor health and reading data, user input, etc.) and ECU voltage data 424 after the vehicle event. Similarly, Figure 4 As shown, additional data 431 (e.g., Global Positioning System (GPS) data, other location data, vehicle identification data (e.g., VIN), other identifiers [e.g., RPO code], etc.) may also be determined). In various embodiments, various data from 401-431 above are provided to the damage assessment model 440 (i.e., corresponding to...) Figure 3 Step 330 (damage model).

[0096] like Figure 4 As shown, in various embodiments, an event database 450 is utilized. In various embodiments, the event database 450 corresponds to the event database of step 329 and is generated using machine learning based on previous vehicle events (e.g., using vehicle 12 and / or other vehicles).

[0097] In various embodiments, a probability model 460 is generated using a damage assessment model 440 and an event database 450. In various embodiments, the probability model 460 includes one or more probability frequency plots and / or other probability graphs, functions, tables, other models, etc., to assess the probabilities of various possible outcomes for a vehicle due to a vehicle event (e.g., the requirement for repair or replacement parts, related costs, etc.).

[0098] In various embodiments, the probabilistic model 460 is used to generate a vehicle repair estimate 470. In various embodiments, the repair estimate 470 includes a parts list 471 of parts that need to be repaired or replaced, the associated parts costs 472, and the associated labor costs 473.

[0099] Therefore, in various embodiments, processing methods and systems related to vehicle events are provided. In various embodiments, various types of vehicle sensor data are utilized to generate analyses of vehicle events, including fault assessments, damage assessments of the vehicle, injury assessments of occupants, and so on. In various embodiments, these assessments can be used to take various vehicle actions, including summoning medical personnel, arranging vehicle repairs and rentals, providing relevant information to government and legal agencies, and insurance companies, and so on.

[0100] It should be understood that the systems and methods may differ from those shown in the figures and described herein. For example, in various embodiments, Figure 1 The communication system, including its vehicle and control systems and other components, may differ from... Figure 1 The procedures (and / or sub-procedures) described herein and / or as described herein. It should also be understood that the procedures (and / or sub-procedures) disclosed herein may differ from those described herein and / or... Figure 3 The processes shown, and / or the steps therein, may be performed simultaneously and / or as described herein and / or Figure 3 The different execution orders shown, as well as other possible variations, are illustrated. Similarly, it should be understood that... Figure 2 and Figure 4 The implementation method can also vary in different embodiments.

[0101] While at least one example has been described in the foregoing detailed description, it should be understood that numerous variations exist. It should also be understood that the one or more examples are merely illustrative 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 one or more examples. It should be understood that various changes can be made to the function and arrangement of the elements without departing from the scope of the appended claims and their legal equivalents.

Claims

1. A method for processing data related to vehicle events, the method comprising: Obtain vehicle sensor data from one or more vehicle sensors associated with a vehicle event; Obtain an event database of previous vehicle events from computer memory; Based on vehicle sensor data, a processor determines an assessment of a vehicle event, including the fault or severity associated with the event, or both. The steps for determining the assessment of vehicle incidents include: using sensor data, and generating a damage assessment model for the vehicle caused by the vehicle incident via a processor; Based on a damage assessment model and an event database, a probabilistic model is generated via a processor. This probabilistic model evaluates the probabilities of different possible outcomes for a vehicle as a result of a vehicle event; and Based on the probability model, the processor determines the service requirements of the vehicle resulting from the vehicle events determined using the probability model, including parts and labor for repairing the vehicle. and Based on the assessment of vehicle events and service requirements using a probabilistic model, the processor automatically takes vehicle control actions.

2. The method according to claim 1, further comprising: A database of previous vehicle events is generated using one or more computer processors through machine learning.

3. The method according to claim 1, wherein: The steps for obtaining vehicle sensor data include acquiring vehicle sensor data from one or more vehicle sensors built into the vehicle; and The steps for determining the assessment include using vehicle sensor data from one or more vehicle sensors built into the vehicle via a processor.

4. The method according to claim 1, further comprising: The vehicle incident and its assessment are communicated to the insurance provider via instructions provided by the processor.

5. The method according to claim 1, wherein: The steps to obtain vehicle sensor data include: Prior to a vehicle incident, first sensor data is obtained from one or more vehicle sensors; During a vehicle incident, second sensor data is obtained from one or more vehicle sensors; and After a vehicle incident, third sensor data is obtained from one or more vehicle sensors; and The steps for determining the assessment of a vehicle incident include using each of the first sensor data, second sensor data, and third sensor data via a processor to determine the assessment of the vehicle incident.

6. The method according to claim 1, wherein: The steps for assessing a vehicle incident include: determining the cause of the malfunction via a processor based on vehicle sensor data; The steps to obtain vehicle sensor data include acquiring at least some vehicle sensor data prior to a vehicle event; and The steps to determine the cause of a vehicle incident are performed by the processor based on the driver's driving behavior and on at least some vehicle sensor data obtained prior to the incident.

7. The method according to claim 1, wherein: The steps for obtaining vehicle sensor data include acquiring at least some vehicle sensor data during a vehicle incident; and The steps for determining the assessment of a vehicle incident include, based on the impact on the vehicle, including the severity and location of the impact, and based on at least some vehicle sensor data obtained during the vehicle incident, determining an assessment of vehicle damage via a processor.

8. The method according to claim 1, wherein: The steps for obtaining vehicle sensor data include acquiring at least some vehicle sensor data during a vehicle incident; and The steps for determining the assessment of a vehicle incident include, based on the impact on the vehicle, including the severity and location of the impact, and based on at least some vehicle sensor data obtained during the vehicle incident, determining via a processor an assessment of injury to one or more occupants of the vehicle.

9. A system for processing data related to vehicle events, the system comprising: One or more vehicle sensors, the one or more vehicle sensors being configured to generate vehicle sensor data in relation to vehicle events; and A processor, which is coupled to the one or more vehicle sensors and configured to at least facilitate: Obtain an event database of previous vehicle events generated via machine learning from computer memory; An assessment of the vehicle event is determined based on the vehicle sensor data, including a fault or severity associated with the vehicle event, or both, including by means of: Using sensor data, a damage assessment model for vehicles caused by vehicle incidents is generated; Based on the damage assessment model and the event database, a probabilistic model is generated that evaluates the probability of different possible outcomes for a vehicle as a result of a vehicle event. and Based on the probability model, determine the service requirements of the vehicle caused by the vehicle events determined using the probability model, including parts and labor for repairing the vehicle; and Based on the assessment of vehicle events and service requirements using a probabilistic model, automatic vehicle control actions are taken.

Images