Center --> Field:
field equipment software install/upgrade
Definitions
field equipment software install/upgrade (Information Flow): This flow supports installation and update of software residing in ITS roadway equipment. It supports download of the software installation files, including executable code and associated support files.
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
- TUF - Secure Internet (ITS) (4)
- (None-Data) - Secure Internet (ITS) (32)
- Data for Distribution (TBD) - Apache Kafka (36)
- Data for Distribution (TBD) - OMG DDS (36)
- (None-Data) - OASIS MQTT (42)
- Data for Distribution (TBD) - OASIS MQTT (42)
- (None-Data) - OASIS AMQP (45)
- Data for Distribution (TBD) - OASIS AMQP (45)
Selected Solution
Solution Description
ITS Application Entity
No Standard Needed |
Click gap icons for more info.
|
||
Mgmt
|
Facilities
TUF |
Security
|
|
TransNet
|
|||
Access
Internet Subnet Alternatives |
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 | 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 | High | Moderate | |
Basis | Field equipment software could be sensitive, both from a vulnerability assessment standpoint and because the software itself may be competition-sensitive. | Software updates to Roadway Equipment must be authenticated as having come from a source entitled to provide that software, or roadway equipment may be comprimised. Similarly, such software must be guaranteed to being the intent of the originator; not manipulated midstream or corrupted, or the roadway equipment may be mis-configured or compromised. | The ability to remotely update 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 |