Basic Transit Vehicle --> Transit Vehicle OBE:
host transit vehicle status
Definitions
host transit vehicle status (Information Flow): Information provided to the ITS on-board equipment from other systems on the Transit Vehicle Platform.
Basic Transit Vehicle (Source Physical Object): The 'Basic Transit Vehicle' represents the transit vehicle that hosts the on-board equipment that provides ITS functions. It includes a specialized and extended databus that is subject to different vehicle databus standards and hosts a broad range of components that are unique to a transit vehicle including the farebox and associated electronics, passenger counters, and transit security systems. The Transit Vehicle may represent a bus, paratransit vehicle, light rail vehicle, or other vehicle designed to carry passengers.
Transit Vehicle OBE (Destination Physical Object): The 'Transit Vehicle On-Board Equipment' (OBE) resides in a transit vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient movement of passengers. The types of transit vehicles containing this physical object include buses, paratransit vehicles, light rail vehicles, other vehicles designed to carry passengers, and supervisory vehicles. It collects ridership levels and supports electronic fare collection. It supports a traffic signal prioritization function that communicates with the roadside physical object to improve on-schedule performance. Automated vehicle location enhances the information available to the transit operator enabling more efficient operations. On-board sensors support transit vehicle maintenance. The physical object supports on-board security and safety monitoring. This monitoring includes transit user or vehicle operator activated alarms (silent or audible), as well as surveillance and sensor equipment. The surveillance equipment includes video (e.g. CCTV cameras), audio systems and/or event recorder systems. It also furnishes travelers with real-time travel information, continuously updated schedules, transfer options, routes, and fares. A separate 'Vehicle OBE' physical object supports the general vehicle safety and driver information capabilities that apply to all vehicles, including transit vehicles. The Transit Vehicle OBE supplements these general capabilities with capabilities that are specific to transit vehicles.
Included In
This Triple is in the following Service Packages:
- PT03: Dynamic Transit Operations
- PT05: Transit Security
- PT06: Transit Fleet Management
- PT11: Transit Pedestrian Indication
- PT12: Transit Vehicle at Station/Stop Warnings
- PT13: Vehicle Turning Right in Front of a Transit Vehicle
- PT15: Transit Stop Request
- PT17: Transit Connection Protection
- ST01: Emissions Monitoring
This triple is associated with the following Functional Objects:
- Transit Vehicle Emissions Monitoring
- Transit Vehicle On-Board Connection Protection
- Transit Vehicle On-Board Maintenance
- Transit Vehicle On-Board Paratransit Operations
- Transit Vehicle On-Board Trip Monitoring
- Transit Vehicle Passenger Counting
- Transit Vehicle Pedestrian Safety
- Transit Vehicle Schedule Management
- Transit Vehicle Security
- Transit Vehicle V2V Safety
This Triple is described by the following Functional View Data Flows:
- fbtv-availability
- fbtv-brake_servo_response
- fbtv-diagnostics_data
- fbtv-operator_safety_status
- fbtv-steering_servo_response
- fbtv-throttle_servo_response
- fbtv-transit_vehicle_disable_acknowledge
- fbtv-vehicle_attitude_data
- fbtv-vehicle_condition
- fbtv-vehicle_headway
- fbtv-vehicle_identity
- fbtv-vehicle_lane_position
- fbtv-vehicle_maintenance_data
- fbtv-vehicle_motion_data
- fbtv-vehicle_occupants
- fbtv-vehicle_on_avo_lane
- fbtv-vehicle_operator_inputs
- fbtv-vehicle_proximity_data
- fbtv-vehicle_safety_status
- fbtv-vehicle_security_status
- fbtv-vehicle_size
- fbtv-vehicle_speed
- fbtv-vehicle_trip_data
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 | True |
| Interoperability | Description |
|---|---|
| Local | In cases where an interface is normally encapsulated by a single stakeholder, interoperability is still desirable, but the motive is vendor independence and the efficiencies and choices that an open standards-based interface provides. |
Security
| Information Flow Security | ||||
|---|---|---|---|---|
| Confidentiality | Integrity | Availability | ||
| Rating | Moderate | Moderate | Moderate | |
| Basis | This can include some sensitive data. However, other data, such as vehicle location and motion will then be broadcast. There also may be proprietary information included in this. DISC THEA believes this to be LOW: "sensor data is not confidential; harm should not come from seeing status." | This is used later on to determine whether a vehicle should request priority at an intersection. If this information is incorrect the vehicle may make false requests. All other flows that use the data from this flow have a MODERATE integrity requirement, therefore, this must also have a MODERATE integrity requirement. DISC: THEA believes this should be HIGH: "sensor data needs to be accurate and should not be tampered with." | This information would need to be available immediately for the application to work.DISC: THEA believes this should be HIGH: "sensor data must be consistently available to feed BSMs broadcast at 10Hz, notifications, etc.." | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | True |