| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
• Move to add the following to the 11bn SFD
– The CoBF Sync frame carries the following information
• How to indicate the information is TBD
|
Category |
|
|
Control |
‘CoBF Sync’ |
|
PHY Common Info |
Length |
|
PHY Version Identifier |
|
|
Bandwidth |
|
|
Punctured Channel Information |
|
|
BSS Color 1, BSS Color 2 |
|
|
TXOP |
|
|
Number of UHR-SIG Symbols |
|
|
GI+LTF Size |
|
|
Number Of UHR-LTF Symbols |
|
|
Number of CoBF Users |
|
|
Per-User Info in Both BSS |
STA ID |
|
BSS Color Indication |
|
|
MCS |
|
|
Spatial Configuration |
|
|
2xLDPC |
– Supporting doc: 11-25/389r0, 11-25/399r0, 11-25/401r0
Passed unanimously
• Move to add the following to the 11bn SFD
– In each of the CoBF Invite, Response and Sync frames, if there is information for more than one users, the users are ordered according to Nss in non-increasing order
• The order of users in the sharing BSS in the Sync frame is aligned with that in the Invite frame.
• The order of users in the shared BSS in the Sync frame is aligned with that in the Response frame.
– Supporting doc: 11-25/389r0, 11-25/381r0, 11-25/397r0
Hi Alfred,
Please also add the following SP to the motion queue (PHY COBF)
Move to add the following in the 802.11bn SFD:
Joint/cross-BSS sounding feedback is limited to UL OFDMA if >1 STA is sounded
Passed unanimously
Thanks,
Ron
From: Sameer Vermani <000039a3734fa32e-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Tuesday, March 11, 2025 9:38 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] Motions Requested for COBF
Hi Alfred,
Please also add the following 3 to the motions queue (all based on document 11-25/0381r0)
- Move to add the following in the 802.11bn SFD:
- The COBF PPDU’s GI+LTF support and signaling is as follows:
- Support of following GI+LTF combinations to be mandatory at both AP and STA
- 2x LTF +0.8us, 2xLTF+1.6us, 4xLTF+3.2us
- Additionally, 2x LTF+0.8us GI usage for a COBF pair is exchanged at the group formation stage
- Each AP conveys if it can use 2x+0.8us GI for this COBF group or not
- No further last-minute negotiation before COBF transmission
- Invite frame from sharing AP dictates the LTF+GI combination keeping the shared AP’s ability to use 2x LTF+0.8us in mind
Results of SP were 41Y/12N/32A
- Move to add the following in the 802.11bn SFD:
- BSS ordering of per-user SIG fields in the preamble of a COBF transmission
- In the cases where the user fields of either BSS may go first while preserving the Nss in non-increasing order, the user fields of the sharing BSS go first
Passed unanimously
- Move to add the following in the 802.11bn SFD:
There shall be a frame-exchange before the COBF sounding between the two APs which will at-least serve the following goals:
- Unavailability/decline indication from the responding AP
- Used by responding AP to refuse participation in a COBF sounding process
- Exchange of sounding Nss capability of the STAs being sounded in the two BSSs
- The minimum sounding Nss capability of the participating STAs in each BSS will be exchanged
- Note: Design of the frames is TBD by MAC group
Passed unanimously
Regards,
Sameer
From: Sameer Vermani
Sent: Monday, March 10, 2025 6:36 AM
To: asterjadhi@xxxxxxxxx; STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Motions Requested for COBF
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
To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1