roadway characteristics (Information Flow): Detectable or measurable road characteristics such as friction coefficient and general surface conditions, road geometry and markings, etc. These characteristics are monitored or measured by ITS sensors and used to support advanced vehicle safety and control and road maintenance capabilities.
Roadway Environment (Source Physical Object): 'Roadway Environment' represents the physical condition and geometry of the road surface, markings, signs, and other objects on or near the road surface. It also represents the environmental conditions immediately surrounding the roadway. The roadway environment must be sensed and interpreted to support automated vehicle services. Surrounding conditions may include fog, ice, snow, rain, wind, etc. which will influence the way in which a vehicle can be safely operated on the roadway. The roadway environment must be monitored to enable corrective action and information dissemination regarding roadway conditions which may adversely affect travel. Infrastructure owner/operators can improve the roadway environment to improve the performance and accuracy of vehicle-based sensors that must sense and interpret this environment. Improvements could include changes in the shape, size, design, and materials used in signs, pavement markings, and other road features.
Vehicle (Destination Physical Object): This 'Vehicle' physical object is used to model core capabilities that are common to more than one type of Vehicle. It provides the vehicle-based general sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. Many of these capabilities (e.g., see the Vehicle Safety service packages) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle includes the common interfaces and functions that apply to all motorized vehicles. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. Advanced sensors, processors, enhanced driver interfaces, and actuators complement the driver information services so that, in addition to making informed mode and route selections, the driver travels these routes in a safer and more consistent manner. This physical object supports all six levels of driving automation as defined in SAE J3016. Initial collision avoidance functions provide 'vigilant co-pilot' driver warning capabilities. More advanced functions assume limited control of the vehicle to maintain lane position and safe headways. In the most advanced implementations, this Physical Object supports full automation of all aspects of the driving task, aided by communications with other vehicles in the vicinity and in coordination with supporting infrastructure subsystems.
This Triple is in the following Service Packages:
- VS01: Autonomous Vehicle Safety Systems
- VS02: V2V Basic Safety
- VS03: Situational Awareness
- VS05: Curve Speed Warning
- VS06: Stop Sign Gap Assist
- VS07: Road Weather Motorist Alert and Warning
- VS08: Queue Warning
- VS13: Intersection Safety Warning and Collision Avoidance
- VS14: Cooperative Adaptive Cruise Control
- VS15: Infrastructure Enhanced Cooperative Adaptive Cruise Control
- VS16: Automated Vehicle Operations
This Triple is in the following Functional Objects:
- Vehicle Control Warning
- Vehicle Environmental Monitoring
- Vehicle Gap Assist
- Vehicle Speed Management Assist
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
Communication SolutionsNo communications solutions identified.
|National||This triple should be implemented consistently within the geopolitical region through which movement is essentially free (e.g., the United States, the European Union).|
|Information Flow Security|
|Basis||Sensor-based information flows by definition have no confidentiality concerns.||While typically security concerns related to sensing ignored, if considered this would be LOW, as the obfuscation or failure of any given environmental sensor is likely to be overcome by the mass of data necessary to draw environmental concluisions.||While typically security concerns related to sensing ignored, if considered this would be LOW, as the obfuscation or failure of any given environmental sensor is likely to be overcome by the mass of data necessary to draw environmental concluisions.|