Patent Grant
7117075
The invention relates to driver activity and vehicle operation logging and reporting.
One of the largest government-mandated paperwork and cost burdens imposed upon any segment of private industry are the reporting requirements relating to commercial motor vehicles (CMV). Commercial Motor Vehicles (CMV) and their respective drivers and carriers are required by various federal regulations and international agreements to comply with rules governing the safe operation of the vehicles and the reporting of fuel taxes. In 1937, the federal government imposed hours-of-service (HOS) regulations upon commercial motor vehicle drivers operating commercial vehicles in the domestic motor carrier industry to ensure highway safety. Under direction of Congress, the Federal Motor Carrier Safety Administration (FMCSA) has scrutinized and periodically revised the hours-of-service regulations to aid in the reduction of driver fatigue and sleep disorder related incidents on the nation's highways.
Federal regulations relating to the safe operation of Commercial Motor Vehicles (CMV) are defined in 49 CFR Part 395 and 49 CFR Part 390.5, the entirety of each of which are incorporated by reference. One way in which safety is promoted in the hours-of-service regulations is to prohibit drivers from operating or being forced to operate their vehicles more than a specified amount of time between mandatory off-duty periods. In 1987, the FMCSA permitted carriers the flexibility of using an automatic on-board recording devices (AOBRD) instead of the traditional reporting method involving manual data entry and filing of reports by the CMV drivers and/or their carriers.
The International Fuel Tax Agreement (IFTA) is an agreement among jurisdictions in the United States, Mexico and Canada that simplifies the reporting of fuel-use tax for diesel, gasoline, gasohol, propane, and natural gas consumption by commercial motor vehicles. Fuel-use tax is included in the purchase price of the fuel and then later redistributed to those jurisdictions where the vehicle actually was driven while consuming fuel. For example, a driver of a CMV may purchase diesel fuel in the state of Texas and travel outside of Texas to a neighboring state, e.g., Louisiana, using the same diesel fuel purchased in Texas. IFTA requires carriers to report actual mileage driven in each jurisdiction so that the actual taxes collected may be later apportioned to Texas and Louisiana in accordance with actual vehicle operation. Each day, some 6.4 million drivers complete HOS logs to track driver compliance with HOS regulations. In addition, fuel tax logs are created daily for some 10 million trucks. The cost of compliance with these reporting requirements is extraordinarily burdensome. It is estimated that the annual cost of complying with reporting requirements using paper logs is approximately $2,000.00 per driver and $2,000.00 per commercial motor vehicle. This results in a paper log compliance cost of $31 billion dollars per year imposed upon private industry.
In one aspect, a method for logging and reporting driver activity and vehicle operation includes identifying a driver of a vehicle and recording operating data. The operating data is recorded with an on-board recorder that is hard-wired to a data bus, for example, an engine control module, of the vehicle, coupled to a vehicle mileage sensing system, and linked to a global navigation satellite system. The operating data includes mileage obtained from at least one of the vehicle mileage sensing system and the vehicle data bus; engine use, time, and date obtained from the vehicle data bus; and location, time, and date obtained from the global navigation satellite system. The method includes recording a duty status of the driver. The duty status includes (a) off duty status, (b) sleeper berth status, (c) driving-on duty status, and (d) not driving-on duty status.
The method further includes creating an hours of service log from time, date, and duty status, the hours of service log including a change in duty status of the driver, time and date the change occurred, hours within each duty status, total hours driven today, total hours on duty for seven days, and total hours on duty for eight days; creating a fuel tax log from mileage obtained from the vehicle mileage sensing system, location obtained from the global navigation satellite system, time obtained from at least one of the vehicle data bus and the global navigation satellite system, and date obtained from at least one of the vehicle data bus and the global navigation satellite system, the fuel tax log including miles traveled between periodic recording intervals, and location, time, and date recorded at each periodic recording interval; comparing the driver's hours of service log to an applicable requirement, for example, law or regulation; indicating to the driver with the on-board recorder whether the driver is in-compliance or out-of-compliance with the applicable requirement; automatically uploading the hours of service log and the fuel tax log to a receiver external to the vehicle using a wireless telecommunications network; and emitting a compliance signal representative of whether the driver is in-compliance or out-of-compliance with the applicable requirement to a second receiver external to the vehicle and under control of authorities.
Embodiments of this aspect may include one or more of the following features.
The method includes identifying the driver of the vehicle by interfacing with a portable memory device, and importing a driver's hours of service log through the portable memory device or the wireless network. The portable memory device is, for example, a smart card or contact memory button. The method further includes verifying the identity of the driver of the vehicle using, for example, biometric verification, and enabling the vehicle to be started, moved, or engine idled in response to identifying the driver of the vehicle.
Recording operating data includes automatically recording the mileage from the vehicle mileage sensing system; the mileage, engine use, time, and date obtained from the vehicle data bus; and the location, time, and date obtained from the global navigation satellite system. Recording the duty status can include automatically determining a change in the duty status and at least one of the time, date and location of the change in the duty status from the operating data. Recording the duty status includes logging a change in the duty status from a manual input by the driver.
The fuel tax log is used to create an IFTA (International Fuel Tax Agreement) compliant fuel tax report. The method includes manually inputting an indication of a border crossing.
When team driving, the method includes logging the duty status of a first driver of the vehicle with the on-board recorder; identifying a next driver of the vehicle with the on-board recorder; logging the duty status of the first driver and the next driver of the vehicle with the on-board recorder; and importing data for an hours of service log for the next driver into the on-board recorder from at least one of a portable memory device and a wireless telecommunications network. The fuel tax log can be created for a single vehicle having the first driver and the second driver.
The method includes calibrating mileage received from the vehicle mileage sensing system using data received from the global navigation satellite system or using vehicle tire size, and providing mileage from the recorder to an odometer display and to the vehicle data bus.
An exceptions report can be created from the comparison of the driver's hours of service log to the applicable requirement, and a cause of being out-of-compliance displayed to the driver.
The method includes encrypting the operating data, the hours of service log, the fuel tax log, and the compliance signal emitted from the recorder to ensure data integrity.
Operating data can be modified by a driver input and/or by a fleet carrier input, and any alterations of operating data recorded with a track changes function of the on-board recorder and/or on the host server.
The hours of service log can be displayed, for example, inside or outside the vehicle on an external display, as a graphical grid.
Automatically uploading includes uploading over a pager connection, a cellular telephone connection, a wide area network connection, an infrared connection, a radio connection, and/or a satellite connection. Automatically uploading includes uploading during an off-peak operating period, for example between 1:00 am and 5:00 am and/or on a weekend, for a wireless telecommunications network. Automatically uploading includes attempting to upload at least daily first over a least expensive connection and, if unsuccessful, then over at least one next least expensive connection, and uploading over a satellite connection when successive daily uploads are unsuccessful. Automatically uploading includes attempting to upload at least daily first over a predetermined wireless telecommunications network connection and, if unsuccessful, then over another predetermined wireless telecommunications network. Automatic uploading is an uploading of the current day, previous days, or day prior to the previous day hours of service and/or fuel tax logs.
The method includes uploading to the second receiver external to the vehicle when a compliance status check is requested by law enforcement, and/or when the vehicle is within a predetermined range of the second receiver. The second receiver is located, for example, on a handheld device, along a highway, at a weigh station, or within a law enforcement vehicle. The compliance signal is uploaded, for example, through a wired or wireless connection connected to a data port inside or outside of the vehicle.
The hours of service log is output to, for example, a display on the on-board recorder, a display on an external display device, the second receiver, or a wired connection connected to a data port inside or outside of the vehicle. The output of the hours of service log occurs responsive to a request from, for example, the driver, a fleet carrier, or the authorities. A data transfer and storage device can be placed in communication with the on-board recorder; and the hours of service log, fuel tax log, and the compliance signal uploaded to the data transfer and storage device.
The receiver to which the logs are automatically uploaded is, for example, a host server, and the fuel tax logs are uploaded from the host server to an external server that creates and files fuel tax reports.
In particular embodiments, the method may include notifying the driver if a particular event occurs, for example, notifying the driver to log into the recorder if the vehicle moves and the driver has not logged in, emitting an out-of-compliance signal if the driver is not logged in within a predetermined period, notifying the driver to log operating data on a paper log if the recorder is malfunctioning, and notifying a driver when the driver is nearing the end of an hours of service parameter. The driver can be notified by, for example, a text message, a visual indicator, and/or an audible signal. Compliance can be indicated by red, yellow, and green lights. A light on the recorder can be flashed when the driver is within a first predetermined time period of the end of the parameter, and another light on the recorder flashed when the driver is within another predetermined time period of the end of the parameter. The carrier can also be notified when the driver is nearing the end of a parameter. The method can also include emitting a signal indicating whether the recorder is present.
The method further includes, for example, the driver certifying the hours of service log prior to the automatic upload, and initiating a self-diagnostic function on the recorder upon a predetermined event. The predetermined event is at least one of a vehicle start, once in a 24-hour cycle, upon demand by law enforcement, and upon demand by the driver.
According to another aspect, a method for logging and reporting driver activity and vehicle operation includes recording only the following operating data mileage obtained from at least one of the vehicle mileage sensing system and the vehicle data bus; engine use, time, and date obtained from the vehicle data bus; and location, time, and date obtained from the global navigation satellite system.
According to another aspect, an on-board recorder for logging and reporting driver activity and vehicle operation includes a memory device configured to store operating data; a power supply; a first interface configured to connect to a vehicle mileage sensing system; a second interface configured to connect to an vehicle data bus of the vehicle; a receiver configured to link with a global navigation satellite system; at least one data portal configured to upload data from the memory device to a receiver external to the vehicle using a wireless telecommunications network, and supporting a connection with a receiver external to the vehicle and under control of authorities; a driver interface configured to record driver identification information input by a driver of the vehicle and duty status input by the driver; a processor operatively connected to the memory device for processing encoded instructions, recording operating data, and creating an hours of service log, a fuel tax log, and determining whether the driver is in compliance with an applicable requirement; and a display.
According to another aspect, a system for logging and reporting driver activity and vehicle operation includes an on-board recorder; wired connection between the on-board recorder and the vehicle data bus; a first server connected with the vehicle through the wireless telecommunications network, the on-board recorder being configured to automatically download the hours of service log, the fuel tax log, and the compliance signal; and a second server connected with the first server and configured to receive the fuel tax log, the second server including a computer readable media encoded with one or more computer programs for filing fuel tax reports based on the fuel tax log.
According to another aspect, a device for logging and reporting driver activity and vehicle operation includes one or more of the following means: means for identifying a driver of a vehicle and recording operating data; means for recording a duty status of the driver; means for creating an hours of service log; means for creating a fuel tax log; means for comparing the driver's hours of service log to an applicable requirement; means for indicating to the driver with the on-board recorder whether the driver is in-compliance or out-of-compliance with the applicable requirement; means for automatically uploading the hours of service log and the fuel tax log to a receiver external to the vehicle; and means for emitting a compliance signal representative of whether the driver is in-compliance or out-of-compliance with the applicable governmental reporting requirement to a second receiver external to the vehicle and under control of authorities.
According to another aspect, a method includes one or more of the following and/or an apparatus includes one or more of the following means for: identifying one or more drivers of a vehicle; verifying the identity of the one or more drivers by at least one of biometric and visual means; determining driver hours of service for more than one driver concurrently; recording driver hours of service for more than one driver concurrently; uploading data via a least cost method over a wireless telecommunications network; uploading through the recorder, via a wireless telecommunications network, driver identity, whether or not verified; identifying a driver, tying identity information to a driver record, determining driver hours of service, recording hours of service, uploading hours of service via a wireless telecommunications network, and optionally verifying identity information and optionally tying verification information to the driver record.
According to another aspect, a method includes one or more of the following and/or an apparatus includes one or more of the following means for: determining miles driven by a vehicle; recording miles driven by a vehicle; determining at least one of present and past location of a vehicle within a jurisdiction; determining at least one of present and past location of a vehicle between jurisdictions; determining border crossings between jurisdictions; recording at least one of present and past location of a vehicle within a jurisdiction; recording at least one of present and past location of a vehicle within two or more jurisdictions; recording border crossings between jurisdictions; uploading via a wireless telecommunications network at least one of present and past location of a vehicle within a jurisdiction; uploading via a wireless telecommunications network at least one of present and past location of a vehicle within two or more jurisdictions; uploading via a wireless telecommunications network border crossings between jurisdictions; and uploading via a least cost method over a wireless telecommunications network at least one of present and past location of a vehicle within a jurisdiction, at least one of present and past location of a vehicle within two or more jurisdictions, and/or border crossings between jurisdictions.
According to another aspect, a method includes one or more of the following and/or an apparatus includes one or more of the following means for: calculating, for example, periodically, when interrogated by authorities, or continuously, whether or not a driver is driving within parameters established by at least one of law(s) or regulation(s); wirelessly notifying, signaling, alerting or informing authorities that a driver is not in compliance with applicable hours of service laws or regulations; transmitting driver hours of service data to law enforcement via at least one of a wired connection, portable memory device and wirelessly; displaying data residing on the recorder via at least one of a wired connection, portable memory device and wirelessly; displaying remaining time for driver hours of service in at least one duty status generated from the recorder; exchanging data between the recorder and devices used to pump fuel into a vehicle; determining a driver's hours of service in compliance with home country and country of operation laws and regulations determining more than one driver's hours of service concurrently in compliance with home country and country of operation laws and regulations; and displaying hours of service data in any one or more languages.
According to another aspect, a method includes one or more of the following and/or an apparatus includes one or more of the following means for: identifying the location at which a trailer is at least one of tethered or un-tethered from a vehicle; recording the location at which a trailer is at least one of tethered or un-tethered from a vehicle; uploading the location at which a trailer is at least one of tethered or un-tethered from a vehicle; identifying the location of a trailer tethered to a vehicle; recording the location of a trailer tethered to a vehicle; and uploading the location of a trailer tethered to a vehicle.
The details of one or more embodiments of the invention are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of the invention will be apparent from the description and drawings, and from the claims.
The systems, methods and apparatus described provide the capability of logging driver activity and vehicle operating data, creating reports from the data containing information required to comply with HOS regulations and IFTA fuel tax reporting, and emitting a signal indicating whether the driver is in-compliance or out-of-compliance with applicable HOS laws or regulations.
Referring to
Recorder 200 includes a front panel 240 having a display screen 250, for example, a scrolling text message bar, for displaying text messages to the driver, a portable memory device reader 241, such as a contact memory button reader or smart card reader, to permit logging-in and logging-out of the driver from recorder 200 as well as transfer of prior driver activity to and from recorder 200, and duty status buttons 244 permitting the driver to manually change the driver's duty status, i.e., “on-duty driving,” “off-duty,” “on-duty, not driving,” or “sleeper berth.”
Front panel 240 has a self-test button 245 that allows the driver to initiate testing of the operability of recorder 200, and an indicator light 246, 248, such as an LED light, that indicates proper or improper operation of recorder 200 and/or the driver that is currently driving when team driving. Additional indicating lights 246 provide a visual indication of whether the driver's hours of service is in compliance or out-of-compliance with applicable hours of service regulations, for example, a red light indicates out-of-compliance, a green light indicates in-compliance, and a yellow light indicates that the driver is approaching the end of permitted driving time. Additionally or alternatively, compliance information can be conveyed to the driver audibly and/or on display screen 250. Front panel 240 also includes either or both of on-duty time remaining and a scrolling text message bar on display 250. Driver buttons 247 permit recorder 200 to switch the display between the drivers driving.
The front panel 240 of the driver interface includes optional biometric reading device(s) 242, 249, for example, a fingerprint recognition reader 242 and a camera 249. Recorder 200 also includes a wired data port 243, such as a USB port, to permit data transfer between the recorder 200 and other external devices or media, such as an electronic display (shown in
Recorder 200 continuously obtains mileage from the vehicle mileage sensing system through a mileage sensing system interface 220, as well as mileage, engine use, miles driven, time and date obtained from the ECM through an ECM interface 225. Vehicle location (latitude and longitude), date, and time are input to recorder 200 from a global navigation satellite system, e.g., GPS, via a satellite interface 230 periodically, such as every fifteen minutes. In addition, a wireless data portal 235 is provided to permit the uploading and downloading of data from and to recorder 200.
On-board recorder 200 includes a back-up power supply 215, for example, an internal battery, processor 205, and a memory device 210. Primary power to on-board recorder 200 is provided by a connection to the vehicle battery. The processor 205 is, for example, a central processing unit (CPU) or a simpler data storage device utilizing encoded and encrypted instructions with processing capabilities in accordance with the available memory 210. The memory device 210 includes read and write capabilities and a variety of commercial, off the shelf memory media. The processor 205 and memory 210 collectively form the logic component of the recorder 200. Recorder 200 includes a display 250 for informing the driver of the remaining driving time permitted by the HOS laws or regulations, and for displaying relevant information to federal, national, state, provincial or local authorities, as discussed below.
Referring to
Referring to
Mileage can be determined from only the ECM or through a broadcasting of an odometer reading from a vehicle dashboard, such as on a SAE J 1708 MID 140 bus. Alternatively, data received from the vehicle mileage sensing system, such as a speed sensor positioned at the transmission tail shaft of a vehicle can be automatically calibrated, for example, by comparing the data to mileage determined from GPS or through GPS mapping from a central server. The device can be automatically re-calibrated, by programming recorder 200 with the size and wear of the vehicle's tires and/or for different gear ratios. Recorder 200 can then provide the calibrated mileage to at least one of the odometer display and the ECM. Vehicle mileage can also be calibrated by using the GPS mapping at the central server and then sending the calibration back to the vehicle.
Recorder 200 automatically, continuously records the vehicle operating data as raw vehicle operating data obtained from the vehicle mileage sensing system and the ECM, and records GPS data at a set period time, for example, every fifteen minutes. GPS data can also be recorded upon the detection of a specific event, such as a change in duty status, or operating parameter, such as the engine being off for more than a specified period of time. To determine the hours of service, the driver's duty status throughout the day is also determined. Duty status includes driving-on duty, not driving-on duty, off duty, and sleeper berth. Each change in duty status can be manually input to recorder 200 by the driver using duty status buttons 244 and recorded with a time and date stamp obtained via GPS. Certain changes in duty status can also be determined automatically by recorder 200, as discussed below.
Data processing 140 creates an HOS log 141 and an IFTA log 142 from the raw data, and compares the HOS log to applicable regulations to determine whether the driver is in-compliance with HOS regulations. A more detailed exceptions report can be created from the comparison of the HOS log to applicable regulations that provide the detail of the comparison. In creating the HOS log, recorder 200 continuously calculates the time the driver has been in each duty status over the course of a day. The HOS log includes the time per duty status for eight consecutive days, including a calculation of the total hours driven today, total hours on duty for the past seven days, and total hours on duty for the past eight days. The hours of service log is typically created from date, time, mileage and duty status.
In creating the IFTA log, at every acquisition of data from GPS, for example, every fifteen minutes, the miles driven over that time period are calculated from mileage data obtained from the vehicle mileage sensing system and/or ECM, and recorded with a location, time, and date stamp obtained from the GPS data. A fuel tax report is then created, preferably by an external server, such as the host server or a second server communicating with the host server, having the requisite software to create a report in compliance with IFTA regulations, from the IFTA log and any required fuel purchase information.
Data processing 140 can also include an automatic determination of change in duty status from off-duty to driving on-duty. By recording the time when the vehicle starts to move, as determined by the ECM indicating engine use, i.e., that the vehicle has been started, and by the vehicle mileage sensing system or ECM indicating motion, recorder 200 automatically records a change of duty status to driving-on duty at that time. By recording the time when the engine is turned off for a predetermined period, such as four minutes, recorder 200 automatically prompts the driver to input a change of duty status to not driving-on duty, off duty, or sleeper berth. Also, by recording the time when the engine remains on but the vehicle is not moving (determined from, for example, either a speed of zero obtained from the ECM or there being no change in mileage) for a predetermined period, such as four minutes, recorder 200 can automatically prompt the driver to input a change of duty status to not driving-on duty, off duty, or sleeper berth. Off duty status is automatically determined at the time the driver logs out from recorder 200, for example, by removing the smart card from smart card reader 241. Alternatively, the driver can use the keys to indicate off-duty status while leaving the card in the reader.
Data reporting 150 includes using recorder 200 to provide information to the driver, as discussed above, displaying on display device 250 the hours of service log and compliance status, with display 250 and indicator lights 246. An additional display tablet can be connected to recorder 200 to display the hours of service log in grid form. For example, operator's total hours driven today, total hours on duty today, total miles driven today, total hours on duty for seven days, total hours on duty for eight days, and the operator's changes in duty status and the times the changes occurred are displayed.
Data reporting 150 also encompasses the ability of system 100 to automatically upload the hours of service log and the fuel tax log to a receiver external to the vehicle using a wireless telecommunications network. Recorder 200 also emits, such as periodically or continuously, a signal representative of the compliance status to a second receiver external to the vehicle and under control of authorities, such as law enforcement, carrier management, regulatory agencies or other approved inspector or agent. In addition, the compliance status, HOS logs or a more detailed exceptions report can be uploaded to a second receiver external to the vehicle when recorder 200 is queried.
Recorder 200 is configured to automatically attempt to transmit data to a host server via the wireless telecommunications network's off-peak hours, e.g., at a pre-determined period of time (e.g., 1:00 am–5:00 am) that is selected because it is available at low cost. A wireless telecommunications network made up of pager networks, cell phone networks and wide area networks provides low cost options. Other options are an infrared connection, a radio connection, and a satellite connection. Recorder 200 is programmed to seek a single wireless telecommunications network to upload data to a host server. Alternatively, recorder 200 can be programmed to seek various wireless telecommunications networks to upload data to a host server, from the least cost to the next most expensive cost and so on until the device finds such a data link and uploads its data. If after a predetermined time period for performing an upload, such as fourteen days, upload has not been successful, each day's HOS log, and IFTA log, and alternatively an exceptions report as well, can be uploaded whenever the recorder comes into contact with the pre-determined method of uploading data, or can be uploaded over a satellite connection. Data is stored on recorder 200 for not less than 14 consecutive days and is organized by driver for hours of service purposes and/or by vehicle for fuel tax reporting purposes.
By continuously emitting a signal indicating the compliance status of the driver, recorder 200 provides a way whereby authorized federal, state or local officials can immediately check the status of a driver's hours of service. Authorities receive this signal whenever the vehicle is within a predetermined range of the second receiver located, for example in a hand-held device, law enforcement vehicle, weigh station, or along a highway. The entire hours of service log can be displayed on recorder 200 or on an electronic display or tablet connected thereto, or downloaded, when recorder 200 is queried. Data can be downloaded to law enforcement personnel using a receiver tied to a computer, for example, in the law enforcement vehicle, that wirelessly interrogates recorder 200 and displays the data, by using a handheld device in the possession of a law enforcement officer that wirelessly interrogates recorder 200 and displays the data, or by using a wired connection through a port inside or outside of the vehicle.
The capability can also be provided to download information from a host server to the recorder. For example, using the communication link by which data is downloaded to the host server, the host server can also communicate data to recorder 200 at the end of the daily upload cycle. Data transmitted can include driver regime, such as 7 day/60 hour or 8 day/70 hour regime. The host server can also communicate with recorder 200 as desired via a wireless telecommunications network to ascertain information, such as compliance status, location as of the last GPS recording and remaining HOS.
Referring to
Recorder 200 automatically records data formatted to meet home country legal requirements and country of operation legal requirements. For example, a driver whose home country is Mexico, may operate a vehicle over a period of time in the United States. The operation of the vehicle within these countries, and their respective states, provincial or local jurisdictions triggers different reporting requirements to comply with respective HOS laws or regulations. Recorder 200 simultaneously records hours of service and/or fuel tax information that is country-specific, such as for the United States, Canada, and Mexico, and has multi-lingual reporting capability, such as English, French and/or Spanish.
As seen in
A complete display of an hours of service log can provide eight such graphical representations, one for each of the eight days, and a summary of the total hours driven today, total hours on duty for seven days and total hours on duty for eight days. As seen in
Referring to
A number of embodiments of the invention have been described. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the invention. For example, the on-board recorder may be configured to include one or more of the following features.
Recorder 200 can include a biometric reader for verifying the identity of the driver using, for example, facial, retinal or thumbprint recognition. The identity data is compared to a database within recorder 200 to verify the identity of the driver by matching the biometric with a specific driver. The unique driver ID can be a Transportation Worker Identification Card (TWIC) currently being developed by the Transportation Security Administration (TSA) or a commercial driver's license (CDL) issued by various state or federal governments. The vehicle can be disabled if the identity of the driver cannot be verified after some pre-determined time.
Camera 249 can be a miniature camera, such as with IR lighting for night driving, positioned on the front face of recorder 200 for visual analyzing the driver. The camera is used to identify the driver and visually tie the driver to the HOS data. Facial recognition, retinal or IRIS mapping, and driver behavior can be periodically assessed such as for drowsy driver syndrome from the recorder or an external source, such as through an external host server. The digital camera feature can be used for gate authorization by sending the drivers' ID and photograph ahead to a destination, such as a shipping dock or border crossing. The camera feature can be used for on-board documentation to the central server. Once the vehicle is in the non-moving and park mode the digital camera can also be used as a FAX/Scanner.
The portable memory device carried by the driver, for example, the smart card or contact memory button (such as the IBUTTON198 available from Dallas Semiconductor Corp.), can be configured to retain driver identity data, driving regime (such as, 7 day or 8 day regime), and the driver's hours of service log such that this information is automatically downloaded from the portable memory device to recorder 200 whenever a driver logs into a vehicle. In this way, the driver's hours of service log and related information can be transferred from one vehicle to another as the driver changes vehicle. Such data can also be downloaded into recorder 200 from the fleet carrier via several methods, for example, a wired connection at the fleet terminal, a wireless connection at the fleet terminal and/or a wireless download at any location within the range of a wireless telecommunications network. The portable memory device can include a programmable logic controller, such as an electrically erasable, programmable, read-only memory (EEPROM) of flash EEPROM.
Additional information that can be stored on the portable memory device includes the driver's current driving regime, the commercial driver license number (CDL #), commercial driver endorsements (e.g., HAZMAT), traffic violations and high risk driver data (e.g., DWI convictions). Transactions such as the last vehicle driven can also be stored on the driver card. Portable memory device technology, such as the IBUTTON™, can be used to transfer fuel purchase information about the vehicle and/or driver to a fuel pump and/or from the fuel pump to recorder 200. Alternatively, or in combination, infrared and RFID technology can be used to transfer data to and from recorder 200 to a user ID card or other external data source.
Recorder 200 can separately record each driver's duty status when more than one driver is driving the vehicle, for example team driving. While the hours of service for a particular driver are transferred, for example, by a wireless telecommunications network connection or portable memory device, when the driver moves to a new vehicle, the IFTA logs, which are vehicle dependent, remain with the recorder on the old vehicle.
IFTA reports identify the miles driven in each jurisdiction. Border crossings, for example, between states, countries, and provinces, can be determined by the driver inputting to recorder 200 when a border is crossed, by mapping software on an external server, or by mapping software on recorder 200. Recorder 200 can emit a signal indicating whether the recorder is present and thus recording data for compliance with applicable IFTA laws or regulations, and can emit safety related information such as tire pressure.
For each change of duty status, whether input manually or determined automatically, location as determined by GPS can be recorded. If a vehicle is equipped with an Intelligent Dash Board with speedometer, on dash odometer and fuel gage 225, data can be collected by recorder 200 from the Intelligent Dash Board rather than through the vehicle mileage sensing system interface 220.
The data processing 140 and data reporting 150 sections can also provide the capability of data encryption to ensure data integrity and to prevent tampering by the vehicle operator. However, the driver and/or carrier can be permitted to modify the operating data, and the processor includes a track changes function that records any alterations of operating data. Recording 200 can also provide the capability of authenticating the recipient of data such that data is only available to authorized users.
Recorder 200 can prompt the driver to review and verify that all entries are accurate prior to uploading data to the carrier. Recorder 200 can further prompt the driver to certify that all entries made by the driver are true and correct or that recorder 200 is operating properly. If recorder 200 malfunctions, the recorder can notify the driver visually, audibly and/or using a text message, prompt the driver to revert to a paper log, and/or emit an out-of-compliance signal. If recorder 200 determines that the vehicle is moving but no driver is logged on, a visual/audio/or text warning is provided to the driver signaling that the driver is not logged-in, and an out-of-compliance signal is emitted. Recorder 200 can also warn the driver when the driver is approaching the maximum limitations established by the hours of service laws or regulations. Recorder 200 can also upload such a warning to the carrier.
To limit “double counting,” whereby a driver uses a paper log book when recorder 200 is on-board, recorder 200 can emit a signal indicating that recorder 200 is on-board the vehicle. Recorder 200 has logic built in to account for, for example, gaps in miles or time to ensure the driver does not tamper with recorder 200, such as by disconnecting the power source, pulling a fuse, or similar tampering.
Recorder 200 continually or periodically performs self-testing and can prompt the driver to troubleshoot for system errors and system rebooting. Recorder 200 can self-test upon demand from law enforcement.
WIFI™ or BLUETOOTH™ technology can be utilized to facilitate data transfer and/or permit the communication of many different devices to form a communication network. BLUETOOTH™ technology can be used to permit the downloading of fuel purchase information to recorder 200 and/or as the communication protocol for the recorder itself in communications with law enforcement or any other data transfer.
Recorder 200 can have a short range RF transmitter which broadcasts the driver's HOS compliance status, electronic vehicle license plate, driver's risk factor based on past records, etc. The receiver can be an RF receiver distributed to state, local, and federal authorities for a snapshot monitoring status of drivers (HOS compliant or non compliant) high risk drivers and vehicles at toll gates and border crossings, and for Homeland Security purposes generally. The receiver can plug into the cigarette lighter of the law enforcement vehicle, similar power source or be positioned within a handheld device. A non-compliant driver can be identified by recorder 200 emitting short range signals, such as 315 MHZ or 434 MHZ (approximately 200 ft) RF signals, which can be detected by authorities. The receiver held by authorities can be a 315 MHZ or 434 MHZ RF device. The data exchange is dependent upon an authentication process, whereby only authorized users (the authorities) can access the data. The authorities can then be alerted while driving past a vehicle on the highway or when sitting along an interstate and monitoring for violators. Once a violation has been detected the authorities can obtain a detailed log from the recorder via a hard connection or a wireless connection, such as BLUETOOTH™ OR WIFI™ adapter in the USB data port of recorder 200. Also the non compliant driver status can be broadcasted on the SAE J1708/1587 data bus and the RS-232 port from the recorder. As another method the RS-232 and/ or SAE J1708 data can allow existing telecommunication products on the vehicle such as QUALCOMM™, XATA™ and PEOPLENET™ to transmit the driver log report status. Also, as another method the RS232, SAE J1708 or USB data port can allow the driver logs to be downloaded via WIFI™ or BLUETOOTH™ adapters or devices at WIFI™ hot spots at truck stops, for example, SIRICOMM™ has incorporated WIFI™ hot spots at Pilot Service Centers, and WIFI™ Hot(s) Networks are planned at weigh stations, toll gates, and Fleet Terminals.
Vehicles emitting an in-compliance signal can pass through a checkpoint or roadside inspection without further delay and those that are not in-compliance can be stopped for further investigation. Recorder 200 can be queried to generate a driver's hours of service graph and display the graph, for example, on a display tablet that can be connected to recorder 200. Electronic tablet 700 can be equipped with a rechargeable battery, such as a NiCd battery or a standard NiCad battery pack used on video cameras. The electronic tablet device 700 can include an antenna for all types of wireless communication and a connection permitting wired communication. The electronic tablet 700 can include a USB port so that printers and other devices can communicate to the electronic table 700. The recorder can be provided with a USB Port to form a direct, non-wireless connection to the tablet.
Recorder 200 can also be provided with the option of detecting whether or not a trailer is tethered to the vehicle. If tethered, recorder 200 connects to a PLC chip located in the trailer from the ABS Trailer Module that contains the trailer's ID number and related data and a PLC receiver chip located in the recorder. The trailer ID information can be obtained from various sources, for example, via a PLC4Trucks power line communications, such as defined in SAE J2497. If the fleet operator wants to locate that particular trailer it can access the PLC network chip via cell or pager network, or via satellite, through recorder 200.
The Recorder 200 can be equipped with a Tractor PLC ID transmitter chip and the driver log information can be downloaded from a Trailer Tracking System, such as TERION™, using a SAE J 2497 power line communication protocol. This method allows the driver's log report along with a tractor ID to be sent through an existing power line, for example, using a standard SAE J560 tractor/trailer connector and SAE J2497 protocol to a trailer communication wireless product.
Accordingly, other embodiments are within the scope of the following claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3518674 | Moorehead et al. | Jun 1970 | A |
| 3680121 | Anderson et al. | Jul 1972 | A |
| 3714650 | Fuller et al. | Jan 1973 | A |
| 3757290 | Ross et al. | Sep 1973 | A |
| 3789409 | Easton | Jan 1974 | A |
| 3848254 | Drebinger et al. | Nov 1974 | A |
| 3906166 | Cooper et al. | Sep 1975 | A |
| 4053893 | Boyer | Oct 1977 | A |
| 4067061 | Juhasz | Jan 1978 | A |
| 4083003 | Haemmig | Apr 1978 | A |
| 4107689 | Jellinek | Aug 1978 | A |
| 4152693 | Ashworth, Jr. | May 1979 | A |
| 4177466 | Reagan | Dec 1979 | A |
| 4222052 | Dunn | Sep 1980 | A |
| 4258421 | Juhasz et al. | Mar 1981 | A |
| 4303850 | Juhasz et al. | Dec 1981 | A |
| 4307455 | Juhasz et al. | Dec 1981 | A |
| 4338512 | Ludwig | Jul 1982 | A |
| 4428052 | Robinson et al. | Jan 1984 | A |
| 4428057 | Setliff et al. | Jan 1984 | A |
| 4435711 | Ho et al. | Mar 1984 | A |
| 4445118 | Taylor et al. | Apr 1984 | A |
| 4547778 | Hinkle et al. | Oct 1985 | A |
| 4555619 | Anderson | Nov 1985 | A |
| 4575803 | Moore | Mar 1986 | A |
| 4590569 | Rogoff et al. | May 1986 | A |
| 4630292 | Juricich et al. | Dec 1986 | A |
| 4644351 | Zabarsky et al. | Feb 1987 | A |
| 4651157 | Gray et al. | Mar 1987 | A |
| 4654879 | Goldman et al. | Mar 1987 | A |
| 4660037 | Nakamura | Apr 1987 | A |
| 4670905 | Sandvos et al. | Jun 1987 | A |
| 4677429 | Glotzbach | Jun 1987 | A |
| 4685061 | Whitaker | Aug 1987 | A |
| 4688244 | Hannon et al. | Aug 1987 | A |
| 4700374 | Bini | Oct 1987 | A |
| 4734928 | Weiner et al. | Mar 1988 | A |
| 4737978 | Burke et al. | Apr 1988 | A |
| 4740792 | Sagey et al. | Apr 1988 | A |
| 4742357 | Rackley | May 1988 | A |
| 4750197 | Denekamp et al. | Jun 1988 | A |
| 4754465 | Trimble | Jun 1988 | A |
| 4757454 | Hisatake et al. | Jul 1988 | A |
| 4774670 | Palmieri | Sep 1988 | A |
| 4775999 | Williams | Oct 1988 | A |
| 4776003 | Harris | Oct 1988 | A |
| 4787053 | Moore | Nov 1988 | A |
| 4788637 | Tamaru | Nov 1988 | A |
| 4791571 | Takahashi et al. | Dec 1988 | A |
| 4791572 | Green, III et al. | Dec 1988 | A |
| 4796189 | Nakayama et al. | Jan 1989 | A |
| 4797948 | Milliorn et al. | Jan 1989 | A |
| 4799162 | Shinkawa et al. | Jan 1989 | A |
| 4804937 | Barbiaux et al. | Feb 1989 | A |
| 4809005 | Counselman, III | Feb 1989 | A |
| 4809177 | Windle et al. | Feb 1989 | A |
| 4819174 | Furuno et al. | Apr 1989 | A |
| 4833477 | Tendler | May 1989 | A |
| 4833701 | Comroe et al. | May 1989 | A |
| 4833702 | Shitara et al. | May 1989 | A |
| 4843575 | Crane | Jun 1989 | A |
| 4850614 | Shanahan et al. | Jul 1989 | A |
| 4853859 | Morita et al. | Aug 1989 | A |
| 4854048 | Goulet | Aug 1989 | A |
| 4860341 | D'Avello et al. | Aug 1989 | A |
| 4866762 | Pintar | Sep 1989 | A |
| 4870759 | Burton et al. | Oct 1989 | A |
| 4876738 | Selby | Oct 1989 | A |
| 4884208 | Marinelli et al. | Nov 1989 | A |
| 4891650 | Sheffer | Jan 1990 | A |
| 4891761 | Gray et al. | Jan 1990 | A |
| 4897642 | DiLullo et al. | Jan 1990 | A |
| 4901340 | Parker et al. | Feb 1990 | A |
| 4905270 | Ono | Feb 1990 | A |
| 4907290 | Crompton | Mar 1990 | A |
| 4908629 | Apsell et al. | Mar 1990 | A |
| 4912756 | Hop | Mar 1990 | A |
| 4914686 | Hagar, III et al. | Apr 1990 | A |
| 4916827 | Rayburn | Apr 1990 | A |
| 4926331 | Windle et al. | May 1990 | A |
| 4939652 | Steiner | Jul 1990 | A |
| 4945570 | Gerson et al. | Jul 1990 | A |
| 4953198 | Daly et al. | Aug 1990 | A |
| 4963865 | Ichikawa et al. | Oct 1990 | A |
| 4993062 | Dula et al. | Feb 1991 | A |
| 4998291 | Marui et al. | Mar 1991 | A |
| 5003317 | Gray et al. | Mar 1991 | A |
| 5008814 | Mathur | Apr 1991 | A |
| 5014206 | Scribner et al. | May 1991 | A |
| 5019963 | Alderson et al. | May 1991 | A |
| 5021961 | Ross et al. | Jun 1991 | A |
| 5025253 | DiLullo et al. | Jun 1991 | A |
| 5032845 | Velasco | Jul 1991 | A |
| 5043736 | Darnell et al. | Aug 1991 | A |
| 5045861 | Duffett-Smith | Sep 1991 | A |
| 5046007 | McCrery et al. | Sep 1991 | A |
| 5046082 | Zicker et al. | Sep 1991 | A |
| 5055851 | Sheffer | Oct 1991 | A |
| 5058201 | Ishii et al. | Oct 1991 | A |
| 5068656 | Sutherland | Nov 1991 | A |
| 5090050 | Heffernan | Feb 1992 | A |
| 5101500 | Marui | Mar 1992 | A |
| 5119102 | Barnard | Jun 1992 | A |
| 5121126 | Clagett | Jun 1992 | A |
| 5121325 | DeJonge | Jun 1992 | A |
| 5131019 | Sheffer et al. | Jul 1992 | A |
| 5131020 | Liebesny et al. | Jul 1992 | A |
| RE34034 | O'Sullivan | Aug 1992 | E |
| 5142281 | Park | Aug 1992 | A |
| 5142654 | Sonberg et al. | Aug 1992 | A |
| 5155490 | Spradley, Jr. et al. | Oct 1992 | A |
| 5155847 | Kirouac et al. | Oct 1992 | A |
| 5159625 | Zicker | Oct 1992 | A |
| 5166694 | Russell et al. | Nov 1992 | A |
| 5172321 | Ghaem et al. | Dec 1992 | A |
| 5191529 | Ramsey et al. | Mar 1993 | A |
| 5208756 | Song | May 1993 | A |
| 5223844 | Mansell et al. | Jun 1993 | A |
| 5224211 | Roe | Jun 1993 | A |
| 5225842 | Brown et al. | Jul 1993 | A |
| 5229947 | Ross et al. | Jul 1993 | A |
| 5235633 | Dennison et al. | Aug 1993 | A |
| 5237612 | Raith | Aug 1993 | A |
| 5243529 | Kashiwazaki | Sep 1993 | A |
| 5247440 | Capurka et al. | Sep 1993 | A |
| 5247564 | Zicker | Sep 1993 | A |
| 5249127 | Komatsu | Sep 1993 | A |
| 5252982 | Frei | Oct 1993 | A |
| 5261118 | Vanderspool, II et al. | Nov 1993 | A |
| 5270936 | Fukushima et al. | Dec 1993 | A |
| 5276729 | Higuchi et al. | Jan 1994 | A |
| 5293163 | Kakihara et al. | Mar 1994 | A |
| 5297191 | Gerszberg | Mar 1994 | A |
| 5297192 | Gerszberg | Mar 1994 | A |
| 5299132 | Wortham | Mar 1994 | A |
| 5303163 | Ebaugh et al. | Apr 1994 | A |
| 5311194 | Brown | May 1994 | A |
| 5323322 | Mueller et al. | Jun 1994 | A |
| 5337236 | Fogg et al. | Aug 1994 | A |
| 5359528 | Haendel et al. | Oct 1994 | A |
| 5365516 | Jandrell | Nov 1994 | A |
| 5392458 | Sasuta et al. | Feb 1995 | A |
| 5394136 | Lammers et al. | Feb 1995 | A |
| 5396540 | Gooch | Mar 1995 | A |
| 5452446 | Johnson | Sep 1995 | A |
| 5579233 | Burns | Nov 1996 | A |
| 5586130 | Doyle | Dec 1996 | A |
| 5594425 | Ladner et al. | Jan 1997 | A |
| 5612875 | Haendel et al. | Mar 1997 | A |
| 5633622 | Patterson | May 1997 | A |
| 5638077 | Martin | Jun 1997 | A |
| 5648768 | Bouve | Jul 1997 | A |
| 5659470 | Goska et al. | Aug 1997 | A |
| 5680328 | Skorupski et al. | Oct 1997 | A |
| 5694322 | Westerlage et al. | Dec 1997 | A |
| 5721678 | Widl | Feb 1998 | A |
| 5729458 | Poppen | Mar 1998 | A |
| 5740548 | Hudgens | Apr 1998 | A |
| 5742229 | Smith | Apr 1998 | A |
| 5742915 | Stafford | Apr 1998 | A |
| 5787373 | Migues et al. | Jul 1998 | A |
| 5802545 | Coverdill | Sep 1998 | A |
| 5815071 | Doyle | Sep 1998 | A |
| 5848365 | Coverdill | Dec 1998 | A |
| 5864831 | Schuessler | Jan 1999 | A |
| 5880958 | Helms et al. | Mar 1999 | A |
| 5886331 | Lyons, Jr. | Mar 1999 | A |
| 5897602 | Mizuta | Apr 1999 | A |
| 5905433 | Wortham | May 1999 | A |
| 5913180 | Ryan | Jun 1999 | A |
| 5917434 | Murphy | Jun 1999 | A |
| 5919239 | Fraker et al. | Jul 1999 | A |
| 5922041 | Anderson | Jul 1999 | A |
| 5923572 | Pollock | Jul 1999 | A |
| 5924075 | Kanemitsu | Jul 1999 | A |
| 5928291 | Jenkins et al. | Jul 1999 | A |
| 5954773 | Luper | Sep 1999 | A |
| 5963129 | Warner | Oct 1999 | A |
| 5970481 | Westerlage et al. | Oct 1999 | A |
| 5974356 | Doyle et al. | Oct 1999 | A |
| 5987378 | Schipper et al. | Nov 1999 | A |
| 5999091 | Wortham | Dec 1999 | A |
| 6008740 | Hopkins | Dec 1999 | A |
| 6026384 | Poppen | Feb 2000 | A |
| 6064929 | Migues et al. | May 2000 | A |
| 6075458 | Ladner et al. | Jun 2000 | A |
| 6087965 | Murphy | Jul 2000 | A |
| 6088650 | Schipper et al. | Jul 2000 | A |
| 6104282 | Fragoso et al. | Aug 2000 | A |
| 6108591 | Segal et al. | Aug 2000 | A |
| 6115655 | Keith et al. | Sep 2000 | A |
| 6151549 | Andrews et al. | Nov 2000 | A |
| 6167333 | Gehlot | Dec 2000 | A |
| 6181995 | Luper et al. | Jan 2001 | B1 |
| 6185484 | Rhinehart | Feb 2001 | B1 |
| 6185501 | Smith et al. | Feb 2001 | B1 |
| 6195023 | Walsh et al. | Feb 2001 | B1 |
| 6215395 | Slaughter et al. | Apr 2001 | B1 |
| 6226577 | Yeo | May 2001 | B1 |
| 6253129 | Jenkins et al. | Jun 2001 | B1 |
| 6259988 | Galkowski et al. | Jul 2001 | B1 |
| 6278935 | Kaplan et al. | Aug 2001 | B1 |
| 6285953 | Harrison et al. | Sep 2001 | B1 |
| 6317668 | Thibault | Nov 2001 | B1 |
| 6331825 | Ladner et al. | Dec 2001 | B1 |
| 6351695 | Weiss | Feb 2002 | B1 |
| 6353796 | Schipper et al. | Mar 2002 | B1 |
| 6359570 | Adcox et al. | Mar 2002 | B1 |
| 6393346 | Keith et al. | May 2002 | B1 |
| 6421590 | Thibault | Jul 2002 | B1 |
| 6424893 | Byrene et al. | Jul 2002 | B1 |
| 6453731 | Yaegashi | Sep 2002 | B1 |
| 6459367 | Green et al. | Oct 2002 | B1 |
| 6502035 | Levine | Dec 2002 | B1 |
| 6519529 | Doyle | Feb 2003 | B1 |
| 6522265 | Hillman et al. | Feb 2003 | B1 |
| 6526341 | Bird et al. | Feb 2003 | B1 |
| 6571168 | Murphy et al. | May 2003 | B1 |
| 6611686 | Smith et al. | Aug 2003 | B1 |
| 6650224 | Weigl et al. | Nov 2003 | B1 |
| 6681987 | Ford | Jan 2004 | B1 |
| 6697735 | Doyle | Feb 2004 | B1 |
| 6714857 | Kapolka et al. | Mar 2004 | B1 |
| 6807481 | Gastelum | Oct 2004 | B1 |
| 6816090 | Teckchandani et al. | Nov 2004 | B1 |
| 6862521 | Fox | Mar 2005 | B1 |
| 6892131 | Coffee et al. | May 2005 | B1 |
| 6894606 | Forbes et al. | May 2005 | B1 |
| 6909398 | Knockeart et al. | Jun 2005 | B1 |
| 6975928 | Timko et al. | Dec 2005 | B1 |
| 20010018628 | Jenkins et al. | Aug 2001 | A1 |
| 20010020204 | Runyon et al. | Sep 2001 | A1 |
| 20020035421 | Warkentin | Mar 2002 | A1 |
| 20020133275 | Thibault | Sep 2002 | A1 |
| 20020165694 | Chene et al. | Nov 2002 | A1 |
| 20030036823 | Mahvi | Feb 2003 | A1 |
| 20030097208 | Doyle | May 2003 | A1 |
| 20030100305 | Parisi | May 2003 | A1 |
| 20030204362 | Beresford et al. | Oct 2003 | A1 |
| 20040004539 | Collins | Jan 2004 | A1 |
| 20040073468 | Vyas et al. | Apr 2004 | A1 |
| 20040157650 | Wissinger et al. | Aug 2004 | A1 |
| 20040243285 | Gounder | Dec 2004 | A1 |
| 20050060070 | Kapolka et al. | Mar 2005 | A1 |
| 20050099279 | Forbes et al. | May 2005 | A1 |
| 20050203816 | Monsor et al. | Sep 2005 | A1 |
| 20050280514 | Doan | Dec 2005 | A1 |
| Number | Date | Country |
|---|---|---|
| 3767589 | Jan 1990 | AU |
| 2 391 155 | May 2001 | CA |
| 35 16 357 | Jun 1994 | DE |
| 44 04 800 | Aug 1995 | DE |
| 44 23 328 | Jan 1996 | DE |
| 197 44 419 | Apr 1999 | DE |
| 100 55 287 | May 2002 | DE |
| 0 242 099 | Oct 1987 | EP |
| 0 367 935 | May 1990 | EP |
| 0 290 725 | Aug 1993 | EP |
| 0 744 322 | May 1996 | EP |
| 0 802 082 | Feb 1997 | EP |
| 1 128 333 | Aug 2001 | EP |
| 1 419 935 | May 2004 | EP |
| 2 717 595 | Sep 1995 | FR |
| 2 193 861 | Feb 1988 | GB |
| 2 221 113 | Jan 1990 | GB |
| 59-161941 | Sep 1984 | JP |
| 63-175537 | Jul 1988 | JP |
| 63-219238 | Sep 1988 | JP |
| 1-226226 | Sep 1989 | JP |
| 8904035 | May 1989 | WO |
| 8912835 | Dec 1989 | WO |
| 9322848 | Nov 1993 | WO |
| 9717232 | May 1997 | WO |
| 9728988 | Aug 1997 | WO |
| 9834812 | Aug 1998 | WO |
| 9837432 | Aug 1998 | WO |
| 9906987 | Feb 1999 | WO |
| 9921383 | Apr 1999 | WO |
| 9935009 | Jul 1999 | WO |
| 0136234 | May 2001 | WO |
