Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Aiguo, Thanks for your comments/questions. Section 34.3.18.3 Adjacent channel rejection is based on 11ax specification.
It seems your questions require technical discussion.
If you have proposed changes, it is better to submit technical contribution so that we can discuss and make change accordingly. Following is my opinion. Question #1. For me, W is PPDU BW.
But I don’t think we are considering mixed (adjacent and non-adjacent) interference scenario as you drew in below. Question #2. If interference is not aligned (in OFDM symbol), then different MCS interferences source maybe doesn’t matter.
Wook Bong Lee From: Aiguo Yan [mailto:aiguo.yan@xxxxxxxx]
Wookbong and other TTTs Question #1:
I checked all documents/specs (old and new). It seems
“W MHz” could have
room for alternate interpretation. Adjacent channel rejection for W MHz (where W is 20, 40, 80, 160 or 320) shall be measured by setting the desired signal’s strength 3 dB above the rate-dependent sensitivity specified in
Table xx-y1 (Receiver minimum input level sensitivity) and raising the power of the interfering signal of
W MHz bandwidth until 10% PER is caused for a PSDU length of 2048 octets for BPSK modulation with DCM or 4096 octets for all other modulations. The difference in power between the signals in the interfering channel and the desired channel is the corresponding
adjacent channel rejection. The center frequency of the adjacent channel shall be placed
W MHz away from the center frequency of the desired signal. One interpretation is that
“W MHz” is the PPDU BW, not the STA capability (use only continuous BW as an example at this moment).
Therefore, following test case is valid for a
320MHz capable STA
with reception of a 80MHz PPDU Another interpretation is just the opposite, i.e.,
“W MHz” is the STA capability. So interference scenario of above is not valid. Question #2:
All 802.11 specs also didn’t say explicitly what MCS should be used for interference signal. An easy choice would be using the same MCS as the wanted signal does. I don’t know whether there already is an unspoken agreement from the past. Even if yes, it is still better to make this kind of agreement explicit. Thanks. Aiguo From: Wook Bong Lee <wookbong.lee@xxxxxxxxxxx>
Hi Edward, Thanks for comment. As I mentioned in the abstract of the contribution, I didn’t include 80+80/160+160 MHz yet as there is some related discussion in PHY adhoc. At this moment, maybe I can put those in PDTs with TBD. I will update all PDTs and upload it soon. Best regards, Wook Bong Lee From: Edward Au [mailto:edward.ks.au@xxxxxxxxx]
Hello Wook Bong , In Table xx-y1, you have an entry "Minimum sensitivity (160 MHz PPDU) (dBm)". In clause 21 and clause 27, this entry is "Minimum sensitivity (160 MHz or 80+80 MHz PPDU) (dBm)".
I may miss the discussion in PHY ad-hoc but may I know whether we shall update this entry in your table to 160 MHz or 80 + 80 MHz too? A similar quarion for your 320 MHz entry too. Thanks and Regards, On Thu, Aug 27, 2020 at 4:49 PM Wook Bong Lee <wookbong.lee@xxxxxxxxxxx> wrote:
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 |