Student driver feedback system allowing entry of tagged events by instructors during driving tests
US-9279697-B1 · Mar 8, 2016 · US
US9751535B1 · US · B1
| Field | Value |
|---|---|
| Publication number | US-9751535-B1 |
| Application number | US-201615152790-A |
| Country | US |
| Kind code | B1 |
| Filing date | May 12, 2016 |
| Priority date | Sep 23, 2014 |
| Publication date | Sep 5, 2017 |
| Grant date | Sep 5, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Real-time feedback may be generated during a driving session from status data collected via one or more sensors. This feedback data may include various metrics related to a student's driving skills, which may be utilized to generate tagged driving events. A user may also manually enter tagged driving events. The tagged driving events may include real-time information based on the collected status data, such as acceleration, braking, cornering data, descriptions entered by the user. The location of these tagged driving events may be mapped in real time. Sensors used to collect this data may be integrated within the device displaying the feedback or located on another device, in which case the status data may be communicated to the device displaying the feedback. The displayed real-time feedback may be viewed by an instructor to assess a student's driving skills in real time and to calculate a driver feedback score.
Opening claim text (preview).
What is claimed is: 1. A computer-implemented method for displaying data during a driving session on a first mobile computing device located in a vehicle, comprising: receiving, at the first mobile computing device by one or more processors, status metrics from a second mobile computing device located in the vehicle during the driving session, the status metrics being generated by the second mobile computing device and including data indicative of one or more vehicle conditions, generating, at the first mobile computing device by one or more processors, a tagged driving event when one of the status metrics meets or exceeds a status metric threshold; and concurrently displaying, on the first mobile computing device, driving session information based upon the status metrics including (i) a map of the driving session and the tagged driving event at a location on the map where the tagged driving event occurred, (ii) a driver status, and (iii) a vehicle status, wherein the first mobile computing device concurrently displays a greater number of different types of driving session information than the number of different types of driving session information the second mobile computing device can concurrently display. 2. The method of claim 1 , wherein the one or more vehicle conditions include one or more of (i) the vehicle's acceleration, (ii) the vehicle's movement while braking, and (iii) the vehicle's movement while cornering. 3. The method of claim 2 , further comprising: calculating, by one or more processors, status metric values associated with each of (i) the vehicle's acceleration, (ii) the vehicle's movement while braking, and (iii) the vehicle's movement while cornering, based upon the status metrics received during the driving session; and calculating, by one or more processors, a driver feedback score based upon the status metric values. 4. The method of claim 1 , wherein the act of concurrently displaying the driving session information further comprises: concurrently displaying in real time each of (i) the map of the driving session and the tagged driving event at a location on the map where the tagged driving event occurred, (ii) the driver status, and (iii) the vehicle status, to provide feedback during the driving session. 5. The method of claim 1 , wherein the driver status comprises one or more of: driver eye movement; a direction of a driver's gaze; driver head position; or a driver biometric. 6. The method of claim 1 , wherein the vehicle status comprises one or more of: vehicle road speed; vehicle engine speed; a time to collision (CTT); a lane position of the vehicle; vehicle light status; or vehicle braking status. 7. The method of claim 1 , further comprising: generating a custom tagged driving event in response to receiving user input indicative of a driving event; tracking a location of the vehicle during the driving session; and displaying the custom tagged driving event on the map of the driving session at a location of the vehicle when the user input was received. 8. A non-transitory, tangible computer-readable medium storing machine readable instructions for displaying data during a driving session on a first mobile computing device located in a vehicle, that when executed by a processor, cause the processor to: receive status metrics from a second mobile computing device located in the vehicle during the driving session, the status metrics being generated by the second mobile computing device and including data indicative of one or more vehicle conditions; generate a tagged driving event when one of the status metrics meets or exceeds a status metric threshold; and concurrently display the driving session information including (i) a map of the driving session and the tagged driving event at a location on the map where the tagged driving event occurred, (ii) a driver status, and (iii) a vehicle status, wherein the first mobile computing device concurrently displays a greater number of different types of driving session information than the number of different types of driving session information the second mobile computing device can concurrently display. 9. The non-transitory, tangible computer-readable medium of claim 8 , wherein the one or more vehicle conditions include one or more of (i) the vehicle's acceleration, (ii) the vehicle's movement while braking, and (iii) the vehicle's movement while cornering. 10. The non-transitory, tangible computer-readable medium of claim 9 , further including instructions, that when executed by the processor, cause the processor to: calculate status metric values associated with each of (i) the vehicle's acceleration, (ii) the vehicle's movement while braking, and (iii) the vehicle's movement while cornering, based upon the status metrics received during the driving session; and calculate a driver feedback score based upon the status metric values. 11. The non-transitory, tangible computer-readable medium of claim 8 , wherein the instructions to concurrently display the driving session information further include instructions that, when executed by the processor, cause the processor to concurrently display in real time each of (i) the map of the driving session and the tagged driving event at a location on the map where the tagged driving event occurred, (ii) the driver status, and (iii) the vehicle status, to provide feedback during the driving session. 12. The non-transitory, tangible computer-readable medium of claim 8 , wherein the driver status comprises one or more of: driver eye movement; a direction of a driver's gaze; driver head position; or a driver biometric. 13. The non-transitory, tangible computer-readable medium of claim 8 , wherein the vehicle status comprises one or more of: vehicle road speed; vehicle engine speed; time to collision (CTT); a lane position of the vehicle; vehicle light status; or vehicle braking status. 14. The non-transitory, tangible computer-readable medium of claim 8 , further including instructions, that when executed by the processor, cause the processor to: generate a custom tagged driving event in response to receiving user input indicative of a driving event; track a location of the vehicle during the driving session; and display the custom tagged driving event on the map of the driving session at a location of the vehicle when the user input was received. 15. A first mobile computing device configured to display data during a driving session when located in a vehicle, the first mobile computing device comprising: a communication unit configured to receive status metrics from a second mobile computing device located in the vehicle during the driving session, the status metrics being generated by the second mobile computing device and including data indicative of one or more vehicle conditions; a processor configured to generate a tagged driving event when one of the status metrics meets or exceeds a status metric threshold; and a display configured to concurrently present the driving session information including (i) a map of the driving session and the tagged driving event at a location on the map where the tagged driving event occurred, (ii) a driver status, and (iii) a vehicle status, wherein the display is further configured to concurrently present a greater number of different types of driving session information based upon the status metrics than the number of different types of driving session information the second mobile computing device is configured to concurrently display. 16. The first mobile computing device of
communicating information to a remotely located station (transmission systems for measured values G08C) · CPC title
for vehicle drivers {or machine operators} · CPC title
in graphical form · CPC title
related to drivers or passengers · CPC title
Traffic procedures, e.g. traffic regulations · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.