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

Re: [STDS-802-11-TGBE] Discussion on 1825



Thanks Dibakar,

Tentatively added to the MAC conf call of April 11.

All, please review and provide any suggestions/feedback on the resolution of these CIDs before the start of that MAC conf call.

Regards,

Alfred 

On Wed, Mar 30, 2022 at 4:17 PM Das, Dibakar <dibakar.das@xxxxxxxxx> wrote:

Hi Alfred,

 

R3 of the document 1825 is now on server. This version addresses 4 deferred CIDs based on the feedback from members offline. Please add it to the MAC agenda for SPs.

 

Hi all,

 

Please review and let me know if you have further comments.

 

For CID 4836 (NSTR Mobile AP + Medium Sync Recovery Procedure), I received the following suggestion from Kaiying that I added to the text:

A STA shall not start any MediumSyncDelay timer unless it is not one of the following:

-       a non-AP STA affiliated with a non-AP MLD operating on an NSTR link pair or

-       a non-AP STA affiliated with a non-AP MLD operating on an EMLSR link or

-       an AP affiliated with an NSTR mobile AP MLD operating on the non-primary link of an NSTR link pair (#4836).

 

 

(#4727)(#4235)If a (#4836) STA is capable of obtaining a TXOP while the MediumSyncDelay timer has a
nonzero value, it shall perform the following when the timer has a nonzero value:
— If it is a non-AP STA it shall (#4836)  transmit an RTS frame to its associated AP as the initial frame an obtained TXOP
(#4235)(#4416).

If it is an AP it shall transmit an RTS frame to an associated non-AP STA as the initial frame in an obtained TXOP following the NSTR mobile AP multi-link operation defined in 35.3.19 (NSTR mobile AP MLD operation) (#4836).
— Shall not attempt to initiate more than MSD_TXOP_MAX TXOPs since the start of the timer
(#4417).”

 

 

For CID 8184, I made the following change based on Yunbo’s suggestion:

8184

244.50

35.2.1.3.2

"The last PPDU transmission by the AP ended less than aSIFSTime before the end of the allocated time in which case it may transmit SIFS after the end of the last PPDU transmission". It could use a time threshold that larger than aSIFSTime as long as the non-AP STA didn't has enough time to transmit any PPDU within this time threshold.

relex aSIFSTime to "aSIFSTime + T" in which T is shorter than the shortest potential PPDU.

 

Revised.

 

We added the threshold T to correspond to the shortest typical frame transmission which is a CTS transmitted at highest Ctrl MCS.

 

TGbe editor:  Apply the changes tagged with #8184 in this document.

 

 

 

If the EHT AP determines that the transmission of an MU-RTS TXS Trigger frame is successful (#4191,4192, 8319, 5242, 5965), then the AP may transmit a PPDU after the end of the
allocated time and before its TXNAV timer has expired if any of the following conditions are satisfied:
— The medium is determined to be idle by the CS mechanism at the end of the allocated time in which
case it may transmit
(#7809)a PIFS after the end of the allocated time.
— The last PPDU transmission by the AP ended less than aSIFSTime plus 24
µs (#8184) before the end of the allocated
time in which case it may transmit
(#7810)a SIFS after the end of the last PPDU transmission.

Note- The number 24 µs is chosen to correspond to the transmission of the shortest typical frame (CTS) transmitted at highest Ctrl MCS rate of 54 Mbps(#8184).”  

 

 

For CID 7782, 5127 I moved the description on how to use the dot11MSDOFDMEDthreshold to 36.3.20.6.3 based on Yongho’s suggestion:

A(#7782, 5127)  (#4836)STA that is capable of obtaining a TXOP while the
MediumSyncDelay timer has a nonzero value shall use dot11MSDOFDMEDthreshold as specified in
36.3.20.6.3 (CCA sensitivity for occupying the primary 20 MHz channel)  in order to detect a channel busy condition in the primary 20 MHz channel channel  (#7782, 5127)

36.3.20.6 CCA sensitivity

36.3.20.6.3 CCA sensitivity for occupying the primary 20 MHz channel

 

The receiver shall issue a PHY-CCA.indication primitive with the STATUS parameter set to BUSY for any

signal that exceeds the below a threshold equal to 20 dB above the minimum modulation and coding rate sensitivity

(–82 + 20 = –62 dBm) in the primary 20 MHz channel within a period of aCCATime after the signal arrives

at the receiver’s antenna(s):

-              a value specified by dot11MSDOFDMEDthreshold if any MediumSyncDelay timer at that STA has not expired (see 35.3.16.8 (Medium access recovery procedure)) .

-              a value equal to 20 dB above the minimum modulation and coding rate sensitivity

(–82 + 20 = –62 dBm) otherwise (#7782).  “

 

Regards,

Dibakar

 

 

 

 

From: Das, Dibakar <dibakar.das@xxxxxxxxx>
Sent: Thursday, March 24, 2022 1:59 PM
To: Das, Dibakar <dibakar.das@xxxxxxxxx>; STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: RE: [STDS-802-11-TGBE] TGbe Teleconferences [01/05/2022, and 01/06/2022]: Agendas Posted

 

Hi Alfred,

 

Document 1825 is now in the server. I added some other unresolved CIDs to it as well from other sections.

 

 

Regards,

Dibakar

 

From: Das, Dibakar <dibakar.das@xxxxxxxxx>
Sent: Friday, February 4, 2022 2:02 PM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] TGbe Teleconferences [01/05/2022, and 01/06/2022]: Agendas Posted

 

HI Alfred,,

 

Please add the following CR doc to MAC queue:

 

11-21-1825-Remaining CR for 35.3.15.8.1 (14 CIDs)

 

Regards,

Dibakar

 

From: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
Sent: Tuesday, January 4, 2022 1:36 PM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBE] TGbe Teleconferences [01/05/2022, and 01/06/2022]: Agendas Posted

 

Hello all,

 

First of all I would like to wish everybody a Happy New Year!

 

I uploaded an updated version of the agendas, which contains the agenda for the next conference calls, scheduled on Wednesday January 05 (JOINT), 10:00-12:00 ET and Thursday January 06 (MAC), 10:00-12:00 ET. 

 

The agendas can be found here:

https://mentor.ieee.org/802.11/dcn/21/11-21-1775-18-00be-nov-jan-tgbe-teleconference-agenda.docx

 

Note for CR documents: Please update the baseline to TGbe D1.31 for the CR documents.

 

DIAL IN DETAILS FOR WEDNESDAY:

Join the JOINT meeting here: https://ieeesa.webex.com/ieeesa/j.php?MTID=m47e46089d108a8ef448b7a3a11976593

Meeting number: 233 886 75218 Meeting password: wireless (94735377 from phones and video systems)

 

DIAL IN DETAILS FOR THURSDAY:

Join the MAC meeting here: https://ieeesa.webex.com/ieeesa/j.php?MTID=mff9e3bd94518bedcc608845d389fdd3e

Meeting number: 234 227 52561 Meeting password: wireless (94735377 from phones and video systems)

 

Let me know if you have any questions and/or suggestions.

 

Best Regards,

 

Alfred

 

--

Alfred Asterjadhi, PhD

IEEE802.11 TGbe Chair,

Qualcomm Technologies Inc.

Cell #:    +1 858 263 9445

Office #: +1 858 658 5302


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


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



--
Alfred Asterjadhi, PhD
IEEE802.11 TGbe Chair,
Qualcomm Technologies Inc.
asterjadhi@xxxxxxxxx
aasterja@xxxxxxxxxxxxxxxx
Cell #:    +1 858 263 9445
Office #: +1 858 658 5302

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