Coordinated Beamforming (Co-BF) is one of the key technologies that enables multi-AP networking performance gains in Wi‑Fi 8. A core challenge in the standardization process is: how can we enable Wi‑Fi 8's multi‑AP coordinated sounding without requiring any hardware or software changes to existing Wi‑Fi 7 clients?
This article provides an in‑depth analysis of the "self‑contained" Co‑BF NDPA frame proposed in the UHR standard — a design that cleverly reuses the EHT frame structure to achieve seamless coexistence between new and legacy devices.
The design of Co‑BF multi‑AP sounding is guided by two core principles:
Avoid Client‑Side Changes: Stations (STAs) that support EHT beamforming sounding/feedback should be able to support UHR Co‑BF sounding/feedback without any modifications.
Maximize Reuse of Existing Components: Co‑BF sounding can directly reuse the NDP (Null Data Packet) frame and MU‑MIMO BF feedback report from EHT.
This means Co‑BF capability can be backward‑compatible — users do not need to replace their existing client devices.
Based on these principles, the standard adopts a unified and "self‑contained" NDPA (Null Data Packet Announcement) frame design. "Self‑contained" means that a single NDPA frame is sufficient to inform the responding APs of all sounding parameters, without requiring additional negotiation or pre‑shared state.
The traditional NDPA frame serves to notify STAs to prepare for receiving the NDP and performing channel measurement. The Co‑BF NDPA frame extends this — the sounding initiating AP uses special user information fields within the NDPA frame to convey sounding parameters to the responding APs, directing how they should transmit their NDP frames.
Core Design Approach: Reuse the EHT NDPA frame's user information field format, using two special user information fields to carry the additional information needed for Co‑BF.
The initiating AP conveys the following critical information to responding APs via the NDPA frame:
The initiating AP assigns an Association Identifier (AID) to each responding AP to uniquely identify it during the sounding process. Using AIDs instead of MAC addresses reduces frame overhead.
The LTF (Long Training Field) parameters determine channel estimation accuracy:
P‑matrix Size: Used to orthogonally separate multi‑stream channel estimates, supporting 4×4 or 8×8.
Stream Allocation: Specifies the number of spatial streams the responding AP will use for sounding and their starting index. The receiver can distinguish which AP's channel estimation results belong to which based on the row number. For example, with an 8×8 P‑matrix, if the initiating AP uses rows 1‑4 and the responding AP uses rows 5‑8, the responding AP's starting stream index = 5 and Nsts = 4.
The U‑SIG is part of the NDP frame header. In joint sounding, the NDPs from the initiating AP and responding APs are transmitted simultaneously and will overlap in the air. Their U‑SIG content must be identical, otherwise the receiver cannot correctly decode them.
The initiating AP must inform responding APs of the U‑SIG values to use, including:
BSS Color: Set to the initiating AP's BSS color to ensure consistent handling on the STA side.
Bandwidth (BW) : The total channel bandwidth for sounding (20/40/80/160 MHz).
Punctured Channel Info: Indicates which sub‑channels are disabled to avoid frequency‑selective interference.
TXOP: Protects the sounding process from interference by other devices.
The initiating AP uses this 5‑bit field to suggest the MCS (Modulation and Coding Scheme) that the responding AP should use in subsequent sounding sequences when sending BFRP Trigger frames. Since the initiating AP can only "overhear" the CSI feedback from the responding AP's associated STAs, this parameter helps ensure that the initiating AP can correctly receive the CSI feedback from OBSS STAs.
The Co‑BF NDPA frame reuses the EHT NDPA frame format and its version identifier. The standard ensures compatibility through a clever design:
Special AID 2047: The first special user information field in the STA Info List uses AID 2047, with the "NDPA Version ID" indicating the UHR version.
Compatibility Guarantees:
The special AID 2047 and responding AP AIDs are not assigned to regular users.
Regular users are not required to read user information fields with mismatched AIDs.
Regular user information fields remain identical to the EHT version.
EHT MU‑MIMO BF feedback can be reused directly.
Identification Mechanism: The presence of the special AID 2047 in the STA Info List distinguishes whether the NDPA is for Co‑BF or traditional BF.
To reduce implementation complexity, the standard imposes clear restrictions on sounding parameters:
| Parameter | Restriction | Impact on NDPA Configuration |
|---|---|---|
| Antenna Count | 4 or 8 | Stream allocation only supports up to 8 streams; P‑matrix only supports 4×4 or 8×8 |
| LTF Type | 2x LTF | Longer training sequences (more noise‑resistant than 1x) but restricts the use of 4x LTF |
| GI Duration | 0.8µs, 1.6µs | Does not support shorter (0.4µs) or longer (3.2µs) GIs, simplifying receiver equalizer design |
| P‑matrix | Only 4×4, 8×8 | Reduces matrix computation complexity |
These restrictions significantly reduce the difficulty of chip design and deployment while maintaining baseline performance.
The Co‑BF NDPA frame design in Wi‑Fi 8 exemplifies the pragmatic standardization approach of "forward compatibility, minimal changes, and maximum reuse." By reusing the EHT frame structure, introducing the special AID 2047 identifier, employing a self‑contained parameter passing mechanism, and applying reasonable complexity controls, multi‑AP coordinated sounding can deliver significant performance gains without impacting existing client devices.
For network equipment vendors and chip designers, understanding the design logic of this frame structure is key to mastering Wi‑Fi 8's multi‑AP coordination capabilities. For everyday users, it means that when upgrading to a Wi‑Fi 8 network in the future, their existing Wi‑Fi 7 devices will continue to work seamlessly and benefit from improved network performance in multi‑AP environments.