Vehicle --> Parking Area Equipment:
loading zone use request

Definitions

loading zone use request (Information Flow): Request, booking, and confirmation that supports reservation for use of a loading or unloading area.

Vehicle (Source Physical Object): This 'Vehicle' physical object is used to model core capabilities that are common to more than one type of Vehicle. It provides the vehicle-based general sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. Many of these capabilities (e.g., see the Vehicle Safety service packages) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle includes the common interfaces and functions that apply to all motorized vehicles. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. Advanced sensors, processors, enhanced driver interfaces, and actuators complement the driver information services so that, in addition to making informed mode and route selections, the driver travels these routes in a safer and more consistent manner. This physical object supports all six levels of driving automation as defined in SAE J3016. Initial collision avoidance functions provide 'vigilant co-pilot' driver warning capabilities. More advanced functions assume limited control of the vehicle to maintain lane position and safe headways. In the most advanced implementations, this Physical Object supports full automation of all aspects of the driving task, aided by communications with other vehicles in the vicinity and in coordination with supporting infrastructure subsystems.

Parking Area Equipment (Destination Physical Object): 'Parking Area Equipment' provides electronic monitoring and management of parking facilities. It supports an I2V link to the Vehicle that allows electronic collection of parking fees and monitors and controls parking meters that support conventional parking fee collection. It also includes the instrumentation, signs, and other infrastructure that monitors parking lot usage and provides local information about parking availability and other general parking information. The two primary approaches to monitoring parking area usage are sensing vehicles within parking spots or counting vehicles as they come in and as they leave the area. This portion of the functionality must be located in the parking area where it can monitor, classify, and share information with customers and their vehicles. See also the separate 'Parking Management Center' physical object that may be located in a back office, remote from the parking area, which interfaces with the financial infrastructure and broadly disseminates parking information to other operational centers in the region.

Included In

This Triple is in the following Service Packages:

• PM06: Loading Zone Management

This triple is associated with the following Functional Objects:

• Loading Zone Management
• Vehicle Loading Zone Access

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

• loading_zone_use_request

This Triple has the following triple relationships:

Communication Solutions

• (None-Data) - Local Unicast Wireless (1609.2) (51)
• (None-Data) - Local Unicast Wireless (EU) (54)

Selected Solution

(None-Data) - Local Unicast Wireless (1609.2)

Solution Description

ITS Application Entity Development needed			Click gap icons for more info.
Mgmt Addressed Elsewhere	Facilities Development needed	Security Bundle: IEEE 1609.2
	TransNet IEEE 1609.3
	Access Bundle: Local Unicast Wireless SubNet (US)

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

Security