Unlicensed Use of the 6 GHz Band; Expanding Flexible Use in Mid-Band Spectrum Between 3.7 and 24 GHz
In this document, the Federal Communications Commission (Commission or FCC) adopts rules allowing unlicensed geofenced variable power (GVP) devices to operate in the U-NII-5 and U-NII-7 portions of the 6 GHz band (5.925-7.125 GHz) at up to 11 dBm/MHz EIRP power spectral density and 24 dBm EIRP. GVP devices must use geofencing systems to prevent harmful interference to licensed microwave links and radio astronomy observatories. The geofencing systems will calculate exclusion zones where GVP devices cannot operate on specified frequencies. Each GVP access point must have a geolocation capability to determine its location and avoid operating on prohibited frequencies within the exclusion zones. Client devices must operate 6 dB below the access point's authorized power. These rules permit the GVP devices to operate at higher power than very lower power 6 GHz band unlicensed devices.
What this rule actually says
The FCC is letting certain Wi-Fi devices operate in the 6 GHz radio spectrum at higher power levels than before, but only if they use GPS-like geofencing to avoid interfering with licensed microwave links and radio astronomy stations. Think of it as a permission slip to broadcast stronger wireless signals, as long as the device knows where it is and doesn't transmit on forbidden frequencies in certain geographic zones.
Who it applies to you
- If you're building hardware (physical Wi-Fi access points or routers) that uses the 6 GHz spectrum band (5.925-7.125 GHz), this applies. Most indie AI founders don't manufacture hardware, so you likely don't need to worry.
- If you're using off-the-shelf Wi-Fi equipment (standard routers, laptops, phones) to power your AI application, this does not apply to you. Equipment manufacturers handle compliance.
- If you're in the US, this matters. The FCC only regulates US spectrum. If you're shipping products internationally, check your target countries' telecom regulators separately.
- If you're a software-only founder (AI medical scribes, hiring assistants, support chatbots using cloud infrastructure), this almost certainly does not apply unless you're also manufacturing wireless hardware.
- If you rely on Wi-Fi connectivity for your product but don't make the Wi-Fi hardware itself, you don't need to do anything—this is a hardware manufacturer compliance issue.
What founders need to do
- Determine if you manufacture wireless hardware. If your product is pure software, a web app, or a mobile app, stop here. You're not affected. (5 minutes)
- If you do manufacture Wi-Fi hardware, consult an RF compliance engineer to verify your devices meet geofencing and power limits. This is required for FCC certification. (2-4 weeks, $5-15K typically)
- Implement geolocation and geofencing in your hardware if you want to use the higher power allowances. Your devices must know their location and disable certain frequencies in exclusion zones. (2-8 weeks, depending on design maturity)
- Run FCC certification testing before selling hardware in the US. Certification labs will verify your geofencing works and power limits are met. (4-12 weeks)
- Monitor FCC updates if you're in hardware—the Commission refines spectrum rules regularly. Set a calendar reminder to check FCC.gov quarterly. (Ongoing, 30 minutes/quarter)
Bottom line
Ignore this unless you're manufacturing Wi-Fi hardware; if you are, budget for RF compliance and geofencing implementation before launch.