Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hello Zinan Please refer to the following text An HE STA that identifies an PSR opportunity may choose to not perform NAV update operations normally executed based on the receipt of the RXVECTOR parameter TXOP_DURATION and the Trigger frame Duration field.
(#2245)An OBSS STA, shown as STAOBSS-A
in Figure 26-13 (PSRR PPDU spatial reuse(#2245)(11ax)), that identifies an PSR opportunity to transmit a PSRT PPDU to another OBSS STA, shown as STAOBSS-B
in the same figure, may issue a PHY-CCARESET.request to ignore the associated HE TB PPDU(s) that are triggered by the Trigger frame of the PSRR PPDU and that occur within aSIFSTime + aRxPHYStartDelay + 2
× aSlotTime of the end of the last symbol on the air of the triggering PPDU (which is also the PSRR PPDU),
provided that the value of the RXVECTOR parameter BSS_COLOR of the HE TB PPDU matches the BSS color of the PSRR PPDU.
An OBSS STA that identifies an PSR opportunity shall not transmit an PSRT PPDU that terminates beyond the PPDU duration of the HE TB PPDU that is triggered by the Trigger frame of the PSRR PPDU. Best wishes Ming Gan 发件人: Zinan Lin [mailto:Zinan.Lin@xxxxxxxxxxxxxxxx]
Hi Ming, Thanks for your comments. Could you please show the paragraph on page 3939 of P802.11REVme_D2.0 that indicates the highlighted part in your email? Thanks, Zinan From: Ganming(Ming Gan) <ming.gan@xxxxxxxxxx>
Hello Zinan Regarding the motivation (The OBSS EHT STA may not be able to hear TB-PPDU) you mentioned
below, it is not correct. In Draft P802.11REVme_D2.0, page 3939.
The PSRT PPDU can only be transmitted if the BSS color of the received HE TB PPDU matched the BSS color of the trigger frame. Hence, the original description is correct and doesn't need further modification. Best wishes Ming Gan 发件人: Zinan Lin [mailto:000019c80da359b9-dmarc-request@xxxxxxxxxxxxxxxxx]
Hi Ross, The previous description is not accurate. There are two main reasons:
a) The value of the UL Spatial Reuse field in the Common Info field of the Trigger frame of the PSRR PPDU
if an HE TB PPDU follows the PSRR PPDU, or b) Special User Info field of the Trigger frame of the PSRR PPDU
if an EHT TB PPDU follows the PSRR PPDU, Therefore, I would suggest the following changes:
a)
The value of the UL Spatial Reuse subfields in the Common Info field of the Trigger frame of the PSRR PPDU
if the Special User Info field exists in the Trigger frame of the PSRR PPDU (following Table 9-45c (Valid combinations of B54 and B55 in the Common Info, B39 in the User Info field, and solicited TB PPDU format))
b)
The value of the EHT Spatial Reuse n subfield, 1<=n<=2, in the Special User Info field of the Trigger frame of the PSRR PPDU
if the Special User Info field does not exist in the Trigger frame of the PSRR PPDU (following Table 9-45c (Valid combinations of B54 and B55 in the Common Info, B39 in the User Info field, and solicited TB PPDU format)) Please let me know if you have any further questions. Thanks, Zinan From: Yujian (Ross Yu) <ross.yujian@xxxxxxxxxx>
Hi Zinan, I think the previous description is good enough. Regarding how to differentiate HE/EHT TB PPDU, there is already description in clause 9, the table you referred. There is no need
to mention it here. Moreover, relying on B55 is not a complete solution. regards 于健 Ross Jian Yu Huawei Technologies 发件人: Zinan Lin [mailto:Zinan.Lin@xxxxxxxxxxxxxxxx]
Hi Ross, Thanks for your feedback. As indicated the current specs (11be D2.2,
35.10.3.1), there are 3 options for the OBSS STA to obtain PSR values (as indicated below). The first two options (a and b) are to obtain PSR values from the Trigger frame if the OBSS STA can hear from the Trigger frame; the last
option is to obtain PSR values from the TB PPDU. The existing explanation structure is clear.
However, as I indicated in the discussion, the OBSS STA may not be able to hear the TB PPDU. The first two options are focused on where the PSR value can obtained from the Trigger frame. That is why it is more straightforward
to use the value of Common Info field of the Trigger frame as a criterion to determine where PSR can be obtained from the Trigger frame and add the corresponding reference. Could you please elaborate more about how to add the reference here? Thanks, Zinan From: Yujian (Ross Yu) <ross.yujian@xxxxxxxxxx>
Hi Zinan, Thanks for the sharing and good work. For CID 11675, I suggest to not touch how to differentiate HE/EHT TB PPDU as there is already detailed description in other
subclauses. You may add references if you like.
regards
于健 Ross Jian Yu
Huawei Technologies 发件人: Zinan Lin [mailto:Zinan.Lin@xxxxxxxxxxxxxxxx]
Dear all, Attached please find the CR document for CIDs (11674, 11675, 12010,12066, 12067, 12363, 14010). Majority of CIDs are related to EHT PSR operation.
Could you please take a look at the document? Please let me know your comments by next Thursday (10/20). I plan to upload the document before next Joint meeting
( 10/26). Thank you for your help in advance! Best regards, Zinan 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 |