The opening of the 6 GHz band solved a lot of problems for enterprise Wi-Fi. It gave us clean spectrum, wider channels, and a break from the legacy device clutter that makes 2.4 and 5 GHz such a mess. It also introduced a problem that doesn’t get talked about enough: the client side of the conversation is quiet. Really quiet. And HPE is pushing Standard Power as the fix, with all the trade offs that come attached to it. They recently outlined the promise and the pitfalls of this approach during Mobility Field Day 14.
Power Underwhelming
Low Power Indoor (LPI) mode, the default for most 6 GHz deployments in the US, caps client transmit power at a power spectral density of -1 dBm per MHz. Translate that into something concrete and you get a MacBook Pro limited to 12 dBm EIRP on an 80 MHz channel, and just 6 dBm if it drops to a 20 MHz channel. Access points can shout as loud as they want under LPI. Clients can barely whisper back. The result is that APs typically hear 6 GHz clients about 10 dB weaker than they hear the same clients on 5 GHz. That asymmetry matters more than it sounds like it should. A network is only as good as its weakest link, and in this case the worst link is baked into the regulatory framework itself. Here’s a great overview of everything from HPE’s Wes Purvis:
Standard Power addresses this directly. When an AP switches into Standard Power mode, it advertises the change to clients through its beacon, using the regulatory info field to communicate the new power ceiling. A Standard Power capable client can then push transmit power up to 24 dBm, a substantial jump from the LPI limit. The real world numbers back up the theory. HPE has reported average RSSI improvements of 10 dB for roaming clients, moving from around -72 dBm up to -62 dBm, and at least one deployment saw its Coverage Service Level Experience score jump 30%. That is not a rounding error. That is a network that actually feels different to the people using it.
Where does this matter most? Lower density environments are the sweet spot. Think warehouses, distribution centers, and multi-dwelling units where APs are spread out and coverage edges are doing a lot of the work. In these layouts, clients often sit far from the nearest AP, and every extra dB of client power translates into fewer retries and fewer dropped associations. Dense deployments are a different story. When APs are packed close together, most clients are living in the meat of the cell rather than out at the edge, so the LPI limitation matters less and the spectrum trade off of Standard Power starts to look less appealing.
And there is a real spectrum trade off. Standard Power reduces the number of available 20 MHz channels in 6 GHz from 59 down to 41, an 18 channel loss driven by the wider exclusion zones needed to protect incumbent operations. That is not a small choice to make. Anyone planning a high density campus network needs to weigh that channel loss against the coverage gains before flipping the switch.
AFC Attention
The bigger operational hurdle is geolocation. Standard Power requires coordination through an Automated Frequency Coordination (AFC) system, and every AP has to report a precise 3D location along with an uncertainty area so the AFC can confirm it won’t interfere with incumbents. GPS does not work well indoors, obviously, so HPE’s approach has a handful of APs acquire a GPS lock and let the rest of the fleet derive their position from those anchors using RF neighborships, BLE, or 802.11mc. The FCC will not let administrators shortcut this by hardcoding coordinates, which is a sensible guardrail even though it adds real deployment complexity. Uncertainty compounds with each hop away from a GPS-locked AP, and if an AP cannot connect to any neighbor at all, a dual mode unit falls back to LPI while a Standard Power-only radio simply shuts off in 6 GHz.
Right now, flipping compatible dual mode APs into Standard Power is a manual job for administrators. HPE has signaled it is exploring letting Radio Resource Management handle this dynamically down the road, based on what it is learning from early deployments. That would be a meaningful step. Manual toggling does not scale well across a large indoor footprint, and RRM is exactly the kind of system that should be making these calls in real time based on actual RF conditions rather than a static admin decision made once during install.
Bringing IT All Together
Standard Power is not a universal upgrade. It is a targeted tool for a specific problem, weak client uplink in low density spaces, and it comes with genuine costs in spectrum and deployment complexity. For the right environment, though, the coverage gains are hard to ignore. You need to know if this solution will solve your challenges before you go through the effort to enable it. Companies like HPE are making sure to have all the information you need up front so you can plan properly if you decide you want to place your bets on Standard Power.
To learn more about HPE and their approach to Standard Power for Wi-Fi deployments, make sure to check out their solutions page here. To see the entire Mobility Field Day presentation, please head over to the presentation appearance page here.
