| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Dibakar, Thanks for incorporating my suggestion. Best, Jason 发件人: Das, Dibakar [mailto:dibakar.das@xxxxxxxxx]
Hi Jason, all, We think there will be discussion on this part eventually. So, we can either have this text explicitly now or postpone that for a later discussion. We can tentatively add this and see if there are 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 From: Das, Dibakar <dibakar.das@xxxxxxxxx>
Hi Jason, Thanks for the suggestion. Lets see if others have an opinion on it.
Regards, Dibakar From: Guoyuchen (Jason Yuchen Guo) <guoyuchen@xxxxxxxxxx>
Hi Dibakar, After reading the contents of your latest SP, I think most of the contents look good to me, the only thing you miss the short frame case. E.g., if the transmission of STA-1 is a very short frame (e.g., a ACK/BA
frame as a response to the data frame, or a CTS frame as a response to the RTS frame), there’s no need for the STA-2 to start the blindness recovery procedure since the probability for STA-2 to miss a frame during the short transmission of STA-1 is very low. Hence, I would like to suggest a minor change to the first paragraph of your SP text as follows:
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
which is 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: Would you please let me know your opinion on this? Best, Jason 发件人: Das, Dibakar [mailto:dibakar.das@xxxxxxxxx]
Hi Alfred, Based on some offline discussions among the involved parties, we see value in running the SPs in 1312 and 1009/613 in the same call as they have some dependency. As such assuming 613 and 992/903 are going to be scheduled for next Thursday
call successively, can we please revise the agenda as follows:
So, the requested order is following:
Regards, Dibakar From: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
Hello all, I uploaded an updated version of the agendas, which contains the agenda for the next conference calls, scheduled on Monday, December 14 (MAC/PHY), 19:00-22:00
ET and Wednesday, December 16 (JOINT), 10:00-12:00 ET. The agendas can be found here: https://mentor.ieee.org/802.11/dcn/20/11-20-1615-28-00be-nov-jan-tgbe-teleconference-agendas.docx Important notice for TGbe Joint queue: We are planning to go over deferred SPs on Sounding and Trigger frame format. If you have any SPs that are
deferred on these two topics and are not already listed in the agendas, please let me know. DIAL IN DETAILS FOR MONDAY: Join the Webex MAC meeting here:
https://ieeesa.webex.com/ieeesa/j.php?MTID=me66c9d491680ea511d3d804205ba027d Meeting number: 173 288 9876 Meeting password: wireless (94735377 from phones and video systems) Join the Webex PHY meeting here:
https://ieeesa.webex.com/ieeesa/j.php?MTID=m1243464a52409f62f34e4b746394f06b Meeting number: 173 218 7289 Meeting password: wireless (94735377 from phones and video systems) DIAL IN DETAILS FOR WEDNESDAY: Join the Webex JOINT meeting here:
https://ieeesa.webex.com/ieeesa/j.php?MTID=m54512bd5d8bc99550e1d3c6596328532 Meeting number: 173 358 0755 Meeting password: wireless (94735377 from phones and video systems) Please let me know if you have any questions and/or clarifications. 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 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 |