Re: [STDS-802-11-TGAX] LDPC extra symbol segment setting in TF

Thread Links	Date Links
Thread Prev	Thread Next	Thread Index	Date Prev	Date Next	Date Index

Thanks Edward for the suggestion and detailed reference. I’ll incorporate.

BRs,

Xiaogang.

From: Edward Au <edward.ks.au@xxxxxxxxx>
Sent: Thursday, May 21, 2020 5:04 PM
To: Chen, Xiaogang C <xiaogang.c.chen@xxxxxxxxx>
Cc: STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGAX] LDPC extra symbol segment setting in TF

Hello Xiaogang,

For NOTE 2, I would suggest replacing "may" with "might". "may" is a normative verb that shall not appear in the note, which is an informative text.

I know "should" is a normative verb too but, as per Section 2.8 of the 802.11 Style Guide (09/1034r16), "should" can appear in informative texts.

Regards,

Edward

On Thu, May 21, 2020 at 5:02 PM Chen, Xiaogang C <xiaogang.c.chen@xxxxxxxxx> wrote:

Hi all,

As discussed in the call, I am initiating the discussion to resolve the CID 24326. Based on the feedback from Yan and the online discussions, the changes below are proposed to 1) minimize spec change in current stage; 2) give AP some flexibilities to implement; 3) reflect the original intension of the group.

“should” in Note 1 is to leave room for the AP’s implementation. Note 2 means AP can still set it to 1 even no STA need extra symbol. Since this subclause talks about TB PPDU, I put the AP behavior as notes instead of put into main body. Please feel free to comment. Thanks.

24326

9.3.1.22.1

122.13

It is not clear what the LDPC Extra Symbol Segment field should be set to. The answer is that it should be set to 1 if any of the STAs need it

In 27.3.12.5.5 change " and LDPC Extra Symbol Segment fields" to " field" in the NOTE, and above this NOTE add a para:

"The AP shall set the LDPC Extra Symbol Segment field in the Common Info field of the Trigger frame to 1 if the calculations in 27.3.12.5.4 (Encoding process for an HE MU PPDU) indicate the need for an LDPC extra symbol segment for any STA triggered for HE TB PPDU transmission using LDPC."

Revised

-TGax editor to make the changes shown in 11-20/0717r4 under all headings that include CID 24326.

To the TGax Editor: replace the note in P.L. 617.43 with the two notes below:

NOTE 1 - AP should set the LDPC Extra Symbol Segment field in the Common Info field of the Trigger frame to 1 if the calculations in AP indicate the need for an LDPC extra symbol segment for any STA solicited by the AP for HE TB PPDU transmission using LDPC.

NOTE 2 - AP may set the LDPC Extra Symbol Segment field to 1 regardless of the value derived from the calculations described in the LDPC encoding process. AP may select a different value for the pre-FEC padding factor than the values derived from the calculations described in the BCC or LDPC encoding process.

BRs,

Xiaogang.

From: *** 802.11 TGax - HEW - High Efficiency WLAN *** <STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx> On Behalf Of Chen, Xiaogang C
Sent: Wednesday, May 20, 2020 10:19 PM
To: STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGAX] TGax CRC Teleconference 2020-05-21

Hi Osama

I’d like to present 0717 r3 to solve several more CIDs. Thanks.

BRs,

Xiaogang.

From: *** 802.11 TGax - HEW - High Efficiency WLAN *** <STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx> On Behalf Of Osama AboulMagd
Sent: Wednesday, May 20, 2020 6:03 AM
To: STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGAX] TGax CRC Teleconference 2020-05-21

Hello All,

TGax CRC has a conference call scheduled for Thursday May 21 @ 10:00 ET; for 3 hours.

Please let me know if you plan a submission to be added to the list.

A tentative agenda for the teleconference is available at:https://mentor.ieee.org/802.11/dcn/20/11-20-0538-20-00ax-tgax-crc-teleconference-march-july-2020-teleconference-agendas.pptx

The agenda is available on page 88. Xiaogang has asked to run a motion on some CIDs in 11-20/0717. He hasn’t uploaded a new revision to allow me to get the CID list ready for motion.

Webex info https://ieeesa.webex.com/ieeesa/j.php?MTID=mc6a9be82af0560f9430b80b42d243885

Meeting number: 715 399 731

Meeting password: wireless

Join by phone: +1-510-338-9438 USA Toll +44-20-3198-8144 UK Toll

Access code: 715 399 731

Teleconferences are bound by the conditions stipulated by the documentation below. Please review them and bring up any questions/concerns you may have before proceeding with the teleconference

•       IEEE Code of Ethics

–       https://www.ieee.org/about/corporate/governance/p7-8.html

•       IEEE Standards Association (IEEE-SA) Affiliation FAQ

–       https://standards.ieee.org/faqs/affiliation.html

•       Antitrust and Competition Policy

–       https://standards.ieee.org/content/dam/ieee-standards/standards/web/documents/other/antitrust.pdf

•       IEEE-SA Patent Policy

–       http://standards.ieee.org/develop/policies/bylaws/sect6-7.html

–       https://standards.ieee.org/about/sasb/patcom/

•       IEEE 802 Working Group Policies &Procedures (29 Jul 2016)

–       http://www.ieee802.org/PNP/approved/IEEE_802_WG_PandP_v19.pdf

•       IEEE 802 LMSC Chair's Guidelines (Approved 13 Jul 2018)

–       https://mentor.ieee.org/802-ec/dcn/17/ec-17-0120-27-0PNP-ieee-802-lmsc-chairs-guidelines.pdf

•       Participation in IEEE 802 Meetings

–       https://mentor.ieee.org/802-ec/dcn/16/ec-16-0180-05-00EC-ieee-802-participation-slide.pptx

•       IEEE 802.11 WG OM: (Approved 10 Nov 2017)

–       https://mentor.ieee.org/802.11/dcn/14/11-14-0629-22-0000-802-11-operations-manual.docx

Regards;

Osama.

To unsubscribe from the STDS-802-11-TGAX list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGAX&A=1

To unsubscribe from the STDS-802-11-TGAX list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGAX&A=1

To unsubscribe from the STDS-802-11-TGAX list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGAX&A=1

To unsubscribe from the STDS-802-11-TGAX list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGAX&A=1