| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Xiaogang, Thank you for presenting 11-21/1229r2 in the last week’s Joint meeting. It is an interesting topic. Regarding CID 5770, I am still confused by the motivation of adding TB Sounding Feedback Rate Limit subfield in the EHT PHY Capabilities element. a.
I am not sure why the STA has to indicate its TB Sounding Feedback Rate Limit capability to the AP
i. For TB-based sounding, non-AP STAs can start process CSI feedback after NDP frame. Other solutions are available for AP to provide extra processing time for non-AP STAs. For example,
in 11ax, there is a Padding field in Trigger frame (Figure 9-64a—Trigger frame format and 26.5.2.2.3 Padding for a triggering frame in 802.11ax D8.0) ) and User Info field with AID12 4095 as padding field (Table 9-29h—AID12 subfield encoding). Both of these
can be used to give the non-AP STA more processing time.
ii. For non-TB based sounding, STA can choose the MCS/Nss to transmit the feedback. Note the STA needs to start processing CSI feedback and responding right after NDP within SIFS
time in this case. b.
There are only two reserved bits remained in EHT PHY Capabilities element. Why it has to use the
precious bit in EHT PHY Capabilities element to indicate the TB Sounding Feedback Rate Limit?
i. There are 11 reserved bits in EHT MAC Capabilities element. Is it better to use the reserved bit in EHT MAC Capabilities element if this capability has to be indicated to the
AP? 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 |