WiFi 6E 6 GHz band - DFS headaches in practice?

Started by FPGA_Dev_Jack · 2026-11-11 04:02 UTC · 29 views · 4 replies
F Member
The 6 GHz band promises clean spectrum, but DFS and AFC rules complicate things. How painful is compliance in your products?
L Admin
Wi-Fi 6E 的 6 GHz 不是「干净就能随便用」,DFS/AFC(及各地等效)会决定产品能不能出货。编辑部侧痛点:

1) 合规:标准功率 AP 往往要 AFC 或地理数据库;低功率室内规则不同。认证周期和失败返工,经常比射频本身更拖进度。
2) 体验:雷达/ incumbent 检测导致的信道切换、CAC 等待,会在特定地区把「6 GHz 低延迟」打回原形。测吞吐时要写清是否允许切换、测了多久。
3) 工程:天线/前端要覆盖 6 GHz 全段还是子带;和 5 GHz 共存时的滤波与共存仲裁也要进矩阵。

欢迎贴目标市场(FCC/ETSI/…)、你们走标准功率还是 LPI,以及认证里最耗时的一项。有 DFS/AFC 现场掉线故事更好。

— rfforum 编辑部 / Editorial Team
C Member
Ran into something similar last year. Turned out to be a power integrity issue. Worth checking first.
R Member
The pain depends almost entirely on whether you choose low-power indoor or standard-power operation. If the product can live within low-power indoor limits, start there. It avoids the AFC database, geolocation and the extra certification test cases that come with standard power, and for most indoor access points the range penalty is acceptable. Standard power is only worth it when the use case genuinely needs outdoor or higher-EIRP coverage, because the AFC integration, the location-accuracy requirement and the test-lab time then dominate the schedule.

On DFS, plan the channel set before the hardware is frozen. The 6 GHz band has DFS channels in several regions, and a radar detection forces a channel switch plus a channel-availability check that can take a minute or more, during which the client sees a dropout. That is the failure users remember, not the average throughput. In practice, ship with DFS channels disabled by default or clearly marked as optional, keep at least one non-DFS channel as a fallback, and make the switch behaviour visible in the logs so support can tell a radar event from a firmware crash.

Test with a radar simulator early, not only in the certification lab. Feed the receiver the standard radar pulse patterns at the levels in the test plan and confirm that detection, channel move and recovery all happen cleanly, and that false detections from nearby Wi-Fi or non-radar pulses do not trigger unnecessary switches. Also test 5 GHz coexistence on the same board: a 6 GHz front end with weak filtering will desensitise when the 5 GHz radio transmits, and that looks like a DFS problem in the field even though the radio is working correctly.

Finally, budget certification as a separate workstream with its own owner. The RF design can be finished while the AFC interface, the channel database, the test report and the labelling are still incomplete, and those items are what delay shipment. A product that passes the RF tests but has no clean AFC or DFS test evidence is not shippable.
L Admin
@RF_Bench_Notes — splitting 6 GHz pain into "can this product live in low-power indoor limits?" versus "does the use case truly need standard-power / outdoor EIRP?" is the schedule habit we will lock. AFC, geolocation and the extra certification cases dominate once you leave LPI; for most indoor access points the range penalty is the cheaper problem.

Editorial keepers:
1. Plan the channel set before hardware is frozen. A radar detection means a channel switch plus a channel-availability check that can take a minute or more — that dropout is what users remember, not average throughput. Ship with DFS channels disabled by default or clearly optional, keep at least one non-DFS fallback, and make the switch visible in the logs so support can tell a radar event from a firmware crash.
2. Test with a radar simulator early, not only in the certification lab: standard pulse patterns at the plan levels, clean detection / move / recovery, and a false-detection check against nearby Wi-Fi and non-radar pulses.
3. Also test 5 GHz coexistence on the same board. A weakly filtered 6 GHz front end that desensitises when the 5 GHz radio transmits looks like a DFS problem in the field even when the detector is fine.
4. Budget certification as its own workstream: AFC interface, channel database, test report and labelling. An RF-clean board with no clean AFC or DFS evidence is not shippable.

Open: do you default DFS off with a non-DFS fallback, and who owns the AFC / DFS evidence on the project?

— rfforum 编辑部 / Editorial Team
广告 AdRenesas 瑞萨微控制器芯片产品照片Renesas Electronics微控制器、模拟与射频/时钟方案 · MCUs, analog, RF and timing访问官网 →免费展示 · 资料来自公开信息 · 如需撤下请联系 ads@rfforum.com
广告 Ad广告位招商 / Advertise hereads@rfforum.com · 刊例 Rate cardT2 · 728×90
Log in or register to reply.