System and method for viewing and correcting data in a street mapping database

Information

  • Patent Grant
  • 8963702
  • Patent Number
    8,963,702
  • Date Filed
    Friday, February 13, 2009
    15 years ago
  • Date Issued
    Tuesday, February 24, 2015
    9 years ago
Abstract
A system and method for detecting use of a wireless device is disclosed. In one embodiment, a system and method for using street map data broadcasts a warning to a driver, wherein the warning is triggered when a vehicle operating parameter does not comply with a limitation for a current street in a street mapping database. The limitation for the current street is also broadcast to the driver. An indication that the limitation for the current street is incorrect is received from the driver. The warning to the driver may be an audible warning and/or a visual warning to the driver. Broadcasting a limitation for the current street may include displaying the limitation to the driver or playing a spoken message to the driver. The limitation may be a posted speed limit or a traffic direction, for example.
Description
TECHNICAL FIELD

The present invention relates generally to a system and method for creating, using and maintaining a database of street mapping data and, more particularly, to a system and method for updating street data and identifying errors in the database.


BACKGROUND

Detailed street mapping data is available from companies such as NavTeq and Tele Atlas. The street mapping data may include street location, street names, posted speed limits, numbers of lanes, travel direction, and other information. This street mapping data is used in vehicle navigation systems to provide map displays and other information to drivers. Typically, the only information displayed to a driver is a street map and limited other information, such as the name of the street being used by a vehicle and/or the name of the city or municipality in which the street is located. Other street mapping data may be available for a current street or roadway, but that information is not available to the driver. The street mapping data is used in some applications to evaluate driver performance, such as comparing vehicle speeds to posted speed limits recorded in the street mapping data. If the street mapping data is wrong, such as an incorrect posted speed limit, the driver will not know that a navigation system or vehicle monitoring system using the street mapping data may be using the wrong fundamental parameters to evaluate driver performance and/or vehicle operation. Furthermore, maintaining accurate mapping data can be a very costly endeavor.


SUMMARY OF THE INVENTION

These and other problems are generally solved or circumvented, and technical advantages are generally achieved, by preferred embodiments of the present invention in which street mapping data is available to a vehicle driver. The driver may then evaluate the accuracy of the street mapping data and may report errors in the street mapping data.


In one embodiment, a system and method for using street map data comprises broadcasting a warning to a driver, wherein the warning is triggered when a vehicle operating parameter does not comply with a limitation (e.g., a speed limitation, direction limitation, or otherwise) for a current street in a street mapping database; broadcasting the limitation for the current street to the driver; and receiving an indication that the limitation for the current street is incorrect. Broadcasting the warning to the driver may be providing an audible warning and/or a visual warning to the driver. Broadcasting the limitation for the current street to the driver may include displaying the limitation to the driver or playing a spoken message to the driver. The limitation may be a posted speed limit or a traffic direction, for example. The indication that the limitation is incorrect may be sent to a third party.


In another embodiment, a system and method for identifying errors in a street mapping database, comprises determining driving limitations for a current vehicle location; determining current operating parameters for a vehicle; identifying one or more current operating parameters that violate the driving limitations; broadcasting a warning to a vehicle driver, wherein the warning notifies the driver that one or more driving limitations have been violated; and displaying a stored value of the one or more driving limitations to the driver. The current vehicle location may be displayed to the driver on a map. Broadcasting a warning to a vehicle driver may include displaying a visual warning to the driver identifying one or more categories of driving limitations that have been violated. The one or more categories of driving limitations may be posted speed limits or traffic directions. The stored value may be a stored posted speed limit for the current vehicle location. An indication that the stored value is incorrect may be received, for example, from a driver, and the indication may be sent to a street mapping database provider and/or to a supervisor. For example, if an operator identifies an incorrect speed limitation value, such error can be communicated for purposes of correcting it. The database provider or supervisor, such as fleet manager, navigation system provider, or mapping data provider, may use the indication to evaluate or update a street map database. A replacement entry may be received for the stored value, for example, from a driver. The replacement entry may be sent to a street mapping database provider and/or a supervisor to evaluate or update a street map database.


In a another embodiment, a system and method for updating a street map database, comprises displaying a stored street use parameter to a driver, wherein the street use parameter is associated with vehicle operation on a street being used by the driver; and receiving a replacement value for the street use parameter from the driver. A street map database in a vehicle may be updated by replacing the stored street use parameter with the replacement value. A central street map database may be updated by replacing the stored street use parameter with the replacement value. The street use parameter may be selected from the group consisting of, for example, a speed limit, a traffic flow direction, a traffic signal status, a road condition, a traffic density, a road construction status, a street name, a municipality name, and a road hazard.





BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present invention, and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:



FIG. 1 is a high-level block diagram of a vehicle monitoring system according to one embodiment;



FIG. 2 is a high-level block diagram of a system for detecting wireless device usage in moving vehicles;



FIG. 3 is a flowchart illustrating a method according to one embodiment described herein;



FIG. 4 illustrates one embodiment of a street mapping data display;



FIG. 5 illustrates another embodiment of a street mapping data display;



FIG. 6 illustrates a further embodiment of a street mapping data display; and



FIG. 7 illustrates an alternative embodiment of a street mapping data display.





DETAILED DESCRIPTION

The present invention provides many applicable inventive concepts that can be embodied in a wide variety of specific contexts. The specific embodiments discussed are merely illustrative of specific ways to make and use the invention, and do not limit the scope of the invention.


With reference to FIG. 1, there is shown vehicle monitoring unit 101 that is coupled to one or more systems in vehicle 102. Processor 103 controls the operation of monitoring unit 101. Processor 103 may be a general use processing device having software designed to control unit 101. Alternatively, processor 103 may be a specially designed circuit or device, such as an application specific integrated circuit (ASIC), that is particularly designed for use in unit 101. Processor 103 may use firmware or software, such as an operating system, for control and operation. Operating firmware, software and other data may be stored in random access memory (RAM) 104, read only memory (ROM) 105, electrically erasable programmable memory (EEPROM) devices, or other storage devices, such as magnetic media.


Monitoring unit 101 includes one or more vehicle system interfaces 106 that allow unit 101 to interact with systems in vehicle 102, such as vehicle ignition system 107 and vehicle electrical system 108. Signals exchanged between interface 106 and vehicle ignition system 107 may allow monitoring unit 101 to determine the operating status of vehicle 102 and to command the ignition system to start or shutdown the engine of vehicle 102. Signals exchanged between interface 106 and vehicle electrical system 108 may allow monitoring unit 101 to determine the status of other vehicle systems and to command other systems to operate. For example, vehicle electrical system 108 may provide control of the vehicle's horn, interior and/or exterior lights, entertainment system, navigation system, heating and/or air conditioning systems, alarm, or other vehicle system.


Vehicle diagnostic system interface 109 provides a connection between monitoring unit 101 and vehicle diagnostic system 110. Vehicle diagnostic system 110 may be an on-board diagnostic (OBD) II system or a controller area network (CAN) system in vehicle 102 that is accessed via a port or data bus. The OBD/CAN system provides access to engine performance and status data, speedometer, odometer and tachometer data, and data from other vehicle systems. Power supply 111 provides power to monitoring unit 101. Power supply 111 may be a self-contained battery, for example, or it may be coupled to another power source, such as vehicle battery 112. There may be a connection between power supply 111 and vehicle battery 112 or power supply 111 may receive vehicle power via the vehicle's OBD/CAN bus, for example.


In addition to vehicle sensors and diagnostic systems, such as OBD/CAN 110, monitoring unit 101 may be coupled to other original equipment and aftermarket sensors 113 in vehicle 102. For example, monitoring unit 101 may be coupled an RF transmission sensor, which is configured to detect transmissions such as cellular voice and data signals that originate from or are received at vehicle 102, such as the sensors described in U.S. patent application Ser. No. 11/866,247, entitled “System and Method for Detecting Use of a Wireless Device in a Moving Vehicle,” filed Oct. 2, 2007, the disclosure of which is hereby incorporated herein by reference in its entirety. Other sensors may include, for example, seatbelt use sensors, alcohol or ethanol vapor sensors, cameras, microphones, accelerometers, adaptive control devices, angular acceleration sensors, traction control, ABS, or crash detectors.


Monitoring unit 101 further includes geographic position locating system 114, which provides location information for vehicle 102, such as a latitude/longitude, street address, or map coordinates, for example. In one embodiment, geographic position locating system 114 may be a global positioning system (GPS) that uses satellite signals to determine location. Other navigation or location-determining systems may also be used, such as inertial navigation systems that update a vehicle's location as it moves from a known position or terrestrial-based radio navigation systems, such as Long Range Aid to Navigation (LORAN). In other embodiments, position locating system 114 may use transmissions or data from cellular or wireless network towers to determine a geographical location.


Monitoring unit 101 may include one or more systems that provide communications with other devices and systems. For example, monitoring unit 101 may include cellular or mobile telephone transmitter/receiver 115 that allows unit 101 to communicate with other devices and to send or receive data via a cellular or mobile network. Satellite transmitter/receiver 116 allows unit 101 to communicate with other devices and to send or receive data via satellite network communications. Bluetooth transmitter/receiver 117 allows unit 101 to communicate with other devices that have Bluetooth capability. Data network transmitter/receiver 118 allows unit 101 to communicate via networks, such as data communication networks using WiFi, IEEE 802.11, WiMAX, or other standards or protocols, for example. Monitoring unit 101 may further include one or more antennas 119 to support such communications. Antennas 119 may be internal to monitoring unit 101, may be formed as an integral part of a housing for unit 101, may be externally mounted on vehicle 102, or may be embodied in any antenna configuration now known or later developed.


