Edward
Hi Genadiy,
So far, we agree to use compressed beamforming.
802.11be supports defining a compressed beamforming feedback in 802.11be for following cases:
· Number of streams: 1-16
· Number of antennas: 2-16
· Note: Compressed beamforming feedback is the same as defined in 802.11ax except for the new parameter values of Nc and Nr.
[Motion 111, #SP0611-23, [13] and [82]]
I took a look at section 27.3.13.2, and think that following text will be enough for now.
34.3.13.2 Beamforming feedback matrix V
Upon receipt of an EHT sounding NDP, the beamformee computes a set of matrices for feedback to the beamformer as described in 27.3.11.2 (Beamforming Feedback Matrix V).
Please let me know your opinion.
Best regards,
Wook Bong Lee
From: Genadiy Tsodik (TRC) [mailto:genadiy.tsodik@xxxxxxxxxx]
Sent: Tuesday, July 28, 2020 11:18 PM
To: Ruchen Duan <r.duan@xxxxxxxxxxx>; Wook Bong Lee <wookbong.lee@xxxxxxxxxxx>; STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: RE: [STDS-802-11-TGBE] PDT-PHY-Beamforming
Hi Ruchen,
I guess there will be no significant changes, mostly small editorial updates.
So we have by now:
34.3.13.1 – Genadiy
34.3.13.2 – Wool Bong
34.3.13.3 – Ruchen Duan
Thank you guys, let’s put a target to get an first version by 13/8, so we have two weeks to make a changes.
Again thank you all!
Genadiy Tsodik
Algorithm Expert
Huawei TLV Research Center
Office: +972-74-7198101 | Mobile: +972-526773161 | fax: +972-9-9511218
From: Ruchen Duan [mailto:r.duan@xxxxxxxxxxx]
Sent: Wednesday, July 29, 2020 3:06 AM
To: Wook Bong Lee <wookbong.lee@xxxxxxxxxxx>; Genadiy Tsodik (TRC) <genadiy.tsodik@xxxxxxxxxx>; STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: RE: [STDS-802-11-TGBE] PDT-PHY-Beamforming
Hi, Genadiy and Wook Bong
I am thinking of volunteer for taking care of 34.3.13.3 – CQI feedback, if needed. Let me know your opinion on this.
Best,
Ruchen Duan
From: Wook Bong Lee
Sent: Tuesday, July 21, 2020 1:43 PM
To: Genadiy Tsodik (TRC) <genadiy.tsodik@xxxxxxxxxx>; STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: RE: [STDS-802-11-TGBE] PDT-PHY-Beamforming
Hi Genadiy,
Sure, we can ask the scope of PHY-beamforming.
Best regards,
Wook Bong Lee
From: Genadiy Tsodik (TRC) [mailto:genadiy.tsodik@xxxxxxxxxx]
Sent: Tuesday, July 21, 2020 12:32 PM
To: Wook Bong Lee <wookbong.lee@xxxxxxxxxxx>; STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: RE: [STDS-802-11-TGBE] PDT-PHY-Beamforming
Hi Wook Bong,
I can agree that those sections from clause 9 related to both MAC and PHY, but I think any topic that you, Sameer and me are in charge of can cover them.
So my suggestion that we will start with 34.3.13 which is clear for all of us.
And perhaps Alfred and Edward can instruct us on how to allocate relevant sections from clause 9 to listed SFD/Draft 0.1 topics.
Thanks.
Genadiy Tsodik
Algorithm Expert
Huawei TLV Research Center
Office: +972-74-7198101 | Mobile: +972-526773161 | fax: +972-9-9511218
From: Wook Bong Lee [mailto:wookbong.lee@xxxxxxxxxxx]
Sent: Tuesday, July 21, 2020 8:24 PM
To: Genadiy Tsodik (TRC) <genadiy.tsodik@xxxxxxxxxx>; STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: RE: [STDS-802-11-TGBE] PDT-PHY-Beamforming
Hi Genadiy,
I think 9.4.1.65 ( HE Compressed Beamforming Report field ) should be covered within “Spatial stream and MIMO protocol enhancement-General”
And that is why it is in Joint while beamforming is in PHY. (Section 9 is in MAC but contents are PHY, and thus need joint discussion.)
Best regards,
Wook Bong Lee
From: Genadiy Tsodik (TRC) [mailto:genadiy.tsodik@xxxxxxxxxx]
Sent: Tuesday, July 21, 2020 8:45 AM
To: Wook Bong Lee <wookbong.lee@xxxxxxxxxxx>; STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: RE: [STDS-802-11-TGBE] PDT-PHY-Beamforming
Hi Wook Bong,
Thanks for volunteering.
I agree that some subclauses may be marked as part of multiple topics.
For my opinion, at least 9.4.1.65 ( HE Compressed Beamforming Report field ) should be covered within the scope of Beamforming.
Other subclauses may be have contributions from several topics but I think we need to decide who will be in POC to take care of them (we may keep it within Beamforming or everyone can take one subclause to balance the efforts).
As you and Sameer are POCs of mostly related (at least for R1) topics, I think it will be easy to consolidate our contributions.
Genadiy Tsodik
Algorithm Expert
Huawei TLV Research Center
Office: +972-74-7198101 | Mobile: +972-526773161 | fax: +972-9-9511218
From: Wook Bong Lee [mailto:wookbong.lee@xxxxxxxxxxx]
Sent: Tuesday, July 21, 2020 6:15 PM
To: Genadiy Tsodik (TRC) <genadiy.tsodik@xxxxxxxxxx>; STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: RE: [STDS-802-11-TGBE] PDT-PHY-Beamforming
Hi Genadiy,
Thanks for your effort.
First of all, I can volunteer for 34.3.13.2 – Beamforming feedback matrix V. It seems, so far, no change is required. But will work on it.
Second, I don’t know whether Beamforming TTT’s scope is beyond 34.3.13.
I see following items in the as well.
PHY
EHT sounding NDP
Sameer Vermani
Bo Sun, Youhan Kim, Junghoon Suh
Joint
Spatial stream and MIMO protocol enhancement-General
Wook Bong Lee
Minyoung Park, Yanjun Sun, Stephen McCann, Youhan Kim, Chenchen Liu
No motions.
Joint
Spatial stream and MIMO protocol enhancement-16 spatial stream operation
Wook Bong Lee
Junghoon Suh, Yanjun Sun, , Chenchen Liu
R1/R2?
Joint
MAP-Channel sounding
Junghoon Suh
Lei Huang, Kosuke Aio, Stephen McCann, Matthew Fischer, Myeongjin Kim
R1/R2?
Best regards,
Wook Bong Lee
From: Genadiy Tsodik (TRC) [mailto:genadiy.tsodik@xxxxxxxxxx]
Sent: Tuesday, July 21, 2020 1:46 AM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBE] PDT-PHY-Beamforming
Hello Beamforming TTTs!
Our topic is covered both in clause 34(PHY) and clause 9(Frame Formats). I think we will follow the structure of 11ax within the relevant sections.
Thus here is the list of subclauses we need to develop/modify:
· 34.3.13 – SU-MIMO and DL MU-MIMO Beamforming
o 34.3.13.1 – General
o 34.3.13.2 – Beamforming feedback matrix V
o 34.3.13.3 – CQI feedback
· 9.3.1.19 – VHT/HE NDP Announcement frame format
· 9.3.1.22.3 – Beamforming Report Poll (BFRP) variant
· 9.4.1.64 – HE MIMO Control Field
· 9.4.1.65 – HE Compressed Beamforming Report field
My plan is to be in charge of at least 34.3.13.1, please tell me which subclauses you’d like to volunteer for.
My suggestion is that one of the volunteers of EHT Sounding NDP will be in charge of subclause 9.3.1.19 as it’s a related topic. It may be better if one more person assists in this subclause, as it is quite long.
Note that we need to include only those decisions that passed motions and are incorporated by 20/566 doc, thus for subclauses 9.X.X I suggest we only modify text where required (e.g. HE to EHT) and prepare placeholders for tables and figures for the later versions of the Draft.
Please feel free to reply if I’ve missed anything and share with me which subclause you want to be in charge of.
Genadiy Tsodik
Algorithm Expert
Huawei TLV Research Center
Office: +972-74-7198101 | Mobile: +972-526773161 | fax: +972-9-9511218
