WiFi 6E opens up the 6 GHz wireless spectrum for unlicensed WiFi operation. WiFi 6 introduced the high-efficiency 11ax technology, while Wi-Fi 6E supports the 11ax technology in the unlicensed 6 GHz spectrum.
The ability to use the 6 GHz band has opened a vast range of WiFi frequencies. In total, the 6 GHz WiFi 6E band includes a total of 1200 MHz, which doubles the range available in the 5 GHz WiFi 6 band.
Despite the 5 GHz band still being pretty unclogged, the situation is already changing. The number of devices on 5 GHz is rising fast and in urban environments such vast growth is already causing issues.
The 6 GHz spectrum is continuous, allowing for easy formation of wide channels. This promotes the use of 160 MHz channels. The doubled channel bandwidth also doubles the data traffic capacity.
The complete list of 6 GHz PSC channels; 5, 21, 37, 53, 69, 85, 101, 117, 133, 149, 165, 181, 197, 213, 229:
Hostap Channels Configuration (6 GHz)
|
The following OVSDB tables define and show the channels configuration: Wifi_Radio_Config and Wifi_Radio_State, Wifi_VIF_State.
|
Actions needed:
Wifi_VIF_State::channels → extend the available channels list
|
|
Actions needed:
Wifi_Radio_Config/State::channel → extend the available channel list
Wifi_Radio_State::allowed_channels → extend the available channel list
Wifi_Radio_State::fallback_parents → extend the available channel list
Wifi_VIF_State::channel_list → extend the available channel list
Wifi_VIF_State::freq_band → add a new freq band: 6G
Wifi_Stats_Config::radio_type → add a new radio type: 6G
Wifi_Stats_Config::channel_list → extend the available channel list
Wifi_VIF_Neighbors::channel →extend the available channel list
Wifi_VIF_Neighbors::freq_band → add a new freq band: 6G
|
Actions needed (Band_Steering_Config):
Band_Steering_Config::if_name_2g → deprecate field, use Band_Steering_Config::ifnames instead
Band_Steering_Config::if_name_5g → deprecate field, use Band_Steering_Config::ifnames instead
Actions needed (Band_Steering_Clients):
Band_Steering_Clients::max_rejects → deprecate field; a timer-based pre-assoc 5 GHz steering will be used instead.
Band_Steering_Clients::rejects_tmout_secs → deprecate field; a timer-based pre-assoc 5 GHz steering will be used instead.
Band_Steering_Clients::pref_5g_reject_timeout_msecs → new field, specifying for how long a STA should be blocked
Band_Steering_Clients::pref_6g → introduce new enumeration field (values: "never", "always"). This field will control the pre-assoc 6 GHz steering policy.
Actions needed:
Switch from Band_Steering_Config::(if_name_2g,if_name_5g) to Band_Steering_Config::ifnames.
Support 6 GHz in code maintaining the BTM neighbors table.
Implement a timer-based 5 GHz HWM pre-assoc steering policy.
Implement 6 GHz steering pre-assoc steering.
Implement 6 GHz steering post-assoc steering.
Actions needed:
Updated functions and structures with newly introduced fields (mainly reflecting changes in schema discussed above).
To implement WiFi 6E on an OpenSync-enabled node, hardware support is mandatory. OpenSync was focusing on the following chipsets:
Qualcomm:
IPQ8074 (SoC), QCN9074 (radio)
IPQ5018 (SoC), QCN9074 (radio)
Broadcom:
BCM6755 (SoC), BCM943684MCH6 (radio)
Support for channel selection in UNII 5, UNII 6, UNII 7 and UNII 8
Ability to select any primary channel in each UNII x band (e.g., any 20 MHz channel)
Ability to operate in 20 MHz, 40 MHz, 80 MHz, 160 MHz channels
Will be handled by Channels configuration chapter.
OpenSync and OVSDB must support a power level setting to operate in standard power mode.
AFC system is currently not supported. |
The AFC system requires inputs per AP of geolocation, including location confidence, antenna height, FCC ID and device serial number to an AFC operator.
The AFC will return the allowed power levels per frequency.
The cloud should maintain a list of allowed channel power levels for each AP along with the information about when the power levels were last updated.
The AFC values should be updated at least 1x per calendar day.
Operation of the AFC is not a necessity for OpenSync, thus use of a 3rd party vendor is allowed. However, the cloud should manage this relationship with the AFC vendor with a cloud-to-cloud interface.
The controller must support enabling and setting a time interval for off-channel scanning using a non-intrusive channel scanning method with a single radio chain.
The dwell time for the off-channel scan must be configurable.
The off-channel scan must be configurable only to PSC channels or all 20 MHz channels.
The off-channel scan must be configurable in bandwidth size (e.g., 20 MHz, 40 MHz, 80 MHz and 160 MHz)
The changes depend on WiFi chipset possibilities. Currently, only 20 MHz can be set for off-channel.
The AP may be able to cancel the off-channel scan request if the radio is busy beyond a configurable threshold.
Since many devices do not yet support the 6 GHz band, it is required to support simultaneous operation on 5 GHz and 6 GHz for device compatibility.
When the AP supports both 5 GHz and 6 GHz radios, both are available for use as backhaul and client connections.
When 5 GHz and 6 GHz radios are available, both 5 GHz and 6 GHz radios must present the Home SSID at a minimum for device connections.
The 6 GHz band will also be available only for 11ax devices (HE mode is a requirement to operate in the 6 GHz band). It is expected that 11ac clients will be prevalent for many years, so 5 GHz radio SHOULD be available in WiFi 6E APs.
Upon initial boot up, the device shall enable the 6 GHz interface in low power mode.
The AP with 6 GHz shall be able to scan and connect to another 6 GHz backhaul connection for initial connection to the network.
The onboarding network flow shall be the same as for 2.4 GHz or 5 GHz radios.
WiFi statistics
Steering driver events handling
WiFi 6E uses WPA3 for authentication. WPA2 authentication is not allowed by the WiFi 6E standard.
6GHz radio supports many VAPs, STA and AP mode, M-BSSID
The following SDKs support WiFi 6E:
Qualcomm: SPF 11.4
Broadcom: 5.02L.07p1, 5.02L.07p2, 5.04L.02p1