WO1997013208A1 - Livre de bord electronique pour vehicules - Google Patents

Livre de bord electronique pour vehicules Download PDF

Info

Publication number
WO1997013208A1
WO1997013208A1 PCT/US1995/012459 US9512459W WO9713208A1 WO 1997013208 A1 WO1997013208 A1 WO 1997013208A1 US 9512459 W US9512459 W US 9512459W WO 9713208 A1 WO9713208 A1 WO 9713208A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
vehicle
protected
evl
log
Prior art date
Application number
PCT/US1995/012459
Other languages
English (en)
Inventor
Peter B. Houser
Original Assignee
Scientific-Atlanta, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Scientific-Atlanta, Inc. filed Critical Scientific-Atlanta, Inc.
Priority to PCT/US1995/012459 priority Critical patent/WO1997013208A1/fr
Publication of WO1997013208A1 publication Critical patent/WO1997013208A1/fr

Links

Classifications

    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07CTIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00Registering or indicating the working of vehicles
    • G07C5/008Registering or indicating the working of vehicles communicating information to a remotely located station
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07CTIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00Registering or indicating the working of vehicles
    • G07C5/08Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
    • G07C5/0841Registering performance data
    • G07C5/085Registering performance data using electronic data carriers
    • G07C5/0858Registering performance data using electronic data carriers wherein the data carrier is removable

