Light 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.
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 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 Control Automation
- 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:
- 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 |
This Triple is an instantiation of the more general triple:
Communication Solutions
-
US: SAE J3067 (J2735 SE) - LTE-V2X WSMP (18)
-
US: SAE J3067 (J2735 SE) - WAVE WSMP (31)
-
(None-Data) - BTP/GeoNetworking/G5 (58)
Selected Solution
(None-Data) - BTP/GeoNetworking/G5Solution 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.
This Triple is an instantiation of the more general triple:
Characteristics
| Characteristic | Value |
|---|---|
| Time Context | Recent |
| 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 | Low | Moderate | Moderate | |
| Basis | Includes no PII and probably includes information that could be observed, so no need for obfuscation. | As this information will be used to determine the vehicle's ability to access services or be charged usage fees, it must be correct and not easily forgeable. | This flow enables various services; if the flow is not available the vehicle may not be able to use those services, and also may be charged incorrectly. | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | False |