Hi Jianhan,
Thanks. I think 4x996-tone RU should also be treated as a single RU instead of a MRU since it can only be used in 320 MHz full BW non-OFDMA transmission.
Best regards,
Lei
From: Jianhan Liu <jianhanliu@xxxxxxxxx>
Sent: Saturday, September 19, 2020 6:08 AM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] draft text for "Subcarriers and Resource Allocation for Multiple RUs"
Ho Wookbong and Lei,
I removed the 2x996 from the MRU. please see the following link for updates:
Thanks,
Jianhan
On Fri, Sep 18, 2020 at 11:49 AM Wook Bong Lee <wookbong.lee@xxxxxxxxxxx> wrote:
Hi Jianhan,
Thanks. That is good.
My additional suggestion is to make a table like below for MRUs in addition to figures.
Best regards,
Wook Bong Lee
From: Jianhan Liu [mailto:jianhanliu@xxxxxxxxx]
Sent: Friday, September 18, 2020 11:44 AM
To: Wook Bong Lee <wookbong.lee@xxxxxxxxxxx>
Cc: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] draft text for "Subcarriers and Resource Allocation for Multiple RUs"
Hi Wookbong,
What is your suggestion? We can remove 996x2 as a single RU as Lei huang suggested.
Thanks,
JIanhan
On Fri, Sep 18, 2020 at 9:07 AM Wook Bong Lee <wookbong.lee@xxxxxxxxxxx> wrote:
Hi Jianhan,
Thanks for your effort.
I have one question.
In page 8 second to the bottom block, it says 2x996 tone MRU in 320 MHz transmission.
But this is for non-OFDMA sentence. I think 2x996 is not supported in 320 MHz for non-OFDMA.
Also have one suggestion.
Currently you have figured to specify what are allowed MRUs in both small MRU and large MRU.
Is it possible that you can add table as well?
Table like table 27-7 to table 27-9.
Best regards,
Wook Bong Lee
Sent with BlackBerry Work (www.blackberry.com)
________________________________
From: Jianhan Liu <jianhanliu@xxxxxxxxx>
Sent: Sep 17, 2020 11:58 AM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] draft text for "Subcarriers and Resource Allocation for Multiple RUs"
Hi Ron,
Please see the updated document according to your comments.
https://mentor.ieee.org/802.11/dcn/20/11-20-1447-02-00be-pdt-subcarriers-and-resource-allocation-for-multiple-rus.docx<https://urldefense.proofpoint.com/v2/url?u=https-3A__mentor.ieee.org_802.11_dcn_20_11-2D20-2D1447-2D02-2D00be-2Dpdt-2Dsubcarriers-2Dand-2Dresource-2Dallocation-2Dfor-2Dmultiple-2Drus.docx&d=DwMFaQ&c=JfeWlBa6VbDyTXraMENjy_b_0yKWuqQ4qY-FPhxK4x8w-TfgRBDyeV4hVQQBEgL2&r=F1dvNUi0uHkT3MFJNe2F126UHE49M7tR_CIkwdjzKQ4&m=t3HOhFowXaNP6cBA4OvgwyDqTaghlqXviXW5iZi6Cm8&s=51YJYZ3TwWxWmK4hHOhWiBXLZ1ysf00BpNUk4gdPPXM&e=>
Thanks,
Jianhan
On Thu, Sep 17, 2020 at 10:03 AM Ron Porat <000009a0da80e877-dmarc-request@xxxxxxxxxxxxxxxxx<mailto:000009a0da80e877-dmarc-request@xxxxxxxxxxxxxxxxx>> wrote:
Hi Jianhan,
A small typo Page 6, line 3: “The data subcarriers of a 996+484+484 tone MRU consist of the…”, Typo.
Suggestion: mandatory support in pages 8 and 11 - may be good to combine with BW support (meaning make it conditional support based on BW)
“It is mandatory for non-AP STA to support the transmission and reception of 484+242 tone MRU, 996+484 tone MRU, 2×996-tone MRU, 2×996+484 tone MRU, 3×996-tone MRU, and 3×996+484 tone MRU in OFDMA”
Thanks,
Ron
From: Lei Huang [mailto:nusleihuang@xxxxxxxxxxx<mailto:nusleihuang@xxxxxxxxxxx>]
Sent: Wednesday, September 16, 2020 12:51 AM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx<mailto:STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-11-TGBE] draft text for "Subcarriers and Resource Allocation for Multiple RUs"
Hello Jianhan,
Thanks for preparing this draft text.
I have a comment. A 2x996-tone RU is treated as a MRU in your draft text but is treated as a single RU in 20/1371r4. Such an inconsistency needs to be solved. Personally I prefer treating a 2x996-tone RU as a single RU due to the defined 160 MHz BW EHT PPDU.
Best regards,
Lei
From: Jianhan Liu <jianhanliu@xxxxxxxxx<mailto:jianhanliu@xxxxxxxxx>>
Sent: Friday, September 11, 2020 8:39 AM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx<mailto:STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx>
Subject: [STDS-802-11-TGBE] draft text for "Subcarriers and Resource Allocation for Multiple RUs"
Dear all,
The draft text for "Subcarriers and Resource Allocation for Multiple RUs" has been uploaded to the server. You can access it with the following link.
https://mentor.ieee.org/802.11/dcn/20/11-20-1447-00-00be-pdt-subcarriers-and-resource-allocation-for-multiple-rus.docx<https://urldefense.proofpoint.com/v2/url?u=https-3A__mentor.ieee.org_802.11_dcn_20_11-2D20-2D1447-2D00-2D00be-2Dpdt-2Dsubcarriers-2Dand-2Dresource-2Dallocation-2Dfor-2Dmultiple-2Drus.docx&d=DwMFaQ&c=JfeWlBa6VbDyTXraMENjy_b_0yKWuqQ4qY-FPhxK4x8w-TfgRBDyeV4hVQQBEgL2&r=F1dvNUi0uHkT3MFJNe2F126UHE49M7tR_CIkwdjzKQ4&m=t3HOhFowXaNP6cBA4OvgwyDqTaghlqXviXW5iZi6Cm8&s=6TN58v9t9pNT0k6DQwRMycRx577SbX-qgqbGPXz0abY&e=>
Your comments are welcome.
Thanks,
Jianhan
________________________________
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<https://urldefense.proofpoint.com/v2/url?u=https-3A__listserv.ieee.org_cgi-2Dbin_wa-3FSUBED1-3DSTDS-2D802-2D11-2DTGBE-26A-3D1&d=DwMFaQ&c=JfeWlBa6VbDyTXraMENjy_b_0yKWuqQ4qY-FPhxK4x8w-TfgRBDyeV4hVQQBEgL2&r=F1dvNUi0uHkT3MFJNe2F126UHE49M7tR_CIkwdjzKQ4&m=t3HOhFowXaNP6cBA4OvgwyDqTaghlqXviXW5iZi6Cm8&s=fPvV4J4Au4xZzuq827q041HxtawU3nQrqVEYFqx0h7A&e=>
________________________________
To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.or<https://urldefense.proofpoint.com/v2/url?u=https-3A__listserv.ieee.org_cgi-2Dbin_wa-3FSUBED1-3DSTDS-2D802-2D11-2DTGBE-26A-3D1&d=DwMFaQ&c=JfeWlBa6VbDyTXraMENjy_b_0yKWuqQ4qY-FPhxK4x8w-TfgRBDyeV4hVQQBEgL2&r=F1dvNUi0uHkT3MFJNe2F126UHE49M7tR_CIkwdjzKQ4&m=t3HOhFowXaNP6cBA4OvgwyDqTaghlqXviXW5iZi6Cm8&s=fPvV4J4Au4xZzuq827q041HxtawU3nQrqVEYFqx0h7A&e=>
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
OPPO
本电子邮件及其附件含有OPPO公司的保密信息，仅限于邮件指明的收件人使用（包含个人及群组）。禁止任何人在未经授权的情况下以任何形式使用。如果您错收了本邮件，请立即以电子邮件通知发件人并删除本邮件及其附件。This e-mail and its attachments contain confidential information from OPPO, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!
