Connected Vehicle Roadside Equipment --> Light Vehicle OBE:
access violation notification
Definitions
access violation notification (Information Flow): Notification that an individual vehicle or user has committed an access violation. The flow identifies the nature of the violation and the time and location where the violation was recorded.
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:
- Light Vehicle Payment Service
- Light Vehicle Restricted Lanes Application
- RSE Restricted Lanes Application
This Triple is described by the following Functional View Data Flows:
- None
This Triple has the following triple relationships:
None |
Communication Solutions
- (None-Data) - G5 TCP (39)
- (None-Data) - LTE-V2X TCP (44)
- (None-Data) - WAVE TCP (46)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
|
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
Characteristic | Value |
---|---|
Time Context | Recent |
Spatial Context | Adjacent |
Acknowledgement | True |
Cardinality | Unicast |
Initiator | Source |
Authenticable | True |
Encrypt | True |
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 | Moderate | High | Moderate | |
Basis | May contain PII of a black listed user account, and/or vehicle identification. | Given the potential for PII to be involved, this needs to be correct and unalterable to avoid confusion or malfeasance. | Availability is at least MODERATE since the information has potential legal (or at least traffic law) implications that would otherwise involve a far less prompt and possibly manpower intensive interaction. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |