Wi-Fi 6E

• 1: Features and benefits
• 2: Planning and deployment

1 - Features and benefits

In 2020, the Wi-Fi Alliance announced Wi-Fi 6E, which extends Wi-Fi 6 into the 6 GHz spectrum. Adding Wi-Fi 6 to the 6 GHz band offers several advantages over Wi-Fi in the 2.4 GHz and 5 GHz bands. The Federal Communications Commission (FCC) then made history by opening up 1200 MHz for unlicensed use by technologies like Wi-Fi.

The iterations of Wi-Fi have done a remarkable job with backwards-compatibility over the years, but come at a cost of carrying and accommodating legacy protocols and reduced bandwidth efficiency. The 6 GHz band does not accommodate Wi-Fi technologies older than Wi-Fi 6. The band allows Wi-Fi 6E to operate without the constraints of legacy protocols, enabling improved bandwidth and latency. Crucial to understand and note, Wi-Fi 6E shares unlicensed spectrum with other technologies which might be operating at the same time. In certain scenarios, Wi-Fi 6E APs must perform frequency coordination through a frequency coordinator prior to medium access for minimized interference with licensed incumbent users of the spectrum.

Regulations in the 6 GHz band

Spectrum allocation is a regulatory function, and rules can be different at varying national levels. This page covers regulations in the FCC and ETSI regulatory domains; most countries will follow one or the other of these models, potentially with minor national variations.

Channels

The FCC unlicensed grant in 6 GHz is 1200 MHz of spectrum, compared to 83.8 MHz in the 2.4 GHz band and 570 MHz in sections of 5 GHz (FCC). After a 20 MHz guard band at the low end, usable 6 GHz spectrum starts at 5.945 GHz and continues up to 7.125 MHz. This allows for 59 channels at 20 MHz width, 29 at 40 MHz, 14 at 80 MHz, or 7 at 160 MHz (the maximum channel width supported by Wi-Fi 6E).

The number of wide channels in 6 GHz is especially significant, as gaps in allocated spectrum in the 5 GHz band limit 80 MHz channels to 6 (seven if we include U-NII-4) and 160 MHz channels to 2 (3 if we include U-NII-4), and wide channels are necessary for the highest data rates.

The FCC designates four sub-bands across the 1200 MHz of 6 GHz: U-NII-5, U-NII-6, U-NII-7, and U-NII-8. These sub-bands are significant because they contain different incumbent types (covered in a section below), so while indoor APs will have uniform power limits across the entire 1200 MHz, there are differing restrictions for higher power and outdoor use across the sub-bands.

The rules from European regulators are not the same as from the FCC. They have taken a more cautious approach, allowing operation in just the lower 500 MHz of the band (480 MHz after the 20 MHz guard band), the equivalent to U-NII-5. This is primarily due to caution over spectrum sharing approaches like the FCC’s Automated Frequency Coordination (AFC) which is necessary to protect incumbents from interference from 6 GHz unlicensed transmitters.

A consequence of this caution is that European countries will restrict 6 GHz operation to indoor WLANs initially. Decisions on extending into the upper part of the 6 GHz band and allowing outdoor and higher-power operation have been deferred, for now.

Many other countries worldwide are in the process of adopting the 6 GHz band for unlicensed use; most of them are expected to follow either the FCC (1200 MHz) or ETSI (lower 500 MHz) approaches, with minor deviations possible for national regulation.

Incumbents

While the 6 GHz band is continuous and channelized across the entire 1200 MHz, existing non-Wi-Fi technologies are active in all sub-bands of 6 GHz. To allow new users into the bands without disrupting the operation of incumbents, spectrum-sharing models are required; new users can be allowed to transmit only when they will not cause interference to incumbents.

However, there is no requirement in the 6 GHz band for special in-band sensing of incumbent transmissions, similar to the Dynamic Frequency Selection (DFS) mechanism used in parts of the 5 GHz band for radar avoidance. Instead, the 6 GHz band uses two spectrum-sharing techniques. Where possible to identify incumbent users in the vicinity of an unlicensed transmitter, power and frequency options are restricted to stay clear of the incumbents. Alternatively, where specific knowledge of nearby incumbents is unavailable, power levels must be kept low enough to ensure they will never cause interference, even in the worst case.

