Field Maintenance Equipment --> Connected Vehicle Roadside Equipment:
equipment control commands

Definitions

equipment control commands (Information Flow): System-level control commands issued to the RSE such as reset and remote diagnostics.

Field Maintenance Equipment (Source Physical Object): 'Field Maintenance Equipment' represents the portable equipment used by field personnel to locally troubleshoot, initialize, reprogram, and test infrastructure equipment. It may include a laptop, specialized diagnostics tools, or any other general purpose or specialized equipment that is interfaced locally to infrastructure equipment to support maintenance and repair.

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:

RelationshipSourceDestinationFlow
Interactive Connected Vehicle Roadside Equipment Field Maintenance Equipment RSE status

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

US: NTCIP Roadside Unit - SNMPv3/TLS

Solution Description

This solution is used within Canada and the U.S.. It combines standards associated with US: NTCIP Roadside Unit with those for I-F: SNMPv3/TLS. The US: NTCIP Roadside Unit standards include upper-layer standards required to implement center-to-field roadside unit communications. The I-F: SNMPv3/TLS standards include lower-layer standards that support secure center-to-field and field-to-field communications using simple network management protocol (SNMPv3); implementations are strongly encouraged to use the TLS for SNMP security option for this solution to ensure adequate security.

ITS Application Entity

NTCIP 1218
Click gap icons for more info.
Mgmt

NTCIP 1201
Bundle: SNMPv3 MIB
Facilities

NTCIP 1218
ISO 15784-2
Security
Mind the gapMind the gap

IETF RFC 6353
IETF RFC 9456
TransNet
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 Recent
Spatial Context Adjacent
Acknowledgement True
Cardinality Unicast
Initiator Source
Authenticable True
Encrypt True


Interoperability Description
Local In cases where an interface is normally encapsulated by a single stakeholder, interoperability is still desirable, but the motive is vendor independence and the efficiencies and choices that an open standards-based interface provides.

Security

Information Flow Security
  Confidentiality Integrity Availability
Rating High High High
Basis RSE control, configuration and software/firmware update should all be protected from view. A hostile third party could use this information to reverse engineer control/configuration/update processes, and use that information in an attack across a broad swatch of infrastructure, which would have severe effects to the connected vehicle infrastructure. RSE control, configuration and update need to be correct or the RSE may be misconfigured, which for some applications could have severe safety impacts. RSE control, configuration and update needs to be available; field versions of these flows should always be available, which is why they are higher than the C2I versions.


Security Characteristics Value
Authenticable True
Encrypt True