Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hello all I presented this contribution 22/1768 in Bangkok meeting. AAR in current text is used to ask for AP’s help to address the issue of blindness. Because
blindness about NSTR was discussed first, then current text only mentions NSTR. However, EMLSR meets the same blindness issue, the corresponding description was added later as following and it is in the same subclause with AAR (35.3.16.8 Medium access recovery
procedure) When a non-AP MLD is operating in the EMLSR mode, a (#12242)non-AP STA affiliated with a non-AP MLD that is operating on one of the EMLSR links is considered to have lost medium synchronization
if it is not able to perform CCA during frame exchanges that includes the link switch delays between an AP affiliated with an AP MLD and one of the other STAs operating on the other EMLSR links, which are affiliated with the same non-AP MLD. The STA that has
lost medium synchronization shall start a MediumSyncDelay timer (#10422)and begin counting down immediately after returning to the listening operation if the duration of the loss of medium synchronization is longer than aMediumSyncThreshold; otherwise, the
STA may not start the MediumSyncDelay timer. EMLMR also meets the same issue, this part is now drafted by liwen 22/1505. It is quite straightforward to add EMLSR and EMLMR to AAR. I received
support from the below commenters. Gaurang asked for defer, Shubho from BRCM help debate. Because of limited time, we can’t understand Garuang’s argument.
@Garugang, could you help raise your specific
technical concern here?
Best wishes Ming Gan 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 |