For U-NII-5 running from 5.925 to 6.425 GHz and U-NII-7 from 6.525 to 6.875 MHz, the most important incumbents are point-to-point, licensed radio links used by service providers and private communications for utility companies and others. These links are licensed by the FCC and included in a database known as the Universal Licensing System (ULS). As they are point-to-point, they have narrow-beam antennas, often on tall masts, and can reach for tens of kilometers. The ULS database contains tens of thousands of these links, along with their location (transmitter and receiver, giving direction), frequency, and other characteristics. The FCC allows two spectrum sharing models for these sub-bands. At a low power threshold, and indoors only, unlicensed radios can transmit anywhere. Meanwhile, outdoor locations and higher-power transmitters are allowed where a calculation based on the ULS database shows they will not interfere with incumbents.

The spectrum sharing protocol for high-powered or outdoor unlicensed transmitters requires them to contact a central AFC server, which uses their location and transmit power to calculate whether any of the licensed incumbents in the ULS database might be affected and identifies safe power and frequency parameters.

In other sub-bands, U-NII-6 and U-NII-8, the incumbents are more difficult to coordinate, as they include mobile transmitters, and also temporary links used by local TV stations for outside broadcasts. These bands are less suited for spectrum sharing because the usage patterns are more dynamic, so outdoor, high-power transmitters are not allowed.

The protection of incumbents, and differing views of how to solve this problem, shapes regulators’ approach to opening the 6 GHz band to unlicensed transmitters. Some national regulators are following the FCC approach and introducing spectrum-sharing mechanisms to ensure new unlicensed services can use the spectrum without causing interference, while others are shelving the question by addressing only the lower part of the 6 GHz band, without more complex spectrum sharing arrangements like the FCC’s AFC.

Equipment classes for 6 GHz unlicensed operation

The FCC wants to allow 6 GHz networks to have the best possible performance while ensuring that licensed incumbents are not adversely affected. The FCC policy achieves their goal by defining four separate operating classes for 6 GHz equipment: Low Power Indoor (LPI), Standard Power (SP), Very Low Power (VLP) and Client Devices. VLP is not in scope for this page.

Low power indoor

The most common class for Wi-Fi 6E access points (APs) is low power indoor (LPI). These will be the familiar home or enterprise campus APs. By definition, these APs are shielded by buildings, to some extent, so the signal ’leaking’ outside will be attenuated, which allows safe operation across the band at a power level similar to today’s indoor Wi-Fi APs.

Low power indoor (LPI) AP characteristics:

• Fixed indoor only
• PSD 5 dBm/MHz
• No antenna connectors
• No weatherproofing
• Wired power

The limiting power level for LPI APs is not defined in absolute dBm, as for the lower bands, but at 5 dBm/MHz spectral density. This method of limiting allows an increase of 3 dB for every doubling of channel bandwidth, which gives approximately 18 dBm EIRP for a 20 MHz channel, and up to 27 dBm for a 160 MHz channel in Wi-Fi 6E. Note that spectrum is never perfectly flat and actual maximum EIRP may be further restricted as to not exceed regulatory limits or by hardware limits.

The FCC can apply this rule because incumbent links are generally narrow band compared to Wi-Fi channels. This is advantageous to Wi-Fi network because noise increases proportionally with channel bandwidth. SNR will remain similar for different channel widths, given maximum transmit power levels, hardware capability, and environmentals are the same.

Low power indoor (LPI) APs can operate across the whole 1200 MHz band, as their transmit power is considered safe for all incumbents after building exit loss is subtracted and attenuated. To ensure that these indoor-only units are not used outdoors, or with external high-gain antennas (which have the potential to cause interference), the FCC provides a list of physical requirements for certifying a LPI AP:

• No connectors for external antennas
• No battery-powered operation
• Not weatherized

The current rules from European regulators allow only Low Power Indoor (LPI) APs; outdoor mounting is not allowed and transmit power (EIRP) is limited to 23 dBm. Some countries deviate from this value, but only by one or two dBm.

Standard power

APs mounted outdoors, or indoors operating at higher power than LPI, are subject to ‘Standard Power’ (SP) rules. This is because they may interfere with incumbents and, because they would not otherwise be aware of the risk of interference, they must check periodically with the AFC for channel availability.

Standard power (SP) AP characteristics:

• Fixed indoor/outdoor
• EIRP 36 dBm max
• Controlled by an AFC database
• Automated geolocation
• Pointing angle restriction

The AFC query protocol is defined by the Wi-Fi Alliance and consists of an inquiry message from the AP and a response from the AFC server. The most important information in the inquiry is the AP’s geolocation. In exchange for latitude, longitude, antenna height (above ground level) and some other information in an inquiry message, the AP or controller receives a response containing the set of channels or frequency ranges and the maximum power levels that will not cause interference.

The transmit power of a standard power AP can be as high as 36 dBm EIRP. Because of the increased risk of interference to incumbents, standard power APs are only allowed in the U-NII-5 and U-NII-7.

