# US 9,751,535 B1 · Real-time driver monitoring and feedback reporting system > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 9,751,535 B1 - Document ID: US9751535B1 - Status: Granted - Kind: B1 - Application number: 15/152,790 - Filed: 2016-05-12 - Granted: 2017-09-05 - Earliest claimed: 2014-09-23 - Assignees: State Farm Mutual Automobile Insurance Company - Applicants: State Farm Mutual Automobile Insurance Company - Inventors: Brian Mark Fields; Steve Roberson; Abhishek Harish; Hyunji Lim; Matthew James Waughtel - Web page: https://patentgrep.com/patent/US9751535B1 ## CPC - B60W 40/09: Driving style or behaviour - A61B 5/18: for vehicle drivers {or machine operators} - B60K 35/10: Input arrangements, i.e. from user to vehicle, associated with vehicle functions or specially adapted therefor - B60K 35/21: using visual output, e.g. blinking lights or matrix displays - B60K 35/85: Arrangements for transferring vehicle- or driver-related data - B60W 40/08: related to drivers or passengers - G07C 5/0816: {Indicating performance data, e.g. occurrence of a malfunction} - G07C 5/0858: {wherein the data carrier is removable} - G07C 5/12: in graphical form - G09B 19/14: Traffic procedures, e.g. traffic regulations - G09B 19/167: {Control of land vehicles} - H04W 4/029: Location-based management or tracking services - H04W 4/40: for vehicles, e.g. vehicle-to-pedestrians [V2P] - G07C 5/008: {communicating information to a remotely located station (transmission systems for measured values G08C)} - H04W 4/80: Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication - B60W: CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT - A61B: DIAGNOSIS; SURGERY; IDENTIFICATION (usefulness limited to only animals A61D) - B60K: ARRANGEMENT OR MOUNTING OF PROPULSION UNITS OR OF TRANSMISSIONS IN VEHICLES; ARRANGEMENT OR MOUNTING OF PLURAL DIVERSE PRIME-MOVERS IN VEHICLES; AUXILIARY DRIVES FOR VEHICLES; INSTRUMENTATION OR DASHBOARDS FOR VEHICLES; ARRANGEMENTS IN CONNECTION WITH COOLING, AIR INTAKE, GAS EXHAUST OR FUEL SUPPLY OF PROPULSION UNITS IN VEHICLES - G07C: TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE - G09B: EDUCATIONAL OR DEMONSTRATION APPLIANCES; APPLIANCES FOR TEACHING, OR COMMUNICATING WITH, THE BLIND, DEAF OR MUTE; MODELS; PLANETARIA; GLOBES; MAPS; DIAGRAMS (devices for psychotechnics or for testing reaction times A61B5/16; games, sports, amusements A63; projectors, projector screens G03B) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract 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. ## Claims ### Claim 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. ### Claim 2 (depends on 1) 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. ### Claim 3 (depends on 2) 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. ### Claim 4 (depends on 1) 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. ### Claim 5 (depends on 1) 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. ### Claim 6 (depends on 1) 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. ### Claim 7 (depends on 1) 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. ### Claim 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. ### Claim 9 (depends on 8) 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. ### Claim 10 (depends on 9) 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. ### Claim 11 (depends on 8) 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. ### Claim 12 (depends on 8) 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. ### Claim 13 (depends on 8) 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. ### Claim 14 (depends on 8) 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. ### Claim 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. ### Claim 16 (depends on 15) The first mobile computing device of claim 15, 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, and wherein the processor is further configured 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 to calculate a driver feedback score based upon the status metric values. ### Claim 17 (depends on 15) The first mobile computing device of claim 15, wherein the display is further configured to concurrently present 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. ### Claim 18 (depends on 15) The first mobile computing device of claim 15, 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. ### Claim 19 (depends on 15) The first mobile computing device of claim 15, 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. ### Claim 20 (depends on 15) The first mobile computing device of claim 15, wherein the processor is further configured to generate a custom tagged driving event in response to receiving user input indicative of a driving event, and to track a location of the vehicle during the driving session, and wherein the display is further configured to present the custom tagged driving event on the map of the driving session at a location of the vehicle when the user input was received.