| Device (AP) | IEEE 802.11ax
802.11be | Standard Power (SP) device requests authorization from AFC system before transmitting in 6 GHz. Must not transmit until AFC response received. | Device serial, geo-location (GPS/IP/manual), antenna height, device category, requested channels/EIRP | Pre-transmission; query repeated every 24h minimum or on channel change | LPI devices: NO AFC needed (indoor, ≤30 dBm EIRP). SP devices: AFC mandatory. |
| Spectrum Inquiry (Step 1) | WFA AFC spec
JSON over HTTPS | AP sends AvailableSpectrumInquiryRequest to the AFC. Includes device descriptor (manufacturer, model, serial, cert ID). | Request: {deviceDesc: {serialNum, certificationId, rulesetIds}, location: {point: {lat,lon}, uncertainty}, requestType} | < 30 s typical response | PAWS = Protocol to Access White-Space databases. Reused for AFC. Port 443 HTTPS. |
| Inquiry Response (Step 2) | RFC 7545 | AFC server returns available channels + max EIRP per channel based on incumbent protection. | AvailableSpectrumInquiryResponse: {rulesetInfos, spectrumSchedules: [{timeRange, spectra: [{resolutionBwHz, profiles: [{hz, dbm}]}]}]} | Validity period typically 24h | Response includes per-frequency EIRP limits. Device must comply exactly. |
| Geolocation | FCC 20-51
GPS / IP geoloc | SP devices must know their location within a reported horizontal/vertical uncertainty (typically ≤50 m; AFC enlarges protection zones by the uncertainty). | Lat/Lon/Alt ± uncertainty. Height above ground. | At device startup; re-check if moved | GPS preferred. Some APs use IP-based geolocation (less accurate, FCC allows for certain device categories). |
| Incumbent Protection | FCC 20-51
ITU-R | AFC database contains locations of microwave fixed-service links, satellite earth stations, and other incumbents. AFC computes interference margin. | Incumbent database: fixed-service link coordinates, satellite dish coords, protection contours | Real-time per AFC operator database | Incumbents have priority. AFC computes path loss from device to each incumbent → determines max EIRP at device location. |
| AFC Operators (FCC-approved) | FCC KDB | Companies approved to operate AFC databases and APIs. FCC-certified (2024+): Broadcom, Google, Comsearch (CommScope), Sony, Kyrio, Key Bridge Wireless, Federated Wireless, Qualcomm. | Operator API endpoints: varies per operator but must comply with FCC spec | - | APs must support at least one FCC-approved AFC operator. Multi-operator support recommended for redundancy. |
| Renewal / Recheck | WFA AFC spec | SP device must re-query AFC before validity period expires. If AFC unreachable, device must stop SP transmissions (fall back to LPI or cease TX). | Re-send AvailableSpectrumInquiryRequest with current location | Every 24h (or per AFC response validity field) | Devices that cannot reach AFC after validity expiry must NOT transmit at SP power. Fail-safe = LPI or no TX. |
| Security | HTTPS / TLS 1.2+
Certificate pinning | All AFC communications over TLS. Device authenticates AFC server certificate. Device presents its FCC certification ID. | Mutual TLS or server-only TLS with device cert ID in payload | Per query | Man-in-the-middle on AFC = device could be misled to transmit on protected channels → FCC enforcement risk. |