October 2026
For several years, the Wi‑Fi industry described 6 GHz as a once‑in‑a‑generation capacity expansion. That is true — but incomplete. In 2026 the bigger story is not simply that Wi‑Fi has more spectrum. The bigger story is that 6 GHz is becoming a shared, policy‑controlled, regionally fragmented operating environment where Wi‑Fi, incumbent services, very‑low‑power devices, geofenced devices, and future mobile services must coexist.
This changes the engineering mindset. A WLAN architect can no longer treat 6 GHz as “clean spectrum forever.” A campus or venue designer can no longer assume that today’s indoor low‑power rules will map neatly to tomorrow’s outdoor, standard‑power, or upper‑6 GHz use cases. And a procurement team can no longer buy “Wi‑Fi 7” or “Wi‑Fi 8 ready” hardware without asking which regulatory domains, AFC behaviours, and device classes are actually supported.
The October 2026 moment is especially important because the policy direction is now concrete in multiple regions. Ofcom has updated its approach to expanding access to 6 GHz for both commercial mobile and Wi‑Fi services, including licence‑exempt higher‑power Wi‑Fi under AFC control and proposals for hybrid sharing in upper 6 GHz. The FCC has continued expanding unlicensed 6 GHz use cases through very‑low‑power and geofenced variable power mechanisms. Australia’s ACMA is reviewing AFC‑assisted sharing for standard‑power outdoor operation in part of the 6 GHz band, while New Zealand’s RSM position remains narrower: 5925–6425 MHz is available for LPI and VLP WLAN use, and wider 6 GHz decisions remain tied to international developments.
This post is a practical engineering playbook for 6 GHz coexistence. We’ll cover the device classes, AFC and geofencing models, Wi‑Fi/mobile coexistence, what recent measurement research suggests, and how to design WLANs that remain stable even as the spectrum rules evolve.
What you’ll take away
Before diving into the engineering, it is worth separating a few terms that are often blurred in vendor and policy discussions. AFC is not the same thing as “better channel planning.” It is an authorization mechanism for standard‑power operation, typically based on location and incumbent‑protection rules. VLP is not a substitute for campus coverage; it is a short‑range device class. GVP is not simply “VLP turned up louder”; it is a geofenced model with location and exclusion‑zone assumptions. And upper‑6 GHz hybrid sharing is not yet a globally uniform Wi‑Fi entitlement; it is a policy design space where regulators are balancing Wi‑Fi, mobile, and incumbent users.
Those distinctions matter because mistakes here become design mistakes. If a team assumes VLP devices will behave like managed APs, they will miss a growing source of uncontrolled short‑range traffic. If a team assumes AFC behaves like static channel assignment, they may fail to monitor grant state and degraded behaviour. If a global enterprise assumes upper 6 GHz is available everywhere, its design will break across regulatory domains. Coexistence engineering starts with precise language.
The phrase “6 GHz Wi‑Fi” hides multiple realities. Depending on country, frequency range, device class, and indoor/outdoor use, the same client or AP may operate under very different assumptions. The core classes engineers need to understand are:
These classes are not just different power levels. They imply different operational dependencies. LPI mostly feels like conventional enterprise Wi‑Fi with a stronger security baseline. Standard power introduces AFC and location governance. VLP introduces new client categories and body‑area/near‑field use cases. Geofenced variable power introduces a “device must know where it is allowed to operate” model. That is a major shift from the old assumption that unlicensed Wi‑Fi was mostly governed by static device rules.
The practical design lesson: start with the local regulatory class before you design the RF. Channel width, AP density, outdoor viability, client behaviour, and procurement all depend on what the device is legally allowed to do in that country.
Automated Frequency Coordination (AFC) is the mechanism that allows standard‑power 6 GHz systems to operate while protecting incumbent users such as fixed microwave links. At a basic level, an AFC system evaluates the AP’s location and characteristics, determines which channels and powers are permitted, and returns an authorization.
That makes AFC feel database‑like, but it behaves operationally like a new control plane. It creates dependencies:
In July 2026, Ofcom’s AFC statement set out decisions to enable licence‑exempt higher‑power Wi‑Fi in the 6 GHz band under AFC control. The same statement explains AFC as a flexible mechanism that can restrict Wi‑Fi operation in parts of upper 6 GHz where future mobile services are deployed in high‑density areas, and Ofcom indicated it would invite applications from prospective AFC service providers from 1 September 2026. That is an important signal: AFC is not just a tool for “turning on outdoor Wi‑Fi.” It is also becoming a policy instrument for sharing spectrum dynamically.
Operational takeaway: Treat AFC like DNS, DHCP, NTP, or identity: a foundational dependency that must be monitored, logged, tested, and included in change management.
The lower 6 GHz band is already available for Wi‑Fi in many places, but the upper 6 GHz band is where the policy debate gets harder. Mobile operators see upper 6 GHz as valuable mid‑band capacity. Wi‑Fi advocates see it as the spectrum needed to make wide channels and high‑capacity indoor networks scale. Regulators are trying to maximize economic value while protecting incumbents and avoiding fragmented device ecosystems.
The UK is the most visible hybrid‑sharing experiment. Ofcom’s September 2026 update sets out decisions and proposals following earlier consultations on expanding access to 6 GHz for commercial mobile and Wi‑Fi. It includes a decision to allow outdoor and higher‑power Wi‑Fi in lower 6 GHz using AFC, and proposals to extend AFC concepts to upper 6 GHz. Ofcom also references practical sharing work, including a June workshop on cross‑technology sensing in upper 6 GHz.
That matters because it suggests a future where Wi‑Fi and mobile may not simply live in separate, fixed slices. Instead, access may be shaped by:
For engineers, the conclusion is clear: upper 6 GHz is not guaranteed to behave globally like a simple “more Wi‑Fi channels” extension. Designs must remain flexible, especially for multinational enterprises and vendors shipping global products.
The United States has taken a more expansive path on unlicensed 6 GHz. The FCC previously enabled standard‑power AFC‑controlled access in portions of the band, expanded VLP operation across the band, and in 2026 adopted rules for geofenced variable power devices. The 2026 GVP rules authorize a new class of unlicensed devices in the U‑NII‑5 and U‑NII‑7 portions of 6 GHz at higher power than VLP, subject to geofencing and device location requirements. For enterprise WLAN teams, the message is clear: 6 GHz will not be populated only by infrastructure APs you control.
Two device categories are especially important:
This matters for Wi‑Fi architects because the client ecosystem is expanding beyond laptops and phones. AR/VR headsets, body‑worn devices, AI accessories, personal hotspots, sensors, and short‑range media devices may increasingly use 6 GHz in ways that enterprise WLAN teams do not directly control. That means “our AP channel plan” is only part of the interference story. The surrounding client and device ecosystem becomes a variable.
A key question in the upper‑6 GHz debate is whether Wi‑Fi and mobile can coexist safely and predictably. Policy discussions often become abstract, so measurement research is important. A 2026 experimental paper on coexistence of 5G NR and Wi‑Fi 6E/7 at 6 GHz reported conducted interference measurements using commercial VLP Wi‑Fi 6E/7 equipment and a live 5G NR testbed. The study found no measurable degradation below a specific injected Wi‑Fi power threshold, with progressive degradation above that threshold, and concluded that compliant VLP behaviour with listen‑before‑talk would vacate before harmful interference in the tested scenario.
That result is encouraging, but engineers should read it correctly. It does not mean “coexistence is solved everywhere.” It means carefully designed rules, device power limits, sensing/listen‑before‑talk behaviours, and realistic separation assumptions can make coexistence plausible under specific conditions. Real deployments add more variables:
The engineering takeaway: coexistence must be validated as a system, not assumed from one rule or one lab result.
For New Zealand engineers, RSM’s published position remains important: the 5925–6425 MHz range is available for WLAN under LPI and VLP regimes, aligned broadly with approaches adopted in Australia, the UK, and Europe. RSM also notes that wider 6 GHz decisions remain under international discussion. In practical terms, New Zealand WLAN designs should treat lower‑6 GHz indoor/VLP capability as real, but avoid assuming upper‑6 GHz or standard‑power outdoor AFC availability unless the regulatory position changes.
Australia is more active on the AFC discussion. ACMA’s consultation material says it is considering enabling AFC systems for authorising standard‑power Wi‑Fi in the 6 GHz band and how that could be implemented. ACMA’s broader spectrum outlook also points to upper 6 GHz moving toward implementation-stage work. For organizations operating across Australia and New Zealand, that creates an important regional split: Australia may move toward AFC‑enabled outdoor/standard‑power options sooner, while New Zealand may remain more conservative until international outcomes settle.
This affects procurement. A Wi‑Fi 7 AP that supports 6 GHz in one country may not support the same outdoor power classes or channel sets in another. Cloud controllers may expose different options per regulatory domain. And client devices may behave differently depending on region code, driver policy, and allowed channels. A global WLAN standard must therefore include local regulatory profiles, not just “one corporate RF template.”
Coexistence-aware Wi‑Fi design is not radically different from good Wi‑Fi design, but it changes the emphasis. Instead of assuming spectrum cleanliness, you design for adaptive, observable, policy‑controlled operation.
Wide channels are useful when the environment supports them. But 160 MHz and 320 MHz channels reduce reuse and increase the cost of coexistence mistakes. In shared/uncertain spectrum, narrower channels can deliver more predictable outcomes by creating more independent contention domains. The default high-density answer remains conservative: 80 MHz for many enterprise 6 GHz deployments, 160/320 MHz only where reuse and client support are proven.
6 GHz usually has shorter effective range than 5 GHz for comparable power and building conditions. LPI power limits reinforce that. A good design places 6 GHz where modern clients need capacity and low retries, rather than assuming 6 GHz should mirror 5 GHz coverage.
For years, 5 GHz has carried the enterprise WLAN. Even in 2026, many clients are 5 GHz‑only or prefer 5 GHz under some conditions. A poor 5 GHz design will still break user experience, even if the 6 GHz layer is excellent. Think of 6 GHz as an added modern lane, not an excuse to abandon 5 GHz engineering discipline.
If you use standard power, monitor AFC grant status. If you depend on geofenced devices, understand their location/geofencing model. If you operate across countries, inventory which modes are enabled per regulatory domain. Regulatory state is now an operational input.
Coexistence problems usually show up as tail behaviour: retry spikes, latency outliers, roaming stalls, and intermittent throughput collapse. Average speed tests hide these problems. Acceptance criteria should include 95th/99th percentile latency, retry rates, airtime utilization, and client distribution by band/channel width.
A 2026 Wi‑Fi procurement checklist should include spectrum policy readiness. Ask vendors:
The goal is not to predict every regulatory outcome. The goal is to avoid buying a platform that cannot adapt when the rules change.
6 GHz operations needs a runbook that includes policy state. At minimum:
In other words: RF operations and regulatory operations are merging. That does not mean every wireless engineer must become a lawyer. It means the WLAN runbook must know which regulatory assumptions are part of the service design.
Wi‑Fi 8 (IEEE 802.11bn) is still in draft work, but its Ultra‑High Reliability direction is directly relevant to 6 GHz coexistence. The IEEE task group update lists a wide set of PHY/MAC topics being resolved, including multi‑AP coordination, coordinated spatial reuse, coordinated beamforming, roaming, critical update mechanisms, and security topics. This is exactly the toolkit needed when spectrum becomes more crowded and shared.
But Wi‑Fi 8 will not eliminate the need for coexistence discipline. It may improve coordination, reduce tail latency, and help devices behave better in overlap, but it will still operate within regulatory rules and real RF environments. The best Wi‑Fi 8 deployments will be built on the same foundations as good 6 GHz Wi‑Fi 7 designs: clear spectrum policy, reuse-first channel planning, measured tail performance, and operational visibility.
The biggest 6 GHz mistakes in 2026 are not exotic RF failures. They are planning assumptions that age badly as the regulatory and client ecosystem changes. The most common traps are:
A tight design is one that can survive those assumptions changing. That means flexible RF profiles, good telemetry, conservative channel planning where density is high, and procurement language that requires explicit country and power‑class support.
The 6 GHz story is no longer simply “more spectrum for Wi‑Fi.” It is a new operating model: shared, dynamic, region‑specific, and increasingly policy‑aware. The organizations that benefit most will be the ones that treat 6 GHz as a governed infrastructure layer — not as a magic clean band.
Want more deep‑dive Wi‑Fi engineering posts?
Follow the blog: wifiblog.eawtech.net
Connect on LinkedIn: Eduardo Wnorowski
Eduardo Wnorowski is a Technologist and Director.
With over 30 years of experience in IT and consulting, he helps organizations design and operate stable, secure, and high‑performance networks through disciplined architecture, measurement, and continuous optimization.
LinkedIn Profile