Maint and Constr Vehicle OBE --> Connected Vehicle Roadside Equipment:
vehicle location and motion
Definitions
vehicle location and motion (Information Flow): Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size.
Maint and Constr Vehicle OBE (Source Physical Object): The 'Maint and Constr Vehicle OBE' resides in a maintenance, construction, or other specialized service vehicle or equipment and provides the processing, storage, and communications functions necessary to support highway maintenance and construction. All types of maintenance and construction vehicles are covered, including heavy equipment, supervisory vehicles, unmanned remote controlled field maintenance robots, and sensory platforms that may be wheeled or low altitude aerial vehicles (e.g. drones, balloons). The MCV OBE provides two-way communications between drivers/operators and dispatchers and maintains and communicates current location and status information. A wide range of operational status is monitored, measured, and made available, depending on the specific type of vehicle or equipment. A snow plow for example, would monitor whether the plow is up or down and material usage information. The Maint and Constr Vehicle OBE may also contain capabilities to monitor vehicle systems to support maintenance of the vehicle itself. A separate 'Vehicle OBE' physical object supports the general vehicle safety and driver information capabilities that apply to all vehicles, including maintenance and construction vehicles. The Maint and Constr Vehicle OBE supplements these general capabilities with capabilities that are specific to maintenance and construction vehicles.
Connected Vehicle Roadside Equipment (Destination Physical Object): 'Connected Vehicle Roadside Equipment' (CV RSE) represents the Connected Vehicle roadside devices (i.e., Roadside Units (RSUs)) equipped with short range wireless (SRW) communications technology, as well as any other supporting equipment that leverage the RSU and are not described by other objects (e.g., a local roadside processor). CVRSE are used to send messages to, and receive messages from, nearby vehicles and personal devices equipped with compatible communications technology. 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.
This Triple is an instantiation of the more general triple:
Included In
This Triple is in the following Service Packages:
This triple is associated with the following Functional Objects:
- RSE Environmental Monitoring
- RSE Incident Scene Safety
- RSE Intersection Management
- RSE Intersection Safety
- RSE Rail Crossing Warning
- RSE Restricted Lanes Application
- RSE Traffic Gap Assist
- RSE Traffic Monitoring
- RSE Traveler Information Communications
- RSE Work Zone Safety
- RSE Wrong Way Vehicle Warning
- Vehicle Basic Safety Communication
- Vehicle Gap Assist
- Vehicle Rail Crossing Warning
- Vehicle Restricted Lanes Application
This Triple is described by the following Functional View Data Flows:
- vehicle_roadside_current_status_data
- vehicle_roadside_light_setting
- vehicle_roadside_location_data
- vehicle_roadside_size_data
- vehicle_roadside_speed_data
- vehicle_status_for_intersection
This Triple has the following triple relationships:
| None |
This Triple is an instantiation of the more general triple:
Communication Solutions
-
US: SAE LTE-V2X BSM - LTE-V2X WSMP (13)
-
EU: CA Service - BTP/GeoNetworking/G5 (21)
-
US: SAE Basic Safety Messages - WAVE WSMP (26)
Selected Solution
US: SAE LTE-V2X BSM - LTE-V2X WSMPSolution Description
|
ITS Application Entity
![]()
SAE J2735 ![]() SAE J3161/1 ![]() |
Click gap icons for more info.
|
||
|
Mgmt
SAE J3161 ![]() 3GPP 24.301 ![]() 3GPP 36.331 ![]() |
Facilities
SAE J2735 ![]() |
Security
|
|
|
TransNet
IEEE 1609.3 ![]() |
|||
|
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.
This Triple is an instantiation of the more general triple:
Characteristics
| Characteristic | Value |
|---|---|
| Time Context | Now |
| Spatial Context | Adjacent |
| Acknowledgement | False |
| Cardinality | Broadcast |
| Initiator | Source |
| Authenticable | True |
| Encrypt | False |
| Interoperability | Description |
|---|---|
| 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). |
This Triple is an instantiation of the more general triple:
Security
| Information Flow Security | ||||
|---|---|---|---|---|
| Confidentiality | Integrity | Availability | ||
| Rating | Not Applicable | High | Moderate | |
| Basis | This data is intentionally transmitted to everyone via a broadcast. Much of its information content can also be determined via other visual indicators | Incorrect information could lead to the system not operating properly. If the system does not properly know where the vehicle is, it cannot make an accurate decision about whether there is going to be a pedestrian in the crosswalk that the vehicle is approaching. This can have a safety impact.; DISC: NYC believes this to be MODERATE | This data is required for the system to operate properly. If this data is not available, the system cannot give accurate warning information. | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | False |