Number of channels available for standard power (FCC):

Client devices

As with the lower sub-bands, client devices are expected to be limited in geography by APs. If there is no AP signal, devices must not transmit or attempt connection. Therefore, we assume the AP is transmitting in an authorized manner, and the client can adjust client transmit power and channel with reference to the AP. Refer to the respective regulatory in your locale for rules regarding client devices.

6 GHz operation

One attractive feature of the 6 GHz band is that there are no older Wi-Fi devices that need to be accommodated. Wi-Fi has done a remarkable job with backwards-compatibility over the years, but these efforts come at a cost of carrying legacy protocols and reduce bandwidth efficiency. The initial Wi-Fi 6E release sets a high bar with the new baseline of Wi-Fi 6 (802.11ax).

Devices using the 6 GHz band must use Wi-Fi 6 standards, must conform to WPA3 or Enhanced Open security, and cannot offer older security options like WPA2 and Open modes. For WPA3-Enterprise, the differences are slight and exclude some combinations of WPA2-Enterprise security protocols that could expose vulnerabilities, but these combinations were never configurable on most enterprise class APs. The pre-shared key options for WPA2 are significantly changed and improved with WPA3-Personal, and a new ‘Enhanced Open’ standard replaces Open mode to ensure that over-the-air transmissions are encrypted even without authentication of the client device or the network. These mandates are in line with the Wi-Fi 6 standard, without allowance for backwards-compatibility for older client devices.

The Wi-Fi Alliance has introduced a limited number of new features in Wi-Fi 6E, many previously optional features are now mandatory, with two goals:

• Improved airtime efficiency. In crowded areas, much of the available airtime is taken up with AP discovery frames such as beacons, probe requests, and probe responses. This detracts from airtime efficiency, so several features allow client devices to discover target APs and channels with fewer frames on the air.

• Faster AP discovery. Although the large number of new channels is a significant advance, client devices would take a long time to step through each channel, transmitting probe requests and awaiting replies to find a suitable AP. Therefore, new features aim to improve the speed and efficiency of AP discovery

The features are classified as ‘in-band’ and ‘out of band’, meaning the client device discovers APs on the 6 GHz channel where they transmit, or on another channel in a lower band, 2.4 GHz or 5 GHz.

In-band AP discovery features

The traditional way for a client device to discover a suitable AP for connection is to tune its radio to a 20 MHz channel, transmit a number of probe requests, wait on-channel for ~20 msec for probe responses from APs operating on that channel, then tune to the next channel and repeat. This takes time, may result in jitter or data loss as the device is away from its serving AP, and reduces battery life through extra frame transmissions. In addition, the probe requests and responses on the air reduce throughput for other user traffic.

For some time, the industry has been working towards passive scanning where devices learn about other APs and their serving channels through Neighbor Reports. This allows the device to switch to the new channel, reducing time off-channel and frames on the air, but can require up to 102 msec off-channel waiting for the next beacon transmission. This last issue is mitigated in the Neighbor Report by a beacon offset time value, allowing efficient passive scanning, but only in cases where an AP provides comprehensive Neighbor Reports in the beacon or probe response.

As a new, greenfield band, 6 GHz offers an opportunity to mandate features that reduce acquisition time, improve battery life, and avoid excess frames on the air. Several existing and new features improve 6 GHz AP discovery in all these areas.

Preferred scanning channels

Starting with channel 5, every fourth 20 MHz channel is designated for scanning, and APs should align their transmitting channels with Preferred Scanning Channels (PSCs) when using wider channel widths.

For wider channels, the ‘primary’ 20 MHz channel where the beacon is transmitted should align with a PSC where possible. This achieves two goals.

1. Client devices searching for a suitable AP must to scan at most 15 channels to find a beacon or other advertisement.
2. Ensures that non-PSC channels are not burdened by beacons, probe requests or responses, and thus can transfer the maximum possible user data.

To enforce good behavior, several rules are in place to reduce excessive probing and encourage client device designers to optimize their probing algorithms.

For example, a client device should not transmit (e.g. probe requests) in a non-PSC channel unless the client has learned that an AP is present, either by listening for 802.11 frames or through one of the mechanisms explained here. Even in PSC channels, wildcard probe requests are restricted, and the rate at which probes can be sent is limited.

Probe request rules:

Beacon changes

The beacon itself can be shortened in time and complexity because there are no existing Wi-Fi devices operating in the 6 GHz band. 6 GHz takes advantage of opportunities for house cleaning, forgoing transmissions that would only be of interest to older equipment. An example is the backwards-compatibility in the form of ‘capabilities’ and ‘operation’ information elements. Because, for example, a Wi-Fi 4 device is not programmed to understand Wi-Fi 5 parameters, beacons in the 5 GHz band must include the older Information Elements (IEs) in addition to newer ones added for subsequent generations.