Definitions

  • This invention relates to the field of electronic vehicle logs used particularly in commercial vehicles and, more particularly, to a data collection and processing system for a vehicle serving multiple users including the driver, the owner/operator and governmental authorities. Even more particularly, the invention is directed to securing access to parucular data by such users via the application of evolving "smart" or “flash” card, public key /private key encryption and electronic signature, speech recognition and speaker verification and global positioning or other navigation system technologies.
  • vehicle credential data is defined as data describing the vehicle, the carrier, cargo, driver, and passengers independently of the transit involved.
  • Vehicle credential data may thus include the following data, the following list being exemplary of such data: vehicle registration, vehicle insurance, driver's license, driver's credentials, driver's safety record and health, cargo manifest and shipping invoice, tariff-related documentation, and declared itinerary or intended route data.
  • In-transit data is defined for the purposes of the present application as data obtained during transit or in route (whether the vehicle is in motion or not). Such data may be acquired by periodically monitoring sensors on the vehicle to determine how the vehicle is being used. Exemplary data falling into this category of data include: date and time of data collection, vehicle speed, brake usage, steering wheel motion, engine RPM, engine temperature, cargo container temperature, engine vibration and other health metrics, and vehicle location from a navigation source such as the so-called Global Positioning System (GPS) or equivalent data gathering system.
  • GPS Global Positioning System
  • Cargo monitoring data is defined for the purposes of this application as data related to either the status or security of the cargo, for example, whether the cargo seal has been maintained or broken.
  • event record data is defined for the purposes of this application as data recorded in transit for particular events effecting the vehicle or cargo or both.
  • Typical events include: vehicle weight, for example, obtained during a weight-in- motion or stationary scale weighing, vehicle environmental, emissions or safety status checks, for example, determined at an inspection facility, border crossing data, either state or national, hazardous material (HAZMAT) warnings or transit regime changes (when the vehicle starts motion or has stopped).
  • route monitoring data is defined for the purposes of the present application as data obtained through monitoring the vehicle in transit to compare with the above-defined vehicle credential data for an intended route. This data is preferably collected through the application of a navigation system such as GPS or other equivalent system as well.
  • Ebaugh et al. US Patent No. 5,303,163, describes a configurable vehicle monitoring system having first and second configuration levels for an owner/operator and a driver respectively. Besides being able to independently configure data in memory, each is independently able to access certain data of interest to that party alone.
  • the data that can be gathered and analyzed includes miles per gallon, fuel consumed, trip time, idle time, fuel consumed and other pertinent information relevant to fleet or vehicle operation. For example, according to Figure 7 thereof, a printout may be obtained showing these and other data.
  • the owner/operator may obtain an indication of the period of time the vehicle is operated in excess of the 65 mile per hour overspeed limit.
  • radio or generally wireless radio communication may provide data mobility from one user to another (US 4,804,937, 5, 185,700 or WO 90/09645).
  • an electronic vehicle log comprises a processor for processing data, a memory for storing software algorithms and fixed data, preferably non-volatile in nature, a secret key unique to the vehicle log, and a unit serial number that is unique to that unit (hereinafter, an EVL identifier), a removable non-volatile log memory for securely recording data and a navigation and time-of-day and date input data circuit.
  • a microphone input for receiving user speech coupled to the processor (for example, via an analog to digital converter) and a memory for storing digitized voice samples.
  • Optional sensors are coupled to the log for providing for the input of data for vehicle and cargo, for example, through an external interface, in particular, a wireless interface.
  • an EVL may acquire event data such as weight-in-motion (WIM) data.
  • WIM weight-in-motion
  • Those who would obtain access to data or input data are provided with a public key which is likewise unique to the vehicle log.
  • any data entries are signed with an electronic signature for verifying the entered data, for example, comprising a calculated hash value encrypted with the secret key.
  • the driver inserts the removable non-volatile log memory for the duration of the trip.
  • a driver may obtain access and log into the EVL by inputing their speech, a password or a biometric after inserting their card memory.
  • the driver-unique data is used to decrypt a secret key member of a public key encryption pair.
  • protected data packets (PDP's) containing this log data are generated with digital signatures formed by encrypting digital hash values with this secret key member of the public key pair.
  • Protected data packets are transmitted to a requesting user via electronic means, for example, wireless, telephone modem or a memory card.
  • the requesting user has a trusted (escrowed) copy of the public key of the above- referenced public key pair, the public key pair including the secret key (securely stored in and never released from EVL memory) used for forming the electronic signature.
  • the secret key should be protected and secured as closely as possible and should not be transmitted (otherwise, it might be intercepted by an uncertified individual).
  • the public key is used to verify that the electronic signature of the PDP is accurate. Correct verification of the electronic signature then confirms the data source (the driver-protected secret key) and the integrity of the data (since the hash value matches the PDP data).
  • a governmental authority may obtain access by a defined process.
  • One example of such a process for obtaining an early transmission of vehicle data in advance of a border crossing or like event is described by the following.
  • the agency wishing to receive secure data generates a public key encryption pair different from that used by the driver and distributes the public key portion to any person or system desiring to transmit secure data.
  • the public key portion is stored in EVL memory.
  • a profile of a commercial vehicle and a cargo may be extracted from the vehicle via a card memory or may be electronically extracted by wireless means prior to the vehicle's departure and delivered to the authority with the stored public key portion.
  • the EVL generates a private encryption key and uses it to encrypt PDP's with their corresponding digital signatures.
  • the EVL encrypts this private encryption key using the public key and transmits that information to the agency receiving the data.
  • the receiving agency decrypts the EVL private encryption key using the secret key portion of the key pair and then decrypts the PDP's using the decrypted key.
  • the profile and public key are transmitted via a centralized authority data base to regional data bases for distribution to checkpoints, port of entry border crossings and the like along the intended route of the vehicle.
  • the vehicle is polled or interrogated, for example, preferably by wireless means in advance of reaching the facility, so the vehicle need not stop its movement.
  • the vehicle transmitted profile data is compared with the previously transmitted profile data and the inspector may preclear the vehicle through the inspection station. If the inspection data is a weigh station, for example, and data is to be entered into the log by the authority, an electronic signature is utilized to verify the entered data, preventing subsequent modifications of the logged information. Moreover, at the time the entry is made, the vehicle position and time from the global positioning system may be automatically and simultaneously recorded, allowing detection of fraudulent entries.
  • a short range communications system may be used to verify that the vehicle crossing the border is the vehicle which received the preclearnace to cross. It is also possible that the vehicle may carry all the profile information in the
  • EVL and transmit the data via wireless means to the authority just a few minutes before the approval (for example, preapproval at a border crossing) event.
  • some sort of short-range transmission is useful as the vehicle crosses the border to physically confirm hat the vehicle currently crossing the border is the same as the one that provided the profile and credentials and received preapproval to cross.
  • An authorized individual such as an inspector or police officer creates a digital credential in a generating device's memory, for example, a laptop personal computer.
  • a secret key of a public key pair is used to generate a digital signature for the credential data.
  • the credential and signature are transmitted to the EVL using various means, possibly including wireless means, direct input (typing), or memory card transfer.
  • This transfer may be encrypted as discussed above as desired, for wireless or other secure data transmission.
  • the credential and signature are formed into a PDP and logged as described above for the driver data logging operation.
  • the agency will use a trusted copy of the public key portion to verify the electronic signature of the PDP.
  • Figure 2A is a system overview drawing showing the interface between a vehicle 200 carrying an electronic vehicle log of Figure 1 with a governmental or other authority and Figure 2B shows vehicle 200 with expanded boxes describing data that may be stored in DPIU 210 including an electronic vehicle log of the present invention;
  • Figure 3 is a schematic block diagram of the electronic vehicle log of Figure 1 for maintenance in a vehicle;
  • Figure 3A provides a first embodiment,
  • Figure 3B provides a second embodiment and
  • Figure 3C provides a third embodiment;
  • Figure 4A provides an overview of the key and security features of the present invention in flow diagram form and
  • Figure 4B shows a table showing the use of different public key pairs by different entities for accessing the data stored in the EVL 400 of Figure 4A;
  • Figure 5A provides a table of examples of data maintained ' in an in-vehicle data base of memory of the in-vehicle unit of Figure 4;
  • Figure 5B comprises a table showing data elements and characteristics recoverable through utilization of the present invention and their characteristics;
  • Figures 6 A and 6B provide a table showing service, application, technology or product availability, demonstrable feature and utilization of the present invention. DETAILED DESCRIPTION OF THE PRESENT INVENTION
  • FIG. 1 there is shown an overview drawing of the electronic vehicle log of the present invention.
  • the present device is intended to be placed in a vehicle, hence, the present invention is described herein as an in-vehicle data processing unit.
  • the log is described herein as electronic because it generally operates via electronic circuits including at least memory circuits and a data processor.
  • the present invention is characterized as a log because the memory of the present invention substitutes for prior art hand-written log books typically used by drivers of vehicles, especially commercial vehicles.
  • the electronic vehicle log (EVL) 1 is described by box la as comprising a package of elements suitably housed to be mounted in a vehicle, for example, in an operator compartment or secure area therein or proximate thereto.
  • a mounting arrangement would be to provide a bracket mounting plate permanently secured to the vehicle.
  • the EVL housing herein referred to as a data processing interface unit (DPIU) then is removably secured thereto by mechanical locking apparatus so that the DPIU may be removed from the vehicle as necessary.
  • the mechanical locking apparatus should be tamper-resistant so that the EVL itself cannot be surreptitiously moved from one vehicle to another without detection. (To accomplish this objective, electronic tamper detection may be employed).
  • the DPIU housing is adapted to receive a removable security module as will be further described herein which is the electronic vehicle log itself.
  • the EVL housing 1 contains a processor, preferably a microprocessor and a non-volatile memory coupled thereto for storing at least secret key data, secret
  • the EVL 1 further may comprise a random access memory that typically is volatile for storing data on a temporary basis and a real time clock (typically a software algorithm that is preferably periodically updated).
  • a real time clock typically a software algorithm that is preferably periodically updated.
  • Most processors require a clock Oscillator output that is controlled for providing processor operation clocking functions.
  • This clock can provide a clocking input to a real time clock algorithm as is well known in the art.
  • an independent clock source may be used or an intemal isolated hardware clock circuit (not shown).
  • a navigation system such as the Global Positioning System (GPS) or Loran or other system can provide the independent clock source or periodic indications as to true time for synchronizing a local real time clock as is likewise known in the art.
  • GPS Global Positioning System
  • Loran Loran
  • EVL housing 1 has insertable therein a removable non-volatile memory module 2 described by box 2a which becomes the log in place of known paper logs or other known electronic logs.
  • the log memory 2 stores secured or protected data packets output from the EVL included processor as will be further described in connection with Figure 4.
  • the EVL 1, according to the present invention, may communicate with governmental authorities via radio 3, according to box 3a which may be optional or through wired or other means.
  • radio is intended communication via all radio frequencies including light frequencies or via laser or other known means that is wireless in nature.
  • the EVL communicates with an inspection facility for border preclearance before reaching the border via wireless means, so the vehicle need not stop.
  • the EVL 1 may be provided with a display or other output means 4.
  • the display as indicated by descriptive box 4a, may be optional.
  • the display may comprise a liquid crystal display, cathode ray tube display, light emitting diode or other display.
  • Other output means may comprise a printer or speech synthesis means or other output means. All such means provide the user (typically the vehicle operator) with feedback of proper operation, an indication that the " vehicle is being polled, clearance to proceed, log data, if appropriate, and other information.
  • Controls 5, as described by box 5a are likewise optional.
  • the controls typically comprise a keyboard, keypad or related switch control but may comprise speech receiving means 7 described by box 7a as a microphone such as an electret microphone or digital microphone. Also, both keys and microphones may be provided. The microphone may be eliminated if speech input is not contemplated by one designing a system according to the present invention.
  • the controls may be keys representing, for example, numeric or alphabetic characters for inputing the operator's identity, password or other data as will be described further herein. If necessary the microphone is coupled to the processor of the present invention via an analog to digital converter for sampling the voice input and converting the input to digital samples.
  • sensors 6 may be provided which are only generally described.
  • brake sensors may comprise brake sensors, accelerator sensors, tachometer or mileage sensors, speedometer sensors, steering column sensors, tire pressure monitoring sensors, cargo bonding sensors, cargo temperature or smoke or fire sensors, driver alcohol (breath) detection sensors and the like which may be coupled to EVL 1 by wired or wireless means.
  • Credentials and event data recording typically requires acquiring data from systems separate from the EVL housing 1 which are not permanently mounted on the vehicle.
  • a customs agent may be empowered to record a credential within the EVL which indicates that paperwork is in place and tariffs paid to allow expedited international or state border crossings as will be described further in reference to the example of Figure 2.
  • This credential information is placed within the EVL by any number of transmission methods and via security means including direct entry, via a removable credential memory, via direct connection and via radio connection.
  • the EVL 1 may provide a keyboard and limited display for manual entry of the information. This may be relatively tedious and insecure.
  • the entry process may include the agent (inspecto ) specifying an encryption key, either public or private, which may be used in a signature process for authenticating entered data.
  • the process may involve speech recognition and voice entry of the data in combination with a keyboard/display or alone.
  • the process may further comprise speaker identification or verification processes known in the art for confirming a subject's claimed identity based upon a digitized speech sample.
  • EVL memory is removable, it may be placed in a data entry device belonging to the agent and the electronic credential or event data copied into the memory. When the memory device is replaced into the EVL 1, the newly acquired data will be processed as a normal PDP as described below in connection with Figure 4.
  • Direct connection may be cumbersome.
  • the EVL may be directly cabled to the agent's data entry device, using a media such as an RS 232 serial data channel or equivalent serial or parallel connector. Data processing in this case is comparable to that when using removable credentials.
  • radio connection may be preferable for, for example, coupling to mobile police forces, air such as helicopter carrying radio, or roadside radio polling stations so the vehicle may transmit in motion.
  • Radio may be used to receive or transmit credential and event data.
  • One example is a weight in motion (WIM) station operated by a governmental authority.
  • a WIM sensor may, when interrogated by the EVL, transmit the vehicle's weight to the EVL for storage.
  • an agent uses a personal computer or workstation to generate, for example, border crossing or inspection credential data.
  • An agent-specific secret key is used to embed their electronic signature within the credential data transferred to the EVL 1.
  • the data may not be accessible to the driver or even the vehicle system operator.
  • an authorizing agent such as the border crossing inspector
  • the corresponding public key is used to decrypt the signature, thereby authenticating the source and permitting preclearance of the vehicle.
  • Figure 2 generally represents in diagrammatic form the events at a border crossing of a vehicle 200 equipped with the EVL 1 (Figure 1) of the present invention (represented as box 210).
  • Vehicle 200 may be a truck, for example, approaching a border crossing 202 which may be a state or international border along a route 201.
  • Zone 205 comprises a reporting zone.
  • Zone 206 comprises an evaluation/clearance zone.
  • Zone 207 comprises an inspection zone for performing a detailed inspection, as necessary, of vehicle 200 or health check of the vehicle's driver.
  • the arrows on route 201 indicate the expected direction of passage of vehicle 200.
  • Block 261 describes motor vehicle data such as ID number, EVL or DPIU identification number and status, vehicle weight and registration data.
  • Driver data 262 comprises their identification, their licenses, safety record, transit log and safety biometrics among other data.
  • Carrier data 263 includes identification, location, registration, insurance, licenses and permits, ICC, PUC, USDOT records, violations and offenses and fees paid records.
  • Cargo data 266 includes trailer identification, invoice, manifest, HAZMAT warnings, gross and tare weight, export declaration, inspection record, tariff record and crossing approval data. Together, these data 261 , 262, 263 and 266 may be vehicle credential data as used in the context of the present application.
  • Transit security block 264 refers to electronic bonding data, route verification data and time-in-travel verification data.
  • Safety and environmental data block 265 refers to a combination of event data and in transit data.
  • block 265 refers to inspection records, emission records on-board sensor records and HAZMAT warnings.
  • an inspection facility 203 typically at a border 202 or proximate thereto is an inspection facility 203.
  • work stations shown as computer workstations, 204 are provided governmental employees, such as inspectors.
  • the work stations and/or inspection facility 203 preferably communicate with vehicle 200 which may be moving by wireless means.
  • the PC-based inspector workstations 204 are described by box 220.
  • the workstations function to interface with an interface unit described by block 210 usually refe ⁇ ed to herein as the EVL of vehicle 200 and to roadside sensors of a polling station (not shown). These sensors respond as a vehicle passes a polling station in motion to obtain data from the EVL.
  • the workstations 220 function to record electronic credentials either downloaded in advance or provided from the EVL 210 of the vehicle 200.
  • the workstation 204 may interface with centralized databases to obtain data that is not stored in the workstation as necessary.
  • the workstations 204 are networked together for intercommunication and interchangeability. That is, if one workstation is occupied, a first spare workstation is allocated to an new incoming vehicle 200 to the system.
  • the work stations 204 and/or inspection facility 203 generally are provided with an EVL interface unit for interfacing with the in-vehicle EVL 1 of vehicle 200.
  • the functions of this interface unit are described by box 210 which couples the inspection facility 203 or workstation 204 or both with the EVL resident in vehicle 200.
  • This interface unit carries and provides credentials/manifests/inspection records collected for a vehicle.
  • the interface unit also collects multi-sensor reports from on- board sensors on the commercial vehicles such as vehicle 200, for example, on odometer readings, brakes, cargo bondings and the like as optionally provided.
  • the interface unit provides vehicle to roadside (or fly over) polling stations communication between the EVL and the governmental employees such as inspectors and inspection stations such as weight-in-motion measuring stations. The latter data may be recorded in the EVL as will be described in connection with Figure 4 as protected data packets.
  • Another function of the interface unit is general information management and the updating of the EVL data base and records due to governmental activity. For example, the opportunity for preclearance of a vehicle through an inspection station is one type of data that may be entered into the EVL.
  • the interface unit provides electronic security in accordance with the security features described by Figure 4. Communications to and from the vehicle 200, especially if wireless, are preferably secured from interception by coding and/or encryption as desired.
  • a vehicle 200 moves along route 201 into a reporting zone 205.
  • the vehicle 200 may initiate radio contact with inspection facility 203 or the vehicle may be polled via roadside or other monitors.
  • manifests for the vehicle and associated data are preferably electronically downloaded by a broker (a carrier or other party) for storage at the facility 203.
  • Cu ⁇ ent manifests of expected vehicles are provided to individual inspector workstations 204.
  • the vehicle data of particular vehicle 200 is provided via wireless means to inspection facility 203 and compared at workstations 204 with downloaded data, such as manifest data.
  • the driver may be provided with a display indicating the EVL is being monitored and thereby reported to him. Moreover, a report or record of the monitoring activity may be stored in the EVL along with a real time of day and location indication as will be subsequently described herein.
  • the vehicle then enters an evaluation/clearance zone 206.
  • the governmental authority such as an inspector assesses the records/data obtained from the EVL at his workstation 204. If the inspector is satisfied, the inspector communicates a bypass or, if not satisfied, a no-go signal to the truck. Of course, the EVL records and updates itself according to the bypass or no-go signal.
  • roadside monitors may poll the vehicle in transit as it crosses the border to assure that the vehicle crossing the border is in fact the vehicle given preclearance to cross.
  • preclearance may not have been received in a timely manner even though preclearance could have been granted as the vehicle enters the inspection area 207.
  • Vehicles not receiving timely preclearance and vehicles whose credentials are suspect may be signaled to stop in inspection zone 207.
  • Inspection zone 207 co ⁇ esponds thereto and, at the area, a detailed inspection of vehicles which fail or do not timely receive preclearance occurs.
  • Vehicles which may not receive preclearance may include those providing a cargo bonding breakage signal, an indication of improper or errored credentials or manifest data and the like or presenting safety issues such as faulty brake or related signals.
  • driver health issues may also be checked (for example, vision or drug/alcohol levels).
  • the inspections may be random, i.e., ordered as a result of proper data reporting but nevertheless a no-go signal is signaled to the particular vehicle 200. If the vehicle safety, driver health or driver safety (overspeed or erratic activity) are signaled as problematical, each of these in turn may be checked or inspected.
  • an embodiment of the present invention may provide for a vehicular data processing method for use by a vehicle in crossing a border comprising the steps of initiating a request for preclearance or automatically receiving a polling signal; responsive to a polling signal, transmitting at least vehicle credential data; and receiving a bypass signal or a stop signal, the bypass signal indicating that the vehicle may pass and the stop signal indicating the vehicle must stop.
  • the data is transmitted in a secure manner as will be further described in connection with Figure 4.
  • Other related methods that will be further described herein include the automatic monitoring of safety equipment, driver credential, driver health or driver safety by police, the automatic monitoring of cargo bonding devices and cargo temperature, cargo weight, tariff payment and the like.
  • FIG. 3A there is shown one alternative embodiment of an electronic vehicle log according to the present invention.
  • FIG 3B A further embodiment is described by Figure 3B and yet a third embodiment is described by Figure 3C.
  • Figure 4 From a study of each embodiment, one of skill in the art will be prepared to design an electronic vehicle log for a particular application and/or vehicle type and, in accordance with Figure 4, design an appropriate security method and means depending on the level of security desired.
  • FIG. 3A shows an in-vehicle data processing interface unit.
  • Box 300 exemplifies a housing for housing components of an EVL according to the present invention.
  • the EVL system apparatus 300 includes, for example, a radio or other vehicle-to-roadside, vehicle-to-vehicle or vehicle-to-aircraft communications apparatus 301.
  • Examples of short range devices include a Hughes Radio or Mark IV (MklV) units or other similar radio systems known in the art or so-called automatic vehicle identification units.
  • Longer range communication may be cellular radio via telephone modem or 220MHz radio manufactured by Scientific- Atlanta and other suppliers.
  • Qualcomm Omnitrax provides longer range communications.
  • Apparatus 301 is coupled between a suitable antenna (via link 309) and computer processing unit 302.
  • systems applications apparatus 303 for, for example, receiving GPS or Loran or other location and time update data via an antenna via link 310.
  • Other functions of apparatus 303 include security and built-in- test (BIT) test circuitry.
  • Processing set 302 and systems applications apparatus 303 may be powered by the vehicle battery via a 12- volt power inverter or other circuitry 304.
  • Computer processing set 302 houses the processor, non-volatile (software algorithm) memory, PCMCIA (card or module) receiver, analog/digital interfaces as necessary, operator/machine interfaces as necessary and built-in test circuitry.
  • the plug-in security EVL module is represented by both 307a and 308a for storing fixed and variable data respectively via respective links 307 and 308.
  • Fixed data 307a of an EVL includes and should not be considered to be limited to include cab identification data, truck line identification data, registration data, location data and the like.
  • Variable data 308a may be considered to include and not be limited to include driver identification data, trailer identification data, load identification data, route data, initial weight data, credentials and fees data, hazardous material data and safety inspection data.
  • one purpose of the device 300 and log 307a, 308a is to provide via antenna(s) 309 certain outputs 310a responsive to certain external inputs 309a.
  • Inputs 309a comprise the polling request and the identification of the poller. Once the polling request is made, data returned and authorization determined a preclearance authorization signal is another input. Yet another input may be a request to stop for a detailed inspection as has been already described above that may be an alternative to a preclearance authorization signal.
  • the outputs 310a typically provided in response to a poll, comprise the identification, classification and location of the vehicle and driver. As necessary, a preclearance request signal may be generated. Other credentials necessary for polling site preclearance are provided as necessary. The safety/health of the vehicle/operator may be output. Also, there may be provided a mileage and fuel report for purposes of comparing with intended route and typical fuel consumption figures.
  • Vehicle sensor data 305a comprises driver condition data (for example, alcohol sensors for intoxication determination), load condition/security (temperature, bonding), vehicle condition (engine temperature)/security and the like and internal data processing unit security sensing (the BIT test) among others too numerous to list.
  • driver condition data for example, alcohol sensors for intoxication determination
  • load condition/security temperature, bonding
  • vehicle condition engine temperature/security and the like
  • internal data processing unit security sensing the BIT test
  • Processor 302 is also linked, for example, as necessary to alternatives to known short range roadside polling devices via known in the art systems described above such as automatic vehicle identification systems. These devices return data to the inspection facility responsive to inspection facility initiated polling requests by altemative means.
  • apparatus for maintaining an electronic log of vehicular activity for an automatic border crossing comprising radio apparatus for communicating with an inspection facility and for periodically receiving time and location data.
  • Protected data packets as electronically signed and stored in variable data EVL 308a as will be described in connection with Figure 4.
  • Figure 3B Yet another prefe ⁇ ed embodiment of an in-vehicle unit is shown in Figure 3B. While the whole of Figure 3B is labeled as an Electronic Vehicle Log, Figure 3B is similar to Figure 3A in that box 350 represents a housing in which are situated elements including a processor and memory and connections are shown to other elements outside the housing such as the EVL log media 370 preferably comprising a disk, flash memory, card or other NVM. For simplicity, Figure 3B does not show a microphone, all the optional sensors, the antennas for wireless commumcation and the like shown in Figures 1 or Figure 3 A.
  • a bus system 356 for coupling various circuits together and providing intercommunication at a sixteen bit level such as an International Standards Authority (ISA) standard bus system known in the art.
  • the ISA bus 356 provides 16 bit data lines and 24 bit address lines for addressing and retrieving data from memories connected thereto.
  • a processor 351 Connected to the bus 356 are a processor 351, a PCMCIA controller 352, a flash memory 353, a volatile memory 354 and an interface controller such as a quad serial interface controller 355.
  • Sample capacities are 512 kbytes for volatile memory 354 and flash memory 353.
  • Processor 351 provides the intelligence for the unit and may comprise, for example, an ELAN 80386 integrated processor or other microprocessor.
  • the "386” 97/13208 PC17US95/12459
  • processor 17 has intemal random access memory and program memory which may be insufficient for the present purposes. Consequently, external flash memory 353 and volatile memory 354 are provided for providing sufficient capacity for the tasks at hand. Flash memory 353 is non-volatile and amy store fixed data such as the unit identification, algorithms and the like in permanent secure form. Volatile memory preferably random access memory provides working space for processor 351.
  • Controllers 352 and 355 provide slave control of input/output functions for the processor 351.
  • PCMCIA controller 352 is coupled to the EVL credentials non ⁇ volatile memory 370 which may be in the form of one or more disks, flash memories, smart cards or other like removable secure memory which may be inserted into yet another processor (personal computer, mainframe, or like computer) for loading credential data prior to vehicle departure.
  • credentials may be inserted briefly into the PCMCIA slot, read into EVL volatile memory, and the credentials then removed freeing the slot. Altematively, the credentials may be left in the EVL during the entire transit. In this case, the log may be placed on the same physical device as the credentials, or the spare PCMCIA slot 390 may be used as the EVL log memory device.
  • Controller 352 also handles input functions from a global positioning system card 380 known in the art.
  • This card may be coupled to an antenna for periodically receiving real time of day and location data and storing the data in buffer memory for use by processor 351 for forming protected data packets as will be further described herein.
  • the card may be clocked by a local oscillator and have an intemal real time of day clock algorithm which is periodically maintained at a correct time of day by a satellite downlink signal received at an antenna (not shown).
  • Controller 352 also interfaces with a spare card that may be used for storing credentials, may comprise an analog interface or an interface to another bus system such as a vehicle bus system for collecting vehicle data (engine temperature, ignition, oil, fuel consumption, odometer and the like).
  • controller 355 provides a plurality of, for example, RS232 serial line interfaces to, for example, digital cellular communications apparatus or Type 3 AVI tags for roadside-to-vehicle short range communications via link 395, to other wireless communications via link 396, to additional sensors, such as digital sensors via link 397 different from those supported by card 390 and/or accessible through a vehicle bus and to a user interface via link 398 such as a keyboard, speech interface and/or display or speech synthesis interface.
  • RS232 serial line interfaces to, for example, digital cellular communications apparatus or Type 3 AVI tags for roadside-to-vehicle short range communications via link 395, to other wireless communications via link 396, to additional sensors, such as digital sensors via link 397 different from those supported by card 390 and/or accessible through a vehicle bus and to a user interface via link 398 such as a keyboard, speech interface and/or display or speech synthesis interface.
  • the processor 351 provides overall processing control and includes the intemal capabilities to control two PCMCIA ports on its own, namely ports for PCMCIA cards 360 and 370.
  • One the EVL media or card 370
  • the other is analog acquisition card 360 providing eight connections each for continuous and discrete analog signals, with the continuous signals typically digitized to 8 or 12 bits of resolution, for reception of such vehicle data as ignition switch position, speed, steering, brake accelerator data, tachometer data, electronic cargo bonding data and the like.
  • Some processors 351 desirably provide on-board One Time Programmable (OTP) memory which may be used to securely record the EVL-unique secret key and identification number. These are most desirably maintained as closed to the function of forming protected data packets as possible and desirably are not removed to FLASH memory 353 for fear of being intercepted and known by one not intended to possess them.
  • the FLASH memory 353 then is more desirably used for permanently storing the executable software.
  • the memory 353 may be loaded at the time of manufacture with the EVL-unique secret key and identification number if that data is not included in the processor's (351) on-board OTP memory. All memory capacities, bus sizes, capabilities and speeds are nominal.
  • the unit may provide DRAM and FLASH memory sizes from 256 kilobytes to 1024 kilobytes or larger by utilizing altemate sized chips cu ⁇ ently available.
  • Cu ⁇ ently available PCMCIA analog acquisition cards provide four to eight channels each of continuous or discrete inputs, but higher densities are anticipated and can be incorporated without changes to the unit's (300) hardware. Flexibility is enhanced using a PCMCIA design supporting cards for multiple functions and tasks. Altematively the co ⁇ esponding circuitry may be directly inco ⁇ orated onto the unit's motherboard (similar to the design of Figure 3A) or placed onto a daughterboard interfacing the ISA bus 356. The latter design may have a lower EVL hardware cost.
  • box 320 represents the data processing and information management function.
  • Data processing power has been increased to the level of an integrated 486 type microprocessor 322 with approximately 256 kilobytes of flash memory 321 and 1 megabyte of DRAM 323.
  • the processor interfaces with a data and information display and control function 335 including a keyboard or other input (not shown), touchscreen, or LCD, LCD controller and memory 336.
  • an extemal interface 340 To receive input and provide output externally, there are provided parallel port 341 of the processor and serial port 342 of an extemal interface 340. Through the extemal interface 340, there pass cellular phone data, roadside reader or tag data, GPS data, satellite communications data (such as LEOSAT) and Qualcomm OmniTrax data.
  • extemal interface 340 Through the extemal interface 340, there pass cellular phone data, roadside reader or tag data, GPS data, satellite communications data (such as LEOSAT) and Qualcomm OmniTrax data.
  • a PC- 104 mezzanine interface To obtain vehicle and other sensor data, there is an eight channel analog sensor interface 330 designated 331 through which multi-sensor data is acquired. As has already been described, the sensors obtain safety, emission, cargo security and vehicle security and safety data among other data.
  • EVL data information storage and retrieval are represented by box 325 including a first and second PCMCIA interface 326 and 327 for electronic credential data of driver, cargo and vehicle.
  • Figure 4 represents the creation of the log memory of the Electronic Vehicle Log (EVL) 1 of the present invention.
  • the protection provided for EVL memory 430 is described by outer dashed line box 433 as comprising a password and/or speaker verification.
  • an EVL-unique secret key is provided to processor and DRAM 400 (for example, processor 302, 351).
  • the processor gathers the vehicle location data and via link 402 the processor gathers date and real time data, for example, from the same source 303 or 380 as described earlier in connection with Figures 3A and 3B.
  • Processor 400 also obtains vehicle sensor data via link 403, credentials and event data via link or links 404 and cargo status data via link 405.
  • the output of the processor 400 is a protected data packet forwarded via link 420 to a non-volatile log memory 410, for example, similar in form to variable data 308a or memory 370.
  • An expanded view of the contents of a protected data packet 411 of the present invention is represented by block 411.
  • the protected data packet 411 contains logged information 420a, a real time of day and date stamp 420b, a vehicle location stamp 420c, the unique vehicle identification 420d and an electronic signature 420e formed as will be described herein.
  • Logged information 420a may represent a printed page scanned from a page scanner or more data and thus may comprise megabytes of memory.
  • a date and time stamp 420b may comprise just a hundred bytes of memory or less, for example, representing approximately twenty ASCII characters.
  • Vehicle location data 420c including latitude and longitude may require ten to twenty bytes.
  • a vehicle identifier 420d may comprise just the equivalent of about twenty ASCII characters.
  • the electronic signature 420e may require 200 bytes of data.
  • the EVL log data will be generated using the following steps: 1) Data for logging will be acquired from various sources including, but not limited to, on-vehicle sensors, extemal systems and cargo monitors. The types of data logged and methods for acquiring the data have been described already above. 2) When a log entry is to be made, the EVL processor 400 will obtain the cu ⁇ ent date and time of day, vehicle location (at least in the form of latitude and longitude and possibly in the form of map location data such as route and mileage along a route from a given point), the EVL secret key and the EVL unique identification data. The processes for obtaining that data have likewise been described above. 3) The EVL processor prepares a protected data packet (PDP) using the information from step 2. The processor computes the packet's electronic signature 420e using a secure hash algorithm, a public key encryption algorithm and the EVL secret key. The PDP is then stored on the data logging medium (card, disk or the like).
  • PDP protected data packet
  • Public key/private key encryption algorithms are known in the art including one formerly licensed through PKP Partners (a partnership of RSA and Cylink, which has recently been ordered dissolved by an arbitrator in California). Another is promoted through the National Institute of Standards and Technologies in Gaithersburg, Maryland (N.I.S.T.). US Patents numbered 4,405,829, 4,424,414, 4,200,770, 4,218,582, 4,995,082 and 5,231,668 describe this technology.
  • various methods may be used to transmit or transport the PDP's to other systems which may require the information (owners, drivers or governmental authorities). Additional encryption techniques may be used during transmission to prevent information from becoming available to unauthorized third parties who may be tapping the communications channel.
  • Figure 4B shows the public key encryption pairs used by different authorities.
  • data logging will be described in the context of the driver entering log data by way of example.
  • the driver inserts the removable non-volatile log memory 430 for the duration of the trip.
  • a driver may obtain access and log into the EVL by inputing their speech, a password or a biometric 433 after inserting their card memory 430.
  • the driver-unique data is used to decrypt a secret or private key member (for example, 45 la which is never released from secure memory) of a public key encryption pair 451a and 451b.
  • a secret or private key member for example, 45 la which is never released from secure memory
  • protected data packets containing this log data are generated with digital signatures formed by encrypting digital hash values with this secret key member 451a of the public key pair.
  • PDP's 420 are transmitted to a requesting user via electronic means, for example, wireless, telephone modem or a memory card.
  • the requesting user has a trusted (escrowed) copy of the public key 45 lb of the above-referenced public key pair 45 la, 451b, the pair including the secret key 451a (which never leaves secure memory) used for forming the electronic signature.
  • the public key 45 lb is used to verify that the electronic signature of the PDP is accurate. Co ⁇ ect verification of the electronic signature then confirms the data source (the driver-protected secret key 451a) and the integrity of the data (since the hash value matches the PDP data).
  • a governmental authority may obtain access by a defined process.
  • One example of such a process for obtaining an early transmission of vehicle data in advance of a border crossing or like event is described by the following.
  • the agency wishing to receive secure data generates a public key encryption pair 452a, 452b different from that used by the driver and distributes the public key portion 452b to any person or system desiring to transmit secure data.
  • the public key portion 452b is stored in EVL memory.
  • a profile of a commercial vehicle and a cargo may be extracted from the vehicle via a card memory or may be electronically extracted by wireless means prior to the vehicle's departure and delivered to the authority with the stored public key portion 452b.
  • the EVL generates a private encryption key 431 and uses it to encrypt PDP's with their co ⁇ esponding digital signatures.
  • the EVL encrypts this private encryption key 431 using the public key 452b and transmits that information to the agency receiving the data.
  • the receiving agency decrypts the EVL private encryption key 431 using the secret key portion 452a of the key pair 452a, 452b and then decrypts the PDP's using the decrypted key 431.
  • the profile and public key 452b are transmitted via a centralized authority data base to regional data bases for distribution to checkpoints, port of entry border crossings and the like along the intended route of the vehicle.
  • the vehicle is polled or inte ⁇ ogated, for example, preferably by wireless means in advance of reaching the facility so the vehicle need not stop its movement.
  • the vehicle transmitted profile data is compared with the previously transmitted profile data and the inspector may preclear the vehicle through the inspection station. If the inspection data is a weigh station, for example, and data is to be entered into the log by the authority, an electronic signature is utilized to verify the entered data, preventing subsequent modifications of the logged information. Moreover, at the time the entry is made, the vehicle position and time from the global positioning system may be automatically and simultaneously recorded, allowing detection of fraudulent entries.
  • a short range communications system may be used to verify that the vehicle crossing the border is the vehicle which received the preclearance to cross.
  • the vehicle may carry all the profile information in the EVL and transit the data via wireless means to the authority just a few minutes before arrival or before the approval (for example, preapproval at a border crossing) event.
  • some sort of short range transmission is useful as the vehicle crosses the border to physically confirm that the vehicle crossing the border is the same as the one that provided the profile and credentials data and received preapproval to cross.
  • credential data storage will be described in some detail.
  • An authorized individual such as an inspector or police officer creates a digital credential in a generating device's memory, for example, a laptop personal computer.
  • a secret key 454a of a public key pair 454a, 454b is used to generate a digital signature for the credential data.
  • the credential and signature are transmitted to the EVL using various means, possibly including wireless means, direct input (typing), or memory card transfer. This transfer may be encrypted as discussed above as desired, for wireless or other secure data transmission.
  • the credential and signature are formed into a PDP and logged as described above for the driver data logging operation. When the credential is subsequently transmitted to a requesting agency, the agency will use a trusted copy of the public key portion 454b to verify the electronic signature of the PDP.
  • the EVL will internally store the data for subsequent display, processing or transmission. Much of the data stored will be sensitive. For example, the tariff- related data may be used to facilitate international border crossing and if this data could be electronically forged, it would result in a loss of revenue or worse.
  • the storage techniques described above respond to this need for data security.
  • the storage approach is also related to the data reception and transmission approaches described above and further in the following discussion.
  • a removable non-volatile memory This may comprise flash memory or other non-volatile memory adapted to form a removable unit such as a PCMCIA card. One or more of these cards may comprise the EVL.
  • Another memory is a removable disk drive. This may comprise a floppy disk drive or removable hard disk drive such as one, likewise mounted on a PCMCIA card. This may likewise be secure enough to form an EVL.
  • An intemal non-volatile memory or disk drive may likewise comprise an EVL.
  • This storage device may be hosted entirely within the EVL housing 300, 350 of Figures 3 A or 3B. In one embodiment, it may not be removed without destruction of the data contained within.
  • an intemal volatile memory may be used as an EVL if protected from erasure, for example, by a battery pr other power back-up device permanently associated therewith.
  • removable memory will allow a certified person to place credentials or event data on the storage device by removing it from the EVL housing, placing it into another electronic device (such as a portable computer), and writing the credentials in a secure manner onto the memory device.
  • Non-volatile memory would require an interface between the EVL housing and the certified persons' electronic device. This interface could be either wired or wireless (radio frequency).
  • each discrete group of information to be protected is processed by assembling the data in an area of volatile memory.
  • the date and time of the packet creation are obtained from a reliable source and added to the packet.
  • GPS and a clock intemal to the EVL are possible sources.
  • the position of the vehicle at the time of the packet creation are obtained from a reliable source and added to the packet.
  • GPS and Loran are possible sources.
  • the EVL unique identification data is obtained and added to the packet.
  • a secure hash value is computed for the packet from the above-acquired data.
  • the secure hash value is then encrypted using the EVL unique secret key from a public key encryption key pair.
  • the encrypted secure hash value is the electronic signature for the packet which may be recovered by those having the key to the exclusion of others.
  • Packets with their co ⁇ esponding signatures are stored in the EVL on the various storage media chosen for the application as described above.
  • the addition of reliable date, time of day, and location data is a significant security feature. It can prevent an unscrupulous person skilled in the art of computer hardware and software manipulation from forging protected data packets and inserting them into the EVL memory when the EVL is at a location inconsistent with the legitimate position or at a time inconsistent with an expected time of day for legitimate packet creation.
  • the EVL secret key and EVL unique identification data may be further protected using other cryptographic or other technologies.
  • the EVL secret key and identification data may be encrypted by a password known only by the user (such as the driver). The user (driver) would be required to enter their password prior to the start of transit or the entry of their data. The unencrypted data would be maintained only as long as the vehicle travels and adheres to an intended route or defined itinerary prestored with the password of the driver.
  • PDP generation may be contingent upon successful completion of a Speaker Verification function within the EVL.
  • the EVL may include a speaker verification (identity verification) and speech recognition (password recognition) subsystem or subsystems which verbally accepts the password used to decrypt the EVL secret key and EVL identification data. If the registered vehicle driver's voice is not confirmed (through speaker verification, for example), then the PDP encryption is not performed.
  • Figure 5A provides a table as an example of a memory table of protected data packets that may be maintained in an in-vehicle database (EVL) according to the method of Figure 4.
  • One item may be the vehicle identification data which uniquely identify at least the vehicle.
  • Vehicle classification data may describe the type of vehicle/ trailer(s) and an oversize or overweight condition. For example, some states require no trailer(s) having a greater length than a predetermined length for safety reasons as automobiles allegedly are unable to pass such long trailers. Vehicle height limits are important for bridge and tunnel construction. Weight limits are imposed for highways because overweight vehicles are an important cause of the failure of roadways over time.
  • cargo description Another data item is cargo description. Their are various types including "hazardous" cargos that require special handling and special routing. Quantity must be logged and maintained for certain tariffs are based on quantity rather than weight or size. Cargo security is important to the trucker as well as the owner of the cargo. The cargo security is protected by bonding, by assuring environmental factors and the like. The cargo destination may vary with the route. Cargo is deposited and new cargo is picked up requiring new credential data be entered.
  • Route data comprises the following: intended route and intended stops along the way, altemate routes, expected times of arrival and destinations along the route. This data may be stored in the form of maps and compared with GPS data by appropriate algorithms to determine deviations from intended routes.
  • Safety information can contain inspections, dates of inspections, records of the inspections, and measurements taken. For example, brakes, engine failure, tire safety and the like, signal indicators and the like may be regarded over time.
  • credential data includes licenses permits, inspections, reports, trip logs of other trips, and manifests. This data is not intended to be entirely inclusive.
  • brake performance can demonstrate over time the mechanical status and history of the cab and trailer(s) brakes.
  • the driver status and history may be recorded.
  • the driver can collect road mileage, time or duration of travel for the mileage logged and health record. More particularly, the driver's vision, alcohol or dmg record and the like can be maintained with the driver's identification.
  • Figure 5B also refers to environmental systems for detecting temperature, pressure and the like which are factors of the environment of the vehicle, driver and cargo. Inspection records and on-board monitors and sensor data is recorded in an environmental system table over time.
  • Figures 6A and 6B provide charts showing several applications of the present invention identified as to service, application, technology or product applicable for providing that application, what can be demonstrated and its use.
  • Figure 6B is merely a continuation of Figure 6A.
  • the following services are performed by the present invention in combination with extemal systems as required: commercial fleet management so that a fleet operator may maintain data on their fleet of vehicles, emergency notification and personal security, hazardous material and incident notification, commercial vehicle electronic clearance and administrative procedures for state and intemationai border crossing, automated roadside safety inspections and on-board safety monitoring.
  • the reader will please refer to the charts for application, technology or product available, demonstration and utilization information for each of these.

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Traffic Control Systems (AREA)

