Hi Morteza,
Thanks for the comment. Please find my response inline.
Thanks,
Yousi
发件人: Morteza Mehrnoush <mmehrnoush@xxxxxxxx>
发送时间: 2022年12月8日
2:31
收件人: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx; linyousi <linyousi@xxxxxxxxxx>
主题: Re: question on 11-22/1743
Hi Yousi,
Regarding your resolution: I think the value of EMLMR Supported MCS and NSS Set subfield could
be larger than the sum of per link TX/RX NSS. For example if non-AP MLD has 2 STAs, each non-AP STA could set TX/RX NSS to 1, while it actually has 2 antenna per non-AP STA, so it could potentially set the NSS in EMLMR Supported MCS and NSS Set subfield to
3 (total antennas in the non-AP MLD is 4).
Yousi: In the resolution, my point is that since the non-AP MLD knows its max capability on every link, it knows the max
NSS that it can use for each EMLMR link given that “shall” rule. How about I change the resolution to:
“Based on the current specification, it is clear that a non-AP MLD in EMLMR mode shall be able to support the TX/RX NSS up to the value
indicated in the EMLMR Supported MCS And NSS Set subfield. It is up to the non-AP MLD to decide the value in EMLMR Supported MCS and NSS Set subfield as long as it follows this “shall” rule.”?
I think the requirement should be that the TX/RX NSS in EMLMR Supported MCS and NSS Set subfield
should not be set lower than the max of the per link TX/RX NSS, otherwise what is the value of the EMLMR; for the max value the non-AP MLD can decide.
Yousi: Since 10043 only asks for clarification on max TX/RX NSS, would you mind we resolving this CID as rejected? For the
minimum NSS requirement, actually I have a related CID which is 10936. The resolution is provided in doc 1742 but it is deferred now, we can have more discussions on this CID if it is okay for you.
Thanks,
Morteza
From: Morteza Mehrnoush <mmehrnoush@xxxxxxxx>
Sent: Friday, December 2, 2022 10:50 AM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
<STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx>
Subject: Re: question on 11-22/1743
Hi Yousi,
My comment is actually about the 2nd part of your resolution. Can you please point out which part of text clarifies this "the max
TX/RX NSS in EMLMR mode should be smaller than or equal to sum of each EMLMR link's TX/RX NSS"?
"Based on the current specification, it is clear that a non-AP MLD in EMLMR
mode shall be able to support the TX/RX NSS up to the value indicated in the EMLMR Supported MCS And NSS Set subfield,
meaning that such values are the max TX/RX NSS in EMLMR mode and should be smaller than or equal to the
sum of each EMLMR link’s RX/TX NSS"
Thanks,
Morteza
From: linyousi <00001bcb1894c2a5-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Thursday, December 1, 2022 8:15 PM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
<STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx>
Subject: [STDS-802-11-TGBE] 答复: question on 11-22/1743
Hi Zinan, Thanks for your question. My understanding is that, because EMLMR Supported MCS And NSS Set subfield contains 1-3 MCS maps and each corresponds
to one BW, a non-AP MLD can determine its capabilities on any EMLMR link or its
“per-link
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
ZjQcmQRYFpfptBannerEnd
Hi Zinan,
Thanks for your question.
My understanding is that, because EMLMR Supported MCS And NSS Set subfield contains 1-3 MCS maps and each corresponds to one BW, a non-AP MLD can determine its
capabilities on any EMLMR link or its “per-link spatial stream capabilities” by checking the MCS maps given the link’s BW. That’s why I say the values in these MCS maps in the EMLMR Supported MCS And NSS Set subfield are for all links, but also provide “per-link
capability”.
For 1), “such values” refer to the values in each MCS map in the EMLMR Supported MCS And NSS Set subfield. By saying “the sum”, I mean that since the non-AP
MLD in EMLMR mode will do the link switch, the sum of each EMLMR link’s RX/TX NSS before the non-AP MLD enters the EMLMR mode (i.e., the non-AP MLD’s per link capability given in EHT-MCS maps) should be equal to or larger than each EMLMR link’s RX/TX NSS when
the non-AP MLD is in EMLMR mode. And this is my answer to the commenter’s question. And I see your point here, I will modify the resolution as below:
“Based on the current specification, it is clear that a non-AP MLD in EMLMR mode shall be able to support the TX/RX NSS up to the value indicated in the EMLMR
Supported MCS And NSS Set subfield, meaning that such values are the max TX/RX NSS in EMLMR mode and should be smaller than or equal to the sum of each EMLMR link’s RX/TX NSS
before the non-AP MLD enters the EMLMR mode (i.e., the non-AP MLD’s per link capability given in EHT-MCS maps).”
Hope this clarifies.
Thanks,
Yousi
发件人: Zinan Lin <Zinan.Lin@xxxxxxxxxxxxxxxx>
发送时间: 2022年12月2日
7:09
收件人: linyousi <linyousi@xxxxxxxxxx>;
STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
主题: question on 11-22/1743
Hi Yousi,
Thanks for presenting 11-22/1743r2. I have one question:
- The resolution of 10043 indicates that “such values are the max TX/RX Nss in EMLMR mode and should be smaller than or
equal to the sum of each EMLMR link’s RX/TX NSS”. What does “such values” refer to? Why it is “the sum”?
- The spec text you proposed for CID 10509 indicates the values in the EMLMR Supported MCS And NSS Set subfield are defined
per Link (your contribution 11-22/1742r2 shows the similar concept).
It seems to me that 1) and 2) are not consistent. Could you please explain?
Thanks,
Zinan
From: linyousi <00001bcb1894c2a5-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Tuesday, November 29, 2022 2:28 AM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBE] 答复: [STDS-802-11-TGBE] Initial Revision of Agendas for Nov'22-Jan'23 Telcos
Uploaded-CORRECTED LINK
|
Hi Alfred, Could you please add the following document to the MAC queue? 11-Nov-2022 ET202219650TGbeLB 266 Resolution for CID 11383Yousi Lin (Huawei)11-Nov-2022
22:23:33 ETDownload Thanks,Yousi 发件人:顾祥新
(Xiangxin Gu) [mailto:Xiangxin.Gu@xxxxxxxxxx]发送时间:
2022年11月29日
13:52收件人: STDS- |
Hi Alfred,
Could you please add the following document to the MAC queue?
|
11-Nov-2022 ET |
2022 |
1965 |
0 |
TGbe |
LB 266 Resolution for CID 11383 |
Yousi Lin (Huawei) |
11-Nov-2022 22:23:33 ET |
Thanks,
Yousi
发件人:
顾祥新 (Xiangxin Gu) [mailto:Xiangxin.Gu@xxxxxxxxxx]
发送时间: 2022年11月29日
13:52
收件人: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
主题: Re: [STDS-802-11-TGBE] Initial Revision of Agendas for Nov'22-Jan'23 Telcos
Uploaded-CORRECTED LINK
Hi Alfred,
Would you please add the document
22/1815(1
CID) to MAC queue?
Thanks!
BR,
Xiangxin Gu
Communication Standards Devision
From: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
Sent: Tuesday, November 29, 2022 5:17 AM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] Initial Revision of Agendas for Nov'22-Jan'23 Telcos Uploaded-CORRECTED LINK
With Corrected Link:
Regards,
AA
On Mon, Nov 28, 2022 at 1:15 PM Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
wrote:
Hello all,
I uploaded the telco agendas for the Nov'22-Jan'23 time period.
Please take a look at the submissions list and let me know if any of the contributions are missing from the queues.
In addition please take a look at the contributions that are listed for the first and second MAC (this weeks) teleconferences, and let me know if there is a need for any updates.
Last but not least, please make sure that if you have a submission with a request for SP then that submission appears in the queue as pending SP. This way it does not end up in the quarantine queues/docs. Updated revision of docs containing CIDs in quarantine will be uploaded by end of this week.
Best Regards,
Alfred
--
Alfred Asterjadhi, PhD
IEEE802.11 TGbe Chair,
Qualcomm Technologies Inc.
Cell #: +1 858 263 9445
Office #: +1 858 658 5302
--
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