The greenfield nature of 6 GHz allows these older elements to be dropped, saving time on the air and improving bandwidth efficiency. The example above shows that the HT and VHT operations and capabilities IEs are removed, and those values that are not superseded are added to the equivalent HE (Wi-Fi 6) IEs.

The ‘operations’ IEs are announcements from the AP about the transmission channel and are part of the beacon, probe response, association response, and re-association response frames. The ‘capabilities’ IEs list the options that APs and devices can use, and are transmitted in the information elements listed above and also the equivalent requests from client devices. Other modifications to the beacon include the rate at which the elements are transmitted: no pre-Wi-Fi 6 rates are allowed, forcing higher rates, shorter durations, and better bandwidth efficiency.

Multiple BSSIDs in one beacon

This feature was introduced as optional in 802.11v-2011 and was not initially implemented in clients or APs. For Wi-Fi 6E, clients are required to support multiple BSSIDs.

Where many SSID/BSSIDs are advertised on the same radio, as is commonplace in residential and enterprise WLANs, previously, each BSSID or virtual AP had to transmit its beacon separately. If an wanted to transmit four SSIDs, four separate beacons were transmitted in each 102.4 msec beacon interval, and many IEs were duplicated across beacons.

With the multiple BSSID feature, the common elements are transmitted once, and a separate information element is appended with the values unique to each virtual AP, now termed a ’non-transmitted’ BSSID.

The “new” beacon is considerably shorter, improving WLAN efficiency. However, this method may not be universally applied. For example, a limit on the beacon size may restrict the number of multiple BSSIDs to a maximum of 4, so when more than 5 SSIDs are used, multiple MBSSID beacons are still necessary to support the multiple BSSID feature. Thus, more than 4 SSIDs are split into multiple MBSSID sets.

Unsolicited probe responses

Unsolicited probe responses (UPR) function like mini beacons. While the usual beacon interval is 102.4 msec, unsolicited probe responses can be transmitted every 20 msec. The increased rate enables clients to decide whether the AP is suitable for connection through fast passive scanning rather than active probing or passive discovery of neighbor APs through reduced neighbor reports. The unsolicited probe response allows a client, rather than tuning to a channel and transmitting some probe requests and waiting ~20 msec for responses, to listen passively for just 20 msec and be sure the client has heard all BSSIDs on that channel. Unsolicited probe responses can contain the same information elements as a ’normal’ probe response, but they are transmitted to the broadcast address.

FILS announcements

Fast initial link setup (FILS) is a complete protocol for AP discovery, authentication, and handover that was introduced in 802.11ai and the Wi-Fi Alliance optimized connectivity certification. FILS was aimed particularly at public networks but was not widely adopted. FILS announcements act as mini beacons, transmitted every 20 msec. Each announcement frame contains the information necessary for a client device to decide whether the AP is suitable for connection.

FILS announcements can also incorporate reduced neighbor reports to advertise the channels of other APs of the same network. The ‘short SSID’ can optionally be substituted for the SSID in the FILS announcement. This value is a (non-reversible) hash of a full SSID.

FILS announcements and unsolicited probe responses serve similar purpose. Only one or the other would normally be required. Starting in AOS-8.11 and AOS-10.5, FILS announcements are the default advertisement for 6 GHz channels when capable HPE Aruba Networking APs are operating as single-band 6 GHz only (without 2.4 GHz or 5 GHz operation enabled). When the capable AP is operating in a multi-band state, FILS advertisement in 6 GHz is automatically disabled to conserve airtime. This is not configurable.

Out-of-band (OOB) AP discovery

The techniques mentioned above allow a client to scan the 6 GHz band to discover APs in-band. But most 6 GHz APs will operate as multi-band, where non-6 GHz radios can be coordinated, enabling a client scanning 2.4 GHz or 5 GHz can learn about a 6 GHz AP without tuning the radio to, or scanning, 6 GHz.

Reduced neighbor report

The reduced neighbor report (RNR) was initially developed for use with the FILS discovery protocol, but use is expanded for 6 GHz operation. When associated at 2.4 GHz or 5 GHz, the client can listen for BSSIDs containing RNR information elements and discover the channels where 6 GHz neighbor APs, in the same physical unit or separate units, are transmitting. This allows clients to move directly to the target 6 GHz channel.

