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

Re: [STDS-802-11-TGBE] CID 15103 in document 317

Thanks Gaurang. IMO, the switch back rule will not be changed at all with the proposed text. It actually helps to clarify the behavior of AP and non-AP in TB sounding.

 

All, please find the proposed changes and let me know for any feedback before PM2. Thanks.

 

Proposed changes:

11be editor please make the following changes: add a note 11 after note 10 in

P.L. 569.20.

 

Note 11: If a beamformee is operating in EMLSR mode, the beamformee shall only be addressed in the first BFRP trigger frame in the current sounding TXOP. Otherwise, this beamformee shall not be addressed by the other BFRP trigger frame(s) in the current sounding TXOP.

 

 

BRs.

Xiaogang

 

From: Gaurang Naik <gnaik@xxxxxxxxxxxxxxxx>
Sent: Thursday, March 16, 2023 10:56 AM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBE] CID 15103 in document 317

 

Hi Xiaogang, all,

 

Following up from the discussion, I wanted to clarify that the Rejection reason I mentioned during the call was as follows. Note that CID 14115 was discussed in the previous round and it was rejected after some discussion within the group.

 

14115

Li-Hsiang Sun

35.3.17

464.30

"The STA affiliated with the non-AP MLD that received the initial Control frame does not
respond to the most recently received frame from the AP affiliated with the AP MLD that
requires immediate response after a SIFS"

This should not be applicable to sounding because EMLSR STA may not be the first group of STAs triggered by the first BFRP trigger

For sounding sequence, the end of frame exchange does not occur until the EMLSR receives a BFRP trigger or until intra-BSS NAV expires

22/1848r2

J

REJECTED
The EMLSR switch back rules are quite clear - an AP knows that if it does not schedule all the STAs affiliated with non-AP MLDs in EMLSR mode (that it has triggered via BSRP/MU-RTS and included in the NDP Announcement frame) in the first BFRP Trigger frame, the non-AP MLDs that aren’t included in the first BFRP Trigger frame will switch back to listening operation.

 

If we are to go with a NOTE, the note should reflect what is mentioned in the above rejection reason.

 

Also, to clarify to Rakesh, I was not suggesting that the normative rules be converted a NOTE.  The normative rules were to specify AP behavior. The NOTE is to clarify non-AP behavior if AP does not include the non-AP in the first BFRP trigger frame.

 

Thanks,

Gaurang

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