Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Alfred,Could you please add the following passed SP to motion?• M4: Move to add the following to 11bn SFD
– The Number of UHR-SIG Symbols in CoBF transmission is equal to the minimum number of UHR-SIG symbols needed to accommodate the UHR-SIG information
• No extra UHR-SIG symbols will be allowed
• Supporting doc: 11-25/842r1
No objection
Regards,AliceOn Thu, May 15, 2025 at 3:10 AM Alice Jialing Li Chen <jialing.li.phd2@xxxxxxxxx> wrote:Hi Alfred,Could you please add the following passed SPs to the PM2 motion list?• M1: Move to add the following to 11bn SFD
– Use fixed values for the following fields in the CoBF transmission
• UHR-SIG MCS is fixed to MCS0
• Spatial Reuse is fixed to ‘PSR_AND_NON_SRG_OBSS_PD_PROHIBITED’
• LDPC Extra Symbol Segment is fixed to 1
• PE Disambiguity is fixed to 1
• Interference Mitigation is fixed to ‘Disable’
• Supporting doc: 11-25/842r1, 11-25/389r2, 11-25/399r1, 11-25/401r0
No objection
• M2: Move to add the following to 11bn SFD
– The Bandwidth and Punctured Channel Information indication in the CoBF Invite and Sync frames are the same with the following rules:
• When the static puncturing patterns of the two APs are the same, the puncturing information in the invite and sync frames corresponds to that
• If the static puncturing patterns of the two APs are not the same, the sharing AP will need to reduce to a smaller BW in which the two APs have the same puncturing pattern, and the information in the invite and sync frames will correspond to that reduced BW configuration
• Note: Indication format is TBD
• Supporting doc: 11-25/842r1
No objection
• M3: Move to add the following to 11bn SFD
– The indicated GI+LTF Size (for the COBF transmission) in the CoBF Invite and Sync frames is the same
• GI+LTF size indication format is TBD
• Supporting doc: 11-25/842r1
119Y/26N/82A
Could you please add the following SP to the PM2 session?• SP4: Do you agree to add the following to 11bn SFD?
– The Number of UHR-SIG Symbols in CoBF transmission is equal to the minimum number of UHR-SIG symbols needed to accommodate the UHR-SIG information
• No extra UHR-SIG symbols will be allowed
• Supporting doc: 11-25/842r1
Regards,AliceOn Thu, May 15, 2025 at 1:13 AM Alice Jialing Li Chen <jialing.li.phd2@xxxxxxxxx> wrote:Hi Alfred,I presented 11-25/842r0 in the last TGbn PHY call in the May Interim. No time to run 4 SPs in the PHY call. Just uploaded the latest 11-25/842r1. May I run the following SPs in the Joint call if time permits?• SP1: Do you agree to add the following to 11bn SFD?
– Use fixed values for the following fields in the CoBF transmission
• UHR-SIG MCS is fixed to MCS0
• Spatial Reuse is fixed to ‘PSR_AND_NON_SRG_OBSS_PD_PROHIBITED’
• LDPC Extra Symbol Segment is fixed to 1
• PE Disambiguity is fixed to 1
• Interference Mitigation is fixed to ‘Disable’
• Supporting doc: 11-25/842r1, 11-25/389r2, 11-25/399r1, 11-25/401r0
• SP2: Do you agree to add the following to 11bn SFD?
– The Bandwidth and Punctured Channel Information indication in the CoBF Invite and Sync frames are the same with the following rules:
• When the static puncturing patterns of the two APs are the same, the puncturing information in the invite and sync frames corresponds to that
• If the static puncturing patterns of the two APs are not the same, the sharing AP will need to reduce to a smaller BW in which the two APs have the same puncturing pattern, and the information in the invite and sync frames will correspond to that reduced BW configuration
• Note: Indication format is TBD
• Supporting doc: 11-25/842r1
• SP3: Do you agree to add the following to 11bn SFD?
– The indicated GI+LTF Size (for the COBF transmission) in the CoBF Invite and Sync frames is the same
• GI+LTF size indication format is TBD
• Supporting doc: 11-25/842r1
• SP4: Do you agree to add the following to 11bn SFD?
– The Number of UHR-SIG Symbols in CoBF transmission is equal to the minimum number of UHR-SIG symbols needed to accommodate the UHR-SIG information
• No extra UHR-SIG symbols will be allowed
• Supporting doc: 11-25/842r1
Regards,
Alice ChenQualcomm
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