Light Vehicle Driver --> Light Vehicle OBE:
light vehicle driver input
Definitions
light vehicle driver input (Information Flow): Driver input to the light vehicle on-board equipment including configuration data, settings and preferences, interactive requests, and control commands.
Light Vehicle Driver (Source Physical Object): The 'Light Vehicle Driver' represents the person that operates a light vehicle on the roadway. This physical object covers the interactions that are specific to light, passenger vehicles. See also the 'Driver' physical object that covers interactions that are shared by operators of light, transit, commercial, and emergency vehicles where the interactions are not particular to the type of vehicle.
Light Vehicle OBE (Destination Physical Object): The 'Light Vehicle OBE' includes traveler-oriented capabilities that apply to passenger cars, trucks, and motorcycles that are used for personal travel. The rules vary by jurisdiction, but generally light vehicles are restricted in their weight and the maximum number of passengers they can carry. In ARC-IT, the Light Vehicle OBE represents vehicles that are operated as personal vehicles that are not part of a vehicle fleet and are not used commercially; thus, the choice between the various vehicle subsystems should be based more on how the vehicle is used than how much the vehicle weighs. See also the 'Vehicle' subsystem that includes the general safety and information services that apply to all types of vehicles, including light vehicles.
Included In
This Triple is in the following Service Packages:
- MC12: One-Way Convoy Driving
- PM01: Parking Space Management
- PM02: Smart Park and Ride System
- PM03: Parking Electronic Payment
- PS10: Wide-Area Alert
- PS14: Disaster Traveler Information
- ST05: Electric Charging Stations Management
- ST06: HOV/HOT Lane Management
- ST10: Low Emissions Zone Management
- TI02: Personalized Traveler Information
- TI03: En-Route Guidance
- TI04: Trip Planning and Payment
- TI06: Shared Use Mobility and Dynamic Ridesharing
- TI09: Travel Services Information and Reservation
- TM10: Electronic Toll Collection
- TM11: Road Use Charging
- TM23: Border Management Systems
This triple is associated with the following Functional Objects:
- Light Vehicle Basic Toll/Parking Payment
- Light Vehicle Border Crossing Support
- Light Vehicle Electric Charging Assist
- Light Vehicle Interactive Traveler Information
- Light Vehicle Payment Service
- Light Vehicle Trip Planning and Route Guidance
This Triple is described by the following Functional View Data Flows:
- flvd-border_traveler_inputs
- flvd-guidance_data
- flvd-guidance_request
- flvd-guidance_route_accepted
- flvd-request_advisory_information
- flvd-toll_payment_request
- flvd-traveler_electric_charging_inputs
- flvd-trip modifications
This Triple has the following triple relationships:
| Relationship | Source | Destination | Flow |
|---|---|---|---|
| Interactive | Light Vehicle OBE | Light Vehicle Driver | light vehicle driver updates |
Communication Solutions
No communications solutions identified.Characteristics
| None defined |
| Interoperability | Description |
|---|---|
| Not Applicable | Interoperability ratings don't apply per se to some types of interfaces like human interfaces. These interfaces may still benefit from associated standards (e.g., ergonomic and human factors standards for human interfaces), but the primary motive for these standards is not interoperability. |
Security
| Information Flow Security | ||||
|---|---|---|---|---|
| Confidentiality | Integrity | Availability | ||
| Rating | Moderate | High | High | |
| Basis | Data included in this flow may include origin and destination information, which should be protected from other's viewing as it may compromise the driver's privacy. | Commands from from the driver to the vehicle must be correct or the vehicle may behave in an unpredictable and possibly unsafe manner | Commands must always be able to be given or the driver has no control. | |