Wi-Fi 6, 6E and Wi-Fi 7: Which Generation Should an Enterprise Network Choose?

In which environments do the differences between Wi-Fi 6, 6E and Wi-Fi 7 pay off? We cover the access point refresh decision through the client inventory, PoE budget and uplink checks.
Technical summary
Technology
IEEE 802.11ax, 802.11be, Wi-Fi 6E, OFDMA, MLO, 802.3bz, 802.3at/bt
Topic
Choosing an enterprise AP generation and timing the refresh
Level
Intermediate
Prerequisites
  • Basic Wi-Fi concepts (band, channel, SSID)
  • Knowledge of access switches and PoE
In this article8 sections

Most AP refresh projects start with the wrong question: “Which is the fastest?” The peak speed on the datasheet is a number no client in your office will ever see. When deciding between Wi-Fi 6 (802.11ax), Wi-Fi 6E (the extension of 802.11ax to 6 GHz) and Wi-Fi 7 (802.11be), three things are decisive: user density per cell, the client inventory, and whether the access switches can power these APs. Below we explain the differences between generations through features that matter in the field, and the refresh decision in the order of checks.

Technical features that set the generations apart

Peak speed is calculated when the widest channel, the highest modulation and the most spatial streams are achieved at the same time. In an office, these three rarely come together even for a single client. On the enterprise network side, it’s more accurate to group the useful features under four headings:

  • Efficiency: sharing channel time among many clients with less waiting (OFDMA, MU-MIMO).
  • Spectrum: the number of usable clean channels and channel width (the 6 GHz band, 160/320 MHz).
  • Link resilience: using multiple bands at the same time and skipping subchannels under interference (MLO, preamble puncturing).
  • Client behavior: battery saving and coexistence with neighboring cells (TWT, BSS coloring).

1024-QAM and 4096-QAM only come into play for clients close to the AP with a very high signal-to-noise ratio. Don’t write this into the capacity plan. It’s a bonus that comes in good conditions, nothing more.

Wi-Fi 6: OFDMA, BSS coloring and TWT

What Wi-Fi 6 really brings to an enterprise network is efficiency under density. In earlier generations, a transmission opportunity belonged to a single client; even for a small packet such as a voice packet, a chat message or IoT telemetry, the channel was occupied from start to finish. OFDMA divides the channel into resource units (RUs), sends data to multiple clients in the same transmission opportunity and allows scheduled multi-user transmission in the uplink direction. The gain doesn’t show in peak speed. It shows in latency.

BSS coloring assigns each BSS a color value between 1 and 63. If a frame that is heard belongs to another BSS and its signal is below a certain threshold, the device can transmit without treating the channel as busy. It reduces co-channel effects in dense deployments that are forced to reuse the same channel. It doesn’t rescue a bad channel plan.

TWT (Target Wake Time) lets the client negotiate wake times with the AP. It’s useful for battery-powered devices such as barcode scanners, sensors and handheld terminals; its effect on laptops is limited. In the field, TWT-related connection problems are seen with some client drivers. When a problematic client appears, you need to be able to disable the feature per SSID; look for this flexibility when choosing a platform.

Wi-Fi 6 operates in the 2.4 and 5 GHz bands. How many channels you have in 5 GHz depends on whether you can use DFS channels. We cover channel width and DFS decisions in detail in the channel width and transmit power settings article.

What Wi-Fi 6E and the 6 GHz band bring

Wi-Fi 6E isn’t a new protocol; it’s 802.11ax running in the 6 GHz band. All its value comes from spectrum. In this band there are only 6 GHz-capable devices, no management and protection traffic from older 802.11a/n/ac clients, and no need for DFS radar avoidance. 6 GHz can offer more channel options. Usable channels, widths and power limits vary by country, device support and installation type.