• List networks on adjacent radios or neighboring APs
• Supports faster 6 GHz BSS discovery
• Includes a relative offset for target beacon transmission time
• Found in existing passive/active scanning through beacon or probe response frames.
• No configuration and is automatically appended to all BSSes on 2.4 GHz and 5 GHz radios on capable APs.

The reduced neighbor report IE is included in the beacon and probe response frames of the lower-band (2.4 GHz or 5 GHz) BSSID. The report includes fields for each neighbor BSS, if transmitting the same SSID in the 6 GHz band, along with channel and beacon offset.

The operating class and channel number refer to tables in IEEE 802.11 listing all possible channel widths and center frequencies. For 6 GHz, this guides the client device to the correct channel out of the possible 59 at 20 MHz, 29 at 40 MHz, etc. With this information, the client device can parse the RNR from a 2.4 GHz or 5 GHz BSSID and go directly to the channel in the 6 GHz band to find an equivalent SSID/BSSID.

The target beacon transmission time (TBTT) information in the reduced neighbor report refers to the beacon offset in time. The TBTT is measured in time units of 1.024 msec, and allows the client device to schedule an accurate time to go off-channel from the current AP and passively scan the beacon of the 6 GHz BSSID, subsequently authenticating if desired.

The full neighbor report could be used in place of the RNR, as a superset of the RNR information is contained with-in, but the standard promotes the latter because the RNR is shorter and more efficient. Reduced neighbor reports are supported on 6 GHz capable HPE Aruba Networking APs starting in AOS-8.9.

Access network query protocol

The access network query protocol (ANQP) is a pre-association exchange protocol initially added for Passpoint operation. ANQP allows a client device to query an AP about capabilities such as Passpoint, information about the venue, and identity providers that can be reached for authentication. When used for 6 GHz WLANs, ANQP conveys a full neighbor report for 6 GHz BSSIDs that may be in the same WLAN, whether using the same SSID or different SSIDs. Transmitting the neighbor report element over ANQP rather than directly in the beacon or probe responses is more efficient, as air time is not consumed unless the client device requests the neighbor report.

In a multi-band network, BSSIDs in the lower bands (2.4 GHz or 5 GHz) could advertise ANQP capability, and multi-band client devices could request neighbor reports via ANQP, allowing them to discover full SSID, BSSID, channel and beacon offset information without leaving the lower band to receive or transmit in the 6 GHz band.

Automatic frequency coordination

The 6 GHz bands contain incumbent users, and for higher power or outdoor operation with standard power APs, the FCC requires that incumbents are protected from interference from unlicensed 6 GHz users, including Wi-Fi. Some areas of the band are not allowed, even under automatic frequency coordination (AFC) control. The available channels for higher power or outdoor operation are from 5945-6425 MHz and 6525-6875 MHz, the U-NII-5 and U-NII-7 bands.

Fortunately, the majority of incumbent, such as point-to-point fixed service, users are known, as they are licensed and their details are listed in the ULS database, maintained and updated by the FCC.

The general architecture for automatic frequency coordination (AFC) centers on an AP, or group of managed APs, generating an inquiry message that includes respective location, elevation, and indications of the desired transmit power levels, channels or frequencies for transmission. The AFC uses this information as input to algorithms along with ULS data of licensed links and a terrain map. Some AFC operators may add building outlines to their terrain map to identify RF shadows. The response from the AFC to the AP inquiry will include a range of channels or frequencies that are available, and the AP, or RRM can pick from this list and transmit. The FCC will license a number of AFC service providers. APs must check with an AFC at least every 24 hours to receive fresh information.

The general concept of AFC calculations is as follows. Each licensed receiver’s location, antenna pattern, elevation above ground, and sensitivity are taken from the ULS database and used to plot contours defining zones of interference for given transmit power levels. The example above shows one contour calculated for interference to the antenna A; another plot would be generated for antenna B.

As the antennas for point-to-point links are usually very high-gain, these plots are shaped like a keyhole, with a short-distance circle around the back for sidelobe sensitivity and a long path down the antenna boresight.

The contour is significant because any Wi-Fi transmitter within the contour and above the power threshold for which the contour is calculated would cause interference at the fixed link’s receive antenna and should not be allowed at that location, frequency, and transmit level.

Many plots or contours must be calculated and plotted depending on the power of the interfering signal, and terrain is taken into account to determine line-of-sight conditions or whether high ground obscures the path. AFCs may pre-calculate the contours to reduce response delays. The diagram above shows a set of contours from an AFC, calculated for different power levels for a single fixed link receiver.

