Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Matthew, Thank you for sharing your PDT document. I have a few concerns and would like to share my comments below in-line. Best regards, Juseong Moon. 37.10.2 Switching to the NPCA channel (#1505) (…) 2) All of the following conditions are true: a) A sequence of three PPDUs, separated by aSIFSTime, is identified on the BSS primary channel, comprising an initial Control frame, an initial response frame and a third PPDU following the initial response frame b) The STA received at least the first PPDU containing the initial Control frame and the PHY-RXSTART.indication and/or the PHY-RXEARLYSIG.indication of the third PPDU (#1513) (#2649) (#2678) (#2679) (#3047) (#3048) (#3416) c) An indication that a valid TXOP was obtained on the BSS primary channel, as verified by the receipt of a PHY-RXEARLYSIG.indication or PHYRXSTART.indication primitive corresponding to the third PPDU that occurs during a time window that: i) has a duration that is equal to NPCA_START_TIMEOUT which is aSIFSTime + (2 x aSlotTime) + aRxPHYStartDelay ii) begins at aSIFSTime + ICR_Timeout after the MAC receives a PHY-RXEND.indication primitive corresponding to the first PPDU, where ICR_Timeout is equal to: (1) The length (in usec) of the expected CTS if the initial Control frame is an RTS or an MU-RTS Trigger frame (2) The value of the UL Length field of the Common Info field if the initial Control frame is a BSRP Trigger frame or a BSRP NTB Trigger frame (#2146) (#2433) (#2649) Juseong: The value of the UL Length field does not directly represent the time duration of the ICR frame. It is derived from TXTIME, which indicates the actual transmission time duration from the transmitter of the ICR. According to IEEE 802.11-2024, subclause 26.5.2.2.4, Allowed settings of the Trigger frame fields and TRS Control subfield, “The AP shall set the UL Length subfield of a Trigger frame to the value given by Equation (27-11) with m = 2.” Therefore, when using the UL Length field value for timeout calculation, it must first be converted using Equation (27-11) of IEEE 802.11-2024 or an equivalent method. I suggest a modified text as follows: The TXTIME, derived from the value of the UL Length field of the Common Info field if the initial Control frame is a BSRP Trigger frame or a BSRP NTB Trigger frame. NOTE: The TXTIME can be derived from Equation (27-11), with m = 2. d) At least one of the three PPDUs in the sequence of PPDUs is classified by the STA as an inter-BSS PPDU following the procedure defined in 37.4 (Intra-BSS and inter-BSS PPDU classification for UHR STA) (#1056) (#2146) (#3593) (#3049) e) At least one of the following conditions is true: i) The NPCA AP corresponding to the BSS of which the STA is a member has enabled PHYLEN NPCA only and the value of the MAC variable NPCA_PPDU_REM_DUR derived from the received third PPDU of the sequence of PPDUs is greater than the value indicated in the most recently received or transmitted NPCA Minimum Duration Threshold field corresponding to its BSS (#1056) (#2146) (#3593) (#3050) ii) If the NPCA AP corresponding to the BSS of which the STA is a member has enabled MOPLEN NPCA in addition to PHYLEN NPCA and the value of the MAC variable NPCA_CFRAME_TXOP_REM_DUR derived from the received first PPDU (containing the initial Control frame of the control frame exchange) of the sequence of PPDUs is greater than the value indicated in the most recently received or transmitted NPCA Minimum Duration Threshold field corresponding to its associated BSS (#1056) (#2146) (#3593) f) (#1057) (#1217) (#1218) (#2146)The bandwidth of the third PPDU is determined by the STA to be 20, 40, 80, 160 or 320 MHz based on the Bandwidth field in the PHY preamble of the PPDU not overlap with the NPCA primary channel and the channel occupied by the PPDU does not overlap with the NPCA primary channel..(#3045) (#3046) (#3016) g) If the STA maintains an intra-BSS NAV, it is zero; If the STA does not maintain an intra-BSS NAV, the basic NAV is zero. (#833) (#2148) Juseong: If the NPCA STA has received at least a valid ICF and a subsequent frame (the ICR or the third frame following the ICR) during the NAVTimeout, it shall set the basic NAV. This is the baseline NAV rule, and the basic NAV will not reset until the NPCA STA receives a CF-End frame. Therefore, under the current PDT 25/0936r12, the NPCA STA cannot switch to the NPCA primary channel. The previous PDT revisions prior to r12 also have a similar issue. At present, I understand that a separate NAV for the NPCA primary channel is not defined. As a matter of common sense, the NAV is considered to be shared between the BSS primary channel and the NPCA primary channel. In this situation, once the NPCA STA switches to the NPCA primary channel based on condition 2) (ICF–ICR–third PPDU), it definitely sets the NAV and therefore cannot transmit on the NPCA primary channel at all. To resolve this issue, I have prepared a CR document, 25/1326r0. Please refer to CID #1823.
To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1 |