Vehicle monitoring unit 101 may also be used to provide information, such as vehicle status or location, to a driver and passengers in vehicle 102 using driver displays and interface 120. For example, processor 103 may be configured to identify alarm conditions, such as when vehicle 102 is operated outside of preselected conditions, and to provide feedback or alarms to the driver. Upon detection of an alarm condition, processor 103 may present a warning to the driver, such as text messages, alarm horn, audible tone or message, or a visual warning via driver displays and interface 120. Driver displays and interface 120 may include, for example, speakers, horns, warning lights, keypads, graphics, text or image display screens, or touch-screen displays. Possible displays may include the vehicle's OEM equipment.


Driver displays and interface 120 may also provide position and routing data to the driver, such as street maps, maps of current or destination locations, suggested or actual routes, vehicle heading, vehicle speed, estimated trip duration, predicted destination arrival time, points of interest, and the like. The position and routing information may be provided to driver display and interface 120 from processor 103 or from geographic position locating system 114, for example. Vehicle monitoring unit 101 may further include street mapping database 121 for use with geographic position locating system 114 and/or processor 103. For example, street mapping database 121 may include street maps for multiple locations and street data for specific streets, such as posted speed limits, lane number and direction, road conditions, and traffic conditions. The data in street mapping database 121 may be stored in a compact disc (CD), digital video disc (DVD), random access memory, read only memory, electrically erasable programmable memory, or other magnetic media or electronic storage.


In other embodiments, street mapping database 121 may be stored in RAM 104 or ROM 105, or in geographic position locating system 114. In one embodiment, geographic position locating system 114 or processor 103 determine a current location of vehicle 102 and use data from street mapping database 121 to display a map of the current location to the driver via displays and interfaces 120, such as the current street on which vehicle 102 is driving. Additional information may be presented to the driver, such as a street name, driving direction, posted speed limit, expected traffic conditions, or the like.


In one embodiment, the street mapping information stored in database 121 may be updated, for example, by the driver or a third party. The driver may enter data, such as updated traffic or construction information, updated posted speed limits, street names, or street closures, via driver interfaces 120. Alternatively, or additionally, monitoring device 101 may receive updated street mapping data, such as via a wireless transmissions received by one or more of transceivers 115-118, from a third party, such as monitoring service operator, street mapping data provider, fleet manager, or other person or entity.


Vehicle monitoring unit 101 may also include accelerometer module 122, which includes at least one accelerometer for measuring at least one of lateral (sideways), longitudinal (forward and aft) and vertical acceleration, for determining whether the driver is operating vehicle 102 in an unsafe or aggressive manner. For example, excessive lateral acceleration may be an indication that the driver is operating vehicle 102 at an excessive speed in a turn. Excessive lateral acceleration, defined herein as “hard turns,” may be indicative of aggressive driving by the driver and may contribute to excessive wear on tires and steering components as well as potentially causing the load such as a trailer to shift and potentially overturn. Additionally or alternatively, accelerometers 122 may include a self-contained and tamper-resistant event data recorder or crash data recorder (CDR) similar to that which is shown and disclosed in U.S. Pat. Nos. 6,266,588 and 6,549,834 issued to McClellan et al., (the disclosures of which are hereby incorporated by reference herein in their entirety) and which is commercially known as “Witness” and commercially available from Independent Witness, Inc. of Salt Lake City, Utah. The CDR is adapted to continuously monitor vehicle motion and begin recording upon supra-threshold impacts whereupon it records the magnitude and direction of accelerations or G-forces experienced by the vehicle as well as recording an acceleration time-history of the impact event and velocity change between pre- and post-impact for a configurable duration following an impact. In one embodiment, the recordings are time-date stamped and are available to processor 103 for subsequent transmission to a supervisor or central monitoring facility if vehicle accelerations exceed an impulse threshold. Such accelerometers and CDRs are described in U.S. patent application Ser. No. 11/805,238, entitled “System and Method for Monitoring and Updating Speed-by-Street Data,” filed May 22, 2007, the disclosure of which is hereby incorporated herein by reference in its entirety.



FIG. 2 illustrates monitoring unit 201 installed or mounted in vehicle 202. Monitoring unit 201 may include the elements of monitoring unit 101 and may be coupled to systems in vehicle 202 as illustrated, for example, in FIG. 1. Monitoring unit 201 may be mounted in any location within vehicle 202, such as in a trunk, under a seat, in a glovebox, or on a window or dashboard. Monitoring unit 201 is coupled to one or more antennas 203, which may be used to communicate with one or more satellite or terrestrial communications networks. Monitoring unit 201 may be capable of communicating with one or more networks or systems, such as cellular or mobile telephone network 204, having base stations or cell sites 205 and 206, wireless data network 207, such as a Bluetooth, WiFi, WiMAX or 802.11 network, or satellite 208. Monitoring unit 201 may also be in communication with or receive signals from satellites 213, which may be part of a geographical position locating system, such as a GPS system.


Monitoring unit 201 is coupled to and in communication with on board diagnostic system 209 in vehicle 202. Vehicle monitoring unit 201 has access to certain vehicle operating parameters including, but not limited to, vehicle speed such as via the speedometer, engine speed or throttle position such as via the tachometer, mileage such as via the odometer reading, seat belt status, condition of various vehicle systems including anti-lock-braking (ABS), turn signal, headlight, cruise control activation, adaptive cruise control, traction control, and a multitude of various other diagnostic parameters such as engine temperature, brake wear, and the like. Monitoring unit 201 may also be coupled to driver displays and interfaces, such as warning lights or touch-screen display 223 and/or speaker 224. Monitoring unit 201 may also be coupled to additional sensors 210, such as an RF sensor, camera, microphone, ethanol vapor sensor or the like.


Server 214 may be any processor-based system that is capable of communicating with external networks and processing data associated with wireless device usage and vehicle monitoring units. Server 214 may be coupled to multiple networks, such as cellular network 204 or wireless data network 207, via networks 215 and 216, which couple server 214 to other communication networks, may be any public or private data network, such as an Internet, intranet, extranet, or wide or local area network (WAN/LAN). Server 214 may be coupled to satellite 208 via antenna 222. In one embodiment, users may communicate with server 214 via a local or remote personal computer (PC), laptop computer, or terminal, such as devices 217 or 218. Alternatively, server 214 may communicate with users via a wireless device (not shown) or a wireline connection, such as telephone 219, using, for example, voice signals, an interactive voice response (IVR), a voice response unit (VRU), or dual tone multi-frequency (DTMF) tones. Telephone 219 may be coupled to public switched telephone network (PSTN) 220.


Memory 221 may be used to store information, such as user account data, vehicle data, vehicle monitoring unit information, or street mapping data. Server 214 may access data stored on memory 221 and may store data to memory 221. Users may access memory 221, for example, to enter, update, or edit account data, via terminals or computers 217 and 218. Memory 221 may be internal or external to server 214 and may be located near to or remote from server 214. Communication between monitoring unit 201 and server 214 may be via cellular network 204, data network 207 and/or communication satellite network 208 depending upon availability of each network, the urgency of the message, and/or user configuration.


Vehicle monitoring unit 201 may transmit reports to server 214, such as driving conditions, vehicle operation parameters, or violations of operating requirements or limitations. Server 214 may then take action to record, report and/or mentor this behavior. For example, a user may configure server 214 to take certain action upon detecting that vehicle 202 is speeding. Server 214 may command monitoring unit 201 to broadcast warnings, such as audible messages or tones or visual lights or text, to the driver of vehicle 202. Additionally, server 214 may report the wireless device use to the driver's parent, supervisor, fleet manager or other authority. Such vehicle operation violations may trigger any number of actions preselected by the user and/or default actions in server 214.


The user may configure server 214 to send warning feedback to vehicle 202 upon detection of a potentially unsafe driving condition, such as speeding, driving the wrong way, or other conflicts with street mapping data. Such messages may warn the driver of the type of violation and/or direct the driver to discontinue the action or violation. Server 214 may take further action to warn or mentor the driver, notify a supervisor, or otherwise document the event as appropriate. Server 214 may also provide a report or notification to a supervisor or authority of the potentially unsafe driving conditions, such as by calling a fleet manager or parent via telephone 219 or by sending an email or text message to the supervisor.


Driver performance may be measured using vehicle monitoring equipment that is installed in a vehicle and collects information, such as the vehicle's speed, acceleration, and location. The unit may capture data identifying where the vehicle is driven, when the vehicle is driven, and how the vehicle is driven (i.e. driver performance). One embodiment of a vehicle monitoring unit is described in U.S. patent application Ser. No. 11/805,237, entitled “System and Method for Monitoring Vehicle Parameters and Driver Behavior,” filed May 22, 2007, the disclosure of which is incorporated by reference herein in its entirety. The vehicle monitoring unit may receive inputs from internal and external sources and sensors such as accelerometers, geographic position locating systems, global positioning systems (GPS), vehicle on-board diagnostic systems, seatbelt sensors, wireless device, or cell phone use detectors, alcohol vapor detectors, or trans-dermal ethanol detection. The vehicle monitoring unit may be used to evaluate and grade driver behavior, as described in U.S. patent application Ser. No. 11/755,556, filed on May 30, 2007, entitled “System and Method for Evaluating Driver Behavior,” the disclosure of which is hereby incorporated by reference herein in its entirety. The vehicle monitoring unit may also be used to provide feedback and mentoring to the driver in order improve the driver's performance and driving behavior, such as described in U.S. patent application Ser. No. 11/768,056, filed on Jun. 25, 2007, entitled “System and Method for Monitoring and Improving Driver Behavior,” the disclosure of which is hereby incorporated by reference herein in its entirety.


