Follow me:

CTS 393 What is happening when the Wi-Fi Alliance certifies devices?

Ever wonder what actually happens behind the scenes when a device gets Wi-Fi Certified? In this episode, we sit down with Daryl K., who brings years of hands-on experience working inside Authorized Test Labs (ATLs).

We dive deep into how Wi-Fi Alliance testing works, how test beds are constructed, why some standard features fail in the real world, and what it takes to get products certified.


Key Takeaways & Timestamps

  • [00:08] – Introduction
    • Hosts welcome guest Daryl K. to share his background in network testing and his transition into the Wi-Fi industry.
  • [03:13] – What is an Authorized Test Lab (ATL)?
    • Role of ATLs: Third-party labs (ATLs) run the actual hardware and software tests inside anechoic chambers; the Wi-Fi Alliance acts as the issuing body that approves the certification.
    • Value of Certification: Certification ensures interoperability across multi-vendor chipsets and validates proper behavior in edge cases.
  • [07:08] – Test Complexity & Duration
    • Time Requirements: Wi-Fi 5 (802.11ac) testing could be finished in ~2 weeks. Wi-Fi 6 takes about a month, and Wi-Fi 7 can take 6 to 7 weeks due to cumulative backward-compatibility testing and hundreds of test cases.
    • Test Bed Setup: Test environments use standardized hardware racks stacked with modified laptops, access points, and sniffers connected to central control consoles.
  • [10:24] – Certification Drivers & Retail Requirements
    • Devices with 802.11 radios can be sold without certification, but major retailers (e.g., Target, Costco) often require it.
    • Certification is mandatory for integration into major ecosystems like Matter, Apple CarPlay, Android Auto, and Alexa.
  • [14:45] – Handling Test Failures & Interoperability
    • Different ATLs handle failures differently—some offer debugging support and lab time to revise firmware, while others enforce strict “three strikes” policies.
    • Discussion on vendor “Plugfests” where chipset engineers (Qualcomm, Broadcom, Intel, MediaTek) collaborate to resolve root-cause interoperability issues before programs launch to ATLs.
  • [28:36] – Mandatory vs. Optional Features in the Field
    • Protected Management Frames (PMF): Originally optional, PMF was made mandatory after testing showed nearly half of legacy devices failed when connecting to PMF-enabled APs.
    • Vendor “Special Sauce”: How proprietary features (like early band-steering implementations) sometimes broke client connectivity due to unhandled information elements.
  • [8:03] – Promising Tech That Missed the Mark
    • Wi-Fi Direct Services: Designed for simple one-click printing, but superseded by higher-layer network solutions.
    • Wi-Gig (60 GHz / 802.11ad): Originally pitched as wireless HDMI, but extremely tight beamforming and short range made it impractical for consumer adoption.
  • [40:36] – Resources for Wi-Fi Professionals
    • Product Finder: Using the Wi-Fi Alliance online tool to look up certified features once product non-disclosure periods expire.
    • Finding Chipset Details: Navigating FCC documentation (and tools like FCCID.io) to identify real underlying hardware specs for client troubleshooting.

Resources

Hosted by
Mark Nemiz
Join the discussion

This site uses Akismet to reduce spam. Learn how your comment data is processed.

More from this show

Connect With Rowell

Connect With François