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

Re: [STDS-802-11-TGBE] NSTR blindness issue

Hi Zhiqiang,

 

In 11ax one can set NAV from the Rxvector parameter TXOP_DURATION. The intention here was to remind people of that.

 

Maybe we can clarify using similar language as in 11ax:

“a received PPDU whose corresponding RXVECTOR parameter TXOP_DURATION is not UNSPECIFIED”

 

Regards,

Dibakar

 

From: han.zhiqiang1@xxxxxxxxxx <han.zhiqiang1@xxxxxxxxxx>
Sent: Wednesday, January 6, 2021 11:00 PM
To: Das, Dibakar <dibakar.das@xxxxxxxxx>
Cc: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re:[STDS-802-11-TGBE] NSTR blindness issue

 

Hi, Dibakar,

TxOP_duration should be changed to "TXOP", TxOP_duration is a parameter in TXVECTOR. 

Thanks.

 

Best Regards,

Zhiqiang Han

原始邮件

发件人：Das,Dibakar

日 期 ：2021年01月07日 08:13

主 题 ：Re: [STDS-802-11-TGBE] NSTR blindness issue

Hi,

 

Based on the feedback received during last call on this topic, we simplified the previous SP to focus just on the basic timer usage scenarios. Please review and let me know if you have any comments.

 

Do you agree to add the following to 11be SFD R1:  if during a transmission of a STA (STA-1) of a non-STR non-AP MLD, another STA (STA-2) of the same MLD cannot detect its medium state when required (due to STA-1’s UL transmission interference), STA-2 shall start a MediumSyncDelay timer at the end of STA-1's transmission, unless the STA-2 ended a transmission at the same time:

    • the MediumSyncDelay timer expires after a duration value that is either assigned by AP or a default value in spec or if at least either of the following events happens:
      • any received PPDU with a valid MPDU
      • a received PPDU with a valid TxOP_duration

                       whichever happens first.

    • While the timer is running, STA-2 shall not initiate a TXOP except under TBD conditions.

Note: it is TBD whether STA-2 starts the MediumSyncDelay timer if the transmission of STA-1 is shorter than TBD duration

 

 

 

Regards,

Dibakar

 

From: Das, Dibakar <dibakar.das@xxxxxxxxx>
Sent: Tuesday, December 15, 2020 7:58 PM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBE] NSTR blindness issue

 

Hi all,

 

We worked offline and tried to converge on a SP text for blindness. The new version below captures the main aspects of both 1009r4 and 613r2. The highlighted text are the changes relative to r4. Please review and let us know of any comments.

 

Do you agree to add the following to 11be SFD R1:  if during a transmission of a STA (STA-1) of a non-STR non-AP MLD longer than a TBD duration, another STA (STA-2) of the same MLD cannot detect its medium state when required (due to STA-1’s UL transmission interference), STA-2 shall start a MediumSyncDelay timer at the end of STA-1's transmission, unless the STA-2 ended a transmission at the same time:

    • the MediumSyncDelay timer expires after a duration value that is either assigned by AP or specified in spec or if at least either of the following events happens:
      • any received PPDU with a valid MPDU
      • a received PPDU with a valid TxOP_duration

                  whichever happens first

    • while the MediumSyncDelay timer is running the STA is only allowed to attempt to initiate up to number of TxOPs assigned by the AP (at least 1) and shall attempt to initiate that TxOP with the transmission of an RTS frame using regular EDCA backoff using baseline CCA but a TBD ED threshold value
      • The TBD ED threshold value has a default value specified in the spec (e.g., -62dBm) but can also be assigned by the AP MLD within a limited range such as between -82dBm and -62dBm
    • If the channel was busy immediately after the blind period, additional TBD rules to use RTS may apply.
    • If  the PPDU transmitted by STA 1 carries a signal (Signaling is TBD) which indicates that STA 2  intends to send UL frame after transmission from STA-1 then another AP (AP 2) of the same AP MLD should send a Trigger frame to STA-2 soliciting UL PPDU or a modified MU-RTS trigger that allocates time for STA-2 if the channel is idle, MediumSyncDelay timer is not 0 and if the AP2 does not have frame exchange already scheduled with another STA

Note:

    • If either the intra-BSS NAV or the inter-BSS NAV is non-zero in STA-2 at the end of transmission of STA-1, STA-2 does not transmit any PPDU using EDCA until the NAV expires.
    • If either the intra-BSS NAV or the inter-BSS NAV is non-zero in STA-2 at the end of transmission of STA-1, there could be further TBD conditions and requirements to expire the MediumSyncDelay timer.

 

 

Regards,

Dibakar

 

 

 

 

 

 

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