Center --> Field:
field equipment commands

Definitions

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

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

Solution Description

This solution is used within Canada and the U.S.. It combines standards associated with US: NTCIP Generic Device with those for I-F: SNMPv1. 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 standards include lower-layer standards that define how SNMPv1, which does not provide any security, is used within some deployments within the ITS industry. This solution is no longer recommended due to known security vulnerabilities.

ITS Application Entity
Mind the gap
Click gap icons for more info.
Mgmt

NTCIP 1201
Bundle: SNMPv1 MIB
Facilities
Security
Mind the gap

(None)
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 Regional
Acknowledgement True
Cardinality Unicast
Initiator Source
Authenticable True
Encrypt False


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 Low Moderate Moderate
Basis Commands could be sensitive, however this flow is local, meaning the Field Support Equipment is proximate to the ITS Roadway Equipment. Thus the risk of interception should be low. There may also be constraints on this flow that require this information to be transmitted in the clear. 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 False