6.7.1.2: Provide Driver Guidance Interface

This process shall provide a user interface for the vehicle's driver through which route guidance is provided. Three types of route guidance provided by other processes shall be supported by this process (dynamic infrastructure based, autonomous with infrastructure data update, and autonomous). The process shall enable input by the driver of the type of guidance required, the data from which the route is to be determined and output of the resulting route. The process shall not provide on-line guidance until the route has been accepted by the driver. For those forms of guidance that require an on-board map database, the process shall provide an interface to obtain and pay for an initial copy of the database plus updates when needed. The process shall support inputs from the driver in either manual or audio form, and shall provide its outputs in audible or visual forms. It shall enable the visual output to a display. The output shall not impair the driver's ability to control the vehicle in a safe manner.

This process is associated with the Light Vehicle OBE physical object.

This process is associated with the following functional objects:

• Light Vehicle Interactive Traveler Information
• Light Vehicle Trip Planning and Route Guidance

This process is associated with the following data flows:

• driver_guidance_accepted
• driver_guidance_request
• driver_input_request
• driving_guidance_instructions
• flvd-guidance_data
• flvd-guidance_request
• flvd-guidance_route_accepted
• tlvd-driving_guidance
• tlvd-guidance_input_request
• tlvd-guidance_route_details
• driver_advanced_payment_for_map
• driver_credit_identity
• driver_guidance_data
• driver_map_update_request
• driver_map_update_response
• vehicle_trip_feedback
• flvd-trip modifications