In one embodiment, vehicle monitoring unit 101 (FIG. 1) may evaluate a driver's performance based upon the operation of vehicle 102 compared to data in street mapping database 121. For example, the speed of vehicle 102 may be compared to posted speeds, road conditions, or traffic conditions stored in street mapping database 121, or the heading of vehicle 102 may be compared to traffic direction data stored in street mapping database 121. If vehicle monitoring unit 101 detects a violation of an operating parameter, then the vehicle monitoring unit may broadcast a warning or other feedback to the driver. In one embodiment, if a vehicle speed that is more than a posted speed stored in street mapping database 121, then a speeding warning is broadcast to the driver. In another embodiment, if a vehicle speed that is too fast for an expected road or traffic condition stored in street mapping database 121, then an audible and/or visual warning or other mentoring feedback may be broadcast to the driver. In another embodiment, if vehicle 102 is driving on a street in the wrong direction compared to a driving direction stored in street mapping database 121, then another audible and/or visual warning or other mentoring feedback may be broadcast to the driver. In addition to such driver warnings, reports or notification may be sent to third parties, such as a supervisor, fleet manager, or parent.


In known driver warning and feedback systems, when a driving violation or alert condition is detected, an audible and/or visual warning is broadcast to the driver noting the type of violation, such as speeding, but the underlying data that triggers the alert is not presented to the driver. For example, if a posted speed of 45 MPH is stored in a street mapping database for a particular street, and a vehicle is traveling at 50 MPH on that street, then the vehicle monitoring unit may broadcast an audible and/or visual speeding warning to the driver and may instruct or recommend to the driver to reduce speed. However, in known driver warning and feedback systems, the vehicle monitoring unit does not identify the underlying data to the driver, such as the posted speed limit stored in the street mapping database. In the example above, when the vehicle monitoring unit determines that the vehicle speed is greater than a posted speed limit stored in a street mapping database, a warning is broadcast, but neither the posted speed limit nor the amount of the violation—such as a number of miles-per-hour or a percentage that the actual speed is exceeding a posted speed limit in the database—are presented to the driver. Accordingly, if the posted speed limit data in the street mapping database is in error, then the driver will be improperly warned or reported for a speeding violation.



FIG. 3 illustrates a flowchart for an exemplary embodiment of a method for using street mapping data. The method illustrated in FIG. 3 may be implemented, for example, using vehicle monitoring unit 101 or 201, but is not intended to be limited to such configurations. Moreover, it will be understood that the steps illustrated in FIG. 3 may be performed in the order indicated, or in any other order, or simultaneously, or in conjunction with other steps or methods. In step 301, a vehicle's current location is determined. The vehicle's location may be determined using, for example, a geographic position locating system, a satellite-based positioning system, a GPS, or a vehicle monitoring unit. The vehicle location may be associated with specific street or roadway. In step 302, a stored posted speed limit for the vehicle's current location is determined. The stored posted speed limit may be retrieved from a street mapping database, such as database 121 (FIG. 1), using the current vehicle location. The stored posted speed limit may be a speed limit for a street or roadway on which the vehicle is traveling. In step 303, the current speed of the vehicle is determined. The vehicle's speed may be determined, for example, using a vehicle monitoring unit, a GPS, a vehicle navigation system, a vehicle speedometer, or determined from data collected from a vehicle on-board diagnostic system. In step 304, the vehicle's current speed is compared to the stored posted speed limit. In step 305, an evaluation is made to determine if the current vehicle speed exceeds the stored posted speed limit.


If the current vehicle speed is at or below the stored posted speed limit, then the process returns to step 301. If the current vehicle speed is above the stored posted speed limit, then the process moves to step 306 in which a warning is displayed to the driver. Alternatively, or additionally, a warning or notice may be sent to a third party, such as a fleet manager, parent, supervisor, or other authority. The driver warning may be a visual display and/or an audible message, horn or other noise and/or in conjunction with a tactile alert. In step 307, the stored posted speed is displayed to the driver. If the driver believes that the stored posted speed is incorrect, then in step 308, the driver may send an indication that the stored posted speed limit is erroneous. The indication from the driver may be, for example, a signal or input to the driver interface 120 (FIG. 1) that identifies a correct or current posted speed limit (step 309), or merely a signal or input that the stored posted speed limit is incorrect. In one embodiment, if a vehicle monitoring unit displays a speeding violation warning to the driver, and the driver believes that he is driving at or under the speed limit, then the driver can compare the displayed stored posted speed limit with an actual observation of a posted speed limit on the street or roadway. The driver may input the correct speed limit into the unit, or the driver may press a button, for example, on vehicle monitoring unit 101 or 201, to indicate that a speeding warning is erroneous. In step 310, the stored posted speed limit may be updated. For example, a stored posted speed limit in database 121 (FIG. 1) may be updated. In another embodiment, the corrected posted speed limit may be transmitted to a third party, such as a service provider for use in updating a master database. In the alternative, the driver may be exceeding the actual posted speed and notice that the device is not alerting them to the speed overage. The device may display an erroneously high speed in which case the driver may depress a button or other possible alert mechanisms so that the speed limit database may be updated.



FIG. 4 illustrates one embodiment of a street mapping display that may be used, for example, to display vehicle location information to a driver. Display 400 may be used, for example, in connection with a GPS or other geographic position locating system to display vehicle location information. Vehicle location is shown by icon 401 located in the middle of display 400. Streets, railroad tracks, rivers, lakes, and other geographic features are displayed on display 400. Heading information may be displayed, for example, using compass 402, which points to North, or using heading direction 403, which displays an approximate or exact vehicle heading. A current street name 404 may also be displayed to the driver. Other current location information, such as a city or county name, may also or additionally be displayed. Routing information 405 may be shown on display 400, such as upcoming turn warning 406, distance to destination 407, and time to destination 408. As is well known, other location, route and destination information may be displayed, such as a turn list or maneuver list for a selected route, an elapsed route timer, alternate routing options, display zoom and pan controls, and current vehicle speed display. In the event that the system has a display, listing the posted speed limit as well as the vehicle's actual speed and/or the differential is desirable. The displayed information may also be provided to the driver in an audible format, such as a spoken message that recites a current street, current city, upcoming turn or routing directions, or warnings.


Display 400 illustrates the typical information provided in a GPS display. However, additional data may be available from a street mapping database, such as posted speed limits, normal traffic direction, expected traffic conditions, or traffic restrictions. This additional information is not provided to the driver in known GPS or navigation systems. FIG. 5 illustrates additional information that may be provided to a driver. Display 500 provides current location 501, which may be a current street address, city, latitude/longitude, and/or other geographic location or coordinates. Other information for the current street, road or other thoroughfare may be displayed, such as the number of traffic lanes 502, a traffic direction 503, which may designate if a street, lane or other portion of a street is two-way, one-way, and/or what direction traffic normally flows. The posted speed limit 504, known construction conditions 505, and general road condition 506 may also be displayed. The street mapping data shown in display 500 may be obtained by querying a vehicle-based street mapping database, such as database 121 (FIG. 1), or retrieved wirelessly from an external database, such as database 221 (FIG. 2).


In one embodiment, the street mapping data may be used to evaluate driver behavior and performance, such as to detect speeding conditions. For example, when the vehicle's current speed exceeds the posted speed limit that is stored in the street mapping database for the current location, a warning may be issued to the driver. Additionally or alternatively, a notice may be sent to a third party when a speeding or other violation occurs. A grace period, such as a number of seconds or minutes, may be used before reporting the violation to a third party in order to allow the driver to correct the violation and thereby avoid third-party notification.



FIG. 6 illustrates one embodiment of a driver display during a violation, such as exceeding a posted speed limit. Display 600 includes visual warning notice 601 that may overlay or replace the usual location information. Warning notice 601 may be accompanied by or replaced by an audible alarm, horn, tone, or recorded or spoken message. Warning notice 601 preferably identifies a violated parameter, such as a posted speed limit or street travel direction. Additional violation information 602 may be presented to the user. For example, the posted speed limit and/or current vehicle speed may be displayed during a speeding violation condition. Due to data entry error, changes in signage, or temporary road conditions, the actual posted speed limit on the street may be different than the stored posted speed limit in the street mapping database. For example, if the posted speed limit data that is stored in the street mapping database was entered as 35 MPH, but the actual posed speed limit is 45 MPH, then the driver will be warned of a speeding condition while driving at a legal speed between 36 MPH and 45 MPH. Existing navigation systems do not provide users with the capability to correct or report such errors. In one embodiment, display 600 provides the driver with an option, such as update button 603, to enter correct data or to report errors.



FIG. 7 illustrates a data correction and/or error reporting display 700. In one embodiment, the driver may select update button or feature 603 to cause display 600 to change to display 700. Displays 400, 500, 600, 700 may be touch screens that allow a user to select features, such as 603, by touching the feature. Alternatively, the user may highlight or otherwise selecting the feature using buttons or switches external to the display or using other inputs to the display, such as a cursor or other highlighting tool. Display 700 displays the stored street mapping data to the driver and allows the driver to identify and report errors and to confirm correct entries in the street mapping data. Like display 500, the street mapping data shown in display 700 may be obtained by querying a vehicle-based street mapping database, such as database 121 (FIG. 1), or retrieved wirelessly from an external database, such as database 221 (FIG. 2).


In one embodiment, the posted speed data 504 may be highlighted or otherwise selected automatically or manually in display 700. Options 701-703 may be provided to the driver. Confirm option 701 may be selected by the driver to confirm that the stored posted speed limit data 504 in the street mapping database is correct. Update option 702 may be selected by the user to initiate a procedure to enter corrected posted speed limit data. For example, after selecting update feature 702, the driver may be presented with a screen or field in which the correct posted speed may be entered. The corrected data may then be used to update or evaluate the street mapping database. Report error option 703 may be used to send a notice to a third party, such as a fleet manager, navigation system manufacturer, or street mapping data provider, that identifies the posted speed limit error. Report error 703 may be used to simply identify that an error may be present or to enter a corrected posted speed limit.


