Hi Hanseul,
The text is based on NAVsdyncdelay but there are few updates to it as well. The part you highlight falls under that.
Eventually, we will like to allow at least one RTS frame to be transmitted by the NSTR STA to its AP while the timer is running. Then the CTS received in response (with RA as the STA address) is used by the STA to stop the timer. The text
below allows for that.
Regards,
Dibakar
From: Hanseul Hong <hanseul.hong@xxxxxxxxxxxxxx>
Sent: Monday, January 11, 2021 10:19 AM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] [EXT] Re: [STDS-802-11-TGBE] NSTR blindness issue
Hi Dibakar,
If your text is based on the
NAVSyncDelay operation, I have clarification question.
The NAVSyncDelay is expired if a frame is detected by which it can set its NAV, as you’ve
mentioned.
However, the current spec says,
“When the received frame’s RA is equal to the STA’s own MAC address,
the STA shall not update its NAV.”
Similarly, HE STA performing SST operation
“Shall not respond to Trigger frames addressed to it (see 26.5 (MU
operation) and 26.8.2 (Individual TWT agreements))”
when NAVSyncDelay is applied.
The SP in your document says that the MediumSyncDelay is expired when a STA received a PPDU with a
valid MPDU or a PPDU with a valid TxOP_duration.
I think that the condition to expire the MediumSyncDelay is different from the condition to expire the
NAVSyncDelay.
Is there any intention on that?
Best Regards,
Hanseul Hong
The design is based on NAVSyncDelay operation and follow the same principle of terminating the timer whenever you receive a PPDU or frame that can set the NAV.
Was there a reason why NAVSyncDelay relied on setting the NAV rather than just a valid PHY header ?
-Dibakar
From: Matthew Fischer <00000959766b2ff5-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Monday, January 11, 2021 9:44 AM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] [EXT] Re: [STDS-802-11-TGBE] NSTR blindness issue
I'd really rather see any valid PHY header.
No requirement to find a valid MPDU.
EIFS applies if the PPDU does not yield a valid MPDU.
Hi Dmitry,
I’m fine with your suggestion.
Hopefully, everybody is on the same page on what this note implies.
Best,
Young Hoon
Caution:
EXT Email
Hi Young Hoon,
Thanks for your comment.
Yes, the intention of a “Note” is to show that under some conditions STA is not required to start MediumSync timer and this conditions are
for the future discussion.
At the same time I feel that proposed wording may imply that someone gives STA permission (i.e. allows STA not to start) which may unintentionally
define direction of the future discussion.
How about this:
Note: it is TBD whether STA-2 is required to start the MediumSyncDelay timer if the transmission
of STA-1 is shorter than TBD duration "
Dmitry
Hi Dibakar,
Thanks for revising the SP.
I have one comment.
The main bullet says that STA2 starts a MediumSyncDelay regardless of STA1’s TX duration, but the note says that STA2’s starting of a MediumSyncDelay
is TBD if STA1’s TX duration is shorter than TBD, which is not clear.
I guess your intention here is that while STA2 is supposed to start a MediumSyncDelay regardless of STA1’s TX duration, whether to relax the
MediumSyncDelay condition is for further discussion in the future.
So, how about modifying the note to
Note: it is TBD whether
to allow STA-2 not to starts the MediumSyncDelay timer if the transmission of STA-1 is shorter than TBD duration
Best,
Young Hoon
Caution:
EXT Email
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
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
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
This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual
or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering
the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the
sender, delete it from your computer, and destroy any printed copy of it.
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
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
|