Re: [STDS-802-11-TGBN] Co-BF/Co-SR Trigger frame format discussion

Thread Links	Date Links
Thread Prev	Thread Next	Thread Index	Date Prev	Date Next	Date Index

Hi Jason,

I have one more technical question on this spec draft text:

The TX Power Limit field indicates the Co-SR coordinated AP’s combined transmit power limit at the transmit antenna connector of all the antennas used to transmit the PPDU of the Co-SR transmission in units of dBm/20MHz. The transmit power in dBm/20 MHz, PTX, is calculated as PTX = –20 + FVal, where FVal is the value of the TX Power Limit field. Values above 60 are reserved for the TX Power Limit field.

What happens to this TX Power Limit field related text, if the coordinated AP’s transmission is an SU BFed transmission? Do we need to account for un-intentionally BFing to the incumbent transmission’s receiver and potentially causing a higher amount of interference?

Thanks,

Sameer

From: Fang, Juan <juan.fang@xxxxxxxxx>
Sent: Thursday, January 15, 2026 4:09 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] Co-BF/Co-SR Trigger frame format discussion

WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.

Thanks Jason,

Length, GI/LTF, Tx power are all defined for TB PPDU already, but it is reused for Co-BF/Co-SR trigger frame. It makes sense to me to reuse existing field as much as possible. What I found confusing is why we are not reusing the following existing field for TB PPDU as well.

Thanks,

Juan

From: Guoyuchen (Jason Yuchen Guo) <guoyuchen@xxxxxxxxxx>
Sent: Thursday, January 15, 2026 3:47 PM
To: Fang, Juan <juan.fang@xxxxxxxxx>; STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: re: Co-BF/Co-SR Trigger frame format discussion

Hi Juan,

Thanks for the comment.

The mapping that has been defined is for TB PPDU. However, in Co-BF/Co-SR transmission, we need a different mapping, i.e., more fields in the Co-BF PPDU should be copied from the Co-BF Trigger, hence, I placed the fields that need copy in the same order as in the U-SIG/UHR-SIG, this will largely simplify the copy procedure.

Best,

Jason

发件人: Fang, Juan <juan.fang@xxxxxxxxx>
发送时间: 2026年1月16日 3:54
收件人: Guoyuchen (Jason Yuchen Guo) <guoyuchen@xxxxxxxxxx>; STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
主题: RE: Co-BF/Co-SR Trigger frame format discussion

Hi Jason

Thanks for the update.

I have one comment on the special user info field. The specification already defined a mapping from B25-B36 of the special user info field to the B20-B25(BSS color 2 subfield) in U-SIG1 and B2 (CoBF/CoSR indication), B11-B15(number of UHR-SIG symbols field) in U-SIG2 for both EHT and UHR TB PPDU. We can easily extend this mapping to support DL non-OFDMA Co-BF transmission and DL SU Co-SR transmission as Length, GI/LTF size and TX power field, which is reused to support DL non-OFDMA Co-BF transmission and DL SU Co-SR transmission. This would help to make the spec cleaner and more consistent.

Thanks,

Juan

From: Guoyuchen (Jason Yuchen Guo) <000018696e95f088-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Thursday, January 15, 2026 9:55 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] Co-BF/Co-SR Trigger frame format discussion

Dear TGbn members,

I have uploaded a revision of doc. 0023 based on the feedback from members.

Best,

Jason

发件人: Guoyuchen (Jason Yuchen Guo)
发送时间: 2026年1月15日 9:16
收件人: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
主题: Co-BF/Co-SR Trigger frame format discussion

Dear TGbn members,

Please let me know your feedback on doc. 11-26/0023r1 on Co-BF/Co-SR Trigger frame format, thank you!

Best,

Jason

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