Connected Vehicle Roadside Equipment --> Light Vehicle OBE:
local traveler information
Definitions
local traveler information (Information Flow): Traveler information including traffic, road, and weather conditions for a particular locality. This flow includes the location-specific traveler information and time effectivity of the information.
Connected Vehicle Roadside Equipment (Source 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.
Light Vehicle OBE (Destination 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.
Included In
This Triple is in the following Service Packages:
This Triple is described by the following Functional View Functional Objects:
This Triple is described by the following Functional View Data Flows:
- None
This Triple has the following triple relationships:
None |
Communication Solutions
- US: SAE Traveler Info - LTE-V2X WSMP (21)
- US: SAE Traveler Info - WAVE WSMP (23)
- (None-Data) - BTP/GeoNetworking/G5 (42)
Selected Solution
Solution Description
ITS Application Entity
SAE J2735 SAE J2945/4 |
Click gap icons for more info.
|
||
Mgmt
SAE J3161 3GPP 24.301 3GPP 36.331 |
Facilities
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.
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). |
Security
Information Flow Security | ||||
---|---|---|---|---|
Confidentiality | Integrity | Availability | ||
Rating | Not Applicable | Moderate | Low | |
Basis | This data is intentionally transmitted to everyone via a broadcast. It can also be determined via other visual indicators. | Some minimal guarantee of data integrity is necessary for all C-ITS flows. Flaws in this information will have a minimal effect on systems receiving it. All of the information can be verified through other means, and in a worst case scenario will only cause slightly increased traffic in the general proximity of the RSE. | All of the information provided through this flow will be available from other sources and no systems will directly rely upon it. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | False |