Parking Management Center --> Center:
parking maneuver request

Definition
Included In
Communication Solutions
Characteristics
Security

Definitions

parking maneuver request (Information Flow): Request to move a vehicle to a designated parking spot, an intermediate staging area, or a pickup location. The request identifies the vehicle, the starting location, destination location, and information about the recommended route.

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.

Center (Destination Physical Object): This general physical object is used to model core capabilities that are common to any center.

Included In

This Triple is in the following Service Packages:

None

This triple is associated with the following Functional Objects:

None

This Triple is described by the following Functional View Data Flows:

None

This Triple has the following triple relationships:

None

Communication Solutions

(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

(None-Data) - Secure Internet (ITS)

Solution Description

This solution is used within Australia, Canada, the E.U. and the U.S.. It combines standards associated with (None-Data) with those for I-I: Secure Internet (ITS). The (None-Data) standards include an unspecified set of standards at the upper layers. 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 Development needed			Click gap icons for more info.
Mgmt Bundle: SNMPv3 MIB	Facilities Development needed	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	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	Moderate
Basis	Vehicle commands should result in vehicle movement, which is directly observable. There may be instances where remote monitoring of these instructions enables a nefarious use case, which suggests a MODERATE level of obfuscation is reasonable, as the impact is likely limited to a single vehicle with no safety impact.	If this flow is incorrect or unavailable, the vehicle owner/operator may be inconvenienced. It is unlikely there is a serious impact.	If this flow is incorrect or unavailable, the vehicle owner/operator may be inconvenienced. It is unlikely there is a serious impact.

Security Characteristics	Value
Authenticable	True
Encrypt	False

Parking Management Center --> Center:parking maneuver request