Autonomous Vehicle Parking Technology: Infrastructure Preparation and Protocol Development

The timeline for widespread autonomous vehicle deployment has been revised downward by nearly every major forecaster over the past five years — the technology is harder than anticipated, regulation is slow, and public acceptance is uneven. But the vehicles are coming, and they will interact with parking infrastructure in ways that require physical and digital preparation that takes years to implement.

Parking facility operators who are making infrastructure investments today — new construction, major renovations, technology platform upgrades — should understand how AV requirements will affect those investments and which preparations represent prudent infrastructure without premature commitment.

SAE Levels and Parking Relevance

The SAE International J3016 standard defines six levels of driving automation (L0–L5). Parking-relevant levels:

L2 (Partial Automation): The vehicle can steer and control speed simultaneously in certain conditions, but a human driver must remain engaged. Parking assist features at L2 — automated parallel parking, perpendicular parking — are already deployed in many current vehicles. These features use the vehicle’s own sensors and do not require parking infrastructure.

L3 (Conditional Automation): The vehicle can manage all aspects of driving in specific operational design domains (ODDs) but requires a human to be available to take over when the system requests. L3 highway automation is commercially deployed (Mercedes DRIVE PILOT, for example), but L3 in parking environments is less developed.

L4 (High Automation): The vehicle can manage all aspects of driving within defined ODDs without requiring human intervention, even if the human cannot take over. L4 is where automated valet parking becomes technically feasible — the vehicle navigates a parking structure, finds a space, and parks without a driver.

L5 (Full Automation): No operational domain restrictions. Fully self-driving in all conditions. Still a research objective rather than a deployment reality.

Current parking infrastructure planning should focus on L4 requirements: what does a parking facility need to support a vehicle that can navigate, park, and retrieve autonomously within the facility’s operational domain?

Vehicle-to-Infrastructure (V2X) Communication

V2X (Vehicle-to-Everything) communication enables direct data exchange between vehicles and roadside infrastructure, including parking facilities. Relevant V2X standards:

DSRC (Dedicated Short-Range Communications): IEEE 802.11p, operating at 5.9 GHz, provides low-latency V2X communication. DSRC has been deployed in some US DOT pilot projects but has lost ground to C-V2X as the preferred technology in recent regulatory frameworks.

C-V2X (Cellular V2X): Based on 3GPP LTE-V2X (Rel. 14) and 5G NR-V2X (Rel. 16), C-V2X uses cellular infrastructure for both long-range (via network) and direct short-range (sidelink) communication. The FCC’s 2020 decision to reallocate DSRC spectrum in favor of Wi-Fi, with a portion reserved for C-V2X, effectively shifted the US toward C-V2X.

For parking facilities, V2X communication enables:

• Dynamic map data: Real-time facility maps (lane geometries, space locations, obstructions) pushed to vehicles upon entry
• Space reservation and guidance: Direct communication of available space locations to vehicles without relying on driver-observed signage
• Gate authorization: Automatic permit verification and gate control through V2X rather than physical credential presentation
• Safety broadcast: Broadcasting the presence of pedestrians or other vehicles in blind spots to approaching autonomous vehicles

Physical Infrastructure for AV Parking

Clear Wayfinding and Lane Geometry

Autonomous vehicles navigate using a combination of onboard sensors (LiDAR, cameras, radar) and high-definition maps. Parking facilities designed for human-driven vehicles often have ambiguous geometry — poorly defined lane edges, inconsistent lane widths, faded markings — that is tolerable for human interpretation but challenging for automated systems.

AV-friendly parking facility design or retrofit elements:

• Consistent, highly visible lane markings: Machine-readable lane markings with reflective properties optimized for vehicle sensors (not just for human visibility)
• Standardized lane widths: Minimum 10-foot lane widths for two-way traffic; consistent throughout the facility
• Clear vertical clearance marking: Machine-readable height indication at entry and at each level transition
• Defined parking space boundaries: High-contrast space markings that are reliably detectable by vehicle cameras

Connectivity Infrastructure

Autonomous vehicles operating in a parking facility need continuous connectivity for map updates, remote monitoring, and emergency intervention:

• WiFi coverage: Consistent WiFi 6 coverage throughout the facility, including ramps and transitional areas
• Cellular coverage: For facilities where WiFi coverage gaps are unavoidable, cellular coverage ensures connectivity continuity
• Latency specifications: V2X and remote monitoring applications are latency-sensitive; network infrastructure should be specified with maximum latency requirements

Designated AV Zones

Some parking facilities have designated AV-compatible zones — areas specifically designed or retrofitted for AV operation, with better connectivity, markings, and operational procedures. Locating EV charging infrastructure in AV-designated zones reduces the complexity of AV-EV charging coordination (an autonomous vehicle that can navigate to a parking space can also navigate to a charger).

Automated Valet Parking Systems

Automated valet parking (AVP) systems, defined under the ISO 23374 standard, allow a vehicle to park itself within a defined, managed geofenced area while the driver exits the vehicle at a drop-off zone.

AVP systems require:

• A geofenced parking zone with precise mapped geometry
• V2X or cloud-based communication to the AVP management system
• A pedestrian-free operational zone during AV movement (this requirement is operationally complex in mixed-use facilities)
• A vehicle readiness verification interface (the driver activates AVP and grants control to the system)

Commercial AVP demonstrations have occurred at airports and major facilities, but widespread deployment awaits regulatory clarity and liability frameworks.

Standards Landscape

The standards governing AV parking are actively developing:

• ISO 23374 (AVP Systems): Published 2021, provides system requirements for AVP within facilities
• IEEE 802.11p / 5G NR-V2X: Communication layer standards
• SAE J3016: AV level definitions
• SAE J2945/1: V2X safety communication standard
• ETSI ITS standards: European equivalents to US V2X standards, relevant for global AV deployments

Parking facility operators making infrastructure investments should track these standards through ITE (Institute of Transportation Engineers) and SAE membership or monitoring services to ensure planned investments align with the direction of standardization.

FAQ

When should parking facility operators begin investing in AV-compatible infrastructure? New construction and major renovations in urban markets are the right time to incorporate AV-preparedness design elements — lane markings, connectivity infrastructure, lane width standards — since the incremental cost is low at design stage. Retrofitting existing facilities for AV operations is more expensive and disruptive. For small facilities in non-urban markets, active investment may be premature given uncertain AV deployment timelines.

Will autonomous vehicles reduce parking demand? The relationship between AV adoption and parking demand is contested. One scenario: privately owned AVs that can self-park in cheaper remote facilities reduce demand for premium urban parking. Another scenario: AVs are primarily deployed as shared mobility services (robotaxis) that dramatically reduce private vehicle ownership, reducing total parking demand. A third scenario: AV-enabled trip generation (people who cannot currently drive making more trips) increases VMT and, consequently, parking demand. The most likely outcome varies by city density and market characteristics.

What liability framework applies when an AV damages parking facility equipment or another vehicle? AV liability frameworks are still developing in most US states. The general current position: liability falls on the vehicle owner (or the AV system provider, through product liability claims) when the vehicle is operating autonomously. Parking facility operators should review their insurance coverage to ensure adequate protection for property damage caused by AV systems operating within the facility.

Are there parking facility design standards specifically for AV operations? ISO 23374 addresses AVP system requirements. The Urban Land Institute (ULI) and the National Parking Association (NPA) have published research on parking design for future mobility that includes AV considerations. ITE’s design guidance is evolving to incorporate AV requirements. No comprehensive US parking design standard specifically for AV operations had been finalized as of 2025; designers should reference the available guidance documents and monitor for standard updates.