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

Definition
Included In
Communication Solutions
Characteristics
Security

Definitions

parking information (Information Flow): General parking information and status, including current parking availability, parking pricing, and parking space availability information, including features like number and type of electric charging spots.

Parking Management Center (Source 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.

Traffic Management Center (Destination 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.

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

EU: DATEX - DATEX Messaging (3)
US: CDS - Secure Internet (ITS) (6)
Parking - Secure Internet (ITS) (8)
US: ATIS - Secure Internet (ITS) (21)
(None-Data) - Secure Internet (ITS) (32)

Solutions are sorted in ascending Gap Severity order. The Gap Severity is the parenthetical number at the end of the solution.

Selected Solution

EU: DATEX - DATEX Messaging

Solution Description

This solution is used within the E.U.. It combines standards associated with EU: DATEX with those for C-C: DATEX Messaging. The EU: DATEX standards include upper-layer standards required to exchange and share data and information in the field of traffic and travel. The C-C: DATEX Messaging standards include lower-layer standards that support partially secure communications between two centers as commonly used in Europe.

ITS Application Entity Bundle: DATEX			Click gap icons for more info.
Mgmt Bundle: SNMPv3 MIB W3C WSDL 1.1	Facilities No Standard Needed	Security IETF RFC 8446
	TransNet IP Alternatives IETF RFC 9293
	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	Now
Spatial Context	Regional
Acknowledgement	True
Cardinality	Unicast
Initiator	Source
Authenticable	True
Encrypt	True

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	Moderate	Moderate	Moderate
Basis	Does not include PII, but does include usage information for a managed facility that implies a number of vehicles. While this is observable information, it could be considered competitive, and regardless is accessible without being physically present, which is its own barrier.	Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken.	Most likely not a frequently updated flow. Typically MODERATE for applications with a high degree of commercial vehicle parking, but could be LOW otherwise.

Security Characteristics	Value
Authenticable	True
Encrypt	True

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