Abstract:
A method is provided for an aftermarket device to provide telematics service for a vehicle. The method includes accessing sensor data internal to the device and on-board diagnostic data from the vehicle, determining if one or more combinations of the sensor data and the on-board diagnostic data indicate a crash of the vehicle, and wirelessly contacting a call center or an emergency responder when at least one combination of the sensor data and the on-board diagnostic data indicates a crash of the vehicle.

Description:
FIELD OF INVENTION 
       [0001]    This invention relates to a method for verifying a vehicle has crashed and notifying a call center or emergency responders. 
       DESCRIPTION OF RELATED ART 
       [0002]    OnStar®, a wholly owned subsidiary of GM®, is a leading provider of telematics services. An OnStar® module connects an on-board vehicle computer to the OnStar® Center via cellular communications. A GM® vehicle is equipped with multiple built-in sensors, which allows the vehicle computer to capture critical real-time details in the event of a crash. The OnStar® module can provide the details to an advisor at the OnStar® Center, who can alert and pass along critical information to emergency responders. Other car manufacturers offer similar telematics systems and services. It is difficult for an independent party to offer aftermarket telematics systems and services as the telematics module needs to be intimately tied to the vehicle computer, which is often proprietary. 
       SUMMARY 
       [0003]    In one or more embodiments of the present disclosure, a method is provided for an aftermarket device to provide telematics service for a vehicle. The method includes accessing sensor data internal to the device and on-board diagnostic data from the vehicle, determining if one or more combinations of the sensor data and the on-board diagnostic data indicate a crash of the vehicle, and wirelessly contacting a call center or an emergency responder when at least one combination of the sensor data and the on-board diagnostic data indicates a crash of the vehicle. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0004]    In the drawings: 
           [0005]      FIG. 1A  illustrates an in-dash version of an aftermarket device that provides telematics service in one or more embodiments of the present disclosure; 
           [0006]      FIG. 1B  illustrates a portable version of the aftermarket device that provides telematics service in one or more embodiments of the present disclosure; 
           [0007]      FIG. 2  is a block diagram of the device of  FIG. 1A  or  1 B in one or more embodiments of the present disclosure; and 
           [0008]      FIG. 3  is a flowchart of a method for the device of  FIG. 1A  or  1 B to determine a crash and notify a call center or emergency responders in one or more embodiments of the present disclosure. 
           [0009]      FIG. 4  is a block diagram of an automobile bus interface of the device of  FIG. 2  in one or more embodiment of the present disclosure. 
       
    
    
       [0010]    Use of the same reference numbers in different figures indicates similar or identical elements. 
       DETAILED DESCRIPTION 
       [0011]      FIG. 1A  illustrates an in-dash version of aftermarket device  100  that provides telematics services for a vehicle  102  in one or more embodiments of the present disclosure. Vehicle  102  may be a car, a motorcycle, a boat, or any other vehicle. Device  100  may be a detachable head unit received in the dash of vehicle  102 .  FIG. 1B  illustrates a portable version of aftermarket device  100  that the user can carry in and out of the vehicle, similar to a global positioning satellite (GPS) receiver, in one or more embodiment of the present disclosure. 
         [0012]      FIG. 2  is a block diagram of device  100  of  FIG. 1A  or  1 B in one or more embodiments of the present disclosure. Device  100  includes a processor  202 , system memory (volatile memory)  204 , a hard disk or solid state drive (nonvolatile memory)  206 , a GPS receiver  208 , an accelerometer  210 , a gyroscope  212 , an altimeter  214 , an on-board diagnostics (OBD) interface  216  (e.g., OBD-II), and a cellular or broadband transceiver  218 . Hard disk drive  206  stores a telematics application  220 , which is loaded into system memory  204  and executed by processor  202 . 
         [0013]    Executing telematics application  220 , processor  202  monitors sensor data from within device  100  and OBD-II data from vehicle  102  to determine if a crash has occurred. Processor  202  has access to acceleration data from accelerometer  210 , orientation data from gyroscope  212 , and altitude data altimeter  214 . Processor  202  uses OBD-II interface  216  to access OBD-II data from an on-board vehicle computer  224  of vehicle  102 . The OBD-II data include vehicle speed data and engine revolution per minute (RPM) data. OBD-II interface  216  makes either a wired or a wireless connection to the vehicle computer. 
         [0014]    When a crash is detected, processor  202  uses transceiver  218  provide relevant information to a call center  226 , and an advisor contacts emergency responders for assistance. Instead of contacting a call center, processor  202  can directly contact the emergency responders  226 . The relevant information describes the vehicle&#39;s route, including the vehicle&#39;s current location, the vehicle&#39;s orientation along the route, which may indicate any rollover, and the severity of the crash. In other words, device  100  acts similar to a flight data recorder or “black box” for an aircraft. Processor  202  determines the vehicle&#39;s route using GPS receiver  208 . Processor  202  determines the vehicle&#39;s orientation from gyroscope  212 . Processor  202  determines the severity of the crash from a combination of the sensor data and the OBD-II data. Processor  202  records the vehicle&#39;s route, the vehicle&#39;s orientation, and the severity of the crash in hard disk or solid state drive  206 . 
         [0015]      FIG. 3  is a flowchart of a method  300  for device  100  of  FIG. 1A  or  1 B to detect a crash and alert a call center or emergency responders in one or more embodiments of the present disclosure. Method  300  may be implemented by processor  202  executing telematics application  220 . Although the blocks are illustrated in a sequential order, these blocks may also be performed in parallel, and/or in a different order than those described herein. Also, the various blocks may be combined into fewer blocks, divided into additional blocks, and/or eliminated based upon the desired implementation. Method  300  may begin in block  302 . 
         [0016]    In block  302 , processor  202  monitors the sensor data from within device  100 , such as sensor data from accelerometer  210 , gyroscope  212 , and altimeter  214 . Block  302  may be followed by block  304 . 
         [0017]    In block  304 , processor  202  monitors the OBD-II data from vehicle computer  224 . Note that processor  202  may monitor the sensor data and the OBD-II data concurrently. Block  304  may be followed by block  306 . 
         [0018]    In decision block  306 , processor  202  determines if a combination of the sensor data and the OBD-II data indicates a crash of vehicle  102 . The combination may include one or more of a rapid deceleration, a rapid change in direction or orientation, a rapid change in altitude, a rapid decrease in speed, and a rapid decrease in engine RPM indicate a crash. When a combination of the sensor data and the OBD-II data indicates a crash, decision block  306  may be followed by block  308 . Otherwise decision block  306  loops back to block  302 . 
         [0019]    In block  308 , processor  202  uses transceiver  218  to contact a call center or emergency responder  226 . In the communications, processor  202  provides the vehicle&#39;s route, including the vehicle&#39;s current location, the vehicle&#39;s orientation along the route, and the severity of the crash. Block  308  may loop back to block  302 . 
         [0020]      FIG. 4  is a block diagram of OBD-II interface  216  in device  100  of  FIG. 2  in one or more embodiment of the present disclosure. In this embodiment, OBD-II interface  216  is implemented as a radio transceiver, and another radio transceiver  402  is coupled the OBD-II port to vehicle computer  224  for wireless communication between device  100  and vehicle computer  224 . In one embodiment, the data may be encrypted and decrypted at both ends by encryption devices  404  and  406  before reaching radio transceivers  216  and  402 , respectively. Radio transceivers  216  and  402  may be Bluetooth transceivers. Instead of encryption device  404 , processor  202  may perform the encryption. 
         [0021]    Various other adaptations and combinations of features of the embodiments disclosed are within the scope of the present disclosure. Numerous embodiments are encompassed by the following claims.