Field --> Connected Vehicle Roadside Equipment:
asset ID

Definitions

asset ID (Information Flow): A unique identification number and optional additional information. This flow represents the output of an RFID tag that is used for identification and tracking of assets, including both passive and active RFID tag technology options. For active tags, additional stored information that conveys additional information about the asset (e.g., lot number, production date, service data) may be provided along with the unique ID.

Field (Source Physical Object): This general physical object is used to model core capabilities that are common to any piece of field equipment.

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.

Included In

This Triple is in the following Service Packages:

This triple is associated with the following Functional Objects:

This Triple is described by the following Functional View Data Flows:

This Triple has the following triple relationships:

None

Communication Solutions

Solutions are sorted in ascending Gap Severity order. The Gap Severity is the parenthetical number at the end of the solution.

Selected Solution

(None-Data) - BTP/GeoNetworking/G5

Solution Description

This solution is used within Australia and the E.U.. It combines standards associated with (None-Data) with those for V-X: BTP/GeoNetworking/G5. The (None-Data) standards include an unspecified set of standards at the upper layers. The V-X: BTP/GeoNetworking/G5 standards include lower-layer standards that support broadcast, near constant, low latency vehicle-to-vehicle and vehicle-to-infrastructure communications using the ETSI GeoNetworking Bundle over the 5.9GHz spectrum.

ITS Application Entity
Mind the gapMind the gap

Development needed
Click gap icons for more info.
Mgmt
Mind the gapMind the gap

ETSI 302 890-1
Addressed Elsewhere
Facilities
Mind the gap

Development needed
Security
Mind the gapMind the gap
TransNet
Mind the gap
Access
TransNet TransNet

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Access Access

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

ITS Application ITS Application

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Mgmt Mgmt

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Facility Facility

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Security Security

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

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 Static
Spatial Context Local
Acknowledgement False
Cardinality Broadcast
Initiator Destination
Authenticable True
Encrypt False


Interoperability Description
Regional Interoperability throughout the geopolitical region is highly desirable, but if implemented differently in different transportation management jurisdictions, significant benefits will still accrue in each jurisdiction. Regardless, this Information Flow Triple should be implemented consistently within a transportation jurisdiction (i.e., the scope of a regional architecture).

Security

Information Flow Security
  Confidentiality Integrity Availability
Rating Low Moderate Moderate
Basis Unlikely that the ID of a particular asset, or even a group of assets would be useful to an attacker. Slight possibility, which is why Low vs. N/A. Infrastructure information should be correct or maintenance assets may be inappropriately assigned, located or otherwise referenced. Without this flow, asset location based safety applications may not function properly. The availability rating should mirror the importance of that service to the deployer. Generally if an operator goes to the trouble to track assets in the field this way, they consider this important and so the flow should be satisfied. Note that if an operator has multiple methods for tracking assets in the field, one instance of this flow could probably be reduced to LOW with minimal effect on service performance.


Security Characteristics Value
Authenticable True
Encrypt False