Movatterモバイル変換


[0]ホーム

URL:


US9628975B1 - Crash event detection, response and reporting apparatus and method - Google Patents

Crash event detection, response and reporting apparatus and method
Download PDF

Info

Publication number
US9628975B1
US9628975B1US14/819,879US201514819879AUS9628975B1US 9628975 B1US9628975 B1US 9628975B1US 201514819879 AUS201514819879 AUS 201514819879AUS 9628975 B1US9628975 B1US 9628975B1
Authority
US
United States
Prior art keywords
crash
communications device
mobile communications
motor vehicle
application
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Fee Related
Application number
US14/819,879
Inventor
D Scott Watkins
Craig A Tieman
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Mobile Video Computing Solutions LLC
Original Assignee
Mobile Video Computing Solutions LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US14/819,879priorityCriticalpatent/US9628975B1/en
Application filed by Mobile Video Computing Solutions LLCfiledCriticalMobile Video Computing Solutions LLC
Assigned to MOBILE DATA HOLDINGS LIMITED INC.reassignmentMOBILE DATA HOLDINGS LIMITED INC.ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS).Assignors: TIEMAN, CRAIG A, WATKINS, D SCOTT
Assigned to MOBILE COMPUTING SOLUTIONS LLCreassignmentMOBILE COMPUTING SOLUTIONS LLCASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS).Assignors: MOBILE DATA HOLDINGS LIMITED INC.
Assigned to MOBILE VIDEO COMPUTING SOLUTIONS LLCreassignmentMOBILE VIDEO COMPUTING SOLUTIONS LLCCHANGE OF NAME (SEE DOCUMENT FOR DETAILS).Assignors: MOBILE COMPUTING SOLUTIONS LLC
Assigned to MOBILE VIDEO COMPUTING SOLUTIONS LLCreassignmentMOBILE VIDEO COMPUTING SOLUTIONS LLCASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS).Assignors: MOBILE VIDEO COMPUTING SOLUTIONS HOLDINGS LLC
Assigned to MOBILE VIDEO COMPUTING SOLUTIONS HOLDINGS LLCreassignmentMOBILE VIDEO COMPUTING SOLUTIONS HOLDINGS LLCCHANGE OF NAME (SEE DOCUMENT FOR DETAILS).Assignors: MOBILE VIDEO COMPUTING SOLUTIONS LLC
Priority to US15/435,265prioritypatent/US9913099B2/en
Application grantedgrantedCritical
Publication of US9628975B1publicationCriticalpatent/US9628975B1/en
Priority to US15/875,949prioritypatent/US20180146341A1/en
Priority to US16/183,341prioritypatent/US10440514B2/en
Priority to US16/425,697prioritypatent/US10623899B2/en
Priority to US16/809,393prioritypatent/US11051127B2/en
Priority to US17/350,142prioritypatent/US11770681B2/en
Expired - Fee Relatedlegal-statusCriticalCurrent
Anticipated expirationlegal-statusCritical

Links

Images

Classifications

Definitions

Landscapes

Abstract

A crash detection system with a mobile communications device configured for periodically interrogating (a) an acceleration signal to determine whether a change in acceleration exceeds a predetermined acceleration threshold and (b) a sound signal to determine whether a sequence of sensed sound signals within a predetermined period matches crash sound indicators of (i) glass breakage and (ii) metal folding, displaying selectable options upon detection of a crash incident, and upon a failure to select within a predetermined period, communicating an identifier and crash incident information dispatch center for dispatching a response servicer.

Description

TECHNICAL FIELD
The present invention relates to apparatus and methods for responding to motor vehicle crash events. More particularly, the present invention relates to apparatus and methods for detecting the occurrence of a motor vehicle crash, responding to the detection of the motor vehicle crash, and reporting the detection of the motor vehicle crash.
BACKGROUND OF THE INVENTION
In recent years, improved roadways, traffic control devices, and safety devices that are installed and operated in motor vehicles have resulted in safer transportation by motor vehicle. Nevertheless, incidents and accidents involving car and truck motor vehicles continue to occur. These include vehicle-to-vehicle collisions as well as single vehicle accidents. While typically such incidents occur in locations where response personnel may be readily directed to provide medical and tow services, some incidents involving disappearance of the motor vehicle and its operation occur (such as a single vehicle accident in which the vehicle leaves the roadway and becomes hidden from view in woods or water).
Also, monitoring services seek “how am I driving” reports typically for fleet operators to monitor driving activities of vehicle operators but parents having children as new or inexperienced drivers also have become interested in monitoring and reporting on motor vehicle operations.
While systems having GPS location tracking features and cellular telecommunications devices have been installed in motor vehicles for communications between occupants and a tracking service provider, there are drawbacks to such systems.
The operator may be injured or blocked from initiating communications. Also, the operator may be using a different vehicle such as a rental vehicle.
Accordingly, there is a need in the art for an improved system and method for detecting occurrences of motor vehicle incidents, responding to detection of motor vehicle incident occurrences, and tracking and reporting on detection of and responses to motor vehicle incident occurrences. It is to such that the present invention is directed.
BRIEF SUMMARY OF THE INVENTION
The present invention meets the needs in the art by providing a system for detection of a crash of a motor vehicle with crash detection response and reporting, comprising a mobile communications device configured with a sensor that generates an acceleration signal responsive to acceleration of the mobile communications device and a sound receiver for receiving a sound signal of sound proximate the mobile communications device, and including software instructions that upon execution monitors for an occurrence of a crash event by periodically interrogating (a) the acceleration signal to determine whether a change in acceleration exceeds a predetermined acceleration threshold and (b) the sound signal to determine whether a sequence of sensed sound signals within a predetermined period matches crash sound indicators of (i) glass breakage and (ii) metal folding. A display that upon determining the occurrence of the crash incident displays a possible event window with a selectable option (a) to return the mobile communications device to monitoring for the occurrence of the crash incident or (b) to confirm the crash incident. Upon a failure of selection of one of the selectable options within a predetermined period, communicating by a communications network an identifier associated with the mobile communications device and crash incident information including a location data to a tracking and dispatch center having a pre-registered record of the mobile communications device and configured for receiving and storing the acceleration information and the sound signals on which the crash incident was determined. The tracking and dispatch center is configured to dispatch a servicer to a site of the crash incident based on the location data.
In another aspect, the present invention provides a motor vehicle crash detection system, comprising a tracking and dispatch center having a computer processor configured with an electronic memory device that maintains driver information of driver name, address, insurance company and policy number for a plurality of drivers and maintains vehicle crash information of motor vehicle, crash location data, date and time, and optionally one or more sequences of sounds from a crash location, one or more images thereof, for a plurality of crashed motor vehicles. A plurality of mobile communications devices, each associated with a respective one of the plurality of drivers are each configured with a sensor that generates an acceleration signal responsive to acceleration of the mobile communications device and a sound receiver for receiving a sound signal of sound proximate the mobile communications device. The mobile communications device configured with software instructions that upon execution monitors for an occurrence of a crash event by periodically interrogating (a) the acceleration signal to determine whether a change in acceleration exceeds a predetermined acceleration threshold and (b) the sound signal to determine whether a sequence of sensed sound signals within a predetermined period matches crash sound indicators of (i) glass breakage and (ii) metal folding. Upon determining the occurrence of the crash incident a display displays a possible event window for selection of one of (a) to return the mobile communications device to monitoring for the occurrence of the crash incident and (b) to confirm the crash incident. Upon a failure of selection of one of the selectable options within a predetermined period, the mobile communications device communicates by a communications network an identifier associated with the mobile communications device and crash incident information of a location data, date and time to the tracking and dispatch center. The tracking and dispatch center dispatches at least one response servicer to a site of the crash incident based on the location data.
The response servicer provides a lantern device having a light, an imaging device, and a communications device. Images received by the imaging device communicate by the communications device through the network to the tracking and dispatch center.
In yet another aspect, the present invention provides a method system for detecting a crash incident of a motor vehicle with crash detection response and reporting, comprising the steps of:
(a) providing a mobile communications device having a sensor that generates an acceleration signal responsive to acceleration of the mobile communications device and a sound receiver for receiving a sound signal of sound proximate the mobile communications device, with software instructions configured for execution for monitoring for an occurrence of a crash event;
(b) periodically interrogating (a) the acceleration signal to determine whether a change in acceleration exceeds a predetermined acceleration threshold and (b) the sound signal to determine whether a sequence of sensed sound signals within a predetermined period matches crash sound indicators of (i) glass breakage and (ii) metal folding;
(c) based on interrogations of the acceleration signal and the sound signal, determining that the crash incident occurred;
(d) making an alert as to the crash incident with the mobile communications device;
(e) determining whether the alert generated a crash response through the mobile communications device, and if not, communicating a location data of the crash incident to a service provider for response; and
(f) communicating a status of the service provider response to the mobile communications device.
Objects, advantages, and features of the present invention may be readily determined upon a reading of the following detailed description in conjunction with the drawings and the appended claims.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 illustrates a schematic overview of an illustrative embodiment of a crash detection, response, and reporting apparatus in accordance with the present invention.
FIG. 2 illustrates a process flow of an exemplary embodiment of an application for a mobile computer device configured for crash detection, response and reporting in accordance with the present invention.
FIG. 3 illustrates a screen image for operating the crash detection, response and reporting application.
FIG. 4 illustrates a screen image during monitoring the operation of the crash detection, response and reporting application.
FIG. 5 illustrates a crash detected screen displayed when the crash detection, response and reporting application determines that a possible crash event may have occurred.
FIG. 6 illustrates a screen image following detection of a possible crash event by the crash detection, response and reporting application.
FIG. 7 illustrates a screen image of the crash detection, response and reporting application after a request for assistance.
FIG. 8 illustrates a second screen image of the crash detection, response and reporting application after a request for assistance.
Objects, advantages and features of the present invention of crash event detection, response and reporting apparatus and method will become readily apparent upon a reading of the following detailed description in reference to the drawings and the appended claims.
DETAILED DESCRIPTION
With reference to the drawings, in which like parts have like reference numerals,FIG. 1 illustrates a schematic overview of an illustrative embodiment of a crash detection, response, and reportingapparatus10 in accordance with the present invention. Theapparatus10 supports motor vehicle insurance and tracking services for drivers ofmotor vehicles12 with acomputer software application14 configured for crash detection, response and reporting operable on amobile communications device16. Themobile communications device16 includes a microprocessor device, communications module, and display. The mobile communications device includes, but is not limited to cellular telephone, tablet computer, laptop portable computer, or other similar microprocessor device configured with an operating system, information input devices (mouse, keyboard, touchscreen, actual or virtual), and a display device for presentation of information during operation of the application. For example, the possession of cellular telephones is becoming more prevalent. Theapplication14 resident on the cellular telephone in the possession of the driver during motor vehicle operation, and operating in a background mode, provides a passively present crash detection, response, and reporting feature for drivers as well as others having an interest in the status of the driver and the motor vehicle.
Theapparatus10 includes a central tracking/dispatch center18, with a computer server orprocessor20. Thecomputer server20 includes conventional memory or storage devices and is configured for maintaining (adding, updating, revising) adatabase21 with information retained on the storage device. Thedatabase21 of the tracking/dispatch center18 receives and stores the acceleration information and the sound signals on which the crash incident was determined, upon communication from the mobile communications device of such information and signals through a communications network. Further, the database maintains driver information of driver name, address, insurance company and policy number for a plurality of drivers and maintains vehicle crash information of motor vehicle, crash location data, date and time, and optionally one or more sequences of sounds from a crash location, one or more images thereof, for a plurality of crashed motor vehicles. Thecomputer server20 is further configured for analyzing and reporting on the status of motor vehicles having information tracked though the database of the central tracking/dispatch center18.
Theapparatus10 includes one or more response services. These may be independent service providers or dependent providers related to the central tracking/dispatch center18. The illustrated embodiment includes a plurality of tow truck service/features22 as a response service. The response service includes atow truck23 and a portable lantern camera/communications device24. Theportable lantern device24 includes a high-wattage light25, acamera27, and acommunications device29. The light is selectively operable for night illumination. The camera operates in video or still modes for imaging of the crash event, the site, the motor vehicle(s) involved, and other picture documentation related to the crash event. The communications device provides two-way communications, such as cellular, wifi, radio, or other, for communicating with the persons involved in the crash event, with the central tracking/dispatch center18, with the tow service provider, or others as appropriate. Live images may be transmitted as appropriate, for example, but not limited to emergency care and services providers or thedispatcher18. In the illustrated embodiment, thetow truck23 optionally includes digital video recording and telecommunications equipment19 (i.e. MDVR and multiple cameras) for communicating images to theserver20, as well as capturing multiple video images from the tow truck and from theportable lantern camera24 that communicates with and through the telecommunications equipment. In yet another alternate embodiment, the lantern camera/MDVR24 provides the on-site imaging functionality and there is no MDVR equipment mounted on the truck except for other wireless cameras carried, for example, in the truck or by other responders, which communicate through the lantern camera/MDVR24 to theserver20.
Theapparatus10 further includes aclaims servicer26 that provides motor vehicle claims information and processing services to insurance carriers and motor vehicle owners and operators such as fleet operators.
Theapplication14,dispatch18, ISP (independent service provider)22, and theinsurance claims servicer26 communicate through a communications network generally30 including wireless, cellular, telephony, radio (two-way), world wide web communications devices and connections, and other suitable electronic communications devices.
Theserver20 is configured with thedatabase21 for tracking motor vehicles and drivers registered with the service, through a fleet operator, an insurance company as a service for its insured, or independently such as parents of young drivers. Further, theapparatus10 may gainfully be used by a fleet operator as an independent separate system.
FIG. 2 illustrates aprocess flow50 of an exemplary embodiment of theapplication14 operable with themobile communications device16 for crash detection, response and reporting in accordance with the present invention. The driver initiates52 operation of theapplication14. Theapplication14 may operate in a background mode of the mobile communications device so that other routine uses of the mobile communications device16 (such as cellphone calls, internet access, email receiving and transmitting, mapping and routing directions, and other conventional uses) may proceed.
Theapplication14 monitors54 for indicators of a crash event. In the illustrative embodiment, detection of motion above a preset speed causes theapplication14 to commence the crash detection monitoring functions. Themobile communications device16 includes conventionally anaccelerometer17, and theapplication14 periodically interrogates the accelerometer by communicating with, and receiving an acceleration signal from, the accelerometer. Themobile communications device16 includes a sound receiver or microphone. The crash indicators include themotor vehicle acceleration56 signals and thesounds58 received proximate themobile communications device16. Theapplication14 periodically receives60 the acceleration information of the motor vehicle from the force monitoring device or accelerometer. Theapplication14 also receives61 audio signals though the microphone. Rapid declaration and glass breakage/metal folding sounds indicate a possible crash event. Acrash indicator database62 provides accident or crash event correlated acceleration and sounds thresholds. The information is processed64 and compared with standards maintained in thedatabase62 to determine65 whether a possible crash event has occurred. If not, the apparatus continues monitoring66 for crash event signals. The use of multiple indicators of a crash event facilitates reduction of false alarms.
Monitoringcrash event indications54 involves detecting sounds with a mobile device microphone that exceed a predetermined threshold or detecting acceleration with 3-axis (x, y, z) accelerometers that exceed a predetermined threshold. Upon detecting one or more high threshold events, theapplication14 may check a GPS-based speed for evidence that the mobile device is slowing rapidly or has stopped moving. If the GPS-based speed is unchanged, theapplication14 would reject82 the detected event and return tocrash monitoring54. If the GPS-based speed indicated slowing/stopping, the processing of the sound and accelerometer recording files, which would include recording for a predetermined period of pre-event sound and accelerometer information and post-event recording of such information for a second predetermined period.
In an illustrative embodiment, theapplication14 maintains a continuous recording database of the acceleration and audio signals received during monitoring. The database is configured for maintaining a lead portion (pre-event) of a predetermined period preceding the possible crash event and a trailing portion (post-event) of a second predetermined period post-possible crash event. The recorded database uploads to the central tracking/dispatch center18 during notification communication of a possible crash event to the central tracking/dispatch center18.
Thedatabase21 of the tracking/dispatch center18 receives and stores the acceleration information and the sound signals on which the crash incident was determined, upon communication from themobile communications device16 of such information and signals through acommunications network30. Further, thedatabase21 maintains driver information of driver name, address, insurance company and policy number for a plurality of drivers and maintains vehicle crash information of motor vehicle, crash location data, date and time, and optionally one or more sequences of sounds from a crash location, one or more images thereof, for a plurality of crashed motor vehicles.
If the application determines68 that a possible crash event has occurred, the application alerts70 the driver. Determination of a possible crash event in the illustrative embodiment involves both sound and acceleration crash indicators being determined as true (i.e., exceeding respective predetermined thresholds). An exceeded sound threshold alone or an exceeded acceleration threshold alone may be rejected as indicating a crash event and processing would return to monitor54. The alert70 presents a visual message104 (seeFIG. 5) on a display of themobile communications device16. The alert70 may include an unmistakable audio tone at high volume to draw the driver's attention to themobile communications device16. The driver may respond in the negative and theapplication14 then returns to themonitor54 processes. If the driver confirms the crash event, the application presents72 selective choices for calling911 or emergency contact, contact the insurance carrier, request roadside assistance, or cancel, as discussed below in reference toFIG. 6.
If the driver does not respond72 after a predetermined period of time (for example, but not limitation, a period of 60 seconds), theapplication14 initiates assistance. This includes notification to emergency centers (such as to local police authorities)74,notification76 to the central tracking/dispatch center18, andinitial accident notification78 to theclaims service center26. The application may also evaluate80 whether the accelerometer and sounds information should be uploaded to the crash indicator database.
The driver, upon being alerted to the possible crash event, may selectively respond for the system to ignore82 the possible crash event (i.e., no crash event occurred); or83 to initiate84 telephone contact with appropriate local police authorities; to contact theinsurance carrier85 or to request86 assistance. The application providesupdates88 to the driver as to the status of the requested assistance. Such updates for example, may include contact information for a tow truck operator and arrival time. The driver may select to cancel89 the notifications and processing of crash event services by theapplication14.
Theapplication14 accordingly synchronizes the crash event with the motorists, the date and time of crash event, the place of the crash event, and the severity of the crash event. This information provides a basis for accident reconstruction, predictive indications of potential loss and injury, and also perfects the validity of the report of the crash event by the motorist involved while supporting official investigative reports.
FIG. 3 illustrates ascreen image100 for operating the crash detection, response and reportingapplication14 on themobile communications device16. Theapplication14 displays an activatebutton102. Operating thebutton102 causes theapplication14 to operate in the background of themobile communications device16, monitoring for a possible crash event, and responding appropriately, as discussed above. It is to be appreciated that the initiate screen100 (and the monitoring screen110 (FIG. 4) are in an exemplary embodiment of a stand-alone application. A production application in an alternate embodiment such as provided to customers of an insurance provider, may embed theapplication14 within a hosting application for the insured of the insurance provider or a similar hosting application with other consumer-facing features and services of the provider (for example, display a report of policy terms and limits, provide for changes to policy coverage, add, delete or modify driver and motor vehicle information, and other insurance servicing features.)
FIG. 4 illustrates themonitoring screen110 that may be displayed during the monitor processing of the crash detection, response and reportingapplication14. Thescreen110 includes astatus window111. The status window displays a short descriptive phrase as to the status of theapplication14 shown in Table 1 below:
TABLE 1
PhraseDefinition
Crash Sensing -theapplication 14 is monitoring for a possible
Monitoringcrash event
Crash Detected -theapplication 14 detects sound and
Triggeredaccelerometer information indicating a crash
event may have occurred
Crash Sensing -a crash event has occurred; theapplication 14
Confirmedprovides action options for selection by the driver
Crash Sensing -the crash event has been reported and status of
Reportedaction options and of response servicers are
displayed
Thewindow111 inFIG. 4 indicates that theapplication14 is monitoring for a possible crash event. Theapplication14 monitors sound events, and may provide a real-time signal display112 on thescreen110. Further, thescreen110 displays114 the three axis acceleration of the motor vehicle. A cancelbutton116 causes the application to cease operating. A “in accident”button118 enables the driver to initiate crash event processing by theapplication14, including notification to the central tracking/dispatch center18 that a crash event has occurred. In response to the “in accident”button118, theapplication14 communicates crash information, vehicle information and driver information using the communications of themobile communications device16. A window119 displays the driver and vehicle information.
FIG. 5 illustrates a crash detectedscreen103 displayed when theapplication14 determines that a possible crash event may have occurred. Thescreen103 may be accompanied with an unmistakable audio tone at high volume to draw the driver's attention to the mobile device. Thescreen103 displays a possible event window104 that includes thetime104aand GPS coordinates104bas well as the vehicle information119 window. Thescreen103 includes a “no accident—disregard”button106 and anaccident confirmation button105 with text “Yes, I was in an accident.” The driver operates the “I was in an accident”button105 to confirm the detection of a crash event. The driver operates the “no accident—disregard” button if the detection was incorrect as no crash incident had occurred.
The “I was in an accident”button118 shown inFIG. 4 is for circumstances where the driver wants to proceed manually to report a crash event without the application detecting the crash event;FIG. 5 provides the confirmation “accident”button105 for the driver to confirm that the detection of the crash event by the application was correct. Bothbuttons118 and105 cause theapplication14 to proceed to crash event processing in reference toFIG. 6. The “no-accident—disregard”button106 causes theapplication14 to return to themonitoring screen110 and monitoring as shown inFIG. 4.
FIG. 6 illustrates ascreen120 displayed to the driver on themobile communications device16 following detection of a possible crash event by the crash detection, response and reportingapplication14. Thewindow111 inFIG. 6 indicates that theapplication14 acknowledges or confirms receiving the crash event notice following the use of theconfirm button118. Thescreen120 includes aninsurance window122 that displays the name and address of the insured; the make, model and vehicle identification number of the insured motor vehicle; and the insurance carrier and policy number. Thescreen120 provides selectively actuated buttons to direct the activities of theapplication14. A “call”button123 causes theapplication14 to imitate a telephone call to the insurance carrier. A “cancel”button124 directs the application to resume monitoring for a possible crash event. Theapplication14 notifies the central tracking/dispatch center18. A “call 911”button126 directs theapplication14 to initiate a telephone call to local emergency services such as local police and ambulance services.
A “request assistance”button128 initiates services fromindependent service providers22. In the illustrated embodiment, theindependent service provider22 is a roadside assistance service. Theapplication14 communicates this request to the central tracking/dispatch center18. The information communicated by theapplication14 includes the vehicle identification number, the driver information and contact phone number, and the location, time, and event. Acrash event window129 displays crash event information including the report time, the location of the crash event (address, if determined), a geographical coordinate designation, and crash severity. The “cancel”button124 cancels the reporting and status monitoring activities. Appropriate information for cancelation communicates from themobile communication device16, such as to the tracking/dispatch center18 and/or theservice provider22.
FIG. 7 illustrates a screen130 of the crash detection, response and reportingapplication14 after a request for assistance is selected. Thewindow111 inFIG. 7 indicates that theapplication14 has reported the crash event. The screen130 displays theinsurance window122 and thecrash information window129. Optionally, the screen130 may display the time of detection of the crash event and the time the crash event was reported to the central tracking/dispatch center18. The screen130 includes anupdate field134. Theapplication14 presents in theupdate field134 the status of the requested assistance. This includes the type136 of assistance requested, thetime138 the request was made, and the status140 of the response. The screen130 may include an initiateemergency call button137. A cancelassistance button139 communicates a cancellation notice to theindependent service provider22 and to the tracking/dispatch center18.
FIG. 8 illustrates asecond screen150 of the crash detection, response and reporting application after a request for assistance, depicting updatedassistance information152. This may include the time ofdispatch154 and an estimate time ofarrival156. The update field may also present (not illustrated) the contact information of the tow truck driver. Acall button157 initiates telephonic communication with the operator of the tow truck. Optionally, a confirm arrival button enables the driver to communicate status information to the tracking/dispatch center18. A cancelbutton159 communicates a cancellation notice to theindependent service provider22 and to the tracking/dispatch center18.
Although not illustrated, theapplication14 includes user setup screens for entry of driver and vehicle information. This information includes the driver name and address, insurance company and policy, and the vehicle identification number and make and model. The information uploads to thedatabase21 on theserver20. The native application, downloaded and installed on the mobile communications device, maintains background processes such as environmental monitoring that occurs. The environmental conditions for monitoring may be selected through appropriate control screens. For example, environmental monitoring may occur under conditions which correspond to the user driving or riding in a moving vehicle above a specified speed (e.g. 5 mph). Optional detection of known vehicle RF emitters (e.g. BT or WiFi) may be used to enhance recognition of in-vehicle operation. That is, detection of RF signals may cause theapplication14 to commence monitoring. In an alternate embodiment, theapplication14 operates from a selection button provided through a hosting application such as provided as an SAAS web site of an insurance carrier or fleet operator.
As discussed above, the environmental monitoring includes periodically receiving and evaluating x, y, z accelerometer outputs (such as accelerometer devices embodied in the mobile communications device16) and microphone (e.g. engine sounds, ambient sounds) for communication of sounds for analysis of possible crash events. In addition, the application may receive motor vehicle speed signals (either GPS or handset-based cellular assisted) and configured for translating to approximate vehicle x, y, z coordinates and speed.
A determination of a significant possible crash event may be made upon detection of multiple ambient conditions, such as: high negative acceleration in the motor vehicle x or y axis, rapid negative change in vehicle speed, and sounds corresponding to vehicle impacts. An alternate embodiment includes spectral analysis for sounds of glass breaking and metal shearing, bending, folding, or otherwise experiencing high impact change, in the possible crash event determination. The determination is made based on a reasonable match of sounds from the event with sounds from known crash events. Such information may be maintained in a crash indicators database.
Upon determination65 of a significant possible crash event, actions may be initiated (automatically or selectively) which may include:
a. Prompting70 themobile communications device16 via screen message and notification sound requestingdriver confirmation105,106 whether a crash event has occurred and whether the driver wants to place anemergency 911 call.
b. If the user confirms a crash, the application may immediately send83 a message to third-party for roadside assistance initiation and also to the tracking/dispatch center18.
c. If the user does not respond to the application notification (e.g. because the driver is injured or otherwise unable to respond), the application may prompt the driver with an audible message to confirm verbally to call 911 via voice command. Optionally, the application may be configured to include the user/driver opting into an automatic crash notification feature which activates a speakerphone-based 911 call to permit a 911 operator to interrogate the driver hands-free.
Upon initiation of the roadside assistance call, theapplication14 may be used to communicate the status of roadside assistance response. This feature may be subject to the level of integration with the roadside assistance company or other service provider.
The application of the present invention provides improved reporting of motor vehicle accident and crash information to persons having interest in the driver status (such as, parents, central tracking/dispatch, fleet operators, and others), while providing early initiation and first notice to the insurance claim service of the crash event, and providing dispatch of independentservice provider services22 such as tow truck services, though a machine-to-machine monitor, tracking, and notification system. The first notice available through the monitor, tracking, and notification system facilities claims processing by providing the identification of the insured motorist, the motor vehicle involved, the location of the vehicle and the crash event, and updates of the status. Further, the application in an alternate embodiment includes video/photo recording features following detection/confirmation of a crash event. This enables the driver to generate video/photo image files that may automatically upload to the tracking/dispatch center18 andservers20 to complement or substitute for tow truck-generated video/photo information.
With reference toFIGS. 1 and 2, thesystem10 in accordance with the present invention operates52 for detecting a crash incident of the motor vehicle with crash detection response and reporting. Thesystem10 provides (a) the plurality ofmobile communications devices12 each carried by a driver or passenger in the motor vehicle. Eachmobile communications device12 has theaccelerometer52 as an acceleration sensor that generates the acceleration signal responsive to acceleration of themobile communications device12 and the sound receiver for receiving a sound signal of sound proximate the mobile communications device. Themobile communications device12 is configured with software instructions that upon execution monitors54 (preferably in the background of the operation thereof) for the occurrence of a crash event. The software instructions are configured64 for (b) periodically interrogating (a) the acceleration signal of theaccelerometer56 to determine whether a change in acceleration exceeds a predetermined acceleration threshold and (b) the sound signal to determine whether a sequence of sensed sound signals within a predetermined period matches crash sound indicators of (i) glass breakage and (ii) metal folding. Then, (c) based on the interrogations of the acceleration signal and the sound signal, themobile communications device12 determine65 whether a crash incident occurred, and if so68 the display of themobile communications device12 alerts thedriver70 and displays a possible event window104 (seeFIG. 5) for selection by the driver of one of (a)return106 the mobile communications device to monitoring54 for the occurrence of a crash event and (b) to confirm105 the crash event. In one aspect the mobile communications device (d) makes an alert. In response, (e) determining71 whether the alert generated a crash response by the driver through the mobile communications device, and if not,72 communicating a location data of the crash incident to a service provider for response. For example, upon a failure of selection of one of the selectable options within a predetermined period, themobile communications device12 communicating by acommunications network30 an identifier associated with the mobile communications device and crash incident information of the location data, date and time to the tracking anddispatch center18 for entry into thedatabase21. Further, thesystem10 includes at least oneresponse servicer22 for dispatching by the tracking and dispatch center to the site of the crash incident based on the location data, theresponse servicer22 providing the vehicle transporter (tow truck23) and thelantern device24 having a light, an imaging device, and a communications device, whereby images received by the imaging device communicate by the communications device through the network to the tracking and dispatch center. Further, (f) the tracking anddispatch center18 communicating a status of theservice provider22 response to themobile communications device12.
An alternate embodiment includes alternative reporting and action path for commercial vehicle operators that addresses the difference in procedures for motor vehicles and trucks used in cartage. For example, the third party servicer may include cargo insurance carriers, emergency response teams for tracking and fleet operators, hazardous materials handling and clean-up services, salvage and similar such services. Such embodiment provides for simultaneous reporting and alternate claim information streams.
The crash detection, response andreporting apparatus10 according to the present invention establishes, occupies, and provides an effective interlinked network of a plurality ofmotor vehicles12 each tracked locally during motor vehicle operation by a microprocessor-basedapplication14 that executes software code on themobile communications device16 of the driver, featuring communications networked driver/motor vehicle, central tracking/dispatch monitoring center18, and attendant services includingclaims servicer26 for an insurance carrier and support features for drivers such astow truck services22, for an end-to-end motor vehicle status tracking and reporting system featuring improved first notice of loss and machine-to-machine communicating between the motor vehicle, the monitoring center, and the services offering independent service providers (tow truck operators or claims servicers, for illustrative non-limiting examples), and enhanced revenue for insurance providers tracking motor vehicle status, incidents, and incident or accident reconstruction, documentation, and adjustment. The improved first notice of loss provided by the operation of the automatedcrash detection application14 benefits insurance carriers, fleet operators, and individual motor vehicle operators by identifying the insured motorist or driver and the location of the incident involving the driver and the motor vehicle while providing coverage details to improve claims processing efficiencies and advance the handling and resolution of claims though automatic or manual reporting of incident occurrences and communication to service providers of assistance needs. The system tracks and monitors vehicle care and logistics, while further assisting with evaluation of accident causes and reconstruction for resolution purposes. Theapplication14 operates52 in a background mode automatically or upon initiation by a driver and resolves locating insurance information from a wallet or storage within the motor vehicle.Independent service providers22 such as tow truck operators benefit with automated identification of insured drivers, motor vehicle or incident location, and automatic or manual initiation of service support and response. Images of service response at the incident location are readily uploaded using thelantern24 and the video andtelecommunications equipment19 of theservice provider22 to themonitoring center18 to provide documentation for service fees while potentially reducing claims against service providers. Insurance claimsservicers26 obtain automated and seamless communications of identified motorist claimants and improved timely first notice of loss and further benefit with increased efficiency of services dispatch processing and handling of claims resolutions including as appropriate access and uploading of live video and audio from incidents. Fleet (as well as individual) motor vehicles operated by drivers registered with the central tracking/dispatch monitoring center18 are readily monitored, assisted and reported on appropriately.
Computer networks suitable for use with the embodiments described herein include local area networks (LAN), wide area networks (WAN), Internet, or other connection services and network variations such as the world wide web, the public internet, a private internet, a private computer network, a public network, a mobile network, a cellular network, a value-added network, and the like. Computing devices coupled or connected to the network may be any microprocessor controlled device that permits access to the network, including terminal devices, such as personal computers, workstations, servers, mini computers, main-frame computers, laptop computers, mobile computers, palm top computers, hand held computers, mobile phones, TV set-top boxes, or combinations thereof. The computer network may include one of more LANs, WANs, Internets, and computers. The computers may serve as servers, clients, or a combination thereof.
The crash detection, response and reporting apparatus and method can be a component of a single system, multiple systems, and/or geographically separate systems. The crash detection, response and reporting apparatus and method can also be a subcomponent or subsystem of a single system, multiple systems, and/or geographically separate systems. The crash detection, response and reporting components can be coupled to one or more other components (not shown) of a host system or a system coupled to the host system.
One or more components of the crash detection, response and reporting apparatus and method and/or a corresponding interface, system or application to which the crash detection, response and reporting apparatus is coupled or connected includes and/or runs under and/or in association with a processing system. The processing system includes any collection of processor-based devices or computing devices operating together, or components of processing systems or devices, as is known in the art. For example, the processing system can include one or more of a portable computer, portable communication device operating in a communication network, and/or a network server. The portable computer can be any of a number and/or combination of devices selected from among personal computers, personal digital assistant devices, portable computing devices, and portable communication devices, but is not so limited. The processing system can include components within a larger computer system.
The processing system of an embodiment includes at least one processor and at least one memory device or subsystem. The processing system can also include or be coupled to at least one database. The term “processor” as generally used herein refers to any logic processing unit, such as one or more central processing units (CPUs), digital signal processors (DSPs), application-specific integrated circuits (ASIC), etc. The processor and memory can be monolithically integrated onto a single chip, distributed among a number of chips or components, and/or provided by some combination of algorithms. The methods described herein can be implemented in one or more of software algorithm(s), programs, firmware, hardware, components, circuitry, in any combination.
The components of any system that include the crash detection, response and reporting apparatus and method can be located together or in separate locations. Communication paths couple the components and include any medium for communicating or transferring files among the components. The communication paths include wireless connections, wired connections, and hybrid wireless/wired connections. The communication paths also include couplings or connections to networks including local area networks (LANs), metropolitan area networks (MANs), wide area networks (WANs), proprietary networks, interoffice or backend networks, and the Internet. Furthermore, the communication paths include but are not limited to, removable fixed mediums like floppy disks, hard disk drives, and CD-ROM disks, as well as flash RAM, Universal Serial Bus (USB) connections, RS-232 connections, telephone lines, buses, and electronic mail messages.
Aspects of the crash detection, response and reporting apparatus and corresponding systems and methods described herein may be implemented as functionality programmed into any of a variety of circuitry, including programmable logic devices (PLDs), such as field programmable gate arrays (FPGAs), programmable array logic (PAL) devices, electrically programmable logic and memory devices and standard cell-based devices, as well as application specific integrated circuits (ASICs). Some other possibilities for implementing aspects of the crash detection, response and reporting apparatus and method and corresponding systems and methods include: microcontrollers with memory (such as electronically erasable programmable read only memory (EEPROM)), embedded microprocessors, firmware, software, etc. Furthermore, aspects of the crash detection, response and reporting apparatus and method and corresponding systems and methods may be embodied in microprocessors having software-based circuit emulation, discrete logic (sequential and combinatorial), custom devices, fuzzy (neural) logic, quantum devices, and hybrids of any of the above device types. Of course the underlying device technologies may be provided in a variety of component types, e.g., metal-oxide semiconductor field-effect transistor (MOSFET) technologies like complementary metal-oxide semiconductor (CMOS), bipolar technologies like emitter-coupled logic (ECL), polymer technologies (e.g., silicon-conjugated polymer and metal-conjugated polymer-metal structures), mixed analog and digital, etc.
It should be noted that any system, method, and/or other components disclosed herein may be described using computer aided design tools and expressed (or represented), as data and/or instructions embodied in various computer-readable media, in terms of their behavioral, register transfer, logic component, transistor, layout geometries, and/or other characteristics. Computer-readable media in which such formatted data and/or instructions may be embodied include, but are not limited to, non-volatile storage media in various forms (e.g., optical, magnetic or semiconductor storage media) and carrier waves that may be used to transfer such formatted data and/or instructions through wireless, optical, or wired signaling media or any combination thereof. Examples of transfers of such formatted data and/or instructions by carrier waves include, but are not limited to, transfers (uploads, downloads, e-mail, etc.) over the Internet and/or other computer networks via one or more data transfer protocols (e.g., HTTP, FTP, SMTP, etc.). When received within a computer system via one or more computer-readable media, such data and/or instruction-based expressions of the above described components may be processed by a processing entity (e.g., one or more processors) within the computer system in conjunction with execution of one or more other computer programs.
Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense as opposed to an exclusive or exhaustive sense; that is to say, in a sense of “including, but not limited to.” Words using the singular or plural number also include the plural or singular number respectively. Additionally, the words “herein,” “hereunder,” “above,” “below,” and words of similar import, when used in this application, refer to this application as a whole and not to any particular portions of this application. When the word “or” is used in reference to a list of two or more items, that word covers all of the following interpretations of the word: any of the items in the list, all of the items in the list and any combination of the items in the list.
The above description of embodiments of the crash detection, response and reporting apparatus and method and the corresponding systems and methods is not intended to be exhaustive or to limit the systems and methods to the precise forms disclosed. While specific embodiments of, and examples for, the crash detection, response and reporting apparatus and method and corresponding systems and methods are described herein for illustrative purposes, various equivalent modifications are possible within the scope of the systems and methods, as those skilled in the relevant art will recognize. The teachings of the crash detection, response and reporting apparatus and method and corresponding systems and methods provided herein can be applied to other systems and methods, not only for the systems and methods described above.
The elements and actions of the various embodiments described above can be adapted, modified, and combined to provide further embodiments in accordance with the present invention of the crash detection, response and reporting apparatus and methods and corresponding systems and methods in light of the above detailed description. While this invention has been described in detail with particular reference to illustrative, non-limiting embodiments thereof, the principles and modes of operation of the present invention have been described in the foregoing specification. The invention is not to be construed as limited to the particular forms disclosed because these are regarded as illustrative rather than restrictive. Moreover, those skilled in the art may make modifications, variations and changes thereto without departure from the spirit and scope of the invention as described by the following claims.

Claims (6)

What is claimed is:
1. A motor vehicle crash detection system, comprising:
a tracking and dispatch center having a computer processor configured with an electronic memory device that maintains driver information of driver name, address, insurance company and policy number for a plurality of drivers and maintains vehicle crash information of motor vehicle, crash location data, date and time, and optionally one or more sequences of sounds from a crash location, one or more images thereof, for a plurality of crashed motor vehicles;
a plurality of mobile communications devices, each associated with a respective one of the plurality of drivers and configured with a sensor that generates an acceleration signal responsive to acceleration of the mobile communications device and a sound receiver for receiving a sound signal of sound proximate the mobile communications device;
the mobile communications device configured with software instructions that upon execution monitors for an occurrence of a crash event by periodically interrogating (a) the acceleration signal to determine whether a change in acceleration exceeds a predetermined acceleration threshold and (b) the sound signal to determine whether a sequence of sensed sound signals within a predetermined period matches crash sound indicators of (i) glass breakage and (ii) metal folding;
a display that upon determining the occurrence of the crash incident displays a possible event window for selection of one of (a) to return the mobile communications device to monitoring for the occurrence of the crash incident and (b) to confirm the crash incident;
upon a failure of selection of one of the selectable options within a predetermined period, the mobile communications device communicating by a communications network an identifier associated with the mobile communications device and crash incident information of a location data, date and time to the tracking and dispatch center; and
at least one response servicer for dispatching by the tracking and dispatch center to a site of the crash incident based on the location data, the response servicer provides a lantern device having a light, an imaging device, and a communications device, whereby images received by the imaging device communicate by the communications device through the network to the tracking and dispatch center.
2. The motor vehicle crash detection system as recited inclaim 1, wherein the response servicer further provides a vehicle transporter.
3. The motor vehicle crash detection system as recited inclaim 1, wherein the imaging device is operable for video.
4. The motor vehicle crash detection system as recited inclaim 1, wherein the imaging device is operable for single frame images.
5. The motor vehicle crash detection system as recited inclaim 1, further comprising an electronic data storage device installed for communication with the imaging device for recording of images prior to communicating the recorded images to the tracking and dispatch center.
6. The motor vehicle crash detection system as recited inclaim 1, further comprising a claims servicer for processing claims arising from the detected crash occurrence.
US14/819,8792014-08-062015-08-06Crash event detection, response and reporting apparatus and methodExpired - Fee RelatedUS9628975B1 (en)

Priority Applications (7)

Application NumberPriority DateFiling DateTitle
US14/819,879US9628975B1 (en)2014-08-062015-08-06Crash event detection, response and reporting apparatus and method
US15/435,265US9913099B2 (en)2014-08-062017-02-16Crash event detection, response and reporting apparatus and method
US15/875,949US20180146341A1 (en)2014-08-062018-01-19Crash Event Detection, Response and Reporting Apparatus and Method
US16/183,341US10440514B2 (en)2014-08-062018-11-07Crash event detection, response and reporting apparatus and method
US16/425,697US10623899B2 (en)2014-08-062019-05-29Crash event detection, response and reporting apparatus and method
US16/809,393US11051127B2 (en)2014-08-062020-03-04Communications hub for crash event detection, response, and reporting system
US17/350,142US11770681B2 (en)2014-08-062021-06-17Communications hub for crash event detection, response, and reporting system

Applications Claiming Priority (3)

Application NumberPriority DateFiling DateTitle
US201462034070P2014-08-062014-08-06
US201462034247P2014-08-072014-08-07
US14/819,879US9628975B1 (en)2014-08-062015-08-06Crash event detection, response and reporting apparatus and method

Related Child Applications (1)

Application NumberTitlePriority DateFiling Date
US15/435,265Continuation-In-PartUS9913099B2 (en)2014-08-062017-02-16Crash event detection, response and reporting apparatus and method

Publications (1)

Publication NumberPublication Date
US9628975B1true US9628975B1 (en)2017-04-18

Family

ID=58772104

Family Applications (1)

Application NumberTitlePriority DateFiling Date
US14/819,879Expired - Fee RelatedUS9628975B1 (en)2014-08-062015-08-06Crash event detection, response and reporting apparatus and method

Country Status (1)

CountryLink
US (1)US9628975B1 (en)

Cited By (59)

* Cited by examiner, † Cited by third party
Publication numberPriority datePublication dateAssigneeTitle
US20170069034A1 (en)*2015-09-032017-03-09Metropolitan Life Insurance Co.System and method for sensor-enhanced insurance coverage and monitoring service
US20170106876A1 (en)*2015-10-152017-04-20International Business Machines CorporationControlling Driving Modes of Self-Driving Vehicles
US20170221283A1 (en)*2015-08-202017-08-03Zendrive, Inc.Method for smartphone-based accident detection
US9785145B2 (en)2015-08-072017-10-10International Business Machines CorporationControlling driving modes of self-driving vehicles
US9791861B2 (en)2015-11-122017-10-17International Business Machines CorporationAutonomously servicing self-driving vehicles
US9836973B2 (en)2016-01-272017-12-05International Business Machines CorporationSelectively controlling a self-driving vehicle's access to a roadway
US9869560B2 (en)2015-07-312018-01-16International Business Machines CorporationSelf-driving vehicle's response to a proximate emergency vehicle
US9884629B2 (en)2015-09-022018-02-06International Business Machines CorporationRedirecting self-driving vehicles to a product provider based on physiological states of occupants of the self-driving vehicles
US9896100B2 (en)2015-08-242018-02-20International Business Machines CorporationAutomated spatial separation of self-driving vehicles from other vehicles based on occupant preferences
US9944291B2 (en)2015-10-272018-04-17International Business Machines CorporationControlling driving modes of self-driving vehicles
US10029701B2 (en)2015-09-252018-07-24International Business Machines CorporationControlling driving modes of self-driving vehicles
US10037683B1 (en)*2017-03-242018-07-31GM Global Technology Operations LLCCrash detection using GNSS velocity measurements and bus monitoring
US10061326B2 (en)2015-12-092018-08-28International Business Machines CorporationMishap amelioration based on second-order sensing by a self-driving vehicle
US10093322B2 (en)2016-09-152018-10-09International Business Machines CorporationAutomatically providing explanations for actions taken by a self-driving vehicle
US10152060B2 (en)2017-03-082018-12-11International Business Machines CorporationProtecting contents of a smart vault being transported by a self-driving vehicle
US10176525B2 (en)2015-11-092019-01-08International Business Machines CorporationDynamically adjusting insurance policy parameters for a self-driving vehicle
US10246037B1 (en)*2018-07-162019-04-02Cambridge Mobile Telematics Inc.Vehicle telematics of vehicle crashes
US10259452B2 (en)2017-01-042019-04-16International Business Machines CorporationSelf-driving vehicle collision management system
US10278039B1 (en)2017-11-272019-04-30Zendrive, Inc.System and method for vehicle sensing and analysis
US10300876B1 (en)*2015-11-092019-05-28State Farm Mutual Automobile Insurance CompanyDetection and classification of events
US10363893B2 (en)2017-01-052019-07-30International Business Machines CorporationSelf-driving vehicle contextual lock control system
US10442444B1 (en)*2018-08-062019-10-15Denso International America, Inc.Vehicle behavior and driver assistance modules for a mobile network device implementing pseudo-vehicle behavior signal generation based on mobile sensor signals
US10529147B2 (en)2017-01-052020-01-07International Business Machines CorporationSelf-driving vehicle road safety flare deploying system
US10559196B2 (en)2017-10-202020-02-11Zendrive, Inc.Method and system for vehicular-related communications
US10607293B2 (en)2015-10-302020-03-31International Business Machines CorporationAutomated insurance toggling for self-driving vehicles
US10643256B2 (en)2016-09-162020-05-05International Business Machines CorporationConfiguring a self-driving vehicle for charitable donations pickup and delivery
CN111181584A (en)*2018-11-122020-05-19上海擎感智能科技有限公司Mobile terminal and vehicle-mounted intercommunication method and intercommunication application
US10685391B2 (en)2016-05-242020-06-16International Business Machines CorporationDirecting movement of a self-driving vehicle based on sales activity
US11062594B2 (en)2017-06-282021-07-13Zendrive, Inc.Method and system for determining traffic-related characteristics
US11079235B2 (en)2015-08-202021-08-03Zendrive, Inc.Method for accelerometer-assisted navigation
US11175152B2 (en)2019-12-032021-11-16Zendrive, Inc.Method and system for risk determination of a route
US11450099B2 (en)2020-04-142022-09-20Toyota Motor North America, Inc.Video accident reporting
USD967266S1 (en)2016-11-142022-10-18Lyft, Inc.Electronic device with display
US11508189B2 (en)2020-04-142022-11-22Toyota Motor North America, Inc.Processing of accident report
US11553321B2 (en)*2019-07-052023-01-10Rapidsos, Inc.Apparatus and method for dispatching a tow truck in response to a roadway emergency
US20230025199A1 (en)*2021-07-212023-01-26Subaru CorporationVehicle with emergency reporting function, and server
US11574262B2 (en)2016-12-302023-02-07Lyft, Inc.Location accuracy using local device communications
US11615200B2 (en)2020-04-142023-03-28Toyota Motor North America, Inc.Providing video evidence
US11636758B2 (en)2019-06-182023-04-25Toyota Motor North America, Inc.Identifying changes in the condition of a transport
US11659368B2 (en)2016-09-122023-05-23Zendrive, Inc.Method for mobile device-based cooperative data capture
CN116502479A (en)*2023-06-292023-07-28之江实验室 A collision detection method and device for a three-dimensional object in a simulation environment
US11716408B2 (en)2016-12-302023-08-01Lyft, Inc.Navigation using proximity information
US11734963B2 (en)2013-03-122023-08-22Zendrive, Inc.System and method for determining a driver in a telematic application
USD997988S1 (en)2020-03-302023-09-05Lyft, Inc.Transportation communication device
US11775010B2 (en)2019-12-022023-10-03Zendrive, Inc.System and method for assessing device usage
US11878720B2 (en)2016-12-092024-01-23Zendrive, Inc.Method and system for risk modeling in autonomous vehicles
US11887206B2 (en)2015-10-092024-01-30Lyft, Inc.System to facilitate a correct identification of a service provider
US11887386B1 (en)*2020-03-302024-01-30Lyft, Inc.Utilizing an intelligent in-cabin media capture device in conjunction with a transportation matching system
US20240038048A1 (en)*2022-07-272024-02-01Honeywell International Inc.Alarm system states
US11910452B2 (en)2019-05-282024-02-20Lyft, Inc.Automatically connecting wireless computing devices based on recurring wireless signal detections
US11961340B2 (en)2017-08-042024-04-16Cambridge Mobile Telematics Inc.Method and system for accident detection using contextual data
US20240140405A1 (en)*2016-01-262024-05-02Cambridge Mobile Telematics Inc.Systems and methods for sensor-based vehicle crash prediction, detection, and reconstruction
US12020341B2 (en)2016-09-302024-06-25Lyft, Inc.Identifying matched requestors and providers
US12056633B2 (en)2021-12-032024-08-06Zendrive, Inc.System and method for trip classification
US12056755B2 (en)2017-10-162024-08-06Allstate Insurance CompanyGeotagging location data
US12118610B2 (en)2019-06-182024-10-15Toyota Motor North America, Inc.Identifying changes in the condition of a transport
US12300043B1 (en)*2019-07-122025-05-13Allstate Insurance CompanyRoadside assistance detection
US12400272B2 (en)2019-12-022025-08-26Credit Karma, LlcSystem and method for assessing device usage
US12430954B2 (en)*2023-04-282025-09-30Toyota Jidosha Kabushiki KaishaInformation processing device

Citations (3)

* Cited by examiner, † Cited by third party
Publication numberPriority datePublication dateAssigneeTitle
US20020145666A1 (en)*1998-06-012002-10-10Scaman Robert JefferyIncident recording secure database
US20100142715A1 (en)*2008-09-162010-06-10Personics Holdings Inc.Sound Library and Method
US20150084757A1 (en)*2013-09-232015-03-26Agero, Inc.Methods and systems for determining auto accidents using mobile phones and initiating emergency response

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication numberPriority datePublication dateAssigneeTitle
US20020145666A1 (en)*1998-06-012002-10-10Scaman Robert JefferyIncident recording secure database
US20100142715A1 (en)*2008-09-162010-06-10Personics Holdings Inc.Sound Library and Method
US20150084757A1 (en)*2013-09-232015-03-26Agero, Inc.Methods and systems for determining auto accidents using mobile phones and initiating emergency response

Cited By (100)

* Cited by examiner, † Cited by third party
Publication numberPriority datePublication dateAssigneeTitle
US11734963B2 (en)2013-03-122023-08-22Zendrive, Inc.System and method for determining a driver in a telematic application
US12230073B2 (en)2013-03-122025-02-18Credit Karma, LlcSystem and method for determining a driver in a telematic application
US11460308B2 (en)2015-07-312022-10-04DoorDash, Inc.Self-driving vehicle's response to a proximate emergency vehicle
US9869560B2 (en)2015-07-312018-01-16International Business Machines CorporationSelf-driving vehicle's response to a proximate emergency vehicle
US9785145B2 (en)2015-08-072017-10-10International Business Machines CorporationControlling driving modes of self-driving vehicles
US10279804B2 (en)*2015-08-202019-05-07Zendrive, Inc.Method for smartphone-based accident detection
US11079235B2 (en)2015-08-202021-08-03Zendrive, Inc.Method for accelerometer-assisted navigation
US20170221283A1 (en)*2015-08-202017-08-03Zendrive, Inc.Method for smartphone-based accident detection
US11375338B2 (en)*2015-08-202022-06-28Zendrive, Inc.Method for smartphone-based accident detection
US20220286811A1 (en)*2015-08-202022-09-08Zendrive, Inc.Method for smartphone-based accident detection
US10848913B2 (en)2015-08-202020-11-24Zendrive, Inc.Method for smartphone-based accident detection
US11927447B2 (en)2015-08-202024-03-12Zendrive, Inc.Method for accelerometer-assisted navigation
US9896100B2 (en)2015-08-242018-02-20International Business Machines CorporationAutomated spatial separation of self-driving vehicles from other vehicles based on occupant preferences
US10202117B2 (en)2015-08-242019-02-12International Business Machines CorporationAutomated spatial separation of self-driving vehicles from other vehicles based on occupant preferences
US10173679B2 (en)2015-08-242019-01-08International Business Machines CorporationAutomated spatial separation of self-driving vehicles from other vehicles based on occupant preferences
US9884629B2 (en)2015-09-022018-02-06International Business Machines CorporationRedirecting self-driving vehicles to a product provider based on physiological states of occupants of the self-driving vehicles
US20170069034A1 (en)*2015-09-032017-03-09Metropolitan Life Insurance Co.System and method for sensor-enhanced insurance coverage and monitoring service
US10762573B2 (en)*2015-09-032020-09-01Metropolitan Life Insurance Co.System and method for sensor-enhanced insurance coverage and monitoring service
US11132751B2 (en)2015-09-032021-09-28Metropolitan Life Insurance Co.System and method for sensor-enhanced insurance coverage and monitoring service
US11597402B2 (en)2015-09-252023-03-07Slingshot Iot LlcControlling driving modes of self-driving vehicles
US10029701B2 (en)2015-09-252018-07-24International Business Machines CorporationControlling driving modes of self-driving vehicles
US11738765B2 (en)2015-09-252023-08-29Slingshot Iot LlcControlling driving modes of self-driving vehicles
US10717446B2 (en)2015-09-252020-07-21Slingshot Iot LlcControlling driving modes of self-driving vehicles
US11091171B2 (en)2015-09-252021-08-17Slingshot Iot LlcControlling driving modes of self-driving vehicles
US12037004B2 (en)2015-09-252024-07-16Granite Vehicle Ventures LlcControlling driving modes of self-driving vehicles
US11887206B2 (en)2015-10-092024-01-30Lyft, Inc.System to facilitate a correct identification of a service provider
US9981669B2 (en)*2015-10-152018-05-29International Business Machines CorporationControlling driving modes of self-driving vehicles
US9834224B2 (en)*2015-10-152017-12-05International Business Machines CorporationControlling driving modes of self-driving vehicles
US20170106876A1 (en)*2015-10-152017-04-20International Business Machines CorporationControlling Driving Modes of Self-Driving Vehicles
US10543844B2 (en)2015-10-272020-01-28International Business Machines CorporationControlling driving modes of self-driving vehicles
US9944291B2 (en)2015-10-272018-04-17International Business Machines CorporationControlling driving modes of self-driving vehicles
US10607293B2 (en)2015-10-302020-03-31International Business Machines CorporationAutomated insurance toggling for self-driving vehicles
US10300876B1 (en)*2015-11-092019-05-28State Farm Mutual Automobile Insurance CompanyDetection and classification of events
US10176525B2 (en)2015-11-092019-01-08International Business Machines CorporationDynamically adjusting insurance policy parameters for a self-driving vehicle
US10604097B1 (en)*2015-11-092020-03-31State Farm Mutual Automobile Insurance CompanyDetection and classification of events
US9791861B2 (en)2015-11-122017-10-17International Business Machines CorporationAutonomously servicing self-driving vehicles
US10061326B2 (en)2015-12-092018-08-28International Business Machines CorporationMishap amelioration based on second-order sensing by a self-driving vehicle
US20240140405A1 (en)*2016-01-262024-05-02Cambridge Mobile Telematics Inc.Systems and methods for sensor-based vehicle crash prediction, detection, and reconstruction
US10109195B2 (en)2016-01-272018-10-23International Business Machines CorporationSelectively controlling a self-driving vehicle's access to a roadway
US9836973B2 (en)2016-01-272017-12-05International Business Machines CorporationSelectively controlling a self-driving vehicle's access to a roadway
US10685391B2 (en)2016-05-242020-06-16International Business Machines CorporationDirecting movement of a self-driving vehicle based on sales activity
US11295372B2 (en)2016-05-242022-04-05International Business Machines CorporationDirecting movement of a self-driving vehicle based on sales activity
US11659368B2 (en)2016-09-122023-05-23Zendrive, Inc.Method for mobile device-based cooperative data capture
US12192865B2 (en)2016-09-122025-01-07Credit Karma, LlcMethod for mobile device-based cooperative data capture
US10093322B2 (en)2016-09-152018-10-09International Business Machines CorporationAutomatically providing explanations for actions taken by a self-driving vehicle
US10207718B2 (en)2016-09-152019-02-19International Business Machines CorporationAutomatically providing explanations for actions taken by a self-driving vehicle
US10643256B2 (en)2016-09-162020-05-05International Business Machines CorporationConfiguring a self-driving vehicle for charitable donations pickup and delivery
US12020341B2 (en)2016-09-302024-06-25Lyft, Inc.Identifying matched requestors and providers
USD967266S1 (en)2016-11-142022-10-18Lyft, Inc.Electronic device with display
US11878720B2 (en)2016-12-092024-01-23Zendrive, Inc.Method and system for risk modeling in autonomous vehicles
US12095887B2 (en)2016-12-302024-09-17Lyft, Inc.Navigation using proximity information
US11574262B2 (en)2016-12-302023-02-07Lyft, Inc.Location accuracy using local device communications
US11716408B2 (en)2016-12-302023-08-01Lyft, Inc.Navigation using proximity information
US10259452B2 (en)2017-01-042019-04-16International Business Machines CorporationSelf-driving vehicle collision management system
US10363893B2 (en)2017-01-052019-07-30International Business Machines CorporationSelf-driving vehicle contextual lock control system
US10818104B2 (en)2017-01-052020-10-27International Business Machines CorporationSelf-driving vehicle road safety flare deploying system
US10529147B2 (en)2017-01-052020-01-07International Business Machines CorporationSelf-driving vehicle road safety flare deploying system
US10152060B2 (en)2017-03-082018-12-11International Business Machines CorporationProtecting contents of a smart vault being transported by a self-driving vehicle
US10037683B1 (en)*2017-03-242018-07-31GM Global Technology Operations LLCCrash detection using GNSS velocity measurements and bus monitoring
US11062594B2 (en)2017-06-282021-07-13Zendrive, Inc.Method and system for determining traffic-related characteristics
US11735037B2 (en)2017-06-282023-08-22Zendrive, Inc.Method and system for determining traffic-related characteristics
US11961340B2 (en)2017-08-042024-04-16Cambridge Mobile Telematics Inc.Method and system for accident detection using contextual data
US12300042B2 (en)2017-08-042025-05-13Cambridge Mobile Telematics Inc.Method and system for accident detection using contextual data
US12056755B2 (en)2017-10-162024-08-06Allstate Insurance CompanyGeotagging location data
US10559196B2 (en)2017-10-202020-02-11Zendrive, Inc.Method and system for vehicular-related communications
US11380193B2 (en)2017-10-202022-07-05Zendrive, Inc.Method and system for vehicular-related communications
US10278039B1 (en)2017-11-272019-04-30Zendrive, Inc.System and method for vehicle sensing and analysis
US11082817B2 (en)2017-11-272021-08-03Zendrive, IncSystem and method for vehicle sensing and analysis
US11871313B2 (en)2017-11-272024-01-09Zendrive, Inc.System and method for vehicle sensing and analysis
US11203315B2 (en)2018-07-162021-12-21Cambridge Mobile Telematics Inc.Vehicle telematics of vehicle crashes
US10246037B1 (en)*2018-07-162019-04-02Cambridge Mobile Telematics Inc.Vehicle telematics of vehicle crashes
US12202422B2 (en)2018-07-162025-01-21Cambridge Mobile Telematics Inc.Vehicle telematics of vehicle crashes
US10442444B1 (en)*2018-08-062019-10-15Denso International America, Inc.Vehicle behavior and driver assistance modules for a mobile network device implementing pseudo-vehicle behavior signal generation based on mobile sensor signals
CN111181584A (en)*2018-11-122020-05-19上海擎感智能科技有限公司Mobile terminal and vehicle-mounted intercommunication method and intercommunication application
CN111181584B (en)*2018-11-122023-02-17上海擎感智能科技有限公司Mobile terminal and vehicle-mounted intercommunication method and intercommunication application
US11910452B2 (en)2019-05-282024-02-20Lyft, Inc.Automatically connecting wireless computing devices based on recurring wireless signal detections
US12118610B2 (en)2019-06-182024-10-15Toyota Motor North America, Inc.Identifying changes in the condition of a transport
US11636758B2 (en)2019-06-182023-04-25Toyota Motor North America, Inc.Identifying changes in the condition of a transport
US11553321B2 (en)*2019-07-052023-01-10Rapidsos, Inc.Apparatus and method for dispatching a tow truck in response to a roadway emergency
US12300043B1 (en)*2019-07-122025-05-13Allstate Insurance CompanyRoadside assistance detection
US11775010B2 (en)2019-12-022023-10-03Zendrive, Inc.System and method for assessing device usage
US12400272B2 (en)2019-12-022025-08-26Credit Karma, LlcSystem and method for assessing device usage
US11175152B2 (en)2019-12-032021-11-16Zendrive, Inc.Method and system for risk determination of a route
USD997988S1 (en)2020-03-302023-09-05Lyft, Inc.Transportation communication device
US11887386B1 (en)*2020-03-302024-01-30Lyft, Inc.Utilizing an intelligent in-cabin media capture device in conjunction with a transportation matching system
US11954952B2 (en)2020-04-142024-04-09Toyota Motor North America, Inc.Processing of accident report
US11615200B2 (en)2020-04-142023-03-28Toyota Motor North America, Inc.Providing video evidence
US11450099B2 (en)2020-04-142022-09-20Toyota Motor North America, Inc.Video accident reporting
US11853358B2 (en)2020-04-142023-12-26Toyota Motor North America, Inc.Video accident reporting
US12346470B2 (en)2020-04-142025-07-01Toyota Motor North America, Inc.Providing video evidence
US11508189B2 (en)2020-04-142022-11-22Toyota Motor North America, Inc.Processing of accident report
US20230025199A1 (en)*2021-07-212023-01-26Subaru CorporationVehicle with emergency reporting function, and server
US11984027B2 (en)*2021-07-212024-05-14Subaru CorporationVehicle with emergency reporting function, and server
US12288465B2 (en)2021-07-212025-04-29Subaru CorporationVehicle with emergency reporting function, and server
US12056633B2 (en)2021-12-032024-08-06Zendrive, Inc.System and method for trip classification
US12106656B2 (en)*2022-07-272024-10-01Honeywell International Inc.Alarm system states
US20240038048A1 (en)*2022-07-272024-02-01Honeywell International Inc.Alarm system states
US12430954B2 (en)*2023-04-282025-09-30Toyota Jidosha Kabushiki KaishaInformation processing device
CN116502479A (en)*2023-06-292023-07-28之江实验室 A collision detection method and device for a three-dimensional object in a simulation environment
CN116502479B (en)*2023-06-292023-09-01之江实验室Collision detection method and device of three-dimensional object in simulation environment

Similar Documents

PublicationPublication DateTitle
US10623899B2 (en)Crash event detection, response and reporting apparatus and method
US10440514B2 (en)Crash event detection, response and reporting apparatus and method
US9628975B1 (en)Crash event detection, response and reporting apparatus and method
US11770681B2 (en)Communications hub for crash event detection, response, and reporting system
WO2018147881A1 (en)Crash event detection, response and reporting apparatus and method
US12365308B2 (en)Methods of facilitating emergency assistance
US9852555B2 (en)Vehicle impact sensor and notification system
US20240161266A1 (en)Remote verification of image collection equipment for crash event detection, response, and reporting systems
US20220277598A1 (en)Devices and methods for collecting traffic accident information
US20170109828A1 (en)Device-based incident detection and notification
US11553321B2 (en)Apparatus and method for dispatching a tow truck in response to a roadway emergency
JP6595842B2 (en) Information processing technology related to customer service in the event of an accident
US20210132784A1 (en)Cargo vessel operator emergency response system, with operator directives, incident data recording and reporting, and automated relevant party notification
JP7619933B2 (en) Accident analysis device, accident analysis method, and program
JP2016133963A (en)Communication type drive recorder and emergency notification system
JP7431893B2 (en) Accident information display device, accident information display method and program

Legal Events

DateCodeTitleDescription
ASAssignment

Owner name:MOBILE DATA HOLDINGS LIMITED INC., MICHIGAN

Free format text:ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:WATKINS, D SCOTT;TIEMAN, CRAIG A;REEL/FRAME:036269/0375

Effective date:20150806

ASAssignment

Owner name:MOBILE COMPUTING SOLUTIONS LLC, MICHIGAN

Free format text:ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MOBILE DATA HOLDINGS LIMITED INC.;REEL/FRAME:036851/0311

Effective date:20151001

ASAssignment

Owner name:MOBILE VIDEO COMPUTING SOLUTIONS LLC, MICHIGAN

Free format text:CHANGE OF NAME;ASSIGNOR:MOBILE COMPUTING SOLUTIONS LLC;REEL/FRAME:041431/0157

Effective date:20160527

ASAssignment

Owner name:MOBILE VIDEO COMPUTING SOLUTIONS LLC, MICHIGAN

Free format text:ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MOBILE VIDEO COMPUTING SOLUTIONS HOLDINGS LLC;REEL/FRAME:041113/0089

Effective date:20161231

Owner name:MOBILE VIDEO COMPUTING SOLUTIONS HOLDINGS LLC, MIC

Free format text:CHANGE OF NAME;ASSIGNOR:MOBILE VIDEO COMPUTING SOLUTIONS LLC;REEL/FRAME:041541/0397

Effective date:20161214

STCFInformation on status: patent grant

Free format text:PATENTED CASE

MAFPMaintenance fee payment

Free format text:PAYMENT OF MAINTENANCE FEE, 4TH YR, SMALL ENTITY (ORIGINAL EVENT CODE: M2551); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY

Year of fee payment:4

FEPPFee payment procedure

Free format text:MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY

LAPSLapse for failure to pay maintenance fees

Free format text:PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY

STCHInformation on status: patent discontinuation

Free format text:PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362

FPLapsed due to failure to pay maintenance fee

Effective date:20250418


[8]ページ先頭

©2009-2025 Movatter.jp