Light Vehicle OBE --> Connected Vehicle Roadside Equipment:
vehicle location and motion for surveillance
Definitions
vehicle location and motion for surveillance (Information Flow): Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size. This flow represents monitoring of basic safety data ('vehicle location and motion') broadcast by passing connected vehicles for use in vehicle detection and traffic monitoring applications.
Light Vehicle OBE (Source Physical Object): The 'Light Vehicle OBE' includes traveler-oriented capabilities that apply to passenger cars, trucks, and motorcycles that are used for personal travel. The rules vary by jurisdiction, but generally light vehicles are restricted in their weight and the maximum number of passengers they can carry. In ARC-IT, the Light Vehicle OBE represents vehicles that are operated as personal vehicles that are not part of a vehicle fleet and are not used commercially; thus, the choice between the various vehicle subsystems should be based more on how the vehicle is used than how much the vehicle weighs. See also the 'Vehicle' subsystem that includes the general safety and information services that apply to all types of vehicles, including light 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 Border Management
- RSE Map Management
- RSE Parking Management
- RSE Restricted Lanes Application
- RSE Speed Warning
- RSE Traffic Monitoring
- Vehicle Basic Safety Communication
- Vehicle Map Management
- Vehicle Speed Management Assist
This Triple is described by the following Functional View Data Flows:
- vehicle_guidance_probe_data
- vehicle_guidance_probe_data_for_archive
- vehicle_roadside_surveillance_location_data
- vehicle_roadside_surveillance_size_data
- vehicle_roadside_surveillance_speed_data
- vehicle_roadside_surveillance_status_data
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 (24)
-
US: SAE Basic Safety Messages - WAVE WSMP (29)
Selected Solution
US: SAE Basic Safety Messages - WAVE WSMPSolution Description
|
ITS Application Entity
 
SAE J2735  SAE J2945/1 |
Click gap icons for more info.
|
||
|
Mgmt
Addressed Elsewhere |
Facilities
SAE J2735 SAE J2945 |
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 | Recent |
| Spatial Context | Local |
| 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 | Moderate | Moderate | |
| Basis | This is directly observable data; DISC: WYO believes this to be MODERATE | Incorrect information here could lead to the system not functioning properly. If they are unable to properly detect all vehicles crossing the border, it would lead to confusion. There are other factors, such as visual indicators, of vehicles crossing the border, which can be used to help mitigate contradicting information. DISC: THEA believes this should be HIGH: "BSM info needs to be accurate and should not be tampered with" WYO believes this to be HIGH | This information must be available in a timely manner for the system to act upon it. The system can operate correctly if some messages are missed, but overall a majority of them should be received.; WYO believes this to be LOW | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | False |