Traffic Management Center --> Parking Management Center:
parking traffic information

Definition
Included In
Communication Solutions
Characteristics
Security

Definitions

parking traffic information (Information Flow): Instructions for operation of local parking facilities to support regional traffic management objectives (e.g., which parking lot exits to use). Also, includes inputs from traffic sensors to monitor parking queues and support more effective management of parking entrances and exits.

Traffic Management Center (Source Physical Object): The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters.

Parking Management Center (Destination Physical Object): The 'Parking Management Center' manages one or more parking lots by providing configuration and control of field infrastructure, user account management and interfaces with financial systems to manage payment. This p-object takes the back office portion of the Parking Management System's functionality as it was defined in ARC-IT 8.3 and prior.

Included In

This Triple is in the following Service Packages:

PM04: Regional Parking Management

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

(None-Data) - Secure Internet (ITS) (32)
(None-Data) - Apache Kafka (36)
(None-Data) - OMG DDS (36)
(None-Data) - OASIS MQTT (42)
(None-Data) - OASIS AMQP (45)

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 AMQP

Solution Description

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

ITS Application Entity Development needed			Click gap icons for more info.
Mgmt Development needed	Facilities Development needed OASIS AMQP	Security IP Security Alternatives
	TransNet IP Alternatives Internet Transport Alternatives
	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	Recent
Spatial Context	Local
Acknowledgement	True
Cardinality	Unicast
Initiator	Destination
Authenticable	True
Encrypt	False

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	Low	Moderate	Low
Basis	Provides some indication of regional traffic management strategies, which might be useful to an attacker, but that is far from obvious. Marked LOW unless a use case for an attack based on this information seems likely.	If this flow were corrupted or modified then parking systems might not be able to cope with increased traffic as a result of regional management strategies. The impact will be inconvenience on the part of travelers, potentially many, but not a catastrophic event.	Probably does not need to be updated often.

Security Characteristics	Value
Authenticable	True
Encrypt	False

Traffic Management Center --> Parking Management Center:parking traffic information