Basic Vehicle --> Vehicle:
host vehicle status
Definitions
host vehicle status (Information Flow): Information provided to the ITS on-board equipment from other systems on the vehicle platform. This includes the current status of the powertrain, steering, and braking systems, and status of other safety and convenience systems. In implementations where GPS is not integrated into the Vehicle On-Board Equipment, the host vehicle is also the source for data describing the vehicle's location in three dimensions (latitude, longitude, elevation) and accurate time that can be used for time synchronization across the ITS environment.
Basic Vehicle (Source Physical Object): 'Basic Vehicle' represents a complete operating vehicle. It includes the vehicle platform that interfaces with and hosts ITS electronics and all of the driver convenience and entertainment systems, and other non-ITS electronics on-board the vehicle. Interfaces represent both internal on-board interfaces between ITS equipment and other vehicle systems and other passive and active external interfaces or views of the vehicle that support vehicle/traffic monitoring and management. External interfaces may also represent equipment that is carried into the vehicle (e.g., a smartphone that is brought into the vehicle). Internal interfaces are often implemented through a vehicle databus, which is also included in this object. Note that 'Vehicle' represents the general functions and interfaces that are associated with personal automobiles as well as commercial vehicles, emergency vehicles, transit vehicles, and other specialized vehicles.
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.
Included In
This Triple is in the following Service Packages:
- MC07: Work Zone Safety Monitoring
- PS04: Mayday Notification
- PS05: Vehicle Emergency Response
- PS07: Incident Scene Safety Monitoring
- PT10: Intermittent Bus Lanes
- PT12: Transit Vehicle at Station/Stop Warnings
- ST01: Emissions Monitoring
- SU05: Location and Time
- SU12: Vehicle Maintenance
- TM02: Vehicle-Based Traffic Surveillance
- VS01: Autonomous Vehicle Safety Systems
- VS02: V2V Basic Safety
- VS03: Situational Awareness
- VS04: V2V Special Vehicle Alert
- VS05: Curve Speed Warning
- VS06: Stop Sign Gap Assist
- VS07: Road Weather Motorist Alert and Warning
- VS08: Queue Warning
- VS09: Reduced Speed Zone Warning / Lane Closure
- VS10: Restricted Lane Warnings
- VS11: Oversize Vehicle Warning
- VS12: Vulnerable Road User Safety
- 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 associated with the following Functional Objects:
- Vehicle Basic Safety Communication
- Vehicle Control Automation
- Vehicle Control Warning
- Vehicle Cooperative Cruise Control
- Vehicle Emergency Notification
- Vehicle Emissions Monitoring
- Vehicle Environmental Monitoring
- Vehicle Gap Assist
- Vehicle Intersection Warning
- Vehicle Location Determination
- Vehicle Platoon Operations
- Vehicle Restricted Lanes Application
- Vehicle Safety Monitoring
- Vehicle Situation Data Monitoring
- Vehicle Speed Management Assist
- Vehicle System Executive
- Vehicle System Monitoring and Diagnostics
- Vehicle Traveler Information Reception
This Triple is described by the following Functional View Data Flows:
- fbv-brake_servo_response
- fbv-crash_sensor_data
- fbv-diagnostics_data
- fbv-driver_safety_status
- fbv-steering_servo_response
- fbv-throttle_servo_response
- fbv-vehicle_attitude_data
- fbv-vehicle_condition
- fbv-vehicle_headway
- fbv-vehicle_identity
- fbv-vehicle_lane_position
- fbv-vehicle_motion_data
- fbv-vehicle_occupants
- fbv-vehicle_on_avo_lane
- fbv-vehicle_proximity_data
- fbv-vehicle_safety_status
- fbv-vehicle_size
- fbv-vehicle_speed
This Triple has the following triple relationships:
| None |
Communication Solutions
No communications solutions identified.Characteristics
| Characteristic | Value |
|---|---|
| Time Context | Now |
| Spatial Context | Adjacent |
| Acknowledgement | False |
| Cardinality | Unicast |
| Initiator | Source |
| Authenticable | True |
| Encrypt | False |
| 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 | Low | Moderate | High | |
| Basis | Unlikely that this includes any information that could be used against the originator. | This can be MODERATE or HIGH, depending on the application: This is used later on to determine whether a vehicle is likely going to violate a red light or infringe a work zone. This needs to be correct in order for the application to work correctly. | Since this monitors the health and safety of the vehicle and that information is eventually reported to the driver, it should be available at all times as it directly affects vehicle and operator safety. | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | False |