The response from an AFC to an AP inquiry message may be either a list of available channels, or available frequency ranges, along with the maximum power levels available, or both. The graphical example shows how such information might be displayed on an AFC client application. The top row is a frequency range response, giving power spectral density limits for the various ranges. The lower levels show channel availability by transmit power level (coloring is not part of the AFC response). The example clearly shows fixed links near the location, and that these effectively exclude a number of channels in the response. The AP would only be allowed channel assignment from channels allowing viable operation.

Because AFC operation is not permitted in the U-NII-6 and U-NII-8 bands, the results shown in the diagram for those frequencies are invalid.

Note that the AFC does not grant a particular frequency to the AP; the AFC just indicates those channels, frequencies, and power levels that will not cause interference to incumbents. There is no attempt to allocate specific channels or coordinate different channels for neighboring APs or WLANs from the AFC provider. Those tasks are left up to the AirMatch RRM service.

2 - Planning and deployment

Wi-Fi 6E is Wi-Fi 6 (IEEE 802.11ax PHY/MAC) operating in the 6 GHz band offering up to double or triple system capacity compared to previous generations. Note the 6 GHz band is not available in every regulatory domain (region). Ensure you comply with your local regulatory requirements before deploying Wi-Fi 6E.

Key design principles

1. Enable 6 GHz by creating a multi-band SSID rather than creating a 6 GHz only SSID.
2. Choose Enhanced Open for guest networks, WPA3-Personal for passphrase networks, and WPA3-Enterprise for 802.1X corporate networks.
3. Assess your client device mix before enabling compatibility modes for WPA3 or Enhanced Open. Prefer to disable transition mode to improve security.
4. Test new security modes like WPA3 and Enhanced Open in a controlled environment before widespread deployment.
5. Consider enabling 802.11r (Fast Transition) for WPA3-Enterprise security modes.
   • Fast roaming can significantly reduce delays in service when a client transitions between neighboring APs and is crucial for latency sensitive applications like telephony (Voice over Wi-Fi).
6. Plan for a capacity based design with overlapping primary and secondary coverage targets verified by end user devices.
   • In capacity based deployments, AP density may increase 0-10% in key usage areas. Survey, check, and validate for 6 GHz.
   • Coverage based deployments must be revisited and redesigned.
7. Plan channel widths per band based on RF layering strategy and regulatory domain allocations.
   • For FCC (or other 1200 MHz domains) this generally means 20 MHz in 2.4 GHz, 20 or 40 MHz in 5 GHz, and 80 MHz in 6 GHz.
     • With sufficient channel reuse (low density), 160 MHz channel width can be used in 6 GHz.
     • With limited channel reuse (high density), like in large public venues, 40 MHz channel width in 6 GHz is desired.
   • For Europe (or other 500 MHz domains), this generally means 20 MHz in 2.4 GHz, 20 or 40 MHz in 5 GHz, and 40 MHz in 6 GHz.
8. Disable lower management rates in all bands to reduce management frame overhead.
   • For example, removing 1, 2, 5.5, 6, 9, and 11 Mbps rates (across applicable bands) and possible based on coverage and client requirements.

Security requirements

Prior to Wi-Fi 6E, the first Wi-Fi generation to enforce security requirements with the introduction of a new PHY/MAC was Wi-Fi 4 (802.11n). Clients are penalized to 802.11a/b/g speeds when using wired equivalent privacy (WEP) or temporal key integrity protocol (TKIP).

Wi-Fi 6E operation in 6 GHz also introduces new required baseline security requirements. Wi-Fi Protected Access 3 (WPA3) or Enhanced Open are mandatory for Wi-Fi 6E deployments and adoption.

Legacy security protocols are not allowed in 6 GHz:

• Open authentication
• WEP, TKIP, WPA
• WPA2

This means existing SSID deployments using WPA2-Enterprise (802.1X) or WPA2-Personal security modes cannot be enabled for 6 GHz.

This forces either configuration changes to existing SSIDs or new SSID deployment and client migrations.

Security mode options for 6 GHz:

• Enhanced Open (OWE)
  • Leverages opportunistic wireless encryption (OWE) to replace Open System Authentication
  • Diffie-Hellman exchange encrypts all wireless traffic
  • Offers encryption without user authentication
  • MFP required
• WPA3-Personal (SAE)
  • Simultaneous authentication of equals (SAE) replaces the one-way key generation found in WPA2-PSK with a Diffie-Hellman like key exchange
  • Hash-to-element (H2E) required for SAE PWE derivation as an industry response to the Dragonblood vulnerability
  • MFP required
• WPA3-Enterprise
  • AKM:5 key management (SHA-256); CCMP-128 ciphers; MFP required
• WPA3-Enterprise with GCM-256
  • AKM:5 key management (SHA-256); GCMP-256 ciphers; MFP required
