Hi Alfred,
Please add the following PHY motions (all reached consensus in PHY adhoc without any objections based on
document 11-25/0083r1) to the motions queue:
- Move to add the following to the 802.11bn SFD
•
802.11bn defines the concept of a sync-reference AP and a sync-follower AP for CFO correction in COBF
•
Sync-follower AP pre-corrections needed
•
For sequential sounding:
•
All the NDPs sent by it during sounding phase that are sent for the purpose of sounding the STAs in the other BSS (Mandatory)
•
For the NDPs sent by it for sounding the STAs in its own BSS, it is recommended but not mandatory that the sync follower AP pre-correct those NDPs
•
For joint sounding
•
All the NDPs sent by it during the sounding phase (Mandatory)
•
The COBF sync and COBF PPDU during transmission phase using the same frequency pre-correction value as the sounding phase, when it is the sharing AP
•
Sync-reference AP does not pre-correct during transmission phase when it is the sharing AP
- Move to add the following to the 802.11bn SFD
•
The sync-follower AP shall use the NDPA frame sent by the sync-reference AP to pre-correct the NDP frequency to be within a TBD range (e.g., 350Hz) of the sync-reference AP’s frequency
•
Applies to sequential and joint sounding
•
The pre-correction of cross-BSS NDP and joint NDP is mandatory
•
The pre-correction of in-BSS NDPs is recommended but not a mandatory requirement
- Move to add the following to the 802.11bn SFD
•
The sharing AP is the AP that transmits the final sync frame before the COBF PPDU
•
Regardless of who is the sync-reference
•
Note: This ensures a consistent protocol and a consistent behavior at sharing AP
- Move to add the following to the 802.11bn SFD
•
The shared AP always pre-corrects COBF PPDU based on the final sync
•
To bring the two APs within a TBD frequency range of each other (e.g., ~350Hz)
•
Note: Regardless of which AP is the sync-reference, this ensures consistent behavior at shared AP
Thanks,
Sameer
