802.11ac (WiFi 5): Ein technischer Tiefenblick in Funktionen, Leistung und Bereitstellungsstrategien

802.11ac WiFi 5: A Technical Deep Dive into Features, Performance, and Deployment Strategies. A Purple Technical Briefing. Welcome to the Purple Technical Briefing series. Today we're doing a thorough deep dive into 802.11ac — or WiFi 5 as it's more commonly known in vendor literature and procurement conversations. Now, you might be thinking: WiFi 5 has been around since 2013. Why are we talking about it now? The answer is straightforward. Despite WiFi 6 and WiFi 7 generating most of the industry noise, the vast majority of enterprise wireless infrastructure currently deployed globally — in hotels, retail chains, conference centres, and public buildings — is still running on 802.11ac hardware. And it will continue to do so for the next three to five years in most mid-market organisations. So whether you're managing an existing 802.11ac estate, evaluating a refresh cycle, or trying to squeeze more performance out of your current deployment before a capital expenditure conversation, this briefing is for you. We'll cover the technical architecture, the real-world performance characteristics, the limitations you need to plan around, and the deployment strategies that actually work in high-density environments. Let's get into it. The IEEE ratified 802.11ac in December 2013. It operates exclusively in the 5 gigahertz band — and that's the first thing to understand. Unlike its predecessor 802.11n, which could operate on both 2.4 gigahertz and 5 gigahertz, 802.11ac is 5 gigahertz only. That's a deliberate design choice to access wider, less congested channels, but it also means your legacy 2.4 gigahertz devices — older IoT sensors, some building management systems, legacy handheld terminals — won't associate to a pure 802.11ac radio. You'll need dual-band access points in any real-world deployment. Now, the headline number you'll see in vendor datasheets is 3.5 gigabits per second theoretical maximum throughput. That figure comes from Wave 2 hardware using four spatial streams, 160 megahertz channel width, and 256-QAM modulation. In practice, you'll see aggregate throughput in the range of 400 megabits to 1.3 gigabits per second under typical enterprise conditions. The gap between theoretical and practical is significant, and understanding why is central to deploying this standard effectively. Let's break down the three headline features: MU-MIMO, wider channels, and beamforming. Multi-User MIMO — MU-MIMO — is arguably the most significant architectural advancement in 802.11ac Wave 2. Prior to MU-MIMO, access points operated in SU-MIMO mode: single-user MIMO, meaning the AP could only transmit to one client device at a time. Every other device had to wait its turn. In a hotel corridor with forty rooms, or a retail floor with a hundred staff devices, that queuing creates measurable latency and throughput degradation. MU-MIMO allows the access point to transmit simultaneously to up to four client devices on separate spatial streams. Think of it as the difference between a single-lane road and a four-lane motorway. The AP uses beamforming to direct each spatial stream at a specific client, so the signals don't interfere with each other. The practical result in a high-density environment is a meaningful reduction in per-client latency and a more consistent user experience across the cell. There's an important caveat here, though. MU-MIMO in 802.11ac is downlink only. The AP can transmit to four clients simultaneously, but each client still transmits back to the AP one at a time. This is a fundamental architectural limitation that WiFi 6 addressed with uplink MU-MIMO. In environments where clients are uploading large files — think a conference centre with presenters uploading slide decks, or a warehouse with barcode scanners sending inventory data — this downlink-only constraint becomes a real bottleneck. Channel width is the second major lever. 802.11ac supports channel widths of 20, 40, 80, and 160 megahertz. Wider channels mean more data throughput — an 80 megahertz channel delivers roughly twice the throughput of a 40 megahertz channel, all else being equal. However, wider channels consume more of the available spectrum, which reduces the number of non-overlapping channels you can configure. In the 5 gigahertz band, you have a limited pool of channels to work with, and if you're deploying multiple access points in close proximity — as you would in a hotel or a stadium — aggressive channel width settings will cause co-channel interference and actually degrade performance. The practical guidance here is: 80 megahertz channels are the sweet spot for most enterprise deployments. 160 megahertz is theoretically attractive but creates spectrum management headaches in dense environments. 40 megahertz is appropriate for very high-density deployments where you're prioritising channel reuse over per-AP throughput. Beamforming is the third key feature. 802.11ac mandates implicit beamforming and supports explicit beamforming via a sounding protocol between the AP and the client. In practical terms, the AP uses multiple antennas to shape the transmitted signal — concentrating radio energy toward the intended client rather than broadcasting omnidirectionally. This improves signal quality at the receiver, which allows higher modulation schemes to be used, which translates directly to higher throughput and better range. The real-world benefit of beamforming is most pronounced at the cell edge — those clients at the far end of the coverage area who would otherwise be operating at lower modulation rates. In a hotel deployment, that's the room at the end of the corridor. In a retail environment, it's the checkout terminal near the fire exit. Beamforming can meaningfully improve the experience for those edge clients without requiring additional access points. Now let's talk about the modulation scheme. 802.11ac introduced 256-QAM — Quadrature Amplitude Modulation — which encodes 8 bits per symbol compared to 64-QAM's 6 bits per symbol. That's a 33 percent increase in spectral efficiency. The trade-off is that 256-QAM requires a higher signal-to-noise ratio to decode reliably. In practice, this means 256-QAM is only achievable at relatively short range and in environments with low RF interference. In a noisy retail environment or a stadium concourse, you'll often find clients falling back to lower modulation rates, and your real-world throughput will reflect that. One more architectural point worth understanding: the distinction between Wave 1 and Wave 2 hardware. Wave 1 802.11ac access points, released from around 2013 to 2015, support up to three spatial streams and 80 megahertz channels. Wave 2 hardware, from 2015 onwards, adds the fourth spatial stream, 160 megahertz channel support, and critically, MU-MIMO. If you're managing an estate that includes Wave 1 hardware, you're missing MU-MIMO entirely, and that has significant implications for high-density performance. Now let me give you the practical deployment guidance that actually makes a difference. First: access point density. The most common mistake in 802.11ac deployments is under-provisioning AP density. The standard can deliver impressive per-AP throughput on paper, but in a venue with hundreds of concurrent clients, you need to think in terms of clients per AP, not coverage area per AP. A reasonable target for a high-density environment — a hotel conference room, a retail floor, a stadium concourse — is 25 to 30 active clients per AP. If you're planning for more than that on a single radio, you're setting yourself up for performance complaints. Second: channel planning. This is where most deployments go wrong. Use a proper RF survey tool before finalising your AP placement. Identify sources of interference — microwave ovens, DECT phones, neighbouring networks — and build your channel plan around the available clean spectrum. In the 5 gigahertz band, use DFS channels where your hardware and regulatory domain support it. They're often less congested than the lower U-NII-1 channels that everyone defaults to. Third: security architecture. 802.11ac itself doesn't mandate a specific security protocol, so your security posture is entirely determined by your configuration choices. For enterprise deployments, IEEE 802.1X with RADIUS authentication is the baseline. WPA2-Enterprise with AES-CCMP is the minimum acceptable standard. If you're running a guest network — which in a hotel or retail environment you almost certainly are — segment it onto a separate VLAN and SSID, enforce client isolation, and implement a captive portal with appropriate data capture for GDPR compliance. Fourth: the upgrade conversation. If you're on Wave 1 hardware and you're experiencing performance issues in high-density areas, the upgrade to Wave 2 — or better yet, to WiFi 6 — is likely to deliver measurable ROI within twelve to eighteen months through reduced support overhead and improved guest satisfaction scores. If you're already on Wave 2 hardware and your primary use case is guest internet access and basic enterprise applications, you may not need to upgrade for another two to three years. The pitfall to avoid: don't let vendors push you into a full infrastructure refresh based on theoretical throughput numbers. Benchmark your current deployment, identify the specific bottlenecks, and make the upgrade decision on evidence. Now let me run through the questions I get most often from network architects and IT managers. "Can 802.11ac support IoT devices?" — Yes, but with caveats. Many IoT devices only support 2.4 gigahertz, so you'll need dual-band APs. Keep IoT traffic on a separate SSID and VLAN to prevent it from competing with client traffic. "What's the realistic range of an 802.11ac AP?" — In an open office or hotel corridor, expect reliable coverage at 256-QAM out to about 30 to 40 metres. At the cell edge, you'll be operating at lower modulation rates. Plan your AP placement accordingly. "Should I enable 160 megahertz channels?" — In most enterprise environments, no. The spectrum management complexity outweighs the throughput benefit. Stick with 80 megahertz unless you have a specific high-throughput use case and a clean RF environment. "Is WPA3 supported on 802.11ac hardware?" — Many Wave 2 APs support WPA3 via firmware update, but check with your vendor. WPA3-SAE provides meaningful security improvements over WPA2-PSK, particularly for guest networks. "What about roaming?" — Implement 802.11r for fast BSS transition and 802.11k for neighbour reporting. Without these, roaming between APs in a large venue will cause noticeable session drops. To bring this together: 802.11ac remains a capable, well-understood standard that, when deployed correctly, delivers excellent performance for the majority of enterprise use cases. The key is understanding its constraints — downlink-only MU-MIMO, 5 gigahertz exclusivity, the spectrum management challenges of wide channels — and designing your deployment around them rather than against them. If you're planning a new deployment or a refresh, assess your client density requirements first. If you're consistently exceeding 30 clients per AP or you have significant uplink-heavy workloads, WiFi 6 is worth the investment. If you're within those parameters, a well-configured Wave 2 802.11ac deployment will serve you well for the next several years. For the next steps: conduct an RF site survey if you haven't done one recently, review your channel plan and AP density against your actual client counts, and audit your security configuration against current best practice — particularly if you're handling guest data subject to GDPR or payment card data subject to PCI DSS. You'll find detailed deployment guides, case studies, and configuration references at purple dot ai. Thanks for listening, and we'll see you in the next briefing.