| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hello Dibakar Thanks for preparing this sp. In my mind, it is a little bit hurry. This sp changes the exiting Channel Access rule, allowing EDCA channel access in case of non-zero NAV, and may
violate regulation like PIFS access for multi-link. I think we should consider some schemes which follow the existing EDCA rule first and then consider those fancy schemes. Moreover, there are lots of TBD in this sp, like exception, ED threshold, inter/intra
NAV, the number of RTS/TXOP, RTS rule and so on. It seems to need more discussion. By the way, do you consider this in r2? Best wishes, Ming Gan
发件人: Das, Dibakar [mailto:dibakar.das@xxxxxxxxx]
Hi all, We have made revisions to the submission 1009 based on the feedback received offline and uploaded r3: https://mentor.ieee.org/802.11/dcn/20/11-20-1009-03-00be-multi-link-hidden-terminal-followup.pptx Summary of the discussion: The basic idea is a STA starts a timer following a blindness event so as to avoid collision with a hidden transmission. During this time, the STA (1) can still attempt to initiate a TXOP by transmitting limited number
of RTS frames so as to regain some channel access benefits and (2) in managed BSS scenarios use a lower ED threshold that is configured by AP. During offline discussion Yunbo and Sharan pointed out that further discussion may be needed for the case when (a)
the STA detects medium to be busy right after blindness event ends or (b) the NAV is non-zero at the end of the blindness event. As such we revised the text so we could discuss those points in later contributions from others. The revised SP reads as below with the changes highlighted in green. Let me know if you have concerns.:
•
Do you support that 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 the transmission, unless
•
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
•
If the channel was busy immediately after the blind period, additional TBD rules to use RTS may apply.
Note:
•
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 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 |