Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
The EHT Compressed Beamforming Report information contains the channel matrix elements indexed, first, by matrix angles in order shown in Table 9-71 (Order of angles in the compressed beamforming feedback matrix when used in a non-S1G band), and second, by data and pilot subcarrier index from the lowest frequency to the highest frequency for all the subcarrier indices that need to be fed back based on the Partial BW Info subfield and determined (in case of MRU the lowest frequency stands for the lowest frequency of first RU and the highest frequency stands for the highest frequency of the last RU) using as shown in Table 9-127b (Subcarrier indices when not all bits in Partial BW Info subfield corresponding to the 80 MHz frequency subblock are set to 1), Table 9-127c (Subcarrier indices when all bits in Partial BW Info subfield corresponding to the 80 MHz frequency subblock are set to 1 for Ng = 4), and Table 9-127d (Subcarrier indices when all bits in Partial BW Info subfield corresponding to the 80 MHz frequency subblock are set to 1 for Ng = 16).
Hi Jinyoung and Bin,
I totally agree with Bin’s philosophy and suggestion. However, “determined” seems a bit redundant because it already has “based on the Partial BW Info subfield ”. So I am wondering if we can remove “and determined”. Or can we say
“for all the subcarrier indices that need to be fed back based on the Partial BW Info subfield and determined by
as shown in”?
Thanks,
Zinan
The EHT Compressed Beamforming Report information contains the channel matrix elements indexed, first, by matrix angles in order shown in Table 9-71 (Order of angles in the compressed beamforming feedback matrix when used in a non-S1G band), and second, by data and pilot subcarrier index from the lowest frequency to the highest frequency for all the subcarrier indices that need to be fed back based on the Partial BW Info subfield and determined as shown in Table 9-127b (Subcarrier indices when not all bits in Partial BW Info subfield corresponding to the 80 MHz frequency subblock are set to 1), Table 9-127c (Subcarrier indices when all bits in Partial BW Info subfield corresponding to the 80 MHz frequency subblock are set to 1 for Ng = 4), and Table 9-127d (Subcarrier indices when all bits in Partial BW Info subfield corresponding to the 80 MHz frequency subblock are set to 1 for Ng = 16).
From: Jinyoung Chun <jiny.chun@xxxxxxx>
Sent: Tuesday, March 14, 2023 4:14 PM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] Discussion on CID 17494
Hi Bin,
Thank you for your suggestion, and it looks clearer to me.
If somebody has any opinion, please let me know.
Best regards,
Jinyoung
From: Bin Tian [mailto:btian@xxxxxxxxxxxxxxxx]
Sent: Wednesday, March 15, 2023 4:10 AM
To: jiny.chun@xxxxxxx; STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: RE: [STDS-802-11-TGBE] Discussion on CID 17494
Hi Jinyoung
The term MRU brings more confusion since the feedback tone indices are solely determined based on a partial BW bitmap. Among all these tones need to be fed back, we just order them based on the frequency from low to high. How about using the following text
The EHT Compressed Beamforming Report information contains the channel matrix elements indexed, first, by matrix angles in order shown in Table 9-71 (Order of angles in the compressed beamforming feedback matrix when used in a non-S1G band), and second, by data and pilot subcarrier index from the lowest frequency to the highest frequency for all the subcarrier indices that need to be fed back based on the Partial BW Info subfield and determined
(in case of MRU the lowest frequency stands for the lowest frequency of first RU and the highest frequency stands for the highest frequency of the last RU)as shown in Table 9-127b (Subcarrier indices when not all bits in Partial BW Info subfield corresponding to the 80 MHz frequency subblock are set to 1), Table 9-127c (Subcarrier indices when all bits in Partial BW Info subfield corresponding to the 80 MHz frequency subblock are set to 1 for Ng = 4), and Table 9-127d (Subcarrier indices when all bits in Partial BW Info subfield corresponding to the 80 MHz frequency subblock are set to 1 for Ng = 16).Thanks,
Bin
From: Jinyoung Chun <jiny.chun@xxxxxxx>
Sent: Tuesday, March 14, 2023 11:47 AM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBE] Discussion on CID 17494
WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
Hi, All,
I’ve presented CRs on 9.4.1.71 in Joint CC and the CID was deferred for more discussion.
Please let me know your opinion about the CID.
17494
Brian Hart
T
211.65
"(in case of MRU the lowest frequency stands for the lowest frequency of first RU and the highest frequency stands for the highest frequency of the last RU) " is actually very confusing. The Tables do not shed any light either.
If the first RU is lowest in freq and the last RU is highest in freq then this explanation unnecessarily and confusinglyu introduces RU numbering in an MRU - just have "(including for MRUs, noting that tones between RUs in an MRU are not fed back)". If the first/last RU is not necessarily lowest/highest in freq then, a) provide a xref to where this is are explained and b) rewrite this: "... second by the numbering of each RU in the MRU and third by data and pilot subcarrier index in each RU from the lowest freq to the highest freq ..."
Revised
Agree with the commenter, and the first suggestion seems good because the first RU is lowest in freq and the last RU is highest in freq (refer Table 36-5 (Data and pilot subcarrier indices for RUs).
To editor: Change the text in P211L65-P212L1
“(in case of MRU the lowest frequency stands for the lowest frequency of first RU and the highest frequency stands for the highest frequency of the last RU)”
to
“(including for MRUs, noting that tones between RUs in an MRU are not fed back)”
Best regards,
Jinyoung
From: Jinyoung Chun [mailto:jiny.chun@xxxxxxx]
Sent: Tuesday, March 14, 2023 8:45 PM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] [EXT] [STDS-802-11-TGBE] Teleconference Agendas For Next Week: Uploaded
Hi Alfred,
Please add the following 3 CRs in the Queue.
- 11-23-0359-00-00be-lb271-cr-on-36.3.12.10 (PHY)
- 11-23-0365-00-00be-lb271-cr-on-9.4.1.70 (Joint)
- 11-23-0367-00-00be-lb271-cr-on-9.4.1.71 (Joint)
Best regards,
Jinyoung
From: Yan(MSI) Zhang [mailto:yan.zhang_5@xxxxxxx]
Sent: Tuesday, March 14, 2023 12:34 AM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] [EXT] [STDS-802-11-TGBE] Teleconference Agendas For Next Week: Uploaded
Hi Alfred,
Could you please add the following 2 CR documents to 11be PHY queue?
23/0422r0 11be lb271 CR for Clause 36.3.11 Mathematical description of signals Yan Zhang (NXP Semiconductor)
23/0427r0 11be lb271 CR for clause 36.3.13.3 Coding Yan Zhang (NXP Semiconductor)
Thanks
Yan
From: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
Sent: Saturday, March 4, 2023 7:36 AM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: [EXT] [STDS-802-11-TGBE] Teleconference Agendas For Next Week: Uploaded
Caution: EXT Email
Hello all,
I uploaded the telco agendas for the upcoming week.
- Mar 6 Monday – MAC/PHY 19:00-21:00 ET
- Mar 8 Wednesday – Joint 10:00-12:00 ET
Link: https://mentor.ieee.org/802.11/dcn/23/11-23-0269-00-00be-jan-mar-tgbe-teleconference-agenda.docx
We will use these telcos to review and continue LB comment assignments.
Let me know if you have any questions.
Regards,
Alfred--
Alfred Asterjadhi, PhD
IEEE802.11 TGbe Chair,
Qualcomm Technologies Inc.
Cell #: +1 858 263 9445
Office #: +1 858 658 5302
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
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
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
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