CVO12-CV Driver Security Authentication Transaction Set Diagram



Get the Source Graphic, a Windows Metafile (WMF), in ZIP format.
More about ZIP files

The following discusses how the National ITS Architecture provides the transportation service described by this service package. Each numbered item describes the operation of that portion of the service package identified with the corresponding number on the transaction set diagram.

  1. The Fleet and Freight Management Subsystem (FFMS), representing an operations center for a fleet of commercial vehicles, collects the cv driver credential data from the Driver Identification Cards for its staff. FFMS will then send one or more expected driver identities to each Commercial Vehicle Subsystem (CVS). This may be sent on a regular basis or any time there is a change in the expected set of drivers. The list (expected driver identity characteristics) can include driver identification information such as Personal Identification Numbers (PINs) for each driver ID card (that might be swiped or read at the vehicle), and/or particular biometric measurements for individual drivers e.g. finger or handprint parameters, retina pattern parameters. The CVS will then send the expected driver identity characteristics to the Commercial Vehicle Check Subsystem (CVCS) in the field when passing a wireless roadside inspection facility. The cv driver credential from the Dirver Identification Card may also be read directly by the CVCS equipment in the field.

  2. When a driver wishes to operate a vehicle, their cv driver credential data is read from their Driver Identification Card and they provide their personal identification information to the vehicle (driver identity characteristics). The vehicle equipment analyzes the submitted characteristics and/or information, and based on the expected characteristics, identifies the driver (or that the driver is unidentified) and sends that information to the fleet operations center (identities).

  3. If a non-expected driver is attempting to operate the commercial vehicle (possible or likely vehicle hijacking), a message can be issued to the police function with appropriate jurisdiction (alarm). The alarm is provided to the Emergency System Operator (as part of emergency operations status) so that orders can be issued to stop the vehicle or take some other appropriate action.

  4. Disabling a commercial vehicle with an invalid driver can be initiated at any of three levels: by the vehicle (safe vehicle disable) when the driver fails the identity test, by the commercial vehicle operations center with a message from FFMS to the vehicle (commercial vehicle disable), or by an Emergency Management (EM) subsystem, i.e. law enforcement agency, with jurisdiction via the FFMS or commercial vehicle operations center (disable commercial vehicle). In the case of the law enforcement agency initiating the disable, the action is originated by the appropriate system operator (the Emergency System Operator as part of emergency operations inputs). The Commercial Vehicle Subsystem will also provide the CVCS with an indication that it is being disabled and its status (commercial vehicle disable status).

  5. Disabling a commercial vehicle with an invalid driver can be initiated at any of three levels: by the vehicle (safe vehicle disable) when the driver fails the identity test, by the commercial vehicle operations center with a message to the vehicle (commercial vehicle disable), or by the police agency with jurisdiction via the commercial vehicle operations center (disable commercial vehicle). In the case of the police agency initiating the disable, the action is originated by the appropriate system operator (the Emergency System Operator as part of emergency operations inputs).