Parking Management Center --> Transportation Information 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.

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:

Relationship	Source	Destination	Flow
Depends On	Parking Area Equipment	Parking Management Center	parking area information

Communication Solutions

EU: DATEX - DATEX Messaging (3)
US: CDS - Secure Internet (ITS) (9)
Parking - Secure Internet (ITS) (19)
US: ATIS - Secure Internet (ITS) (24)
(None-Data) - Secure Internet (ITS) (43)

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

Selected Solution

US: ATIS - Secure Internet (ITS)

Solution Description

This solution is used within Canada and the U.S.. It combines standards associated with US: ATIS with those for I-I: Secure Internet (ITS). The US: ATIS standards include upper-layer standards required to implement traveler information communications. The I-I: Secure Internet (ITS) standards include lower-layer standards that support secure communications between ITS equipment using X.509 or IEEE 1609.2 security certificates.

ITS Application Entity SAE J2353			Click gap icons for more info.
Mgmt Bundle: SNMPv3 MIB	Facilities SAE J2354 Presentation Format Alternatives IETF RFC 9110 IETF RFC 9112	Security Secure Session 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	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 --> Transportation Information Center:parking information