Wi-Fi 6E and the 6 GHz Band: Design and AFC Playbook

The 6 GHz band is the most significant thing to happen to enterprise Wi-Fi in a decade, and it is also the one most likely to be designed badly. There are roughly 1200 MHz of new spectrum, no legacy clients, and wider channels than ever - which sounds like an easy win until you discover that the rules are different in each power regime, that standard-power operation requires talking to a cloud service before it will transmit, and that most of your installed client fleet cannot see the band at all.

This playbook covers the band, the three power regimes, the design decisions that follow, and the operational lifecycle that standard power introduces.

The Band and the Rules

In the United States, 6 GHz is divided into four sub-bands and three power regimes:

U-NII-5         U-NII-6         U-NII-7         U-NII-8
5925            6425            6525    --      6875            7125 MHz
SP + LPI + VLP  LPI + VLP       SP + LPI + VLP   LPI + VLP
(fixed/satellite incumbents in U-NII-5 and U-NII-7)

Standard power is allowed only where the incumbent fixed links and satellite uplinks can be protected by an Automated Frequency Coordination system. LPI and VLP need no coordination because their power limits make harmful interference implausible. Regulatory frameworks differ by country and several are still in consultation, so the first design question is always which regimes your jurisdiction permits and in which sub-bands.

What 6 GHz Actually Changes

• Capacity. Seven 160 MHz channels instead of two, which makes 80 MHz the new default and 160 MHz realistic in low-density areas.
• Interference. Legacy devices and most consumer gear cannot transmit there, so the noise floor starts low and, for now, stays there.
• Channel structure. Each 20 MHz channel is also a Preferred Scanning Channel (PSC), and clients use PSCs for discovery - which is why your channel plan should keep PSC alignment rather than placing 80 MHz blocks arbitrarily.
• Range. Higher frequencies attenuate faster through walls. LPI at 30 dBm EIRP does not cover what 5 GHz did, and that is by design. Six-gigahertz cells are deliberately smaller, which is good for capacity and requires more APs for the same footprint.
• Client support at the start. Only recent devices are 6 GHz capable. Everything older stays on 5 GHz, so the new band relieves the old one only for the portion of the fleet that can use it.

Standard Power and AFC: A Lifecycle, Not a Setting

AFC is often described as "a database that tells your AP what channel to use". The operationally useful model is that a standard-power AP operates on authorisation, and that authorisation has states:

Boot / join       AP retrieves config, identifies its location (lat/long, sometimes height)
Grant request     AP asks the AFC for available channels and permitted power
Operating         AP configures itself strictly inside the granted envelope
Re-authorisation  Periodic re-query, and on change (location, policy, database update)
Degraded mode     If the AFC is unreachable, vendor and regulatory fallback applies

That last state is the one to engineer for. Typical behaviours are fallback to LPI power, restriction to a smaller channel set, reduced EIRP, or disabling standard-power 6 GHz entirely. Which is correct depends on the site: a stadium that must keep serving customers may prefer reduced-capacity operation; a compliance-sensitive environment may require the conservative option. Either way, test it deliberately - simulate AFC unavailability in a pilot zone and measure what actually happens, because the behaviour is vendor and regulator specific.

Practically, this also means:

• Accurate location data is now infrastructure. Bulk import and a documented workflow for updating AP coordinates, with an audit trail.
• AFC status is a monitored metric. Grant age, errors and current fallback mode per AP, not just "AP is up".
• Vendor and AFC provider are procurement criteria. Ask which AFC providers are supported, whether there is an on-premises option, and how region coverage is handled.

Design Decisions

1. Decide the regime per area. LPI for ordinary indoor coverage; standard power where you genuinely need outdoor or wide-area coverage and can accept the AFC dependency.
2. Plan 80 MHz as the default channel width. Use 40 MHz in high-density venues and reserve 160 MHz for low-density or specific high-throughput zones.
3. Keep PSC alignment. A clean channel plan that respects PSCs makes client discovery fast; an odd plan makes every client scan longer.
4. Expect more APs per area than 5 GHz. Smaller cells are the point. Budget for it rather than turning power up and re-creating the co-channel problem you were solving.
5. Keep 5 GHz healthy. Most of the fleet is still there. The right 6 GHz design reduces 5 GHz load, and if it does not, the deployment has not achieved anything yet.
6. Use the survey discipline you already have. A 6 GHz design needs the same predictive-then-validated approach as any band, with the pass/fail thresholds revisited for the new cell sizes - the method is unchanged from this Wi-Fi site survey guide.

Troubleshooting

• Client cannot see the 6 GHz SSID. First check the client hardware - it may simply not support the band. Then check that the AP is actually operating on 6 GHz. An AP in degraded mode or without a grant may have the radio enabled but no usable channels.
• Client connects but throughput is poor. Check whether it landed on 5 GHz. Band steering policies that push everything to 6 GHz will fail for clients that cannot use it, and radios that are too eager can create sticky clients at cell edges.
• Roaming fails between bands. Cross-band roaming between 5 and 6 GHz depends on the client, and some clients handle it poorly. Validate roaming explicitly, including with Wi-Fi 7 multi-link operation in play, where the behaviour is richer - the mechanism is described in this Wi-Fi 7 MLO deployment guide.
• AP loses standard-power operation after a change. Check the AFC grant state, the AP's reported location, and whether the location was updated without an audit record.
• Radio policy applied inconsistently. On a controller-managed deployment, most 6 GHz misconfigurations are tag or profile mismatches rather than RF problems; the profile and tag structure in this policy profile and policy tag guide is the place to confirm what each AP actually received.

Procurement Questions Worth Asking

Because standard power is a product category with a lot of marketing attached, ask for measurable capabilities: which AFC providers are integrated, how per-AP AFC status is exposed, how location data is bulk-managed and audited, what the defined degraded behaviour is, and whether tail metrics (latency distribution, retries, roam events) are available to prove outcomes. Then pilot a small standard-power zone, validate the grants, simulate AFC loss, and measure the tail.

原文链接：https://wifiblog.eawtech.net/2026/2026_06_01_outdoor_6ghz_afc_playbook_standard_power_wifi6e_wifi7.html