Abstract

La présente invention concerne un procédé et un appareil pour la tenue à jour d'un livre de bord électronique (1) de véhicule faisant intervenir une constitution de paquets de données (411) protégés signés électroniquement par des utilisateurs certifiés. Ce livre de bord électronique (1) de véhicule comporte une mémoire permanente (2) sécurisée qui peut être retirée du véhicule (200). L'appareil (1), ou 'DPIU' (pour 'Data Processing Interface Unit', c'est-à-dire 'interface informatique'), a accès aux données 'date', 'heure réelle' et 'position' de façon que les paquets de données (411) protégés incluent également, outre les données à protéger, les informations de date, d'heure et de position concernant le véhicule (200) afin qu'à titre de protection supplémentaire contre la consignation de données frauduleuses ou falsifiées, il soit possible de faire des comparaisons avec des données vraisemblables. Des capteurs embarquées (6) assurent la collecte de données de suivi du transit et du chargement accessibles par divers utilisateurs certifiés. Les données portant sur les événements tels que les contrôles par les autorités administratives ou le franchissement des frontières peuvent être consignées par les autorités administratives.
PCT/US1995/012459 1995-10-06 1995-10-06 Livre de bord electronique pour vehicules WO1997013208A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US1995/012459 WO1997013208A1 (fr) 1995-10-06 1995-10-06 Livre de bord electronique pour vehicules

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US1995/012459 WO1997013208A1 (fr) 1995-10-06 1995-10-06 Livre de bord electronique pour vehicules

Publications (1)

Publication Number Publication Date
WO1997013208A1 true WO1997013208A1 (fr) 1997-04-10

Family

ID=22249857

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1995/012459 WO1997013208A1 (fr) 1995-10-06 1995-10-06 Livre de bord electronique pour vehicules

Country Status (1)

Country Link
WO (1) WO1997013208A1 (fr)

Cited By (39)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2326720A (en) * 1997-06-25 1998-12-30 Ford Motor Co Method of preventing odometer fraud
WO1999053446A1 (fr) * 1998-04-09 1999-10-21 Ali Reza Meragi Systemes de controle et de commande de vehicule
WO2000045343A1 (fr) * 1999-01-27 2000-08-03 Marcello Federici Systeme de prelevement automatique pour moyens de transport
WO2000060548A1 (fr) * 1999-03-31 2000-10-12 Robert Bosch Gmbh Dispositif et procede pour enregistrer des donnees dans un vehicule automobile et procede pour utiliser les donnees enregistrees
EP1046099A1 (fr) * 1998-11-06 2000-10-25 Phoenix Group, Inc. Systeme de donnees relatif a un accident de voiture
EP1081670A2 (fr) * 1999-08-31 2001-03-07 Hitachi, Ltd. Procédé et appareil de collecte d'information d'un véhicule
WO2001093210A1 (fr) * 2000-06-01 2001-12-06 Universitat Politecnica De Catalunya Procede pour la certification automatique de routes de transport terrestre et analogues et dispositif de mise en oeuvre dudit procede
ES2165268A1 (es) * 1999-04-23 2002-03-01 Ros Roca Sa Sistema de control de trasvase de fluido y otras incidencias en un vehiculo cisterna.
EP1211648A2 (fr) * 2000-11-30 2002-06-05 Fuji Jukogyo Kabushiki Kaisha Système de gestion de véhicule
WO2002045047A1 (fr) * 2000-11-28 2002-06-06 Frv-Electronics Vertriebs- Und Produktionsgesmbh Procede et dispositif permettant de detecter au moins un vehicule
EP1216888A2 (fr) * 2000-12-23 2002-06-26 Bayerische Motoren Werke Aktiengesellschaft Interface standard pour véhicule
EP1286312A2 (fr) * 2001-08-22 2003-02-26 Matsushita Electric Industrial Co., Ltd. Système d'archivage de données pour véhicules comprenant un stockage de données authentifié de façon sûre
WO2004025576A1 (fr) * 2002-09-16 2004-03-25 Logina Informacijske Tehnologije D.O.O. Dispositif pour mettre en evidence et enregistrer l'utilisation d'un vehicule automatiquement
FR2861202A1 (fr) * 2003-10-21 2005-04-22 Paul Grison Systeme de controle d'informations liees a un vehicule
DE10347504A1 (de) * 2003-10-13 2005-05-19 Harman Becker Automotive Systems Gmbh Verfahren zur Navigation und Navigationsgerät
WO2005093668A1 (fr) * 2004-03-09 2005-10-06 Bayerische Motoren Werke Aktiengesellschaft Documentation de prescriptions de service pour un vehicule automobile
EP1587036A1 (fr) * 2004-03-01 2005-10-19 Associated Consulting S.r.l. Appareil pour enregistrer des données relatives à la conduite et aux déplacements de véhicules automobiles
EP1599716A2 (fr) * 2003-02-11 2005-11-30 Smart Start Inc. Appareil pour le test de la sobriete dote d'une capacite de connexion obd-ii
WO2006089813A1 (fr) * 2005-02-24 2006-08-31 Siemens Vdo Automotive Ag Procede pour authentifier un module
EP1759357A1 (fr) * 2004-06-25 2007-03-07 Siemens Aktiengesellschaft Transmission de donnees dans un ensemble comportant un tachygraphe
EP1760623A2 (fr) * 2005-08-18 2007-03-07 Siemens Aktiengesellschaft Dispositif de sécurité pour appareils électroniques
EP1768076A1 (fr) * 2004-07-13 2007-03-28 Matsushita Electric Industrial Co., Ltd. Systeme de gestion d"objets mobiles, terminal mobile et processeur
WO2008087435A2 (fr) * 2007-01-20 2008-07-24 Link Direct Limited Authentification de données provenant de dispositifs d'enregistrement de type gps
WO2008090057A1 (fr) * 2007-01-25 2008-07-31 Continental Automotive Gmbh Tachygraphe
US20100322423A1 (en) * 2008-01-30 2010-12-23 Continental Automotive Gmbh Data Transmission Method, and Tachograph System
ITRM20090464A1 (it) * 2009-09-15 2011-03-16 Associated Consulting S R L Dispositivo di tracciamento memorizzazione e reporting di dati di trasporto
US20110087893A1 (en) * 2009-10-14 2011-04-14 Electronics And Telecommunications Research Institute Apparatus and method for preventing falsification of black box data
EP2362358A1 (fr) 2010-02-22 2011-08-31 Stoneridge Electronics AB Tachygraphe numérique et son procédé
US8892451B2 (en) 1996-01-29 2014-11-18 Progressive Casualty Insurance Company Vehicle monitoring system
US20150046229A1 (en) * 2013-08-06 2015-02-12 Pinc Solutions Managing trailers and shipments
EP2950278A3 (fr) * 2014-05-30 2016-03-09 HERE Global B.V. Signalement d'événement d'une conduite dangereuse
EP3166086A1 (fr) * 2015-11-09 2017-05-10 Cacciotti, Angelo Dispositif électronique ayant un haut niveau de sécurité et apte à réaliser l'acquisition, le stockage et la transmission de données dynamiques réelles et emplacement des données relatif au mouvement d'un véhicule
WO2017108401A1 (fr) * 2015-12-21 2017-06-29 Bayerische Motoren Werke Aktiengesellschaft Configuration automatique de transferts de données télématiques d'un véhicule automobile
CN108053725A (zh) * 2017-11-30 2018-05-18 无锡宙斯物联网股份有限公司 后视镜驾培系统的使用方法
DE102018200807A1 (de) 2018-01-18 2019-07-18 Audi Ag Verfahren und Servervorrichtung zum Bereitstellen eines digitalen Fahrzeugbegleitbuchs für ein Kraftfahrzeug
US11030702B1 (en) 2012-02-02 2021-06-08 Progressive Casualty Insurance Company Mobile insurance platform system
US20210389139A1 (en) * 2018-03-20 2021-12-16 Micron Technology, Inc. Re-Routing Autonomous Vehicles Using Dynamic Routing and Memory Management for Border Security Purposes
US11367033B2 (en) 2011-06-30 2022-06-21 Xrs Corporation Fleet vehicle management systems and methods
US12008840B2 (en) 2011-03-07 2024-06-11 Drivewyze Ltd. Vehicle traffic and vehicle related transaction control system

Citations (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3624608A (en) * 1970-06-08 1971-11-30 Manfred Altman Vehicle shared-use system
US3665397A (en) * 1970-06-08 1972-05-23 Minicars Inc Automobile rental system
US4754255A (en) * 1984-03-12 1988-06-28 Sanders Rudy T User identifying vehicle control and security device
US4804937A (en) * 1987-05-26 1989-02-14 Motorola, Inc. Vehicle monitoring arrangement and system
US4856072A (en) * 1986-12-31 1989-08-08 Dana Corporation Voice actuated vehicle security system
US4910493A (en) * 1988-07-11 1990-03-20 Automated Security (Holdings) Pcl Security systems
US4949263A (en) * 1987-06-01 1990-08-14 Alert-O-Brake Systems Inc. Load handling vehicle monitoring system
US5185700A (en) * 1989-06-15 1993-02-09 Pulse Electronics, Inc. Solid state event recorder
US5249127A (en) * 1990-03-14 1993-09-28 Yazaki Corporation Vehicle movement data recording and analyzing system and recording apparatus
US5303163A (en) * 1992-08-20 1994-04-12 Cummins Electronics Company Configurable vehicle monitoring system
US5307349A (en) * 1992-04-07 1994-04-26 Hughes Aircraft Company TDMA network and protocol for reader-transponder communications and method
US5347274A (en) * 1990-05-17 1994-09-13 At/Comm Incorporated Hazardous waste transport management system
US5359528A (en) * 1993-02-19 1994-10-25 Rockwell International Corp. System for accurately determining the mileage traveled by a vehicle within a state without human intervention
US5359522A (en) * 1990-05-09 1994-10-25 Ryan Michael C Fluid delivery control apparatus
US5379219A (en) * 1990-06-12 1995-01-03 Yazaki Corporation Vehicle digital movement data recording apparatus
US5416706A (en) * 1984-04-27 1995-05-16 Hagenbuch; Leroy G. Apparatus for identifying containers from which refuse is collected and compiling a historical record of the containers

Patent Citations (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3665397A (en) * 1970-06-08 1972-05-23 Minicars Inc Automobile rental system
US3624608A (en) * 1970-06-08 1971-11-30 Manfred Altman Vehicle shared-use system
US4754255A (en) * 1984-03-12 1988-06-28 Sanders Rudy T User identifying vehicle control and security device
US5416706A (en) * 1984-04-27 1995-05-16 Hagenbuch; Leroy G. Apparatus for identifying containers from which refuse is collected and compiling a historical record of the containers
US4856072A (en) * 1986-12-31 1989-08-08 Dana Corporation Voice actuated vehicle security system
US4804937A (en) * 1987-05-26 1989-02-14 Motorola, Inc. Vehicle monitoring arrangement and system
US4949263A (en) * 1987-06-01 1990-08-14 Alert-O-Brake Systems Inc. Load handling vehicle monitoring system
US4910493A (en) * 1988-07-11 1990-03-20 Automated Security (Holdings) Pcl Security systems
US5185700A (en) * 1989-06-15 1993-02-09 Pulse Electronics, Inc. Solid state event recorder
US5249127A (en) * 1990-03-14 1993-09-28 Yazaki Corporation Vehicle movement data recording and analyzing system and recording apparatus
US5359522A (en) * 1990-05-09 1994-10-25 Ryan Michael C Fluid delivery control apparatus
US5347274A (en) * 1990-05-17 1994-09-13 At/Comm Incorporated Hazardous waste transport management system
US5379219A (en) * 1990-06-12 1995-01-03 Yazaki Corporation Vehicle digital movement data recording apparatus
US5307349A (en) * 1992-04-07 1994-04-26 Hughes Aircraft Company TDMA network and protocol for reader-transponder communications and method
US5425032A (en) * 1992-04-07 1995-06-13 Hughes Aircraft Company TDMA network and protocol for reader-transponder communications and method
US5303163A (en) * 1992-08-20 1994-04-12 Cummins Electronics Company Configurable vehicle monitoring system
US5359528A (en) * 1993-02-19 1994-10-25 Rockwell International Corp. System for accurately determining the mileage traveled by a vehicle within a state without human intervention

Cited By (61)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8892451B2 (en) 1996-01-29 2014-11-18 Progressive Casualty Insurance Company Vehicle monitoring system
US9754424B2 (en) 1996-01-29 2017-09-05 Progressive Casualty Insurance Company Vehicle monitoring system
GB2326720B (en) * 1997-06-25 2001-08-15 Ford Motor Co Method of preventing odometer fraud
GB2326720A (en) * 1997-06-25 1998-12-30 Ford Motor Co Method of preventing odometer fraud
WO1999053446A1 (fr) * 1998-04-09 1999-10-21 Ali Reza Meragi Systemes de controle et de commande de vehicule
GB2352592B (en) * 1998-04-09 2003-03-12 Ali Reza Meragi Vehicle monitoring and control systems
GB2352592A (en) * 1998-04-09 2001-01-31 Ali Reza Meragi Vehicle monitoring and control systems
EP1046099A1 (fr) * 1998-11-06 2000-10-25 Phoenix Group, Inc. Systeme de donnees relatif a un accident de voiture
WO2000045343A1 (fr) * 1999-01-27 2000-08-03 Marcello Federici Systeme de prelevement automatique pour moyens de transport
WO2000060548A1 (fr) * 1999-03-31 2000-10-12 Robert Bosch Gmbh Dispositif et procede pour enregistrer des donnees dans un vehicule automobile et procede pour utiliser les donnees enregistrees
AU760059B2 (en) * 1999-03-31 2003-05-08 Robert Bosch Gmbh System and method for storing data in a motor vehicle and method for using the stored data
ES2165268A1 (es) * 1999-04-23 2002-03-01 Ros Roca Sa Sistema de control de trasvase de fluido y otras incidencias en un vehiculo cisterna.
EP1081670A2 (fr) * 1999-08-31 2001-03-07 Hitachi, Ltd. Procédé et appareil de collecte d'information d'un véhicule
EP1081670A3 (fr) * 1999-08-31 2002-11-27 Hitachi, Ltd. Procédé et appareil de collecte d'information d'un véhicule
WO2001093210A1 (fr) * 2000-06-01 2001-12-06 Universitat Politecnica De Catalunya Procede pour la certification automatique de routes de transport terrestre et analogues et dispositif de mise en oeuvre dudit procede
ES2162609A1 (es) * 2000-06-01 2001-12-16 Univ Catalunya Politecnica Sistema de certificacion automatica de rutas para transporte terrestre.
WO2002045047A1 (fr) * 2000-11-28 2002-06-06 Frv-Electronics Vertriebs- Und Produktionsgesmbh Procede et dispositif permettant de detecter au moins un vehicule
EP1211648A3 (fr) * 2000-11-30 2004-11-17 Fuji Jukogyo Kabushiki Kaisha Système de gestion de véhicule
EP1211648A2 (fr) * 2000-11-30 2002-06-05 Fuji Jukogyo Kabushiki Kaisha Système de gestion de véhicule
EP1216888A2 (fr) * 2000-12-23 2002-06-26 Bayerische Motoren Werke Aktiengesellschaft Interface standard pour véhicule
EP1216888A3 (fr) * 2000-12-23 2003-09-17 Bayerische Motoren Werke Aktiengesellschaft Interface standard pour véhicule
EP1286312A2 (fr) * 2001-08-22 2003-02-26 Matsushita Electric Industrial Co., Ltd. Système d'archivage de données pour véhicules comprenant un stockage de données authentifié de façon sûre
EP1286312A3 (fr) * 2001-08-22 2004-05-12 Matsushita Electric Industrial Co., Ltd. Système d'archivage de données pour véhicules comprenant un stockage de données authentifié de façon sûre
WO2004025576A1 (fr) * 2002-09-16 2004-03-25 Logina Informacijske Tehnologije D.O.O. Dispositif pour mettre en evidence et enregistrer l'utilisation d'un vehicule automatiquement
EP1599716A2 (fr) * 2003-02-11 2005-11-30 Smart Start Inc. Appareil pour le test de la sobriete dote d'une capacite de connexion obd-ii
EP1599716A4 (fr) * 2003-02-11 2009-06-24 1A Smart Start Inc Appareil pour le test de la sobriete dote d'une capacite de connexion obd-ii
DE10347504A1 (de) * 2003-10-13 2005-05-19 Harman Becker Automotive Systems Gmbh Verfahren zur Navigation und Navigationsgerät
WO2005041133A1 (fr) * 2003-10-21 2005-05-06 Paul Grison Systeme de controle d'informations liees a un vehicule
FR2861202A1 (fr) * 2003-10-21 2005-04-22 Paul Grison Systeme de controle d'informations liees a un vehicule
EP1587036A1 (fr) * 2004-03-01 2005-10-19 Associated Consulting S.r.l. Appareil pour enregistrer des données relatives à la conduite et aux déplacements de véhicules automobiles
WO2005093668A1 (fr) * 2004-03-09 2005-10-06 Bayerische Motoren Werke Aktiengesellschaft Documentation de prescriptions de service pour un vehicule automobile
EP1759357A1 (fr) * 2004-06-25 2007-03-07 Siemens Aktiengesellschaft Transmission de donnees dans un ensemble comportant un tachygraphe
EP1768076A1 (fr) * 2004-07-13 2007-03-28 Matsushita Electric Industrial Co., Ltd. Systeme de gestion d"objets mobiles, terminal mobile et processeur
EP1768076A4 (fr) * 2004-07-13 2008-09-10 Matsushita Electric Ind Co Ltd Systeme de gestion d"objets mobiles, terminal mobile et processeur
WO2006089813A1 (fr) * 2005-02-24 2006-08-31 Siemens Vdo Automotive Ag Procede pour authentifier un module
EP1760623A2 (fr) * 2005-08-18 2007-03-07 Siemens Aktiengesellschaft Dispositif de sécurité pour appareils électroniques
EP1760623A3 (fr) * 2005-08-18 2009-03-04 Continental Automotive GmbH Dispositif de sécurité pour appareils électroniques
WO2008087435A2 (fr) * 2007-01-20 2008-07-24 Link Direct Limited Authentification de données provenant de dispositifs d'enregistrement de type gps
GB2459227A (en) * 2007-01-20 2009-10-21 Link Direct Ltd Authenticating data from GPS logging devices
WO2008087435A3 (fr) * 2007-01-20 2008-12-24 Andrew Roxburgh Authentification de données provenant de dispositifs d'enregistrement de type gps
WO2008090057A1 (fr) * 2007-01-25 2008-07-31 Continental Automotive Gmbh Tachygraphe
US20100322423A1 (en) * 2008-01-30 2010-12-23 Continental Automotive Gmbh Data Transmission Method, and Tachograph System
US8484475B2 (en) * 2008-01-30 2013-07-09 Continental Automotive Gmbh Data transmission method, and tachograph system
ITRM20090464A1 (it) * 2009-09-15 2011-03-16 Associated Consulting S R L Dispositivo di tracciamento memorizzazione e reporting di dati di trasporto
US20110087893A1 (en) * 2009-10-14 2011-04-14 Electronics And Telecommunications Research Institute Apparatus and method for preventing falsification of black box data
US8527778B2 (en) * 2009-10-14 2013-09-03 Electronics And Telecommunications Research Institute Apparatus and method for preventing falsification of black box data
EP2362358A1 (fr) 2010-02-22 2011-08-31 Stoneridge Electronics AB Tachygraphe numérique et son procédé
US12008840B2 (en) 2011-03-07 2024-06-11 Drivewyze Ltd. Vehicle traffic and vehicle related transaction control system
US11367033B2 (en) 2011-06-30 2022-06-21 Xrs Corporation Fleet vehicle management systems and methods
US11030702B1 (en) 2012-02-02 2021-06-08 Progressive Casualty Insurance Company Mobile insurance platform system
US20150046229A1 (en) * 2013-08-06 2015-02-12 Pinc Solutions Managing trailers and shipments
EP2950278A3 (fr) * 2014-05-30 2016-03-09 HERE Global B.V. Signalement d'événement d'une conduite dangereuse
US10759442B2 (en) 2014-05-30 2020-09-01 Here Global B.V. Dangerous driving event reporting
US11572075B2 (en) 2014-05-30 2023-02-07 Here Global B.V. Dangerous driving event reporting
EP3166086A1 (fr) * 2015-11-09 2017-05-10 Cacciotti, Angelo Dispositif électronique ayant un haut niveau de sécurité et apte à réaliser l'acquisition, le stockage et la transmission de données dynamiques réelles et emplacement des données relatif au mouvement d'un véhicule
CN108292452A (zh) * 2015-12-21 2018-07-17 宝马股份公司 机动车的远程技术数据传输的自动配置
CN108292452B (zh) * 2015-12-21 2020-11-03 宝马股份公司 机动车的远程技术数据传输的自动配置
WO2017108401A1 (fr) * 2015-12-21 2017-06-29 Bayerische Motoren Werke Aktiengesellschaft Configuration automatique de transferts de données télématiques d'un véhicule automobile
CN108053725A (zh) * 2017-11-30 2018-05-18 无锡宙斯物联网股份有限公司 后视镜驾培系统的使用方法
DE102018200807A1 (de) 2018-01-18 2019-07-18 Audi Ag Verfahren und Servervorrichtung zum Bereitstellen eines digitalen Fahrzeugbegleitbuchs für ein Kraftfahrzeug
US20210389139A1 (en) * 2018-03-20 2021-12-16 Micron Technology, Inc. Re-Routing Autonomous Vehicles Using Dynamic Routing and Memory Management for Border Security Purposes

Similar Documents

Publication Publication Date Title
WO1997013208A1 (fr) Livre de bord electronique pour vehicules
US9990782B2 (en) Method for analyzing operation characteristics of a vehicle driver
US20240119768A1 (en) Recording and reporting of driving characteristics with privacy protection
US9037852B2 (en) System and method for independent control of for-hire vehicles
EP1159720B1 (fr) Procede pour accumuler des informations relatives a la circulation
CN103189900B (zh) 通用车辆管理系统
US20050278082A1 (en) Systems and methods for verification and resolution of vehicular accidents
JP2004526234A (ja) 通行料金判定システムで使用するための制御方法
JPH09506449A (ja) 運行ルート情報記録装置
CN1971656A (zh) 一种能对机动车和驾驶员进行可靠管理的电子检测系统
GB2451167A (en) Separation of cost calculation means and payment services in a Position-Based Charging system.
US11615649B2 (en) Systems and methods for pairing of for-hire vehicle meters and medallions
JP3419201B2 (ja) 移動体搭載端末装置並びに移動体
WO2017119817A1 (fr) Système et procédé de facturation de moyen de transport
JP4046013B2 (ja) 車両用ドライブレコーダ,車両分析装置、および鍵管理方法
Forkenbrock et al. A new approach to assessing road user charges
US20030034889A1 (en) Host system and method for sensed vehicle data
US20070024466A1 (en) System for controlling information relating to a vehicle
JP2004206510A (ja) 車両運行システム
JP2006168561A (ja) 車載装置および車両管理制御システム
CN201749565U (zh) 出租车和城市公交运营管理仪
JP2007230404A (ja) 免許改ざん防止装置、免許改ざん防止システム、免許改ざん防止方法およびプログラム
Ruby et al. State of Maryland Intelligent Transportation Systems: Security and Implementation Recommendations.

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): CA JP MX US

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): AT BE CH DE DK ES FR GB GR IE IT LU MC NL PT SE

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: JP

Ref document number: 97514214

Format of ref document f/p: F

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: CA