• WPA3-Enterprise 192-bit (CNSA)
  • AKM:12 key management (SHA-384); GCMP-256 ciphers; MFP required; strong EAP-TLS methods only (no mix and match, no PEAP)

Clients

Wi-Fi 6E support requires both driver and operating system support.

Recommendation is to always know and understand the capabilities of the clients being serviced by the APs in order to configure and plan accordingly.

Minimum versions required:

• Android 13+

• iOS 16.1+, check which Apple devices support Wi-Fi 6E

• Windows 11+ with a capable NIC such as the Intel AX210

Software updates can improve the capabilities enabled by hardware. Recommend to periodically check release notes and update client OS and drivers.

SSID planning

With Wi-Fi 6E traditional dual-band enterprise SSID layouts must be considered for how they might evolve into a tri-band deployment.

Consider this deployment approach prior to Wi-Fi 6E.

Potential strategy after migrating to Wi-Fi 6E.

Multi-band SSIDs are recommended for the following reasons.

• Traditional active/passive scanning does not scale well when adding up to 59 more 20 MHz channels in 6 GHz. HPE Networking APs automatically append Reduced Neighbor Reports (RNRs) to out-of-band (OOB) BSSes in 2.4 GHz and 5 GHz. When the client scans in 2.4 GHz or 5 GHz, the RNR acts as a seed telling the client exactly where to discover a 6 GHz network.
• APs operating with a single radio and a 6 GHz-only will force clients to do in-band discovery which is a much slower discovery process and may cause a poor connection experience.
• Multi-band SSIDs provide a fallback band when the 6 GHz band is not available due to pending frequency coordination (AFC) bring up or expiration.

In the majority of cases, multi-band SSIDs should restrict bands to 5 GHz and 6 GHz. In other words, use the infrastructure to restrict where clients can connect. This is due to the BSS selection (discovery and association) being primarily up to the client, however, after connection HPE Networking ClientMatch can be used to influence (nudge) the client to a more optimal band. For example, place 2.4 GHz only IoT clients on a 2.4 GHz only SSID. Place tri-band capable clients on a 5 GHz + 6 GHz multi-band SSID.

There are some options to consider when deciding whether to create a new SSID or modify the configuration of an existing SSID to enable 6 GHz.

Migrate all security modes

Migrate security modes of all SSIDs to WPA3-Enterprise, WPA3-Personal, or Enhanced Open (OWE) with a multi-band SSID across 5 GHz and 6 GHz.

If transition mode is disabled, this will remove all legacy client support and is applicable for certain greenfield deployments or pop-up event networks like HPE Discover where users are professionals who typically refresh their BYOD devices often.

Proceed with caution and understand the client population.

Single SSID approach

Band specific SSIDs

This option is to create a new SSID for exclusively for 6 GHz support.

Dual SSID approach

SSID-A dedicated to WPA3-only devices and 5 GHz + 6 GHz bands. Disable transition mode.

SSID-B dedicated to WPA2 and legacy devices on the 2.4 GHz and/or 5 GHz bands. This allows support for WPA2-only clients to connect and minimizes any impact of operational parameters with WPA3-transition causing client bugs due to poor implementation or outdated drivers.

This approach adds an additional SSID which does increase management frame overhead, but can be negated by trimming lower basic rates. In general, aim to keep the number of SSIDs per AP low.

Existing SSIDs

Certain SSIDs like Hotspot 2.0 passpoint SSIDs such as eduroam recommend a single multi-band SSID. This approach should be taken for other federated SSIDs like Govroam, OpenRoaming, Cityroam, etc.

Before:

After:

Transition mode may be enabled to maintain support for WPA2-Enterprise only clients. Test in a controlled environment before widespread deployment.

AP planning

Propagation loss of 6 GHz vs 5 GHz is similar, 1-2 dB, when comparing free space path loss (FSPL). Real world tests show an additional 3-6 dB difference depending on the frequency location in the 6 GHz band and measurement points.

An industry study also shows propagation loss through different common building materials will have different effect. For example, brick has a much larger impact than drywall. Plan to increase AP density for 6 GHz when interior walls are composed of thick, dense materials.

In existing high-density deployments there may be no changes required for AP placement, but depends on the effective power levels for 6 GHz compared to 5 GHz. Factors include channel width, LPI, and SP depending on the regulatory domain. As an example, in the FCC domain under LPI rules, an 80 MHz channel width achieves higher EIRP than a 20 MHz channel because the more restrictive limit is based on power spectral density (PSD) rather than total power.