The third party may use the reported error information in a number of ways, such as collecting error reports from a plurality of drivers until the number of error reports for a particular data entry reach a preselected level. For example, instead of correcting the street mapping data after one error report, the third party may conduct a visual inspection of the location to verify the posted speed limit before editing the street mapping database. Alternatively, the third party may wait until multiple drivers report the error before correcting the database, such as waiting for 25, 50 or 100 error reports or some other number of statistically significant error reports from different drivers or vehicles before the posted speed limit stored in the street mapping is changed or updated. This would allow the third party to identify “hot spots” of frequent error reports. The third party may be, for example, a monitoring service operator, street mapping data provider, fleet manager, or other person or entity that is responsible for maintaining the street mapping database. Additionally, individuals that report database speed errors may have their system adjusted to a temporary higher speed limit until the speed database error can be assessed and corrected if necessary. At that point the temporary speed adjustment would default the database speed. Each reported speed inaccuracy would also be reported to track potential excessive or fraudulent speed database errors.


It will be understood that displays 500 and 700 may be available at anytime and not just during warning conditions. For example, a user may highlight or select vehicle icon 401 or street name 404 (FIG. 4) to request street mapping data 700. Once the street mapping data display 700 is shown, the driver may review the data and verify the data or correct or report errors in the data. Additionally, it will be understood that the correctable or reportable errors are not limited to posted speed limits, but that any street mapping database field may be reviewed and corrected using the embodiments described herein. Moreover, other warnings may also be provided to the driver. For example, if the street mapping data shows that a particular street is configured for one-way traffic in a southern direction, and the vehicle is traveling north-bound on that street, then a warning may be provided to the driver, similar to what is shown in display 600 (FIG. 6). The warning may display “Warning: Traffic Direction,” for example. If the driver believes that the warning is in error, the driver may select display 500 or 700 to view and possibly correct traffic direction 503.


Although the present invention and its advantages have been described in detail, it should be understood that various changes, substitutions and alterations can be made herein without departing from the spirit and scope of the invention as defined by the appended claims. Moreover, the scope of the present application is not intended to be limited to the particular embodiments of the process, machine, manufacture, composition of matter, means, methods and steps described in the specification. As one of ordinary skill in the art will readily appreciate from the disclosure of the present invention, processes, machines, manufacture, compositions of matter, means, methods, or steps, presently existing or later to be developed, that perform substantially the same function or achieve substantially the same result as the corresponding embodiments described herein may be utilized according to the present invention. Accordingly, the appended claims are intended to include within their scope such processes, machines, manufacture, compositions of matter, means, methods, or steps.

Claims
  • 1. In an on-board vehicle monitoring system that monitors and reports real-time driving violations to a driver of a vehicle in order to assist the driver in knowing when a violation is occurring, a method of permitting the driver to identify perceived errors in reported violations which are monitored while driving the vehicle, comprising: detecting at a plurality of sensors installed in a vehicle parameters from which data is derived that defines the following information: i) where the vehicle is being driven, ii) date and time as to when the vehicle is being driven, iii) road conditions, iv) how the vehicle is being operated, v) whether vehicle equipment is being correctly used, and vi) one or more driver behaviors that are related to safe driving behaviors;inputting to an on-board vehicle monitoring system which comprises system memory and one or more processors for data processing, i) the detected parameters from said plurality of sensors installed in the vehicle, ii) thresholds which define criteria against which the detected parameters are evaluated and iii) identification information for the driver of the vehicle;the on-board vehicle monitoring system evaluating the input detected parameters by performing the following computer-implemented data processing: determining a particular date, time and street where the vehicle is traveling; anddetermining from the input parameters and the thresholds whether one or more of the following violations is occurring: the vehicle is being operated in an unsafe manner, the driver of the vehicle is engaging in unsafe behavior, or vehicle equipment is failing to be properly utilized or is being improperly utilized;the on-board vehicle monitoring system broadcasting a warning to the driver when a violation is determined to occur;the on-board vehicle monitoring system identifying the particular type of violation for which said warning is broadcast to the driver so that the driver is aware of the type of violation;in response to said broadcast warning, and in response to an observation by the driver that the broadcast warning is inconsistent with actual driving conditions, at the on-board vehicle monitoring system, activating in response to a single driver input a real-time error indication that said broadcast warning issued by the vehicle monitoring system to the driver of the vehicle is an error based on the vehicle driver's observation of the actual traffic conditions or vehicle operation; andso that the most current parameters are used to evaluate the driver, in response to said activation by the driver of said error indication, the vehicle monitoring system storing in system memory the data for the error indication, including storing at least the following for each particular type of violation for which an error indication was input by said driver: identification of the vehicle,identification of the driver,a particular street location,the date and time the vehicle was traveling on the particular street, andthe detected parameters giving rise to said particular type of violation for which an error indication was input by said driver.
  • 2. The method of claim 1, wherein broadcasting the warning to the driver comprises broadcasting at least one of an audible warning to the driver and a visual warning to the driver.
  • 3. The method of claim 1, wherein identifying the particular type of violation for which said warning is broadcast comprises including an indication of a limitation for the street on which the driver is traveling, which comprises advising the driver of a posted speed limit.
  • 4. The method of claim 1, wherein broadcasting the warning and identifying the particular type of violation for which said warning is broadcast comprises playing a spoken message to the driver.
  • 5. The method of claim 1, wherein the identified violation is based on at least one of the following: use of a cell phone while driving, improper use of vehicle equipment, or failure to use vehicle equipment.
  • 6. The method of claim 1, wherein the identified violation is a traffic direction.
  • 7. The method of claim 1, further comprising transmitting the data for the error indication to a third party.
  • 8. The method of claim 1, further comprising sending to a central server or database said data for the error indication in order to enable evaluation of the driver using the most current parameters.
  • 9. One or more hardware memory devices containing computer-executable instructions, which, when executed by one or more processors, implement a method of mentoring a driver of a vehicle to provide the driver with awareness driving violations that occur while driving, the computer-implemented method comprising: detecting at a plurality of sensors installed in a vehicle parameters from which data is derived that defines the following information: i) where the vehicle is being driven, ii) date and time as to when the vehicle is being driven, iii) road conditions, iv) how the vehicle is being operated, v) whether vehicle equipment is being correctly used, and vi) one or more driver behaviors that are related to safe driving behaviors;inputting to an on-board vehicle monitoring system which comprises system memory and one or more processors for data processing, i) the detected parameters from said plurality of sensors installed in the vehicle, ii) thresholds which define criteria against which the detected parameters are evaluated, and iii) identification information for the driver of the vehicle;the on-board vehicle monitoring system evaluating the input detected parameters by performing the following computer-implemented data processing: determining a particular date, time and street where the vehicle is traveling; anddetermining from the input parameters and the thresholds whether one or more of the following violations is occurring: the vehicle is being operated in an unsafe manner, the driver of the vehicle is engaging in unsafe behavior, or vehicle equipment is failing to be properly utilized or is being improperly utilized.the on-board vehicle monitoring system broadcasting a warning to the driver when a violation is determined to occur;the on-board vehicle monitoring system identifying the particular type of violation for which said warning is broadcast to the driver so that the driver is aware of the type of violation;in response to said broadcast warning, and in response to an observation by the driver that the broadcast warning is inconsistent with actual driving conditions, at the on-board vehicle monitoring system, activating in response to a single driver input a real-time error indication that said broadcast warning issued by the vehicle monitoring system to the driver of the vehicle is an error based on the vehicle driver's observation of the actual traffic conditions or vehicle operation; andso that the most current parameters are used to evaluate the driver, the vehicle monitoring system storing in system memory the data for the error indication, including storing at least the following for each particular type of violation for which an error indication was input by said driver: identification of the vehicleidentification of the driver,a particular street locationthe date and time the vehicle was traveling on the particular street, andthe detected parameters giving rise to said particular type of violation for which an error indication was input by the driver.
  • 10. The method of claim 9, further comprising displaying the current vehicle location on a map.
  • 11. The method of claim 9, wherein the particular type of violation for which said warning is broadcast to the driver comprises at least one of posted speed limits and traffic directions.
  • 12. The method of claim 9, wherein the particular type of violation for which said warning is broadcast to the driver comprises displaying a stored value of the particular type of violation broadcast to the driver.
  • 13. The method of claim 9, further comprising sending to a central server or database said data for the error indication in order to enable evaluation of the driver using the most current parameters.
  • 14. The method of claim 13, wherein the database is a street mapping database and wherein said server is monitored by a supervisor of the driver.
  • 15. The method of claim 13, further comprising receiving a replacement entry for the stored value based on the data for the error indication.
  • 16. The method of claim 15, further comprising sending the replacement entry to at least one of a street mapping database provider and a supervisor.
  • 17. An on-board vehicle monitoring system that monitors and reports real-time driving violations to a driver of a vehicle in order to assist the driver in knowing when a violation is occurring, and that permits the driver to identify perceived errors in reported violations which are monitored while driving the vehicle, comprising: a plurality of sensors installed in a vehicle parameters from which data is derived that defines the following information: i) where the vehicle is being driven, ii) date and time as to when the vehicle is being driven, iii) road conditions, iv) how the vehicle is being operated, v) whether vehicle equipment is being correctly used, and vi) one or more driver behaviors that are related to safe driving behaviors;inputting to an on-board vehicle monitoring system which comprises system memory and one or more processors for data processing, i) the detected parameters from said plurality of sensors installed in the vehicle, ii) thresholds which define criteria against which the detected parameters are evaluated, and iii) identification information for the driver of the vehicle;the on-board vehicle monitoring system evaluating the input detected parameters by performing the following computer-implemented data processing: determining a particular date, time and street where the vehicle is traveling; anddetermining from the input parameters and the thresholds whether one or more of the following violations is occurring: the vehicle is being operated in an unsafe manner, the driver of the vehicle is engaging in unsafe behavior, or vehicle equipment is failing to be properly utilized or is being improperly utilized;the on-board vehicle monitoring system broadcasting a warning to the driver when a violation is determined to occur;the on-board vehicle monitoring system identifying the particular type of violation for which said warning is broadcast to the driver so that the driver is aware of the type of violation;in response to said broadcast warning, and in response to an observation by the driver that the broadcast warning is inconsistent with actual driving conditions, at the on-board vehicle monitoring system, activating in response to a single driver input a real-time error indication that said broadcast warning issued by the vehicle monitoring system to the driver of the vehicle is an error based on the vehicle driver's observation of the actual traffic conditions or vehicle operation; andso that the most current parameters are used to evaluate the driver, the vehicle monitoring system storing in system memory the data for the error indication, including storing at least the following for each particular type of violation for which an error indication was input by said driver: identification of the vehicle,identification of the driver,a particular street location,the date and time the vehicle was traveling on the particular street, andthe detected parameters giving rise to said particular type of violation for which an error indication was input by said driver.
  • 18. The system of claim 17, wherein the particular type of violation for which said warning is broadcast to the driver comprises at least one of posted speed limits and traffic directions.
  • 19. The system of claim 17, further comprising a display operable to communicate a stored value of the particular type of violation for which said warning is broadcast to the driver.
  • 20. The system of claim 19, wherein the processor is further operable to receive an indication that the stored value is incorrect.
  • 21. The system of claim 20, wherein the processor is further operable to send the indication to at least one of a street mapping database provider and a supervisor of the driver.
  • 22. The system of claim 19, wherein the processor is further operable to receive a replacement entry for the stored value based on said data for the error indication.
  • 23. The system of claim 22, wherein the processor is further operable to send the replacement entry to at least one of a street mapping database provider and a supervisor.
  • 24. The system of claim 17, wherein the broadcast warning is a visual warning.
  • 25. The system of claim 17, further comprising a central server or database to which said data for the error indication is sent in order to enable evaluation of the driver using the most current parameters.
  • 26. The system of claim 25, wherein the database is a street mapping database and wherein said server is monitored by a supervisor of the driver.
