Pathway Communications Unit --> ITS Object:
local ITS information

This triple is bi-directional. See also ITS Object --> Pathway Communications Unit: local ITS information

Definitions

local ITS information (Information Flow): ITS information that is relevant to a particular location (e.g., a particular intersection) that is of interest to receivers near that location. This flow is a super-flow; it does not define specific content since it represents any information flow exchange using short range communications between physical objects defined in ARC-IT. This includes both broadcast communications to all receivers within range and unicast communications targeted for a specific receiver. This information flow represents any of those information flows and inherits the data content and attributes defined in the more detailed information flows.

Pathway Communications Unit (Source Physical Object): The 'Pathway Communications Unit' provides wireless communications between the pathway infrastructure (either indoor or outdoor) and nearby mobile devices; Communications with adjacent field equipment (including other PCUs) and back-office centers that monitor and control the PCU are also supported. The PCU provides basic radio communications supporting the lower layers of the OSI stack (TransNet and SubNet layers of the ARC-IT communications model). Importantly, it can also serve as a reference for mobile devices to determine their position more accurately (e.g., through triangulation or other means).

ITS Object (Destination Physical Object): The general 'ITS Object' includes core capabilities common to any class of object.

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

    CharacteristicValue
    Time Context Recent
    Spatial Context Regional
    Acknowledgement True
    CardinalityUnicast
    InitiatorSource
    AuthenticableTrue
    EncryptTrue


    InteroperabilityDescription
    RegionalInteroperability 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.


    Security CharacteristicsValue
    AuthenticableTrue
    Encrypt True