Pathway Equipment --> Transportation Information Center:
pathway equipment state

Definitions

pathway equipment state (Information Flow): Current state of the pathway equipment as it relates to use by pathway users (e.g., elevator on Floor 10, door open)

Pathway Equipment (Source Physical Object): 'Pathway Equipment' represents the equipment that is distributed along pathways that monitors and supports movement on the pathways and interfaces with electronic devices used by travelers on the pathways. This physical object includes elevators, escalators, electronic turnstiles, pedestrian (and other VRU) detectors, electronic signage, electronic waypoints, and warning systems for pathway users.

Transportation Information Center (Destination Physical Object): The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service.

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:

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

(None-Data) - OASIS MQTT

Solution Description

This solution is used within Australia and the U.S.. It combines standards associated with (None-Data) with those for OASIS MQTT. The (None-Data) standards include an unspecified set of standards at the upper layers. The OASIS MQTT standards include lower-layer standards that support data distribution of specific types of data.

ITS Application Entity
Mind the gap

Development needed
Click gap icons for more info.

Mgmt

OASIS MQTT DMP
Facilities
Mind the gapMind the gap

Development needed
OASIS MQTT
Security
Mind the gapMind the gap
TransNet
Access

Internet Subnet Alternatives
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 Probably no obfuscation is needed as most of the information in this flow should be otherwise observable. Information should be correct and available or wayfinding will not function well. A re-levelling of integrity measures may consider this LOW, depending on the importance of wayfinding. Information should be correct and available or wayfinding will not function well. Might be LOW depending on the importance attached to VRU wayfinding.


Security Characteristics Value
Authenticable True
Encrypt False