Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

[STDS-802-11-TGBE] 答复: CR document for EHT PSR CIDs

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]
发送时间: 2022年10月29日 2:08
收件人: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
主题: Re: [STDS-802-11-TGBE] CR document for EHT PSR CIDs

 

Hi Ross,

 

The previous description is not accurate. There are two main reasons:

 

  1. To obtain the Spatial Reuse values does not depend on what type  of TB-PPDU follows but whether Special User Info field exists in the Trigger frame or not.
  2. The OBSS EHT STA may not be able to hear TB-PPDU. That is why “if an HE TB PPDU” or “if an EHT TB PPDU” in the current 802.11be specs is not valid for those OBSS EHT STAs that cannot hear TB PPDU.

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>
Sent: Tuesday, October 25, 2022 9:31 PM
To: Zinan Lin <Zinan.Lin@xxxxxxxxxxxxxxxx>; STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: 答复: CR document for EHT PSR CIDs

 

 

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]
发送时间: 2022年10月26日 9:17
收件人: Yujian (Ross Yu) <ross.yujian@xxxxxxxxxx>; STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
主题: RE: CR document for EHT PSR CIDs

 

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>
Sent: Sunday, October 23, 2022 11:45 PM
To: Zinan Lin <Zinan.Lin@xxxxxxxxxxxxxxxx>; youhank@xxxxxxxxxxxxxxxx; LALAM Massinissa <massinissa.lalam@xxxxxxxxxxxx>; Leonardo Lanante <llanante@xxxxxxxxxx>; Eunsung Park <esung.park@xxxxxxx>; greg.ko@xxxxxxxxxxxxxx
Cc: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>; Rui Yang <Rui.Yang@xxxxxxxxxxxxxxxx>; Hanqing Lou <Hanqing.Lou@xxxxxxxxxxxxxxxx>; Ganming(Ming Gan) <ming.gan@xxxxxxxxxx>; humengshi <humengshi@xxxxxxxxxx>
Subject: 答复: CR document for EHT PSR CIDs

 

 

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]
发送时间: 2022年10月15日 3:20
收件人: youhank@xxxxxxxxxxxxxxxx; Yujian (Ross Yu) <ross.yujian@xxxxxxxxxx>; LALAM Massinissa <massinissa.lalam@xxxxxxxxxxxx>; Leonardo Lanante <llanante@xxxxxxxxxx>; Eunsung Park <esung.park@xxxxxxx>; greg.ko@xxxxxxxxxxxxxx
抄送: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>; Rui Yang <Rui.Yang@xxxxxxxxxxxxxxxx>; Hanqing Lou <Hanqing.Lou@xxxxxxxxxxxxxxxx>
主题: CR document for EHT PSR CIDs

 

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