Re: [STDS-802-11-TGBE] CID on sounding with EMLSR, minimum RU allocation

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

Thanks for this, Youhan. Some thoughts:

A beamformer shall not address a beamformee that is affiliated with a non-AP MLD operating in EMLSR or EMLMR in a BFRP Trigger frame which is not the first BFRP Trigger frame in an EHT TB sounding sequence.

I think IEEE 802.11 prefers "that" to "which".

"mode" or something is needed after "EMLSR or EMLMR".

An EHT beamformer that initiates an EHT TB sounding sequence shall transmit an EHT NDP Announcement frame with two or more STA Info fields and the RA field set to the broadcast address. The EHT NDP Announcement frame shall be followed after a SIFS by an EHT sounding NDP, which shall be followed after a SIFS by a BFRP Trigger frame. Any subsequent BRFP Trigger frames, if any, in the EHT TB sounding sequence shall be transmitted SIFS after an EHT TB PPDU containing EHT Compressed Beamforming/CQI frame(s). Each EHT beamformee that is addressed by a BFRP Trigger frame shall respond after a SIFS with an EHT TB PPDU containing one or more EHT Compressed Beamforming/CQI frames.

Too many "any"s. How about "Subsequent BFRP Trigger frames, if any, in…"?

Also typo "BRFP".

The text highlighted above might be interpreted as suggesting the BFer has to

check whether the TB PPDU contained EHT CBR frames. We already say that we

are in an EHT TB sounding sequence, which implies we're using BFRP frames,

which implies we're getting EHT CBR frames, so I think the

"containing EHT Compressed Beamforming/CQI frames(s)" can just be deleted.

Thanks,

Mark

Mark RISON, Standards Architect, WLAN English/Esperanto/Français

Samsung Cambridge Solution Centre Tel: +44 1223 434600

Innovation Park, Cambridge CB4 0DS Fax: +44 1223 434601

ROYAUME UNI WWW: http://www.samsung.com/uk

From: Youhan Kim <youhank@xxxxxxxxxxxxxxxx>
Sent: Wednesday, 17 May 2023 21:05
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] CID on sounding with EMLSR, minimum RU allocation

Thanks, Xiaogang and Minyoung.

Regarding

A beamformer shall address a beamformee that is affiliated with a non-AP MLD operating in EMLSR or EMLMR mode only in the first BFRP Trigger frame of a sounding sequence.

Please note that 11be D3.1 P621L13 states:

In the EHT TB sounding sequence, the STAs identified in the NDP

Announcement frame should be the same as the ones identified in the Trigger frame(s) in the same TXOP.

So, the standard does not prohibit a situation where an EMLSR STA1 is included in the NDPA, but for whatever reason is not included in the BFRPs.

Hence, I think “A beamformer SHALL address a beamformee … in EMLSR … mode …” might be construed as being in conflict with P621L13.

What is really needed for the EMLSR/EMLMR STAs is that the APs do not poll them in non-first BFRPs. So, I think the best way is to say just that in the rule.

I.e., I suggest the following.

Regarding the proposed change for P618L36, here is my proposed wording.

Regards,

Youhan

From: Minyoung Park <mpark.ieee@xxxxxxxxx>
Sent: Wednesday, May 17, 2023 2:44 PM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] CID on sounding with EMLSR, minimum RU allocation

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

Hi Xiaogang,

One minor comment: in the last part of the second added sentence, '...in a sounding sequence is transmitted.' should be '...in the sounding sequence is transmitted.'

Thanks,

Minyoung

On Wed, May 17, 2023 at 11:12 AM Xiaogang Chen <xiaogang.g.chen@xxxxxxxxx> wrote:

Hi all,

r3 was uploaded based on the discussions this morning. Sounding related changes are pasted below. Feel free to comment. Thanks.

Proposed changes:

11be editor please add the following paragraph in P.L. 618.43 (35.7.3 Rules for EHT sounding protocol sequences).

A beamformer shall address a beamformee that is affiliated with a non-AP MLD operating in EMLSR or EMLMR mode only in the first BFRP Trigger frame of a sounding sequence.

In addition, modify the paragraph below in P.L. 618.36

An EHT beamformer that initiates an EHT TB sounding sequence shall transmit an EHT NDP Announcement frame with two or more STA Info fields and the RA field set to the broadcast address. The EHT NDP Announcement frame shall be followed after a SIFS by an EHT sounding NDP, which shall be followed after a SIFS by a BFRP Trigger frame. If more than one BFRP Trigger frames are present in a sounding sequence, the EHT TB PPDU that contains the EHT Compressed Beamforming/CQI frame(s) shall be followed, after a SIFS, by another BFRP Tigger frame until the last EHT Compressed Beamforming/CQI frame in a sounding sequence is transmitted. Each EHT beamformee that is addressed by a BFRP Trigger frame shall respond after a SIFS with an EHT TB PPDU containing one or more EHT Compressed Beamforming/CQI frames.

On Sat, May 13, 2023 at 11:31 PM Xiaogang Chen <xiaogang.g.chen@xxxxxxxxx> wrote:

Hi Alfred,

Can you help to add the following contribution in the queue of the joint session? Thanks.

https://mentor.ieee.org/802.11/dcn/23/11-23-0317-02-00be-cr-d30-miscs.docx

Hi all,

Please feel free to review the sounding related CIDs on page 4,5 if interested.

BRs,

Xiaogang.

To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1

To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1