US Referenced Citations (629)
Number Name Date Kind
3975708 Lusk Aug 1976 A
4241403 Schultz Dec 1980 A
4344136 Panik Aug 1982 A
4369427 Drebinger et al. Jan 1983 A
4395624 Wartski Jul 1983 A
4419654 Funk Dec 1983 A
4458535 Juergens Jul 1984 A
4591823 Horvat May 1986 A
4785280 Fubini Nov 1988 A
4843578 Wade Jun 1989 A
4926417 Futami May 1990 A
4939652 Steiner Jul 1990 A
5006829 Miyamoto et al. Apr 1991 A
5032821 Domanico Jul 1991 A
5064151 Cerimele et al. Nov 1991 A
5074144 Krofchalk et al. Dec 1991 A
5119504 Durboraw, III Jun 1992 A
5223844 Mansell et al. Jun 1993 A
5225842 Brown et al. Jul 1993 A
5303163 Ebaugh et al. Apr 1994 A
5305214 Komatsu Apr 1994 A
5309139 Austin May 1994 A
5311197 Sorden et al. May 1994 A
5325082 Rodriguez Jun 1994 A
5347260 Ginzel Sep 1994 A
5353023 Mitsugi Oct 1994 A
5359528 Haendel Oct 1994 A
5365114 Tsurushima Nov 1994 A
5365451 Wang et al. Nov 1994 A
5381155 Gerber Jan 1995 A
5394136 Lammers et al. Feb 1995 A
5400018 Scholl Mar 1995 A
5414432 Penny, Jr. et al. May 1995 A
5422624 Smith Jun 1995 A
5424584 Matsuda Jun 1995 A
5430432 Camhi et al. Jul 1995 A
5436612 Aduddell Jul 1995 A
5436837 Gerstung Jul 1995 A
5446659 Yamawaki Aug 1995 A
5453939 Hoffman Sep 1995 A
5457439 Kuhn Oct 1995 A
5475597 Buck Dec 1995 A
5485116 Cserveny et al. Jan 1996 A
5485161 Vaughn Jan 1996 A
5499182 Ousborne Mar 1996 A
5521579 Bernhard May 1996 A
5521580 Kaneko May 1996 A
5525960 McCall Jun 1996 A
5546305 Kondo Aug 1996 A
5548273 Nicol Aug 1996 A
5570087 Lemelson Oct 1996 A
5581464 Woll Dec 1996 A
5586130 Doyle Dec 1996 A
5600558 Mearek Feb 1997 A
5612875 Haendel Mar 1997 A
5617086 Klashinsky et al. Apr 1997 A
5625337 Medawar Apr 1997 A
5638077 Martin Jun 1997 A
5642284 Parupalli Jun 1997 A
5648755 Yagihashi Jul 1997 A
5659289 Zonkoski Aug 1997 A
5689067 Klein Nov 1997 A
5708417 Tallman Jan 1998 A
5717374 Smith Feb 1998 A
5719771 Buck Feb 1998 A
5723768 Ammon Mar 1998 A
5731285 Pavone et al. Mar 1998 A
5731785 Lemelson et al. Mar 1998 A
5740548 Hudgens Apr 1998 A
5742915 Stafford Apr 1998 A
5751245 Janky et al. May 1998 A
5764139 Nojima Jun 1998 A
5767767 Lima Jun 1998 A
5777580 Janky et al. Jul 1998 A
5795997 Gittins Aug 1998 A
5797134 McMillan et al. Aug 1998 A
5801618 Jenkins Sep 1998 A
5801948 Wood Sep 1998 A
5815071 Doyle Sep 1998 A
5819090 Wolf et al. Oct 1998 A
5819198 Peretz Oct 1998 A
5825283 Camhi Oct 1998 A
5825284 Dunwoody Oct 1998 A
5829782 Breed et al. Nov 1998 A
5844475 Horie Dec 1998 A
5847271 Poublon Dec 1998 A
5862500 Goodwin Jan 1999 A
5867093 Dodd Feb 1999 A
5877678 Donoho Mar 1999 A
5880674 Ufkes Mar 1999 A
5880958 Helms et al. Mar 1999 A
5883594 Lau Mar 1999 A
5892434 Carlson Apr 1999 A
5907277 Tokunaga May 1999 A
5914654 Smith Jun 1999 A
5918180 Dimino Jun 1999 A
5926087 Busch Jul 1999 A
5928291 Jenkins et al. Jul 1999 A
5933080 Nojima Aug 1999 A
5941915 Federle et al. Aug 1999 A
5945919 Trask Aug 1999 A
5949330 Hoffman Sep 1999 A
5949331 Schofield Sep 1999 A
5952941 Mardirossian Sep 1999 A
5954781 Slepian Sep 1999 A
5955942 Slifkin Sep 1999 A
5957986 Coverdill Sep 1999 A
5964816 Kincaid Oct 1999 A
5969600 Tanguay Oct 1999 A
5974356 Doyle et al. Oct 1999 A
5978737 Pawlowski Nov 1999 A
5982278 Cuvelier Nov 1999 A
5987976 Sarangapani Nov 1999 A
5999125 Kurby Dec 1999 A
6002327 Boesch Dec 1999 A
6008724 Thompson Dec 1999 A
6018293 Smith Jan 2000 A
6026292 Coppinger et al. Feb 2000 A
6028508 Mason Feb 2000 A
6028510 Tamam Feb 2000 A
6037861 Ying Mar 2000 A
6037862 Ying Mar 2000 A
6038496 Dobler Mar 2000 A
6044315 Honeck Mar 2000 A
6059066 Lary May 2000 A
6060989 Gehlot May 2000 A
6064886 Perez et al. May 2000 A
6064928 Wilson May 2000 A
6064970 McMillan et al. May 2000 A
6067008 Smith May 2000 A
6067009 Hozuka May 2000 A
6072388 Kyrtsos Jun 2000 A
6073007 Doyle Jun 2000 A
6075458 Ladner et al. Jun 2000 A
6078853 Ebner Jun 2000 A
6081188 Kutlucinar Jun 2000 A
6084870 Wooten et al. Jul 2000 A
6094149 Wilson Jul 2000 A
6098048 Dashefsky Aug 2000 A
6100792 Ogino Aug 2000 A
6104282 Fragoso Aug 2000 A
6108591 Segal et al. Aug 2000 A
6112145 Zachman Aug 2000 A
6121922 Mohan Sep 2000 A
6124810 Segal et al. Sep 2000 A
6130608 McKeown Oct 2000 A
6131067 Girerd et al. Oct 2000 A
6133827 Alvey Oct 2000 A
6138516 Tillman Oct 2000 A
6141610 Rothert Oct 2000 A
6147598 Murphy Nov 2000 A
6161072 Clapper Dec 2000 A
6172602 Hasfjord Jan 2001 B1
6178374 Möhlenkamp et al. Jan 2001 B1
6184784 Shibuya Feb 2001 B1
6185501 Smith Feb 2001 B1
6195015 Jacobs et al. Feb 2001 B1
6198995 Settles Mar 2001 B1
6204756 Senyk Mar 2001 B1
6204757 Evans Mar 2001 B1
6208240 Ledesma Mar 2001 B1
6212455 Weaver Apr 2001 B1
6216066 Goebel Apr 2001 B1
6222458 Harris Apr 2001 B1
6225898 Kamiya May 2001 B1
6227862 Harkness May 2001 B1
6229438 Kutlucinar May 2001 B1
6232873 Dilz May 2001 B1
6246933 Bague Jun 2001 B1
6246948 Thakker Jun 2001 B1
6247360 Anderson Jun 2001 B1
6249219 Perez Jun 2001 B1
6253129 Jenkins et al. Jun 2001 B1
6253151 Ohler et al. Jun 2001 B1
6255892 Gärtner Jul 2001 B1
6255939 Roth Jul 2001 B1
6262657 Okuda et al. Jul 2001 B1
6262658 O'Connor Jul 2001 B1
6265989 Taylor Jul 2001 B1
6266588 McClellan Jul 2001 B1
6278361 Magiawala Aug 2001 B1
6282491 Bochmann et al. Aug 2001 B1
6285931 Hattori Sep 2001 B1
6289332 Menig Sep 2001 B2
6294988 Shomura Sep 2001 B1
6294989 Schofield Sep 2001 B1
6295492 Lang Sep 2001 B1
6297768 Allen, Jr. Oct 2001 B1
6301533 Markow Oct 2001 B1
6306063 Horgan et al. Oct 2001 B1
6308120 Good Oct 2001 B1
6308134 Croyle et al. Oct 2001 B1
6313742 Larson Nov 2001 B1
6314367 Ohler et al. Nov 2001 B1
6320497 Fukumoto Nov 2001 B1
6331825 Ladner et al. Dec 2001 B1
6333686 Waltzer Dec 2001 B1
6337653 Buchler Jan 2002 B1
6339739 Folke Jan 2002 B1
6339745 Novik Jan 2002 B1
6343301 Halt et al. Jan 2002 B1
6344805 Yasui Feb 2002 B1
6351211 Bussard Feb 2002 B1
6351709 King et al. Feb 2002 B2
6356188 Meyers Mar 2002 B1
6356822 Diaz Mar 2002 B1
6356833 Jeon Mar 2002 B2
6356836 Adolph Mar 2002 B1
6359554 Skibinski Mar 2002 B1
6362730 Razavi Mar 2002 B2
6362734 McQuade Mar 2002 B1
6366199 Osborn Apr 2002 B1
6378959 Lesesky Apr 2002 B2
6385533 Halt et al. May 2002 B1
6389340 Rayner May 2002 B1
6393348 Ziegler May 2002 B1
6401029 Kubota et al. Jun 2002 B1
6404329 Hsu Jun 2002 B1
6405112 Rayner Jun 2002 B1
6405128 Bechtolsheim et al. Jun 2002 B1
6415226 Kozak Jul 2002 B1
6424268 Isonaga Jul 2002 B1
6427687 Kirk Aug 2002 B1
6430488 Goldman Aug 2002 B1
6433681 Foo Aug 2002 B1
6438472 Tano et al. Aug 2002 B1
6441732 Laitsaari Aug 2002 B1
6449540 Rayner Sep 2002 B1
6459365 Tamura Oct 2002 B2
6459367 Green Oct 2002 B1
6459369 Wang Oct 2002 B1
6459961 Obradovich Oct 2002 B1
6459969 Bates Oct 2002 B1
6462675 Humphrey Oct 2002 B1
6472979 Schofield Oct 2002 B2
6476763 Allen, Jr. Nov 2002 B2
6480106 Crombez Nov 2002 B1
6484035 Allen, Jr. Nov 2002 B2
6484091 Shibata Nov 2002 B2
6493650 Rodgers Dec 2002 B1
6512969 Wang Jan 2003 B1
6515596 Awada Feb 2003 B2
6519512 Haas Feb 2003 B1
6523912 Bond et al. Feb 2003 B1
6525672 Chainer Feb 2003 B2
6526341 Bird et al. Feb 2003 B1
6529159 Fan et al. Mar 2003 B1
6535116 Zhou Mar 2003 B1
6542074 Tharman Apr 2003 B1
6542794 Obradovich Apr 2003 B2
6549834 McClellan Apr 2003 B2
6552682 Fan et al. Apr 2003 B1
6556905 Mittelsteadt Apr 2003 B1
6559769 Anthony May 2003 B2
6564126 Lin May 2003 B1
6567000 Slifkin May 2003 B2
6571168 Murphy May 2003 B1
6577946 Myr Jun 2003 B2
6587759 Obradovich Jul 2003 B2
6594579 Lowrey Jul 2003 B1
6599243 Woltermann Jul 2003 B2
6600985 Weaver Jul 2003 B2
6604033 Banet Aug 2003 B1
6609063 Bender et al. Aug 2003 B1
6609064 Dean Aug 2003 B1
6611740 Lowrey Aug 2003 B2
6611755 Coffee Aug 2003 B1
6615137 Lutter et al. Sep 2003 B2
6622085 Amita et al. Sep 2003 B1
6629029 Giles Sep 2003 B1
6630884 Shanmugham Oct 2003 B1
6631322 Arthur et al. Oct 2003 B1
6633811 Aumayer Oct 2003 B1
6636790 Lightner Oct 2003 B1
6639512 Lee Oct 2003 B1
6643578 Levine Nov 2003 B2
6651001 Apsell Nov 2003 B2
6654682 Kane et al. Nov 2003 B2
6657540 Knapp Dec 2003 B2
6662013 Takiguchi et al. Dec 2003 B2
6662141 Kaub Dec 2003 B2
6664922 Fan Dec 2003 B1
6665613 Duvall Dec 2003 B2
6674362 Yoshioka Jan 2004 B2
6675085 Straub Jan 2004 B2
6677854 Dix Jan 2004 B2
6678612 Khawam Jan 2004 B1
6696932 Skibinski Feb 2004 B2
6701234 Vogelsang Mar 2004 B1
6703925 Steffel Mar 2004 B2
6714894 Tobey et al. Mar 2004 B1
6718235 Borugian Apr 2004 B1
6718239 Rayner Apr 2004 B2
6718258 Barton Apr 2004 B1
6720889 Yamaki et al. Apr 2004 B2
6727809 Smith Apr 2004 B1
6728542 Meda Apr 2004 B2
6728605 Lash Apr 2004 B2
6732031 Lowrey May 2004 B1
6732032 Lowrey May 2004 B1
6737962 Mayor May 2004 B2
6741169 Magiawala May 2004 B2
6741170 Alrabady May 2004 B2
6745153 White Jun 2004 B2
6748322 Fernandez Jun 2004 B1
6750761 Newman Jun 2004 B1
6750762 Porter Jun 2004 B1
6756916 Yanai Jun 2004 B2
6759952 Dunbridge Jul 2004 B2
6766244 Obata et al. Jul 2004 B2
6768448 Farmer Jul 2004 B2
6775602 Gordon Aug 2004 B2
6778068 Wolfe Aug 2004 B2
6778885 Agashe et al. Aug 2004 B2
6784793 Gagnon Aug 2004 B2
6784832 Knockeart et al. Aug 2004 B2
6788196 Ueda Sep 2004 B2
6788207 Wilkerson Sep 2004 B2
6792339 Basson Sep 2004 B2
6795017 Puranik et al. Sep 2004 B1
6798354 Schuessler Sep 2004 B2
6803854 Adams et al. Oct 2004 B1
6807481 Gastelum Oct 2004 B1
6813549 Good Nov 2004 B2
6819236 Kawai Nov 2004 B2
6822557 Weber Nov 2004 B1
6832141 Skeen et al. Dec 2004 B2
6845314 Fosseen Jan 2005 B2
6845316 Yates Jan 2005 B2
6845317 Craine Jan 2005 B2
6847871 Malik et al. Jan 2005 B2
6847872 Bodin Jan 2005 B2
6847873 Li Jan 2005 B1
6847887 Casino Jan 2005 B1
6850841 Casino Feb 2005 B1
6859039 Horie Feb 2005 B2
6859695 Klausner Feb 2005 B2
6865457 Mittelsteadt Mar 2005 B1
6867733 Sandhu et al. Mar 2005 B2
6868386 Henderson et al. Mar 2005 B1
6870469 Ueda Mar 2005 B2
6873253 Veziris Mar 2005 B2
6873261 Anthony Mar 2005 B2
6873998 Dorum et al. Mar 2005 B1
6877007 Hentzel et al. Apr 2005 B1
6879894 Lightner Apr 2005 B1
6885293 Okumura Apr 2005 B2
6888495 Flick May 2005 B2
6892131 Coffee May 2005 B2
6894606 Forbes et al. May 2005 B2
6895332 King May 2005 B2
6909398 Knockeart et al. Jun 2005 B2
6909947 Douros et al. Jun 2005 B2
6914523 Munch Jul 2005 B2
6922133 Wolfe Jul 2005 B2
6922616 Obradovich Jul 2005 B2
6922622 Dulin Jul 2005 B2
6925425 Remboski Aug 2005 B2
6928348 Lightner Aug 2005 B1
6937162 Tokitsu Aug 2005 B2
6950013 Scaman Sep 2005 B2
6954140 Holler Oct 2005 B2
6957133 Hunt et al. Oct 2005 B1
6958976 Kikkawa Oct 2005 B2
6960168 Yanagidaira et al. Nov 2005 B2
6965827 Wolfson Nov 2005 B1
6968311 Knockeart et al. Nov 2005 B2
6970075 Cherouny Nov 2005 B2
6970783 Knockeart et al. Nov 2005 B2
6972669 Saito Dec 2005 B2
6980131 Taylor Dec 2005 B1
6981565 Gleacher Jan 2006 B2
6982636 Bennie Jan 2006 B1
6983200 Bodin Jan 2006 B2
6988033 Lowrey Jan 2006 B1
6988034 Marlatt et al. Jan 2006 B1
6989739 Li Jan 2006 B2
7002454 Gustafson Feb 2006 B1
7002579 Olson Feb 2006 B2
7005975 Lehner Feb 2006 B2
7006820 Parker et al. Feb 2006 B1
7019641 Lakshmanan Mar 2006 B1
7023321 Brillon et al. Apr 2006 B2
7023332 Saito Apr 2006 B2
7024318 Fischer Apr 2006 B2
7027808 Wesby Apr 2006 B2
7034705 Yoshioka Apr 2006 B2
7038578 Will May 2006 B2
7042347 Cherouny May 2006 B2
7047114 Rogers May 2006 B1
7049941 Rivera-Cintron May 2006 B2
7054742 Khavakh et al. May 2006 B2
7059689 Lesesky Jun 2006 B2
7069126 Bernard Jun 2006 B2
7069134 Williams Jun 2006 B2
7072753 Eberle Jul 2006 B2
7081811 Johnston Jul 2006 B2
7084755 Nord Aug 2006 B1
7088225 Yoshioka Aug 2006 B2
7089116 Smith Aug 2006 B2
7091880 Sorensen Aug 2006 B2
7098812 Hirota Aug 2006 B2
7099750 Miyazawa Aug 2006 B2
7099774 King Aug 2006 B2
7102496 Ernst Sep 2006 B1
7109850 Kawazoe et al. Sep 2006 B2
7109853 Mattson Sep 2006 B1
7113081 Reichow Sep 2006 B1
7113107 Taylor Sep 2006 B2
7113127 Banet et al. Sep 2006 B1
7117075 Larschan et al. Oct 2006 B1
7119696 Borugian Oct 2006 B2
7124027 Ernst Oct 2006 B1
7124088 Bauer et al. Oct 2006 B2
7129825 Weber Oct 2006 B2
7132934 Allison Nov 2006 B2
7132937 Lu Nov 2006 B2
7132938 Suzuki Nov 2006 B2
7133755 Salman Nov 2006 B2
7135983 Filippov Nov 2006 B2
7138916 Schwartz Nov 2006 B2
7139661 Holze Nov 2006 B2
7142196 Connor et al. Nov 2006 B1
7145442 Wai Dec 2006 B1
7149206 Pruzan Dec 2006 B2
7155259 Bauchot et al. Dec 2006 B2
7155321 Bromley et al. Dec 2006 B2
7161473 Hoshal Jan 2007 B2
7164986 Humphries Jan 2007 B2
7170390 Quiñones Jan 2007 B2
7170400 Cowelchuk Jan 2007 B2
7174243 Lightner Feb 2007 B1
7176813 Kawamata et al. Feb 2007 B2
7180407 Guo Feb 2007 B1
7180409 Brey Feb 2007 B2
7183942 Rock et al. Feb 2007 B2
7187271 Nagata Mar 2007 B2
7196629 Ruoss Mar 2007 B2
7197500 Israni et al. Mar 2007 B1
7216022 Kynast et al. May 2007 B2
7216035 Hörtner May 2007 B2
7218211 Ho May 2007 B2
7218924 McArdle May 2007 B2
7222009 Hijikata May 2007 B2
7225060 O'Conner et al. May 2007 B2
7225065 Hunt May 2007 B1
7228211 Lowrey Jun 2007 B1
7233235 Pavlish Jun 2007 B2
7236862 Kanno Jun 2007 B2
7239948 Nimmo Jul 2007 B2
7256686 Koutsky Aug 2007 B2
7256700 Ruocco Aug 2007 B1
7256702 Isaacs Aug 2007 B2
7260497 Watabe Aug 2007 B2
RE39845 Hasfjord Sep 2007 E
7269507 Cayford Sep 2007 B2
7269530 Lin Sep 2007 B1
7271716 Nou Sep 2007 B2
7273172 Olsen Sep 2007 B2
7280046 Berg Oct 2007 B2
7283904 Benjamin Oct 2007 B2
7286917 Hawkins Oct 2007 B2
7286929 Staton Oct 2007 B2
7289024 Sumcad Oct 2007 B2
7289035 Nathan Oct 2007 B2
7292152 Torkkola Nov 2007 B2
7292159 Culpepper Nov 2007 B2
7298248 Finley Nov 2007 B2
7298249 Avery Nov 2007 B2
7301445 Moughler Nov 2007 B2
7317383 Ihara Jan 2008 B2
7317392 DuRocher Jan 2008 B2
7317927 Staton Jan 2008 B2
7319848 Obradovich Jan 2008 B2
7321294 Mizumaki Jan 2008 B2
7321825 Ranalli Jan 2008 B2
7323972 Nobusawa Jan 2008 B2
7323974 Schmid Jan 2008 B2
7323982 Staton Jan 2008 B2
7327239 Gallant Feb 2008 B2
7327258 Fast Feb 2008 B2
7333883 Geborek Feb 2008 B2
7339460 Lane Mar 2008 B2
7349782 Churchill Mar 2008 B2
7352081 Taurasi Apr 2008 B2
7355508 Mian Apr 2008 B2
7362239 Franczyk et al. Apr 2008 B2
7365639 Yuhara Apr 2008 B2
7366551 Hartley Apr 2008 B1
7375624 Hines May 2008 B2
7376499 Salman May 2008 B2
7378946 Lahr May 2008 B2
7378949 Chen May 2008 B2
7386394 Shulman Jun 2008 B2
7397363 Joao Jul 2008 B2
7421334 Dahlgren et al. Sep 2008 B2
7433889 Barton Oct 2008 B1
7447509 Cossins et al. Nov 2008 B2
7474264 Bolduc et al. Jan 2009 B2
7474269 Mayer et al. Jan 2009 B2
7495547 Lich et al. Feb 2009 B2
7499949 Barton Mar 2009 B2
7565230 Gardner et al. Jul 2009 B2
7584033 Middelsteadt et al. Sep 2009 B2
7589643 Dagci et al. Sep 2009 B2
7660658 Sheynblat Feb 2010 B2
7671727 Flick Mar 2010 B2
7671752 Sofer Mar 2010 B2
7697917 Camp et al. Apr 2010 B2
7739036 Grimm et al. Jun 2010 B2
7747410 Van Esch Jun 2010 B2
7783406 Rothschild Aug 2010 B2
7821421 Tamir et al. Oct 2010 B2
7859392 McClellan et al. Dec 2010 B2
7880642 Gueziec Feb 2011 B2
7898388 Ehrman et al. Mar 2011 B2
7941258 Mittelsteadt et al. May 2011 B1
8044809 Farmer Oct 2011 B2
8090598 Bauer et al. Jan 2012 B2
8188887 Catten et al. May 2012 B2
8314708 Gunderson et al. Nov 2012 B2
8428307 Bradai et al. Apr 2013 B2
8630768 McClellan et al. Jan 2014 B2
20010014849 King et al. Aug 2001 A1
20010018628 Jenkins et al. Aug 2001 A1
20020019703 Levine Feb 2002 A1
20020024444 Hiyama et al. Feb 2002 A1
20020029226 Li et al. Mar 2002 A1
20020111725 Burge Aug 2002 A1
20020126023 Awada Sep 2002 A1
20020128000 do Nascimento Sep 2002 A1
20020173881 Lash et al. Nov 2002 A1
20030016636 Tari et al. Jan 2003 A1
20030045273 Pyhalammi et al. Mar 2003 A1
20030052797 Rock et al. Mar 2003 A1
20030055555 Knockeart et al. Mar 2003 A1
20030060950 McKeown et al. Mar 2003 A1
20030125854 Kawasaki et al. Jul 2003 A1
20030134660 Himmel et al. Jul 2003 A1
20030169185 Taylor Sep 2003 A1
20030191564 Haugse et al. Oct 2003 A1
20040039504 Coffee et al. Feb 2004 A1
20040054687 McDonough Mar 2004 A1
20040056779 Rast Mar 2004 A1
20040066330 Knockeart et al. Apr 2004 A1
20040077339 Martens Apr 2004 A1
20040083041 Skeen et al. Apr 2004 A1
20040107037 Straub Jun 2004 A1
20040107220 Natesan et al. Jun 2004 A1
20040142672 Stankewitz Jul 2004 A1
20040153362 Bauer et al. Aug 2004 A1
20040172418 Dorum et al. Sep 2004 A1
20040176083 Shiao et al. Sep 2004 A1
20040186661 Barton Sep 2004 A1
20040210353 Rice Oct 2004 A1
20040225557 Phelan et al. Nov 2004 A1
20040236474 Chowdhary et al. Nov 2004 A1
20040236475 Chowdhary Nov 2004 A1
20040254698 Hubbard et al. Dec 2004 A1
20040257245 Jo Dec 2004 A1
20040260579 Tremiti Dec 2004 A1
20050021270 Hong et al. Jan 2005 A1
20050064835 Gusler Mar 2005 A1
20050065711 Dahlgren et al. Mar 2005 A1
20050070245 Nath et al. Mar 2005 A1
20050091018 Craft Apr 2005 A1
20050091175 Farmer Apr 2005 A9
20050096809 Skeen et al. May 2005 A1
20050102098 Montealegre et al. May 2005 A1
20050107944 Hovestadt et al. May 2005 A1
20050119002 Bauchot et al. Jun 2005 A1
20050131597 Raz et al. Jun 2005 A1
20050137757 Phelan et al. Jun 2005 A1
20050143903 Park et al. Jun 2005 A1
20050171663 Mittelsteadt et al. Aug 2005 A1
20050184860 Taruki et al. Aug 2005 A1
20050273218 Breed et al. Dec 2005 A1
20060025894 Oconner et al. Feb 2006 A1
20060055565 Kawamata et al. Mar 2006 A1
20060112573 Hillman et al. Jun 2006 A1
20060121951 Perdomo et al. Jun 2006 A1
20060154687 McDowell Jul 2006 A1
20060193749 Ghazarian et al. Aug 2006 A1
20060208169 Breed et al. Sep 2006 A1
20060220905 Hovestadt Oct 2006 A1
20060253307 Warren et al. Nov 2006 A1
20070005404 Raz et al. Jan 2007 A1
20070005609 Breed Jan 2007 A1
20070050130 Grimm et al. Mar 2007 A1
20070057781 Breed Mar 2007 A1
20070061155 Ji et al. Mar 2007 A1
20070126601 Park Jun 2007 A1
20070186923 Poutiatine et al. Aug 2007 A1
20070202929 Satake Aug 2007 A1
20070229234 Smith Oct 2007 A1
20070236342 Hines et al. Oct 2007 A1
20070260363 Miller Nov 2007 A1
20070293206 Lund Dec 2007 A1
20080027642 Winberry et al. Jan 2008 A1
20080030316 Flick Feb 2008 A1
20080046274 Geelen et al. Feb 2008 A1
20080059055 Geelen et al. Mar 2008 A1
20080064413 Breed Mar 2008 A1
20080065325 Geelen et al. Mar 2008 A1
20080082225 Barrett Apr 2008 A1
20080120175 Doering May 2008 A1
20080177469 Geelen et al. Jul 2008 A1
20080221787 Vavrus Sep 2008 A1
20080252487 McClellan et al. Oct 2008 A1
20080255722 McClellan et al. Oct 2008 A1
20080255888 Berkobin Oct 2008 A1
20080258890 Follmer et al. Oct 2008 A1
20080262670 McClellan et al. Oct 2008 A1
20080296968 Culbert Dec 2008 A1
20080319602 McClellan et al. Dec 2008 A1
20090024273 Follmer et al. Jan 2009 A1
20090024419 McClellan et al. Jan 2009 A1
20090079555 Aguirre De Carcer et al. Mar 2009 A1
20090085728 Catten Apr 2009 A1
20100030459 Geelen et al. Feb 2010 A1
20100130182 Rosen May 2010 A1
20100131189 Geelen et al. May 2010 A1
20100134182 Kapoor et al. Jun 2010 A1
20100207787 Catten et al. Aug 2010 A1
20100265074 Namba et al. Oct 2010 A1
20110115618 Catten May 2011 A1
20110179080 Miyazaki et al. Jul 2011 A1
20110267205 McClellan et al. Nov 2011 A1
20120181765 Hill et al. Jul 2012 A1
Foreign Referenced Citations (20)
Number Date Country
2071931 Dec 1993 CA
2307259 Oct 2001 CA
2631103 Nov 2008 CA
197 00 353 Jul 1998 DE
0843177 May 1998 EP
0 921 509 Jun 1999 EP
1811481 Jul 2007 EP
2434346 Jul 2007 GB
2454224 May 2009 GB
2004326492 Nov 2004 JP
2005-250825 Sep 2005 JP
2007235530 Sep 2007 JP
WO 2004019646 Mar 2004 WO
WO 2005003885 Jan 2005 WO
WO 2005109273 Nov 2005 WO
WO2005109369 Nov 2005 WO
WO 2008045320 Aug 2008 WO
WO2008109477 Sep 2008 WO
WO 2013033756 Mar 2013 WO
WO 2013050548 Apr 2013 WO
Non-Patent Literature Citations (54)
Entry
Author: Google Maps, Title: Google Maps, Capture on Dec. 29, 2014, Pertinent Pages: Whole Document.
Ogle, et al.; Accuracy of Global Positioning System for Determining Driver Performance Parameters; Transportation Research Record 1818; Paper No. Feb. 1063; pp. 12-24.
Shen, et al.; A computer Assistant for Vehicle Dispatching with Learning Capabilities; Annals of Operations Research 61; pp. 189-211, 1995.
Tijerina, et al.; Final Report Supplement; Heavy Vehicle Driver Workload Assessment; Task 5: Workload Assessment Protocol; U.S. Department of Transportation; 69 pages, Oct. 1996.
Myra Blanco; Effects of In-Vehicle Information System (IVIS) Tasks on the Information Processing Demands of a Commercial Vehicle Operations (CVO) Driver; 230 pages, 1999.
Zhu et al., “A Small Low-Cost Hybrid Orientation system and Its Error Analysis”, Sensors Journal, IEEE—vol. 9, Issue 3, Digital Object Identifier: 10.1109/JSEN.2008.2012196; Publication Year: Mar. 2009, pp. 223-230.
Almazan et al., “Full auto-calibration of a smartphone on board a vehicle using IMU and GPS embedded sensors”, Intelligent Vehicles Symposium (IV), 2013 IEEE; Digital Object Identifier: 10.1109/IVS.2013.6629658; Publication Year: Jun. 2013, pp. 1374-1380.
Lupton et al., “Efficient Integration of Inertial Observations Into Visual SLAM Without Initialization”, Intelligent Robots and Systems, 2009, IROS 2009, IEEE/RSJ International Conference on: Digital Object Identifier: 10.1109/IROS.2009.5354267, Publication Year: Oct. 2009, pp. 1547-1552.
Mungula et al., “Attitude and Heading System Based on EKF Total State Configuration”, Industrial Electronics (ISIE), 2011 IEEE International Symposium on; Digital Object Identifier: 10.1109/ISIE.2011.5984493; Publication Year: Jun. 2011, pp. 2147-2152.
Huddle et al., “Application of Inertial Navigation Systems to Geodetic Position and Gravity Vector Survey”, Decision and Control including the 17th Symposium on Adaptive Processes, 1978 IEEE Conference on; vol. 17, Part 1; Digital Object Identifier: 10.1109/CDC.1978.267967; Publication Year: 1978, pp. 459-465.
Zhao Yan et al., “Attitude Measurement of Driver's Head Based on Accelerometer and Magnetoresistive Sensor”, Fluid Power and Mechatronics (FPM), 2011 International Conference on; Digital Object Identifier: 10.1109/FPM.2011.6045836; Publication Year: Aug. 2011, pp. 613-617.
U.S. Appl. No. 11/805,237, Oct. 28, 2013, Notice of Allowance.
Phuyal B., “An Experiment for a 2-D and 3-D GPS/INS configuration for land vehicle applications”, Position Location and Navigation Symposium, 2004, PLANS 2004, Digital Object Identifier: 10.1109/PLANS.2004.1308987; Publication Year: 2004, pp. 148-152.
Roberts et al., “Position Control of VTOL UAVs using IMU and GPS Measurements”, Decision and Control and European Conference (CDC-ECC), 2011 50th IEEE Conference on, Digital Object Identifier, 10.1109/CDC.2011.6160854, Publication Year: Dec. 2011, pp. 8082-8087.
Cho et al., “Obeservability Analysis of the INS/GPS Navigation System on the Measurements in Land Vehicle Applications”, Control, Automation and Systems, 2007, ICCAS '07, International Conference on Digital Object Identifier: 10.1109/CCAS.2007.4407018, Publication Year: Oct. 2007, pp. 841-846.
U.S. Appl. No. 11/805,238, Jul. 30, 2009, Office Action.
U.S. Appl. No. 11/755,556, Sep. 1, 2009, Office Action.
U.S. Appl. No. 11/779,176, Mar. 17, 2010, Office Action.
U.S. Appl. No. 11/805,238, Apr. 26, 2010, Notice of Allowance.
U.S. Appl. No. 11/755,556, May 4, 2010, Office Action.
U.S. Appl. No. 11/805,237, Nov. 8, 2010, Office Action.
U.S. Appl. No. 11/768,056, Jan. 18, 2011, Office Action.
U.S. Appl. No. 13/012,660, Feb. 16, 2011, Office Action.
U.S. Appl. No. 12/379,154, Aug. 1, 2008, Office Action.
U.S. Appl. No. 11/805,237, Aug. 8, 2011, Office Action.
U.S. Appl. No. 11/779,176, Aug. 18, 2011, Office Action.
U.S. Appl. No. 11/768,056, Sep. 16, 2011, Office Action.
U.S. Appl. No. 11/779,178, Nov. 2, 2011, Office Action.
U.S. Appl. No. 13/012,660, Nov. 14, 2011, Office Action.
U.S. Appl. No. 12/379,154, Jan. 30, 2012, Notice of Allowance.
U.S. Appl. No. 11/805,237, Feb. 1, 2012, Office Action.
U.S. Appl. No. 11/768,056, Feb. 16, 2012, Office Action.
U.S. Appl. No. 13/012,660, Apr. 11, 2012, Office Action.
U.S. Appl. No. 11/779,178, May 31, 2012, Office Action.
U.S. Appl. No. 11/805,237, Jun. 15, 2012, Office Action.
U.S. Appl. No. 11/768,056, Jul. 19, 2012, Office Action.
U.S. Appl. No. 13/012,660, Aug. 1, 2012, Office Action.
U.S. Appl. No. 13/012,660, Nov. 26, 2012, Office Action.
U.S. Appl. No. 11/805,237 Dec. 3, 2012, Office Action.
U.S. Appl. No. 11/779,176 Dec. 3, 2012, Office Action.
U.S. Appl. No. 11/779,178 Dec. 20, 2012, Office Action.
U.S. Appl. No. 13/012,660, Mar. 18, 2013, Office Action.
U.S. Appl. No. 11/779,178, May 9, 2013, Office Action.
U.S. Appl. No. 11/805,237, Jun. 6, 2013, Office Action.
U.S. Appl. No. 11/768,056, Jun. 21, 2013, Office Action.
U.S. Appl. No. 11/779,176, Jul. 1, 2013, Notice of Allowance.
U.S. Appl. No. 13/012,660, Jul. 8, 2013, Office Action.
U.S. Appl. No. 12/975,489, Oct. 3, 2013, Office Action.
U.S. Appl. No. 11/778,178, Feb. 6, 2014, Office Action.
U.S. Appl. No. 11/768,056, Feb. 6, 2014, Office Action.
U.S. Appl. No. 13/012,660, Feb. 13, 2014, Office Action.
U.S. Appl. No. 11/755,556, Jun. 10, 2014, Office Action.
U.S. Appl. No. 13/012,660, Jun. 6, 2014, Notice of Allowance.
U.S. Appl. No. 11/779,178, May 27, 2014, Notice of Allowance.
Related Publications (1)
Number Date Country
20100207751 A1 Aug 2010 US