Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Alfred,
Please help me add the following passed SP to the PHY motion list:
Motion: Move to incorporate into the latest TGbn draft the proposed text changes from the following documents: 11-25/857r1
relative SP is passed with no objection.
Many thanks.
Thanks
Best Regards
Qisheng Huang
Hi Alfred
Please add the following 4 SPs to the PHY Motion list (from 25/0734r1, all passed with no objection):
Motion 1: Move to add the following into the 11bn SFD:
APs exchange the following 2-bit capability fields with values 1,2,3 or 4 at the time of group formation between the members of a COBF pair. The capabilities are defined for the AP declared BW and assume Nc=2 (# of columns in the feedback)
Field 1 – Total number of OBSS sounding reports that the AP can store for this COBF pair at a given time
Field 2 – Total number of OBSS joint sounding reports that the AP can store for this COBF pair at a given time (can’t be higher than number in field 1)
Motion 2: Move to add the following into the 11bn SFD:
In the TB PPDU carrying OBSS AP sounding feedback do you support limiting Nss to 1
Motion 3: Move to add the following into the 11bn SFD:
In COBF, cross-BSS/joint sounding feedback max Nc is limited to 2
Motion 4: Move to add the following into the 11bn SFD:
In TB PPDU carrying cross BSS (including joint) sounding feedback for COBF the T_PE is fixed as 20uS (nominal_packet_padding=20uS and aFactor=4) and LDPC extra symbol set as 1
• AP will set the UL length field and other parameters in the BFRP trigger frame according to this rule
Thanks,
Ron
From: Rui Cao <rui.cao_2@xxxxxxx>
Sent: Wednesday, May 14, 2025 9:43 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] PHY Motions request for May 2025
Hi Alfred,
Please help to add the following passed SPs to the PHY Motion list:
Motion 1: Move to add the following to 11bn SFD:
The definition for the transmit constellation error in an UHR TB PPDU using RRU:
Transmit Constellation Error requirement of UHR TB PPDU using RRU for MCS0-15 follows the same definition as in EHT.
Transmit Constellation Error requirement of UHR TB PPDU using RRU for the new MCSs (QPSK 2/3, 16QAM 2/3, 16QAM 5/6 and 256QAM 2/3) is:
MCS | Relative constellation error in an UHR TB PPDU using RRU when transmit power is larger than the maximum power of UHR-MCS 7 (dB) | Relative constellation error in an UHR TB PPDU using RRU when transmit power is less than or equal to the maximum power of UHR-MCS 7 (dB) |
QPSK 2/3 | -13 | -27 |
16QAM 2/3 | -18 | -27 |
16QAM 5/6 | -20 | -27 |
256QAM 2/3 | -29 | -29 |
Reference document: [11-25/843r0]
Result: no objection
Motion 2: Move to add the following to 11bn SFD:
The unused tone EVM definition and requirement of UHR TB PPDU when all users are scheduled with RRU is the same as in EHT TB PPDU.
Reference document: [11-25/843r0]
Result: no objection
Thanks,
Ying
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