ITS Communications Equipment --> Other ITS Objects:
proxied ITS information
Definitions
proxied ITS information (Information Flow): Information exchanged by ITS systems or devices where the sender is isolated from the receiver by an intermediary that acts as a proxy for the sender. This flow is a super-flow; it does not define specific content since it represents any information flow exchange between physical objects defined in ARC-IT. This information flow represents any of those information flows and inherits the data content and attributes defined in the more detailed information flows.
ITS Communications Equipment (Source Physical Object): 'ITS Communications Equipment' includes the communications hardware and software that supports secure, reliable communications. It provides the layered protocols and communications services and includes the physical network plant and network hardware that supports ITS communications. It also encompasses security services that protect communications and the management services that support network management. This physical object allows transportation stakeholders that are implementing their own communications solution to represent this implementation in their ITS architecture. The communications capabilities provided by this physical object are frequently purchased from a third party provider. When communications is a purchased service, the hardware and software included in this physical object are largely transparent to transportation stakeholders and may be transparent to the ITS architecture.
Other ITS Objects (Destination Physical Object): Representing other ITS Objects, 'Other ITS Objects' provides a source and destination for information exchange between ITS Objects.
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
No communications solutions identified.Characteristics
| None defined |
| 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 | High | High | High | |
| Basis | This value is derived from the specific flows satisfied by this super-flow. HIGH is set because some flows may require it. If the implementation includes flows with only a MODERATE or LOW confidentiality requirement, then this could be MODERATE or LOW, as appropriate. | This value is derived from the specific flows satisfied by this super-flow. HIGH is set because some flows may require it. If the implementation includes flows with only a MODERATE integrity requirement, then this could be MODERATE. | This value is derived from the specific flows satisfied by this super-flow. HIGH is set because some flows may require it. If the implementation includes flows with only a MODERATE integrity requirement, then this could be MODERATE. | |