driver information Quintuple
Bidirectional?: False
driver information (A-Interconnect): This CVRIA application interconnect encapsulates all of the Layer 2 information flows between the 'Roadway Pedestrian Crossing Safety' application object and the 'Driver' physical object. In this case, there is only a single Layer 2 flow associated with this interconnect, so the Layer 1 application interconnect name and the Layer 2 information flow name are both 'driver information'. This application interconnect is uni-directional since the underlying layer 2 information flows go from 'ITS Roadway Equipment' to 'Driver'.
ITS Roadway Equipment (Source Physical Object): 'ITS Roadway Equipment' represents the ITS equipment that is distributed on and along the roadway that monitors and controls traffic and monitors and manages the roadway itself. In CVRIA, this physical object represents all of the other ITS field equipment that interfaces with and supports the Connected Vehicle Roadside Equipment (RSE). This physical object includes traffic detectors, environmental sensors, traffic signals, highway advisory radios, dynamic message signs, CCTV cameras and video image processing systems, grade crossing warning systems, and ramp metering systems. Lane management systems and barrier systems that control access to transportation infrastructure such as roadways, bridges and tunnels are also included. This object also provides environmental monitoring including sensors that measure road conditions, surface weather, and vehicle emissions. Work zone systems including work zone surveillance, traffic control, driver warning, and work crew safety systems are also included.
Roadway Pedestrian Crossing Safety (Source Application Object): "Roadway Pedestrian Crossing Safety" is an advanced infrastructure application that detects pedestrians and provides active safety warnings to drivers when cross walks are occupied.
Driver (Destination Physical Object): The 'Driver' represents the person that operates a vehicle on the roadway. Included are operators of private, transit, commercial, and emergency vehicles where the interactions are not particular to the type of vehicle (e.g., interactions supporting vehicle safety applications). The Driver originates driver requests and receives driver information that reflects the interactions which might be useful to all drivers, regardless of vehicle classification. Information and interactions which are unique to drivers of a specific vehicle type (e.g., fleet interactions with transit, commercial, or emergency vehicle drivers) are covered by separate objects.