| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Zhiqiang, Thanks for the comment. I mostly agree with you as this timer duration value should follow the same principle as other timers like MU-EDCA timer.
However, for now I think since we are trying to get the group’s opinion on the main proposal on channel access recovery, I prefer if we go ahead with the SP. We can then refine the PDT at a later stage: as part of remaining CRs on this
topic or as CR for D1.0. Regards, Dibakar From: han.zhiqiang1@xxxxxxxxxx <han.zhiqiang1@xxxxxxxxxx>
Hi Dibakar Thanks for accepting my comemts, I have a further comment: The MediumSyncDelay timer is a single timer, shared by all EDCAFs within a non-AP STA, which is initializedto
aPPDUMaxTime defined in Table 27-54 (HE PHY characteristics). I think this procedure happened after the device powers on. The STA shall update the timer duration value with the one contained in
theMedium Synchronization Duration field of theBasic variant MLelement
in the most recent frame received from its associated AP. This procedure describes how to update the MediumSyncDelay. But based on the following text, the timer will reset to zero. In addition,the timer resets to zero when any of the following events occur: — The STA receives a PPDU with a valid MPDU. — The STA receives a PPDU whose corresponding RXVECTOR parameter TXOP_DURATION is not UNSPECIFIED. For example, non-AP MLD hase two affilicated STAs(STA1 and STA2). Based on the above procedure, STA1 and STA2 shall initiated to aPPDUMaxTime or
update based on beacon or other frame. STA1 and STA2 will reset to zero because STA1 and STA2 receive a PPDU with a valid MPDU. When STA2 wants to transmit at the
end of the STA1 transmission event that caused loss of medium synchronization. so STA2 should do Medium synchronization recovery procedure, but the MediumSyncDelay
timer is zero or here STA2 need to set the timer again, but based on which parameter? the Medium Synchronization Duration field? where to store the value indicated
by the Medium Synchronization Duration field? So I think we need a new dot11 parameter to save the value indicated by the Medium
Synchronization Duration field of the Basic variant MLelement, and the dot11 parameter initialized to aPPDUMaxTime,
or update based on beacon or other frame.
When STA2 wants to transmit at the end of the STA1 transmission event that caused loss of medium synchronization. STA2 shall set the timer based on the
new dot11 parameter. That's my understanding, If I have misunderstanding, please let my know, thanks very much. Best Regards,
Zhiqiang Han
原始邮件 发件人：Das,Dibakar 日
期
：2021年04月21日
23:45 主
题
：Re: [STDS-802-11-TGBE] Requesting agenda time for defered SP Hi all, I updated the PDT on blindness to
r9. Please review and send any feedback. Regards, Dibakar From: Das, Dibakar <dibakar.das@xxxxxxxxx>
Hi Alfred, Can you please add the deferred SPs for the following contributions to the agenda: 11-21-221 and 11-21-222 ? 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 |