People get stuck at three points in the field:

  1. Regulatory conditions: Which sub-range of the 6 GHz band can be used, at which power class (e.g. indoor low power) and under which conditions varies from country to country. The common practice in Europe is the 5945–6425 MHz sub-band; for the current situation in Turkey, verify against BTK regulations and the channel list the AP vendor publishes for the Turkey country code.
  2. Coverage: Free-space loss at 6 GHz is slightly higher than at 5 GHz, and indoor power limits are low. Don’t assume an AP layout made for 5 GHz will give the same coverage at 6 GHz. Measure it.
  3. Security: WPA3 (OWE for open networks) and PMF are mandatory at 6 GHz. A WPA2-only client can’t see this band; build the SSID strategy accordingly.

Wi-Fi 7: MLO, 320 MHz and 4096-QAM

802.11be’s most meaningful innovation on the enterprise side is MLO (Multi-Link Operation). Simultaneous links can be established between client and AP on more than one band; traffic is steered to the most suitable link at that moment, or the bands are used together. When interference starts on one band, traffic shifting instantly to the other link is far more valuable than peak speed for latency-sensitive applications. However, MLO has different operating modes: simultaneous transmit/receive, or fast switching between bands with a single radio. Which mode is used depends on the support of the access point and the client; MLO and 320 MHz don’t work the same way on every Wi-Fi 7 device. The gain is determined by the mode the client supports. The AP alone doesn’t change anything.

The 320 MHz channel is defined only in the 6 GHz band. In Europe’s 480 MHz sub-band (5945–6425 MHz), a single non-overlapping 320 MHz channel fits; in a multi-AP office, channel reuse isn’t possible at this width. In enterprise design, even at 6 GHz the realistic range is 20–80 MHz. 4096-QAM carries 12 bits per symbol instead of 10 compared with 1024-QAM; the theoretical gain is about one fifth and is achieved only at very short range.

A feature that may be more useful is preamble puncturing: if a 20 MHz subchannel inside a wide channel is under interference, only that part is disabled instead of giving up the whole channel. It was optional in 802.11ax; in Wi-Fi 7 it’s much more widely supported. The primary source for the standard’s definitions and amendment process is the IEEE 802.11 working group.

Feature Wi-Fi 6 Wi-Fi 6E Wi-Fi 7
IEEE standard 802.11ax 802.11ax 802.11be
Bands 2.4 / 5 GHz 2.4 / 5 / 6 GHz 2.4 / 5 / 6 GHz
Widest channel 160 MHz 160 MHz 320 MHz (6 GHz)
Highest modulation 1024-QAM 1024-QAM 4096-QAM
Multi-band connection None None MLO
OFDMA Single RU / client Single RU / client Multi-RU

Client ecosystem and backward compatibility

The return of an AP generation is limited by the share of clients that can use it. A new AP serves older clients with backward compatibility; but an older client can’t benefit from the new features, stays on the air longer and pulls down the cell’s total throughput. The inventory should be on the table before the decision meeting:

  • Get a report of clients’ PHY type (802.11n/ac/ax/be) and band distribution from the controller or management platform.
  • List laptops’ wireless card models and driver versions from the MDM/inventory tool; operating system and driver support are also required for 6 GHz.
  • Classify slowly refreshed devices such as handheld terminals, label printers, medical devices and VoWiFi phones separately; these mostly support only 2.4 GHz or WPA2.
  • Put the computer refresh calendar side by side with the AP refresh calendar.

A situation you may encounter: most clients don’t support 6 GHz, but Wi-Fi 7 APs are being bought. This isn’t wrong; APs stay in the field for 5–7 years, and clients are refreshed during that time. But the justification is the life cycle, not today’s performance. State this clearly in the budget presentation, otherwise in the first week the question “why didn’t it get faster?” comes.

A generation change is rarely just an AP change. On the wired side, three items are directly affected, and this is where most surprises in the project come from.

Many enterprise APs from Wi-Fi 6 onward come with a 2.5GBASE-T or 5GBASE-T (IEEE 802.3bz) multigigabit uplink. At average load, a 1 Gbit/s port is enough for most office cells; short bursts of total traffic, however, can exceed this limit. 802.3bz was designed with a target of 2.5 Gbit/s up to 100 meters over existing Cat5e/Cat6 cabling; for 5 Gbit/s, cable category and alien crosstalk conditions within the bundle should be tested. If the port drops to 1 Gbit/s, look at the patch cord and intermediate connections first. Details on cable selection are in the choosing Cat6, Cat6A and fiber article.

