The present invention relates to determining vehicle operational status and more specifically to determining when a vehicle has been involved in an accident.
A Global Positioning System (GPS) is a space-based global navigation satellite system that utilizes a network of geo-synchronous satellites that can be utilized by a GPS receiver to determine its location. Many telematics systems incorporate a Global Positioning System (GPS) receiver that can be used to obtain the location of a vehicle at a certain measured time. Using the signals received by the GPS receiver, the heading information of the vehicle can be determined. A GPS receiver can determine velocity information in a variety of ways including, but not limited to, measuring the Doppler shift of the received signals and by comparing the location of a vehicle at a plurality of measured times. The acceleration of the vehicle can be determined as the change in speed divided by the time between the measurements. A GPS receiver's ability to determine acceleration can be limited due to the dependence of the measurement upon factors such as, but not limited to, reception and satellite availability. In addition to location information, a GPS receiver can also be configured to provide time data. However, measurements determined via a GPS receiver can contain errors that affect the accuracy of the measured information. In particular, GPS signals are vulnerable to signal delays, inconsistencies of atmospheric conditions that affect the speed of the GPS signals as they pass through the Earth's atmosphere, and multipath distortions. Additionally, other factors not listed above can influence GPS signals and result in measurement errors.
Telematics is the integrated use of telecommunications and informatics. Telematics units are installed in vehicles to provide a variety of telematics functionality in the vehicle. This functionality includes, but is not limited to, emergency warning systems, navigation functionality, safety warnings, and automated driving assistance. Telematics units are also capable of recording data related to the operation of the vehicle and providing that information for analysis, whether in real-time or during a time when the vehicle is being serviced. This information can be used in a variety of applications, such as fleet tracking, shipment tracking, insurance calculations, and in vehicle management and service.
Systems and methods for crash determination in accordance with embodiments of the invention are disclosed. In one embodiment, a vehicle telematics device includes a processor and a memory connected to the processor and storing a crash determination application, wherein the processor, on reading the crash determination application, is directed to obtain sensor data from at least one sensor installed in a vehicle, calculate peak resultant data based on the sensor data, where the peak resultant data describes the acceleration of the vehicle over a first time period, generate crash score data based on the peak resultant data and a set of crash curve data for the vehicle, where the crash score data describes the likelihood that the vehicle was involved in a crash based on the characteristics of the vehicle and the sensor data, and provide the obtained sensor data when the crash score data exceeds a crash threshold to a remote server system.
In another embodiment of the invention, the at least one sensor includes an accelerometer.
In an additional embodiment of the invention, the crash curve data is based on vehicle data including a vehicle identification number associated with the vehicle.
In yet another additional embodiment of the invention, the crash curve data is dynamically determined based on vehicle data describing a weight of the vehicle.
In still another additional embodiment of the invention, the at least one sensor includes a weight sensor.
In yet still another additional embodiment of the invention, the vehicle telematics system further includes a communications interface and the vehicle telematics unit obtains the sensor data using the communications interface.
In yet another embodiment of the invention, the set of crash curve data is provided by the remote server system.
In still another embodiment of the invention, the remote server system includes a processor and a memory storing a crash analysis application and the processor of the remote server system, on reading the crash analysis application, is directed to obtain vehicle sensor data from the vehicle telematics device, obtain vehicle identification data from the vehicle telematics device, calculate resultant change data based on the obtained sensor data and the vehicle identification data, and generate crash occurred data when the resultant change data exceeds a threshold value.
In yet still another embodiment of the invention, the processor of the remote server system is further directed to provide notification data including the crash occurred data.
In yet another additional embodiment of the invention, the crash score data is generated by calculating peak resultant data based on the obtained sensor data and calculating the crash score data based on a duration of time in which the peak resultant data exceeds the crash curve data.
Still another embodiment of the invention includes a method for determining when a vehicle has been involved in a crash by obtaining sensor data from at least one sensor installed in a vehicle using a vehicle telematics device, where the vehicle telematics device includes a processor and a memory, calculating peak resultant data based on the sensor data using the vehicle telematics device, where the peak resultant data describes the acceleration of the vehicle over a first time period, generating crash score data based on the peak resultant data and a set of crash curve data for the vehicle using the vehicle telematics device, where the crash score data describes the likelihood that the vehicle was involved in a crash based on the characteristics of the vehicle and the sensor data, and providing the obtained sensor data when the crash score data exceeds a crash threshold to a remote server system using the vehicle telematics device.
In yet another additional embodiment of the invention, the at least one sensor includes an accelerometer.
In still another additional embodiment of the invention, the crash curve data is based on vehicle data including a vehicle identification number associated with the vehicle.
In yet still another additional embodiment of the invention, the crash curve data is dynamically determined based on vehicle data describing a weight of the vehicle.
In yet another embodiment of the invention, the at least one sensor includes a weight sensor.
In still another embodiment of the invention, the vehicle telematics system further includes a communications interface and the vehicle telematics unit obtains the sensor data using the communications interface.
In yet still another embodiment of the invention, the set of crash curve data is provided by the remote server system.
In yet another additional embodiment of the invention, the method further includes obtaining vehicle sensor data from the vehicle telematics device using a remote server system including a processor and a memory, obtaining vehicle identification data from the vehicle telematics device using the remote server system, calculating resultant change data based on the obtained sensor data and the vehicle identification data using the remote server system, and generating crash occurred data when the resultant change data exceeds a threshold value using the remote server system.
In still another additional embodiment of the invention, the method further includes providing notification data including the crash occurred data using the remote server system.
In yet still another additional embodiment of the invention, the crash score data is generated by calculating peak resultant data based on the obtained sensor data using the vehicle telematics device and calculating the crash score data based on a duration of time in which the peak resultant data exceeds the crash curve data using the vehicle telematics device.
Turning now to the drawings, systems and methods for determining when a vehicle has been involved in a crash in accordance with embodiments of the invention are disclosed. Many vehicles are equipped with a variety of safety systems, such as airbags and other crash-related protections. These safety systems activate when a variety of sensors installed in the car sense that a crash has occurred, thereby causing the safety system (i.e. the airbags) to deploy. The safety systems are single-vehicle devices specifically calibrated and designed for the specific make and model of vehicle in which they are installed. Each vehicle has different characteristics, such as weight and sensor installation location, which can strongly affect the sensor information that would indicate a crash and each of the safety systems are extensively tested, by both the vehicle manufacturer and the federal government, to determine the proper operation for firing the airbag. Due to the need to quickly deploy the airbags in the event of a crash, these safety systems need to determine if crash has occurred in 2-3 milliseconds as the airbags are deployed within 10-50 milliseconds of the sensors determining a crash. However, the safety systems do not record information about what was occurring at the time of the crash and, especially due to the speed required to deploy the airbag or other safety system, do not have sufficient time to analyze the information generated before and/or during the crash.
Crash determination systems in accordance with embodiments of the invention are capable of capturing data describing the operation of the vehicle before, during, and after a potential crash event. The crash determination systems can also analyze the captured data to determine if a crash has occurred. This type of analysis cannot routinely be performed using the safety systems in the vehicle as the crash has ended by the time crash detection has occurred and the computational and memory capabilities of the integrated safety systems can be a limiting factor. The post-crash analysis performed using a vehicle telematics system can discriminate between impacts (minor bumps, potholes, etc. . . . ) and actual crash events. Crash determination systems can perform a crash analysis in a variety of ways, including comparing a pre-set value against acceleration readings and by comparing the magnitude of the acceleration event against crash curve data, as appropriate to the requirements of specific embodiments of the invention. Many safety systems installed in vehicles utilize a crash curve to determine if a crash has occurred. However, these existing systems are limited in that the crash curve must be pre-set for the specific vehicle in which the safety system is installed and is highly dependent on the location in which the safety sensors are installed as described above.
Crash determination systems include vehicle telematics devices that are installed in a vehicle aftermarket. The vehicle telematics devices can be installed in a variety of locations depending on the make, model, and/or year of the vehicle and the specific installation location can vary between cars of the same make, model, and/or year. In many instances, vehicle telematics devices are installed in a location in a vehicle where data obtained from sensors installed in the vehicle, such as the airbag sensors, and/or data from a diagnostic connector for an onboard vehicle data bus, is unavailable to the vehicle telematics device. In this way, the crash determination devices provide a universal system for analyzing crash events. In several embodiments, the vehicle telematics device automatically determines crash curve data for the specific vehicle in which it is installed. Crash determination systems can also employ a two-stage analysis of the crash data. As is described in more detail below, a vehicle telematics device can obtain data during operation of the vehicle and/or perform a first stage analysis to determine if it is likely that a crash has occurred. The data can also be transmitted to a remote server system for a more detailed analysis. In this way, crash determination systems can differentiate between crash and non-crash events and provide a variety of data to dynamically determine crash curve data across many classes of vehicles.
In a variety of embodiments, the operational state of a vehicle is utilized in determining if a crash has occurred. That is, many crash determination systems in accordance with embodiments of the invention analyze crashes that occur while a vehicle is in operation, not while parked. In a number of embodiments, vehicle ignition state (i.e. the operational status of the vehicle) is ascertained by monitoring the vehicle for signs indicative of the vehicle ignition state without directly connecting to the vehicle ignition line. Information indicative of vehicle ignition state (i.e. vehicle status data) can be ascertained by observing characteristics of the vehicle including but not limited to the power supplied by the vehicle, vehicle vibration, communications on an OBD II or other vehicle data bus line, and/or vehicle position information. In many embodiments, multiple different types of information are combined to ascertain the vehicle ignition state. Systems and methods for using a vehicle telematics device added to the vehicle after the manufacture of the vehicle without a direct connection to the vehicle ignition line that can be utilized to determine ignition state information in accordance with embodiments of the invention are described in U.S. Pat. No. 8,489,271, titled “Systems and Methods for Virtual Ignition Detection” and issued Jul. 16, 2013, the disclosure of which is hereby incorporated by reference in its entirety.
In accordance with many embodiments of the invention, vehicle telematics devices are equipped with one or more sensors capable of determining the speed and/or acceleration of the vehicle. Vehicle speed can be calculated using information provided by a Global Position System (GPS) receiver by dividing the distance traveled by the GPS receiver by the time between measurements taken by the GPS receiver. In several embodiments, the GPS receiver is configured to determine velocity information using the signals received by the GPS receiver. A GPS receiver can determine velocity information in a variety of ways in accordance with embodiments of the invention, including, but not limited to, measuring the Doppler shift of the received signals. The differences in vehicle speed between measurements taken by the GPS receiver can be used to determine acceleration data for the vehicle. GPS receivers are also capable of determining the location of a vehicle and/or the heading of the vehicle utilizing the received signals. A variety of devices other than GPS receivers can be utilized in vehicles to determine information related to the vehicle, such as speed, acceleration, and heading. For example, acceleration information for a vehicle can be measured using an accelerometer, which are often installed on a vehicle or mobile device. Heading information can be determined using a compass. Vibration information can be determined using acceleration information taken using an acceleration sensor. In several embodiments, vehicle telematics systems are calibrated to accurately determine speed and/or acceleration data. Systems and methods for calibrating a 3-axis accelerometer which can be utilized to determine vibration information in accordance with a variety of embodiments of the invention is disclosed in U.S. Pat. No. 9,217,757, titled “Systems and Methods for 3-Axis Accelerometer Calibration” and issued Dec. 22, 2015, the entirety of which is hereby incorporated by reference.
The data captured by a vehicle telematics device can also be utilized to accurately determine the location at which a crash occurred. In a number of embodiments, the determination of the ignition status of a vehicle and/or the start of a trip can be utilized in a variety of ways, such as determining particular events that occur during the operation of the vehicle. Systems and methods for determining the location of events that can be utilized in accordance with embodiments of the invention are described in U.S. Patent Publication No. 2014/0111354, titled “Systems and Methods for Location Reporting of Detected Events in Vehicle Operation” and published Apr. 24, 2014, the disclosure of which is hereby incorporated by reference in its entirety.
Crash Determination Systems
Crash determination systems in accordance with embodiments of the invention can obtain a variety of data describing the status of a vehicle and determine when the vehicle has been involved in a crash. A conceptual diagram of a crash determination system in accordance with an embodiment of the invention is shown in
In a variety of embodiments, the vehicle telematics device 110 is installed in a vehicle having a vehicle data bus 122. The vehicle telematics device 110 can obtain data from any of a variety of vehicle devices connected to the vehicle data bus 122 utilizing any of a variety of techniques as appropriate to the requirements of specific applications of embodiments of the invention. Vehicle devices can include, but are not limited to, engine sensors, electronic control unit (ECU) devices, alternator sensors, vibration sensors, voltage sensors, oxygen sensors, Global Positioning System (GPS) receivers, ignition devices, weight sensors, and/or acceleration determination devices. Systems and methods for connecting to a vehicle data bus that can be utilized in accordance with embodiments of the invention are described in SAE J1978, titled “OBD II Scan Tool,” first published by SAE International of Troy, Mich. on Mar. 1, 1992 and last updated Apr. 30, 2002. Systems and methods for obtaining data from devices connected to a vehicle data bus are described in SAE J1979, titled “E/E Diagnostic Test Modes,” first published by SAE International on Dec. 1, 1991 and last updated Aug. 11, 2014. The disclosures of SAE J1978 and SAE J1979 are hereby incorporated by reference in their entirety.
The vehicle telematics device 110 can include any of a variety of sensors and/or devices, including those described above with respect to the vehicle data bus and those described in more detail below, to obtain data regarding the status of the vehicle. This data can be utilized in a variety of crash determination processes to determine if the vehicle has been involved in a crash as described in more detail below. The vehicle telematics device 110 can also communicate with any of a variety of sensors and/or devices using the I/O interface 124. The I/O interface 124 can be any connection, including wired and wireless connections, as appropriate to the requirements of specific applications of embodiments of the invention. In several embodiments, the vehicle telematics device 110 is capable of executing scripts to read data and/or perform particular processes. These scripts can be pre-loaded on the device and/or obtained from the remote server system 130, vehicle data bus 122, and/or the I/O interface 124 as appropriate to the requirements of specific applications of embodiments of the invention. The vehicle telematics device 110 can be self-powered and/or connected into the electrical system of the vehicle in which the vehicle telematics device 110 is installed. In a variety of embodiments, the vehicle telematics device is powered via the vehicle data bus 122 and/or the I/O interface 124. In many embodiments, the vehicle telematics device 110 utilizes a Global Positioning System (GPS) receiver in order to determine the location, speed, and/or acceleration of the vehicle. However, it should be noted that any location-determining techniques, such as cellular tower triangulation, wireless network geolocation techniques, and dead reckoning techniques, could be utilized as appropriate to the requirements of specific applications of embodiments of the invention.
In a variety of embodiments, the vehicle telematics device 110 and/or remote server system 130 provides a user interface allowing for visualizing and interacting with the data. In several embodiments, the vehicle telematics device 110 and/or remote server system 130 provides an interface, such as an application programming interface (API) or web service that provides some or all of the data to third-party systems for further processing. Access to the interface can be open and/or secured using any of a variety of techniques, such as by using client authorization keys, as appropriate to the requirements of specific applications of the invention.
Although a specific architecture of a crash determination system in accordance with embodiments of the invention are discussed above and illustrated in
Vehicle Telematics Devices
Vehicle telematics devices in accordance with embodiments of the invention can obtain data regarding the status of a vehicle and determine if the vehicle has been involved in a crash. A conceptual illustration of a vehicle telematics device in accordance with an embodiment of the invention is shown in
Remote server systems in accordance with embodiments of the invention can obtain data regarding the status of a vehicle and determine if the vehicle has been involved in a crash. A conceptual illustration of a remote server system in accordance with an embodiment of the invention is shown in
The processor 210 and processor 252 can be directed, by the vehicle telematics application 232 and the crash analysis application 262 respectively, to perform a variety of crash determination processes. Crash determination processes can include obtaining data from a variety of sensor devices, determining data regarding the state of the vehicle, and using the vehicle data and/or crash curve data to determine if the vehicle has been involved in a crash. A number of crash determination processes that can be performed in accordance with embodiments of the invention are described in more detail below.
Although specific architectures for vehicle telematics devices and remote server systems in accordance with embodiments of the invention are conceptually illustrated in
Crash Detection
As described above, crash determination processes can include determining if a vehicle has been involved in a crash. In several embodiments, the crash determination processes include determining an appropriate threshold value and/or crash curve to be utilized in the crash determination process. Once a threshold value and/or crash curve has been determined for the vehicle, a variety of sensor data can be utilized to calculate crash score data describing the likelihood that the vehicle has been involved in a crash. In a variety of embodiments, the crash score data is calculated by determining if and/or how long the peak resultant of the acceleration of the vehicle exceeds a threshold value as described in more detail below. If the crash score data is indicative of a potential crash, the sensor data and/or vehicle identification data can be provided to a remote server system for a second stage analysis, also described in more detail below.
In a number of embodiments, the threshold value is pre-determined and/or determined dynamically. In a variety of embodiments, the threshold value is a crash curve defining a variable threshold value based on the characteristics of the vehicle and/or the measured sensor data. The characteristics of the vehicle can be described using vehicle identification data including any of a vehicle identification number, the weight of the vehicle, the length of the vehicle, the width of the vehicle, the wheelbase of the vehicle, the height of the vehicle, weight map data describing the distribution of weight throughout the vehicle, location data, and any other data as appropriate to the requirements of specific applications of embodiments of the invention. The threshold value can be determined using a vehicle telematics device and/or obtained from a remote server system as appropriate to the requirements of specific embodiments of the invention.
In a variety of embodiments, the threshold value is based on the location in which the telematics unit and/or the sensor devices are installed in the vehicle. In many embodiments, the threshold value is based on the weight of the vehicle. In those embodiments where a threshold value and/or a crash curve has not been defined for a specific vehicle, the characteristics of the vehicle can be utilized to dynamically generate and/or select a threshold value and/or crash curve that is appropriate to the specific vehicle. By way of example, the weight, height, length, and wheelbase of the vehicle can be utilized to determine a class of vehicle (i.e. small/medium/large and/or sedan/coupe/SUV/tractor/trailer) and a threshold value and/or crash curve can be selected based on previously measured events for other vehicles having a similar weight, height, length, and wheelbase. In several embodiments, several threshold values and/or crash curves can be combined to generate an appropriate threshold value and/or crash curve for the specific vehicle.
In many embodiments, the distribution of weight throughout the vehicle is utilized to determine the appropriate threshold value and/or crash curve. A weight map describing the distribution of weight can be generated based on the standard weight for the vehicle (e.g. the weight of the vehicle as provided by the manufacturer) modified by the removal and/or addition of elements to the vehicle. These modifications can include, but are not limited to, the weight of the occupants of the vehicle, the weight of any equipment added to the vehicle, the weight of any equipment removed from the vehicle, and any cargo carried in the vehicle. In several embodiments, the vehicle telematics system installed in the vehicle communicates with one or more weight sensors installed throughout the vehicle to obtain the weight of the vehicle at one or more locations within the vehicle. These weight sensors can be installed anywhere as appropriate to the requirements of specific embodiments of the invention, including in the seats of the vehicle, the trunk of the vehicle, and near the wheels and/or suspension of the vehicle. The vehicle telematics unit can communicate with the weight sensors in any manner as appropriate to the requirements of specific applications of embodiments of the invention, including via wired and/or wireless communication interfaces and onboard diagnostic systems. The weight map can include a scalar value indicating the total weight of the car and/or subdivide the vehicle to two or more regions and describe the weight in each of the regions. For example, the car can be divided into a front half and a back half, into quarters (drivers front, drivers rear, passenger front, passenger rear), into thirds (hood, passenger compartment, trunk), or any other set of regions as appropriate to the requirements of specific applications of embodiments of the invention.
Turning now to
Specific processes for detecting crashes in accordance with embodiments of the invention are described above and shown with respect to
Local Crash Analysis
A variety of crash determination processes include performing a first stage analysis to determine if a vehicle has been involved in a crash. In several embodiments, the first stage analysis is performed using a vehicle telematics device installed in a vehicle. In many embodiments, the first stage analysis includes calculating peak resultant data from acceleration data obtained using acceleration sensors and comparing the peak resultant data to a crash curve for the vehicle. As described above, a variety of sensors can be utilized to obtain the sensor data utilized to perform the crash determination processes. In many embodiments, the sensors include an accelerometer capable of measuring acceleration data along a forward (x) vector and a lateral (y) vector. However, it should be noted that any number of sensors, including multiple single-vector accelerometers oriented along varying vectors, can be utilized to obtain the sensor data as appropriate to the requirements of specific applications of embodiments of the invention. The acceleration data can be utilized to calculate the peak resultant of the acceleration signals for the duration of the potential crash event. In several embodiments, the peak resultant is measured as a weight unit per mass of the vehicle along a particular vector. In a number of embodiments, the peak resultant (PeakR(xy)) for acceleration data measured in a forward (x) and lateral (y) vector can be calculated using the following equation:
PeakR(xy)=√{square root over (Xacceleration2+Yacceleration2)}
where Xacceleration is the measured acceleration along the forward vector and Yacceleration is the measured acceleration along the lateral vector.
In the event that the peak resultant exceeds a threshold value for one or more of the measured axes then a crash event can be indicated. In several embodiments, a number of acceleration samples over a period of time are used to calculate the peak resultant over the time period. When the peak resultant exceeds the threshold value for the time period a potential crash event is indicated. The threshold value can be a pre-determined value, determined dynamically based on the characteristics of the vehicle, and/or a crash curve as described above. The crash curve for the vehicle can be pre-determined and/or determined dynamically based on the characteristics of the vehicle as appropriate to the requirements of specific applications of embodiments of the invention. In several embodiments, the crash curve data is obtained from a remote server system based on the vehicle identification data provided by a vehicle telematics unit.
If the first stage analysis determines that a crash may have occurred, the vehicle sensor data and data identifying the vehicle can be utilized to perform a second stage analysis, described in more detail below. This second stage analysis can be performed using the vehicle telematics unit and/or the data can be provided to a remote server system for processing as appropriate to the requirements of specific applications of embodiments of the invention.
Turning now to
Although specific processes for local crash analysis in accordance with embodiments of the invention are described above and shown with respect to
Remote Crash Analysis
In many embodiments, crash determination processes include performing a second stage analysis to determine if a vehicle has been involved in a crash. In a number of embodiments, the second stage analysis is performed by a remote server system having the time and/or computing resources exceeding those present in a vehicle telematics device, thereby allowing more complex analyses to be performed. Vehicle sensor data can be obtained and utilized to calculate the resultant change in velocity for the vehicle. The vehicle sensor data can include acceleration data along one or more axes. In several embodiments, the sensor data can include acceleration information in both a forward (x) and lateral (y) vector. The acceleration data can be processed to calculate the resultant change in velocity along one or more vectors in accordance with embodiments of the invention. By way of example, the resultant change in velocity along a forward (x) and lateral (y) vector (RESdvXY(xy)) can be calculated by:
RESdvXY(xy)=√{square root over (∫Xacceleration2+∫Yacceleration2)}
where Xacceleration is the measured acceleration along the forward vector and Yacceleration is the measured acceleration along the lateral vector.
\The result change in velocity can be compared to the threshold data to determine if a crash has occurred. By way of example, if the resultant change in velocity is less than a threshold value then the event can be considered a non-crash, if the value is equal to or greater than a threshold value then it is considered a crash. Additionally, the characteristics of the vehicle can be provided as vehicle identification data and utilized in the crash analysis. In several embodiments, the vehicle identification data is used to select crash curve data for the specific vehicle identified from a set of crash curve data for a variety of vehicles. In a variety of embodiments, crash curve data is dynamically generated for the specific vehicle based on the vehicle identification data. In a number of embodiments, the weight of the vehicle can be utilized to determine the threshold value to determine if a crash event has occurred. Returning to the previous example, the weight of the vehicle could be utilized to recalculate the threshold value from the threshold described above. The threshold value can be any value in any units (such as meters per second or feet per second) as appropriate to the requirements of specific applications of embodiments of the invention.
In many embodiments, notification data can be generated when a crash has occurred. The notification data can be used to alert third party systems about a crash, solicit emergency services, and/or be provided to any of a variety of third-party systems as appropriate to the requirements of specific applications of embodiments of the invention. It should be noted that previously received data can be stored and utilized to refine the crash determination processes, including improving the determination of the threshold values based on the vehicle identification data and the calculation of the resultant change based on the vehicle sensor data.
Turning now to
Specific processes for remote crash analysis in accordance with embodiments of the invention are described above and shown with respect to
Although the present invention has been described in certain specific aspects, many additional modifications and variations would be apparent to those skilled in the art. In particular, any of the various processes described above can be performed in alternative sequences and/or in parallel (on the same or on different computing devices) in order to achieve similar results in a manner that is more appropriate to the requirements of a specific application. It is therefore to be understood that the present invention can be practiced otherwise than specifically described without departing from the scope and spirit of the present invention. Thus, embodiments of the present invention should be considered in all respects as illustrative and not restrictive. It will be evident to the person skilled in the art to freely combine several or all of the embodiments discussed here as deemed suitable for a specific application of the invention. Throughout this disclosure, terms like “advantageous”, “exemplary” or “preferred” indicate elements or dimensions which are particularly suitable (but not essential) to the invention or an embodiment thereof, and may be modified wherever deemed suitable by the skilled person, except where expressly required. Accordingly, the scope of the invention should be determined not by the embodiments illustrated, but by the appended claims and their equivalents.
The present application is a continuation of, and claims priority to, U.S. patent application Ser. No. 16/862,985, entitled “Systems and Methods for Crash Determination, to Jenkins et al., filed Apr. 30, 2020, which is a continuation of U.S. patent application Ser. No. 16/106,453, entitled “Systems and Methods for Crash Determination” to Jenkins et al., filed Aug. 21, 2018, which is a continuation of U.S. patent application Ser. No. 15/205,385, entitled “Systems and Methods for Crash Determination” to Jenkins et al., filed Jul. 8, 2016 and issued on Aug. 21, 2018 as U.S. Pat. No. 10,055,909, the disclosures of which are incorporated herein by reference in their entireties
Number | Name | Date | Kind |
---|---|---|---|
4497025 | Hannoyer | Jan 1985 | A |
4549277 | Brunson et al. | Oct 1985 | A |
5058020 | Matsuda | Oct 1991 | A |
5117375 | Worcester et al. | May 1992 | A |
5251161 | Gioutsos et al. | Oct 1993 | A |
5253173 | Drobny et al. | Oct 1993 | A |
5337238 | Gioutsos et al. | Aug 1994 | A |
5339242 | Reid et al. | Aug 1994 | A |
5377108 | Nishio | Dec 1994 | A |
5519613 | Gioutsos et al. | May 1996 | A |
5559699 | Gioutsos | Sep 1996 | A |
5563791 | Gioutsos et al. | Oct 1996 | A |
5587906 | Mciver et al. | Dec 1996 | A |
5588005 | Ali et al. | Dec 1996 | A |
5684701 | Breed | Nov 1997 | A |
5754115 | Woo | May 1998 | A |
5754849 | Dyer et al. | May 1998 | A |
5758301 | Saito et al. | May 1998 | A |
5767766 | Kwun | Jun 1998 | A |
5780782 | O'Dea | Jul 1998 | A |
5805460 | Greene et al. | Sep 1998 | A |
5825283 | Camhi | Oct 1998 | A |
5841201 | Tabata et al. | Nov 1998 | A |
5862511 | Croyle et al. | Jan 1999 | A |
5874675 | Edmans et al. | Feb 1999 | A |
5978722 | Takasuka et al. | Nov 1999 | A |
6029111 | Croyle | Feb 2000 | A |
6076028 | Donnelly et al. | Jun 2000 | A |
6085151 | Farmer et al. | Jul 2000 | A |
6163690 | Lilja | Dec 2000 | A |
6236921 | Mcconnell | May 2001 | B1 |
6269290 | Egami et al. | Jul 2001 | B1 |
6308134 | Croyle et al. | Oct 2001 | B1 |
6337653 | Bchler et al. | Jan 2002 | B1 |
6346876 | Flick | Feb 2002 | B1 |
6356841 | Hamrick et al. | Mar 2002 | B1 |
6363308 | Caruso et al. | Mar 2002 | B1 |
6392527 | Gilano et al. | May 2002 | B1 |
6401027 | Xu et al. | Jun 2002 | B1 |
6417802 | Diesel | Jul 2002 | B1 |
6431593 | Cooper et al. | Aug 2002 | B1 |
6438475 | Gioutsos et al. | Aug 2002 | B1 |
6532419 | Begin et al. | Mar 2003 | B1 |
6540255 | Blank et al. | Apr 2003 | B1 |
6611755 | Coffee et al. | Aug 2003 | B1 |
6737989 | Flick | May 2004 | B2 |
6756885 | Flick | Jun 2004 | B1 |
6812888 | Drury et al. | Nov 2004 | B2 |
6832140 | Fan et al. | Dec 2004 | B2 |
6850839 | Mcgibney | Feb 2005 | B1 |
6912557 | North et al. | Jun 2005 | B1 |
7015830 | Flick | Mar 2006 | B2 |
7020501 | Elliott et al. | Mar 2006 | B1 |
7050897 | Breed et al. | May 2006 | B2 |
7085637 | Breed et al. | Aug 2006 | B2 |
7110880 | Breed et al. | Sep 2006 | B2 |
7158016 | Cuddihy et al. | Jan 2007 | B2 |
7250850 | Mizutani | Jul 2007 | B2 |
7272493 | Hamrick et al. | Sep 2007 | B1 |
7286929 | Staton et al. | Oct 2007 | B2 |
7348895 | Lagassey | Mar 2008 | B2 |
7366608 | Hamrick et al. | Apr 2008 | B2 |
7460954 | Hamrick et al. | Dec 2008 | B2 |
7484756 | Le et al. | Feb 2009 | B2 |
7527288 | Breed | May 2009 | B2 |
7577525 | Hamrick et al. | Aug 2009 | B2 |
7607510 | Mun | Oct 2009 | B1 |
7643919 | Nicaise | Jan 2010 | B2 |
7660652 | Smith et al. | Feb 2010 | B2 |
7671727 | Flick | Mar 2010 | B2 |
7725218 | Hamrick et al. | May 2010 | B2 |
7765039 | Hagenbuch | Jul 2010 | B1 |
7767766 | Tilbrook | Aug 2010 | B2 |
7805231 | Cluff et al. | Sep 2010 | B2 |
7805276 | Byers et al. | Sep 2010 | B1 |
8004397 | Forrest et al. | Aug 2011 | B2 |
8010251 | Hamrick et al. | Aug 2011 | B2 |
8032278 | Flick | Oct 2011 | B2 |
8065342 | Borg et al. | Nov 2011 | B1 |
8155841 | Erb | Apr 2012 | B2 |
8330626 | Adelson | Dec 2012 | B1 |
8489271 | Hergesheimer et al. | Jul 2013 | B2 |
8635091 | Amigo et al. | Jan 2014 | B2 |
8688380 | Cawse et al. | Apr 2014 | B2 |
8749350 | Geisler et al. | Jun 2014 | B2 |
8762009 | Ehrman et al. | Jun 2014 | B2 |
8799034 | Brandmaier et al. | Aug 2014 | B1 |
8812173 | Chen et al. | Aug 2014 | B2 |
8855143 | Acampora | Oct 2014 | B1 |
8874279 | Frye et al. | Oct 2014 | B2 |
8893114 | Cooley | Nov 2014 | B1 |
8996240 | Plante | Mar 2015 | B2 |
9002538 | Hergesheimer et al. | Apr 2015 | B2 |
9171460 | Chen et al. | Oct 2015 | B2 |
9179497 | Mcconnell et al. | Nov 2015 | B1 |
9217757 | Hergesheimer et al. | Dec 2015 | B2 |
9392431 | Barfield, Jr. | Jul 2016 | B2 |
9406222 | Hergesheimer et al. | Aug 2016 | B2 |
9457754 | Christensen et al. | Oct 2016 | B1 |
9459277 | Hergesheimer et al. | Oct 2016 | B2 |
9491420 | Mimar | Nov 2016 | B2 |
9644977 | Camisa | May 2017 | B2 |
9648579 | Abhishek | May 2017 | B2 |
9650007 | Snyder et al. | May 2017 | B1 |
10055909 | Jenkins | Aug 2018 | B2 |
10102689 | Hergesheimer et al. | Oct 2018 | B2 |
10107831 | Hergesheimer et al. | Oct 2018 | B2 |
10171478 | McCauley | Jan 2019 | B2 |
10214166 | Dlagnekov | Feb 2019 | B2 |
10219117 | Hergesheimer | Feb 2019 | B2 |
10395438 | Jenkins | Aug 2019 | B2 |
10466269 | Hergesheimer et al. | Nov 2019 | B2 |
10473750 | Hergesheimer | Nov 2019 | B2 |
10599421 | Cook | Mar 2020 | B2 |
10606605 | Arora | Mar 2020 | B2 |
11206171 | Zywicki | Dec 2021 | B2 |
11472361 | Jenkins | Oct 2022 | B2 |
11570529 | Jenkins | Jan 2023 | B2 |
20020013648 | Feser et al. | Jan 2002 | A1 |
20020065045 | Kim | May 2002 | A1 |
20020100310 | Begin | Aug 2002 | A1 |
20020124166 | Lee et al. | Sep 2002 | A1 |
20020135167 | Mattes et al. | Sep 2002 | A1 |
20020188940 | Breckner et al. | Dec 2002 | A1 |
20030001368 | Breed et al. | Jan 2003 | A1 |
20030005117 | Kang et al. | Jan 2003 | A1 |
20030028766 | Gass et al. | Feb 2003 | A1 |
20030121027 | Hines | Jun 2003 | A1 |
20030151507 | Andre et al. | Aug 2003 | A1 |
20030176959 | Breed | Sep 2003 | A1 |
20030236970 | Palmer et al. | Dec 2003 | A1 |
20040036261 | Breed | Feb 2004 | A1 |
20040075539 | Savoie et al. | Apr 2004 | A1 |
20040088090 | Wee | May 2004 | A1 |
20040132500 | Rogalski et al. | Jul 2004 | A1 |
20040142659 | Oesterling | Jul 2004 | A1 |
20040155790 | Tsuji | Aug 2004 | A1 |
20040171378 | Rautila | Sep 2004 | A1 |
20040257208 | Huang et al. | Dec 2004 | A1 |
20050065711 | Dahlgren et al. | Mar 2005 | A1 |
20050071314 | Caron | Mar 2005 | A1 |
20050099289 | Arita et al. | May 2005 | A1 |
20050240343 | Schmidt et al. | Oct 2005 | A1 |
20050267947 | Patrick et al. | Dec 2005 | A1 |
20050273516 | Patrick et al. | Dec 2005 | A1 |
20050283286 | Kanda et al. | Dec 2005 | A1 |
20060022469 | Syed et al. | Feb 2006 | A1 |
20060031432 | Patrick et al. | Feb 2006 | A1 |
20060034237 | Patrick et al. | Feb 2006 | A1 |
20060041336 | Schubert et al. | Feb 2006 | A1 |
20060047459 | Underbrink et al. | Mar 2006 | A1 |
20060050953 | Farmer et al. | Mar 2006 | A1 |
20060074621 | Rachman | Apr 2006 | A1 |
20060199537 | Eisenbach | Sep 2006 | A1 |
20070027612 | Barfoot et al. | Feb 2007 | A1 |
20070038653 | Li et al. | Feb 2007 | A1 |
20070109117 | Heitzmann et al. | May 2007 | A1 |
20070229251 | Ehrman et al. | Oct 2007 | A1 |
20070257791 | Arita et al. | Nov 2007 | A1 |
20070266078 | Rittle et al. | Nov 2007 | A1 |
20070271014 | Breed | Nov 2007 | A1 |
20070299587 | Breed et al. | Dec 2007 | A1 |
20080043821 | Brockhage et al. | Feb 2008 | A1 |
20080111666 | Plante et al. | May 2008 | A1 |
20080114545 | Takaoka et al. | May 2008 | A1 |
20080128600 | Ogisu et al. | Jun 2008 | A1 |
20080150707 | Shamoto | Jun 2008 | A1 |
20080195261 | Breed | Aug 2008 | A1 |
20080202199 | Finley et al. | Aug 2008 | A1 |
20080211666 | Saidi et al. | Sep 2008 | A1 |
20080211914 | Herrera et al. | Sep 2008 | A1 |
20080275601 | Saito et al. | Nov 2008 | A1 |
20080281618 | Mermet et al. | Nov 2008 | A1 |
20090015392 | Takahashi et al. | Jan 2009 | A1 |
20090037056 | Erb | Feb 2009 | A1 |
20090077229 | Ebbs | Mar 2009 | A1 |
20090177350 | Williams et al. | Jul 2009 | A1 |
20090217163 | Jaroker | Aug 2009 | A1 |
20090217733 | Stachow et al. | Sep 2009 | A1 |
20090221320 | Walley et al. | Sep 2009 | A1 |
20090249858 | Ishikawa et al. | Oct 2009 | A1 |
20100039216 | Knight et al. | Feb 2010 | A1 |
20100039247 | Ziegler et al. | Feb 2010 | A1 |
20100039318 | Kmiecik et al. | Feb 2010 | A1 |
20100042286 | Lich | Feb 2010 | A1 |
20100097316 | Shaw et al. | Apr 2010 | A1 |
20100122246 | Gesquiere et al. | May 2010 | A1 |
20100185524 | Watkins et al. | Jul 2010 | A1 |
20100205427 | Bauer et al. | Aug 2010 | A1 |
20100231002 | Yoshioka et al. | Sep 2010 | A1 |
20100235433 | Ansari et al. | Sep 2010 | A1 |
20100241838 | Cohen et al. | Sep 2010 | A1 |
20100273422 | Garrett et al. | Oct 2010 | A1 |
20100279647 | Jacobs et al. | Nov 2010 | A1 |
20100312473 | Hoshizaki | Dec 2010 | A1 |
20100318257 | Kalinadhabhotla | Dec 2010 | A1 |
20110004444 | Farrow et al. | Jan 2011 | A1 |
20110029726 | Fujimoto | Feb 2011 | A1 |
20110053575 | Veliu et al. | Mar 2011 | A1 |
20110060496 | Nielsen et al. | Mar 2011 | A1 |
20110071971 | Parks et al. | Mar 2011 | A1 |
20110106373 | Hergesheimer et al. | May 2011 | A1 |
20110109438 | Dijkstra et al. | May 2011 | A1 |
20110130906 | Mayer | Jun 2011 | A1 |
20110153367 | Amigo et al. | Jun 2011 | A1 |
20110202225 | Willis et al. | Aug 2011 | A1 |
20110202305 | Willis et al. | Aug 2011 | A1 |
20110218710 | Trinh et al. | Sep 2011 | A1 |
20110238289 | Lehmann et al. | Sep 2011 | A1 |
20110264393 | An et al. | Oct 2011 | A1 |
20110307205 | Vassilieff | Dec 2011 | A1 |
20110320088 | Eom et al. | Dec 2011 | A1 |
20120022780 | Kulik et al. | Jan 2012 | A1 |
20120035881 | Rubin et al. | Feb 2012 | A1 |
20120041618 | Sun et al. | Feb 2012 | A1 |
20120050095 | Scherzinger et al. | Mar 2012 | A1 |
20120072078 | Oosaki | Mar 2012 | A1 |
20120116669 | Lee et al. | May 2012 | A1 |
20120146766 | Geisler et al. | Jun 2012 | A1 |
20120155389 | Mcnamee et al. | Jun 2012 | A1 |
20120158211 | Chen et al. | Jun 2012 | A1 |
20120159142 | Jibbe et al. | Jun 2012 | A1 |
20120231821 | Swanson | Sep 2012 | A1 |
20120233237 | Roa et al. | Sep 2012 | A1 |
20120233668 | Klker et al. | Sep 2012 | A1 |
20120253551 | Halimi et al. | Oct 2012 | A1 |
20120253585 | Harvie | Oct 2012 | A1 |
20120253892 | Davidson | Oct 2012 | A1 |
20120259526 | Inoue et al. | Oct 2012 | A1 |
20120303203 | Olsen et al. | Nov 2012 | A1 |
20120331181 | Govande et al. | Dec 2012 | A1 |
20130002415 | Walli et al. | Jan 2013 | A1 |
20130013907 | Marino et al. | Jan 2013 | A1 |
20130024202 | Harris et al. | Jan 2013 | A1 |
20130030811 | Olleon et al. | Jan 2013 | A1 |
20130038439 | Saito | Feb 2013 | A1 |
20130073142 | Hergesheimer et al. | Mar 2013 | A1 |
20130095841 | Quimby et al. | Apr 2013 | A1 |
20130148554 | Chen | Jun 2013 | A1 |
20130182693 | Sperling et al. | Jul 2013 | A1 |
20130204572 | Sato | Aug 2013 | A1 |
20130244210 | Nath et al. | Sep 2013 | A1 |
20130249713 | Adelson | Sep 2013 | A1 |
20130275001 | Hergesheimer et al. | Oct 2013 | A1 |
20130288659 | Hrabak et al. | Oct 2013 | A1 |
20130297137 | Fushiki et al. | Nov 2013 | A1 |
20130302756 | Takeuchi et al. | Nov 2013 | A1 |
20130320654 | Clark et al. | Dec 2013 | A1 |
20130338855 | Mason et al. | Dec 2013 | A1 |
20140069837 | Naruishi et al. | Mar 2014 | A1 |
20140074315 | Frye et al. | Mar 2014 | A1 |
20140074353 | Lee et al. | Mar 2014 | A1 |
20140075197 | Alrabady et al. | Mar 2014 | A1 |
20140094210 | Gellens et al. | Apr 2014 | A1 |
20140095211 | Gloerstad et al. | Apr 2014 | A1 |
20140111354 | Hergesheimer et al. | Apr 2014 | A1 |
20140118132 | Braunberger et al. | May 2014 | A1 |
20140142886 | Hergesheimer et al. | May 2014 | A1 |
20140143940 | Iuliano et al. | May 2014 | A1 |
20140149145 | Peng et al. | May 2014 | A1 |
20140173581 | Grinberg et al. | Jun 2014 | A1 |
20140180529 | Simon | Jun 2014 | A1 |
20140189335 | Liu et al. | Jul 2014 | A1 |
20140236518 | Hergesheimer et al. | Aug 2014 | A1 |
20140236519 | Hergesheimer et al. | Aug 2014 | A1 |
20140237463 | Sriram et al. | Aug 2014 | A1 |
20140300739 | Mimar | Oct 2014 | A1 |
20140303836 | Phelan | Oct 2014 | A1 |
20140309843 | Chen et al. | Oct 2014 | A1 |
20140357295 | Skomra et al. | Dec 2014 | A1 |
20140358394 | Picciotti | Dec 2014 | A1 |
20140379208 | Mcquade et al. | Dec 2014 | A1 |
20150015385 | Tomita et al. | Jan 2015 | A1 |
20150051796 | Levy | Feb 2015 | A1 |
20150105099 | Luo et al. | Apr 2015 | A1 |
20150149218 | Bayley et al. | May 2015 | A1 |
20150161391 | Johnsen et al. | Jun 2015 | A1 |
20150248731 | Fernandes et al. | Sep 2015 | A1 |
20150268059 | Borghesani | Sep 2015 | A1 |
20150271271 | Bullotta et al. | Sep 2015 | A1 |
20150271299 | Bullotta et al. | Sep 2015 | A1 |
20150339241 | Warner et al. | Nov 2015 | A1 |
20160094964 | Barfield, Jr. et al. | Mar 2016 | A1 |
20160104123 | Viswanath et al. | Apr 2016 | A1 |
20160133130 | Grimm et al. | May 2016 | A1 |
20160146615 | Abhishek | May 2016 | A1 |
20160147523 | Stauffer et al. | May 2016 | A1 |
20160162284 | Meng et al. | Jun 2016 | A1 |
20160173281 | White et al. | Jun 2016 | A1 |
20160328228 | Baptist et al. | Nov 2016 | A1 |
20160335813 | Hergesheimer et al. | Nov 2016 | A1 |
20160341559 | Camisa | Nov 2016 | A1 |
20160362075 | Dlagnekov | Dec 2016 | A1 |
20160364230 | Moeller et al. | Dec 2016 | A1 |
20170017766 | Giraud | Jan 2017 | A1 |
20170023610 | Hergesheimer et al. | Jan 2017 | A1 |
20170075835 | Langer | Mar 2017 | A1 |
20170147331 | Liem et al. | May 2017 | A1 |
20170220404 | Polar Seminario | Aug 2017 | A1 |
20170236339 | Camisa | Aug 2017 | A1 |
20170242678 | Sangameswaran et al. | Aug 2017 | A1 |
20170277530 | Adams et al. | Sep 2017 | A1 |
20170308705 | Karaginides et al. | Oct 2017 | A1 |
20180012429 | Jenkins et al. | Jan 2018 | A1 |
20180053354 | Jenkins et al. | Feb 2018 | A1 |
20180088963 | Arora et al. | Mar 2018 | A1 |
20180103355 | Hergesheimer et al. | Apr 2018 | A1 |
20180145991 | Mccauley et al. | May 2018 | A1 |
20180164401 | Hergesheimer | Jun 2018 | A1 |
20190018669 | Cook et al. | Jan 2019 | A1 |
20190140886 | Zywicki et al. | May 2019 | A1 |
20190141156 | Srinivasulu | May 2019 | A1 |
20190184918 | Dlagnekov | Jun 2019 | A1 |
20190281428 | Hergesheimer et al. | Sep 2019 | A1 |
Entry |
---|
European Search Report in Related Patent Application EP 17824833.2-1215, dated Apr. 15, 2021, 7 pages. |
Number | Date | Country | |
---|---|---|---|
20230269504 A1 | Aug 2023 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16862985 | Apr 2020 | US |
Child | 18104171 | US | |
Parent | 16106453 | Aug 2018 | US |
Child | 16862985 | US | |
Parent | 15205385 | Jul 2016 | US |
Child | 16106453 | US |