In general, the recommendation is to always place APs close to users with an unobstructed view. For example, do not place APs above ceilings. Prioritize placing APs in critical areas such as conference or training rooms. APs in hallways may not sufficiently provide 6 GHz coverage and will require to be moved in room.

Always survey, test, and validate using target end user client devices before widespread deployment.

Channel planning

With up to 59 additional channels, there are two main channel width selection choices depending on regulatory domain.

graph TD;
    reg("Regulatory domain")
    fivehundo("500 MHz")
    twelvehundo("1200 MHz")
    twenties("20 MHz or 40 MHz")
    eighties("80 MHz or 160 MHz")
    reg-->fivehundo;
    reg-->twelvehundo;
    fivehundo-->twenties;
    twelvehundo-->eighties;

If the regulatory domain allows up to 1200 MHz, 80 MHz is recommended for most deployments as each channel will line up with a preferred scanning channel (PSC) which will optimize both in-band (PSC) and out-of-band (RNR) scanning.

If the regulatory domain is restricted to the lower 500 MHz of the 6 Ghz band, 40 MHz channel width is recommended.

These recommendations primarily focus on Low Power Indoor (LPI) deployments.

For Standard power (SP) deployments, use 40 MHz channel width or 20 MHz if AP density is high (such as in LPV). Note that channel availability depends on frequency coordination.

Automatic frequency coordination

In general, 6 GHz usage falls under two categories.

1. Low power indoor (LPI) - no frequency coordination.
2. Standard power (SP) - frequency coordination mandatory.

Standard power APs need to be able to self-locate and submit geolocation information to an AFC provider. HPE Aruba Networking APs use a Frequency Coordination Orchestrator (FCO) service in Central to communicate with AFC.

Geolocation information can be collected in two different methods by HPE Aruba Networking APs.

1. Positional data collected by the APs GPS/GNSS radio.
2. An AP can leverage positional data broadcasted from a neighboring AP in AOS-8.13 and AOS-10.8 or later.

Multiple gigabit throughput planning

The maximum PHY rate on a given channel is determined by the channel width, RF environment, and MCS rates used by the client(s).

In the best case scenario, with the widest channel width and highest order MCS rate, these PHY data rates are possible.

The maximum data rate a client is capable of is determined by the client capabilities such as number of radio chains, maximum MCS rate and channel width supported on both sides of the link, of course along with the ideal RF conditions (SNR and EVM) to sustain those rates. Most clients have one or two radio chains. Consider that mobile clients with two radio chains sometimes disable one of two chains to conserve battery life.

The maximum throughput a single AP is capable of is determined by similar factors across each of the radios.

In the majority of deployments, 2.4 GHz cannot be considered in AP system capacity planning due to limited channel reuse in the crowded ISM band.

Multiple gigabit needs are determined by the configured channel widths along with environmental and traffic patterns. Aggregate data throughput on a tri-band tri-radio AP can easily exceed 1 Gbps under certain conditions.

For example, in environments with a single client per band each using maximum channel widths and rates, multiple gigabit throughput can be achieved during saturation testing.

However, consider target traffic usage patterns and expectations and active client count. As the client count increments on the same channel, throughput is reduced due to the contention based mechanisms in the 802.11 protocol.

1. Each client must wait the channel to become idle before transmitting (listen before talk)
2. When a channel is busy, each client picks a random backoff timer from a contention window and waits that many slot times before transmitting. If a collision occurs, the window size increases, spreading out retry attempts to reduce further collisions.

Thus, each additional client on a given AP reduces throughput and extends transmit opportunity (TXOP) durations as clients content for the medium.

Multiple APs on different channels are a way to scale, up to the channel reuse limits in the neighboring area with the goal of minimizing co-channel interference as much as possible.

Additionally, expected traffic usage patterns are an important characteristic to consider when determining multi-gigabit to the AP is a requirement.

Power sourcing

Additional radios and capabilities come with increased power requirements. Tri-radio APs require more power than dual-radio APs — 802.3at/CL4 or better required. The AP-650 is the only series which can operate and combine two 802.3af/CL3 sources. 802.3bt/CL6 is recommended for new deployments.

Intelligent power monitoring

Intelligent power monitoring or IPM is a method for controlling power usage of HPE Aruba Networking APs. The approach actively measures power usage and dynamically adapts the power budget and restrictions.

When IPM is disabled, static power management will apply reductions in order to not exceed worst case limits and stay within the confines of the power budget.

When IPM is enabled, dynamic power management allows the AP to enable full functionality and performance in the majority of cases.

Enabling IPM will allow for, in most cases, most features when tri-radio APs are powered by a 802.3at/CL4 PSE.

Recommendation is enable IPM.