PoE class

Tri-radio (2.4/5/6 GHz) and 4×4-radio APs mostly go above the 802.3at (PoE+) limit to run with the full feature set and may require 802.3bt. With 802.3at, the PSE provides 30 W per port and the power reaching the device is 25.5 W; with 802.3bt Type 3, these values are 60 W and 51 W. With insufficient power, the AP boots, its light comes on and it shows green on the dashboard. But it runs by reducing the number of radios or spatial streams, or by disabling the USB/second Ethernet port. That’s the silent performance loss. Be sure to read the “power-restricted mode” table on the model’s datasheet.

Switch power budget and heat

Look not only at per-port power but also at the switch’s total PoE budget and power supply redundancy. Worked example: if 24 APs on a 48-port access switch each draw 40 W in the worst case, a budget of 960 W is needed for the APs alone; IP phones and cameras on the same switch are added on top of that. If this load is carried by a single PSU, a PSU failure takes down the wireless for the whole floor. The heating that high-power PoE creates in cable bundles is a separate design topic.

Comparison table for the refresh decision

The table below is a starting recommendation for common scenarios. Verify each row with field measurements and the client inventory.

Scenario Recommended generation Reason
Small branch, older clients Wi-Fi 6 Low cost, PoE+ and 1G uplink are enough
Dense office, open space Wi-Fi 6E or 7 Clean channels at 6 GHz, co-channel effects decrease
Meeting and training rooms Wi-Fi 7 Resilience to interference with MLO and puncturing
Warehouse, production, handheld terminals Wi-Fi 6 Clients mostly 2.4/5 GHz; TWT is useful
Switch and PoE refresh not imminent Wi-Fi 6 or 6E The 802.3bt requirement can strain the infrastructure

Make the decision in this order:

  1. Is today’s problem coverage, capacity or client incompatibility? A coverage problem isn’t solved by changing generation; a site survey and measurement is needed first.
  2. What is the share of 6 GHz-capable devices in the client inventory, and how will it change within 3 years?
  3. Do the access switches support multigigabit and 802.3bt, and is the total PoE budget enough?
  4. What is the support status of the existing APs and controller according to the vendor’s life cycle page?
  5. Has the WPA3 migration been planned?

These answers determine not only the AP generation but also whether a switch refresh goes into the same project. For a roadmap that evaluates the generation choice together with the switch and cabling situation, a preliminary analysis can be done within enterprise network consulting; the installation and RF optimization side is the subject of the wireless network installation and optimization service.

Frequently asked questions

Do clients also need to be 6E to buy a Wi-Fi 6E access point?

To benefit from the 6 GHz band, yes. A Wi-Fi 6E access point serves older clients normally on 2.4 and 5 GHz; its 6 GHz radio is seen only by clients that support 6 GHz. If the share of these devices in the inventory is low, the return on investment stays limited until that share rises.

In most enterprise office scenarios, no. A single AP’s realistic total traffic is usually covered by a 2.5 or 5 Gbit/s multigigabit uplink. Still verify the selected model’s uplink port, PoE class and the power budget the vendor requires for full performance from the datasheet.

Can the 6 GHz band be used for enterprise Wi-Fi in Turkey?

Which sub-range can be used, at which power class and under which indoor/outdoor conditions depends on the national regulator’s decision. Before the project, verify BTK’s current regulation and the country code and channel list published for the AP for Turkey.

Do we need to replace existing Wi-Fi 5 infrastructure right away?

If there’s no capacity problem, end-of-support hardware or device that can’t receive security updates, don’t rush. Plan the refresh according to user density, client inventory, the state of the switch and PoE infrastructure, and the vendor’s life cycle calendar.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Network

We build switching, routing, cabling and wireless networks with VLAN segmentation and redundant uplinks, and provide regular maintenance and fault support.

Knowledge Center

Other articles