Transit Vehicle OBE --> Connected Vehicle Roadside Equipment:
vehicle profile
Definitions
vehicle profile (Information Flow): Information about a vehicle such as vehicle make and model, fuel type, engine type, size and weight, vehicle performance and level of control automation, average emissions, average fuel consumption, passenger occupancy, or other data that can be used to classify vehicle eligibility for access to specific lanes, road segments, or regions or participation in cooperative vehicle control applications.
Transit Vehicle OBE (Source 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.
Connected Vehicle Roadside Equipment (Destination Physical Object): 'Connected Vehicle Roadside Equipment' (CV RSE) represents the Connected Vehicle roadside devices that are used to send messages to, and receive messages from, nearby vehicles using Dedicated Short Range Communications (DSRC) or other alternative wireless communications technologies. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers.
Included In
This Triple is an instantiation of the more general triple:
This Triple is in the following Service Packages:
This triple is associated with the following Functional Objects:
- RSE Automated Vehicle Operations
- RSE CACC Operations
- RSE Infrastructure Restriction Warning
- RSE Low Emissions Zone Application
- RSE Restricted Lanes Application
- RSE Speed Warning
- RSE Traffic Gap Assist
- Vehicle Cooperative Cruise Control
- Vehicle Eco-Driving Assist
- Vehicle Gap Assist
- Vehicle Platoon Operations
- Vehicle Restricted Lanes Application
- Vehicle Speed Management Assist
This Triple is described by the following Functional View Data Flows:
- transit_vehicle_characteristics_for_roadside
- vehicle_characteristics_for_emissions
- vehicle_characteristics_for_roadside
- vehicle_system_characteristics_for_emissions
- vehicle_system_characteristics_for_roadside
This Triple has the following triple relationships:
None |
Communication Solutions
- US: SAE J3067 (J2735 SE) - LTE-V2X WSMP (21)
- US: SAE J3067 (J2735 SE) - WAVE WSMP (23)
- (None-Data) - BTP/GeoNetworking/G5 (42)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
ETSI 302 890-1 Addressed Elsewhere |
Facilities
Development needed |
Security
|
|
TransNet
|
|||
Access
|
Note that some layers might have alternatives, in which case all of the gap icons associated with every alternative may be shown on the diagram, but the solution severity calculations (and resulting ordering of solutions) includes only the issues associated with the default (i.e., best, least severe) alternative.
Characteristics
None defined |
Security
Information Flow Security | ||||
---|---|---|---|---|
Confidentiality | Integrity | Availability | ||
Security levels have not been defined yet. |