Center --> Field:
field equipment configuration settings

Definitions

field equipment configuration settings (Information Flow): Control settings and parameters that are used to configure field equipment.

Center (Source Physical Object): This general physical object is used to model core capabilities that are common to any center.

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

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

US: NTCIP Generic Device - SNMPv1/TLS

Solution Description

This solution is used within the U.S.. It combines standards associated with US: NTCIP Generic Device with those for I-F: SNMPv1/TLS. The US: NTCIP Generic Device standards include upper-layer standards required to implement center-to-field communications for any device functionality. The I-F: SNMPv1/TLS standards include lower-layer standards that define one way to retrofit basic security into SNMPv1 implementations (mainly in the US); however, this only secures the communications link and does not provide end-application security and is not recommended for new deployments.

ITS Application Entity
Click gap icons for more info.
Mgmt

NTCIP 1201
Bundle: SNMPv1 MIB
Facilities
Security
Mind the gapMind the gap

IETF RFC 8446
TransNet

IP Alternatives
IETF RFC 9293
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 Regional
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 Moderate Moderate Moderate
Basis Commands could be sensitive; monitoring of center-based control could enable an attacker's situational awareness, thus should be MODERATE. Commands to Field Equipment must be authenticated as having come from a source entitled to issue that command, or roadway equipment may be comprimised. Similarly, commands and configuration must be guaranteed to be correct; not manipulated midstream or corrupted, or the roadway equipment may be mis-configured or compromised. The ability to remotely diagnose and configure devices is inherent to their successful operation. If this link is down it either suggests or will prompt field maintenance activity, which has a non-trivial cost and resource impact.


Security Characteristics Value
Authenticable True
Encrypt True