Re: [STDS-802-11-TGAX] TGax CRC Teleconference 2020-08-18

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

Hello Liwen,

You are effectively proposing to reject 24043 (which itself refers back to

Pooya's 21203) with the following reason:

Discussion: the TB transmission is different from the transmission through EDCA: the decision about what to transmit is done within SIFS after receiving the soliciting Trigger frame. Other things also need to be done: CCA to decide whther the TB PPDU can be transmitted, the TB PPDU transmission preparing. It is good to give STA flexibility when responding TB PPDU. The current text in D6.0 clearly mentioned two cases single TID A-MPDU and multi-TID A-MPDU in TB PPDU. The resolution proposed by the commenter in 19-1667/r1 only includes the responding multi-TID A-MPDU case.

but:

1) The change proposed in 19/1667r1 still allows the "STA flexibility when responding TB PPDU",

since it's all in terms of "should" not "shall", and indeed there is a NOTE

to emphasise this.

2) The change proposed in 19/1667r1 only includes the multi-TID A-MPDU case

because the issue is when you have a choice of TIDs; clearly if you only have

one TID then you just have to transmit that. However, I'm fine to add this

(see highlight):

In 26.6.3.1 change:

If the AP specifies a value defined in Table 9-154 (ACI-to-AC encoding)(#20006) in the Preferred AC subfield in the Trigger Dependent User Info field of a Basic Trigger frame, then an HE STA that transmits a multi-TID A-MPDU to the AP should aggregate QoS Data frames from any one of the TIDs from the same AC or higher priority AC as indicated in the Preferred AC subfield of the Trigger Dependent User Info field that is addressed to the STA in the Trigger frame, up to the limit indicated in the TID Aggregation Limit subfield in Trigger Dependent User Info field of the Trigger frame.

NOTE—While it is recommended that the STA transmit QoS Data from the AC that is same or higher than the preferred AC, the STA might still(#20227) to aggregate QoS Data from an AC that has lower priority than the preferred AC.

The STA may aggregate MPDUs from TIDs in other ACs within the remaining time to the HE TB PPDU duration value indicated in the UL Length subfield in the Common Info field of the received Trigger frame, up to the limit indicated in the TID Aggregation Limit subfield in Trigger Dependent User Info field of the Trigger frame.

NOTE—If the AP indicates AC_BK in the Preferred AC subfield in the Trigger Dependent User Info field of a Basic Trigger frame, then an HE STA that transmits a multi-TID A-MPDU to the AP might aggregate MPDUs from any AC/TID or combination of TIDs, up to the limit indicated in the TID Aggregation Limit subfield in Trigger Dependent User Info field of the Trigger frame.

An HE STA that intends to send QoS Data frames from a single TID should select a TID from the same or higher priority AC indicated in the Preferred AC subfield in the Trigger Dependent User Info field of a Basic Trigger frame. If the HE STA has no buffered MPDU for TIDs belonging to the same or higher priority AC indicated in the Preferred AC subfield in the Trigger Dependent User Info field of a Basic Trigger frame, then the HE STA may include MPDUs for a TID belonging to any other AC in that A-MPDU carried in the HE TB PPDU.

to:

An HE STA that transmits a multi-TID A-MPDU in an HE TB PPDU should aggregate MPDUs in the following order:

· first, any and all MPDUs that correspond to the Preferred AC subfield of the Trigger Dependent User Info field addressed to the STA in the Trigger frame

· then, any and all MPDUs that correspond to any AC that has a higher priority

· then, any MPDUs that correspond to any AC that has a lower priority

subject to:

· the limit indicated in the TID Aggregation Limit subfield in the Trigger Dependent User Info field addressed to the STA in the Trigger frame

· the duration indicated in the UL Length subfield in the Common Info field of the Trigger frame

NOTE—These rules permit a STA to not aggregate any MPDUs from the preferred AC or a higher priority AC.

An HE STA that transmits a single-TID A-MPDU in an HE TB PPDU should select the TID in the following order:

· a TID that corresponds to the Preferred AC subfield of the Trigger Dependent User Info field addressed to the STA in the Trigger frame, if there is a corresponding MPDU for that TID

· otherwise, a TID that corresponds to any AC that has a higher priority, if there is a corresponding MPDU for that TID

· otherwise, a TID that corresponds to any AC that has a lower priority

subject to:

· the limit indicated in the TID Aggregation Limit subfield in the Trigger Dependent User Info field addressed to the STA in the Trigger frame

· the duration indicated in the UL Length subfield in the Common Info field of the Trigger frame

NOTE—These rules permit a STA to not select MPDUs from the preferred AC or a higher priority AC.

Thanks,

Mark

Mark RISON, Standards Architect, WLAN English/Esperanto/Français

Samsung Cambridge Solution Centre Tel: +44 1223 434600

Innovation Park, Cambridge CB4 0DS Fax: +44 1223 434601

ROYAUME UNI WWW: http://www.samsung.com/uk

From: *** 802.11 TGax - HEW - High Efficiency WLAN *** <STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx> On Behalf Of Liwen Chu
Sent: Monday, 17 August 2020 19:54
To: STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGAX] TGax CRC Teleconference 2020-08-18

Hi Osama,

Please add 11-20/1235 for CID 24043 to the queue.

Best Regards,

Liwen

From: *** 802.11 TGax - HEW - High Efficiency WLAN *** <STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx> On Behalf Of Osama AboulMagd
Sent: Monday, August 17, 2020 11:39 AM
To: STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGAX] TGax CRC Teleconference 2020-08-18

Hi Xiaogang,

I’ll add to the agenda for tomorrow.

Regards;

Osama.

From: Chen, Xiaogang C [mailto:xiaogang.c.chen@xxxxxxxxx]
Sent: Monday, August 17, 2020 2:19 PM
To: Osama AboulMagd <Osama.AboulMagd@xxxxxxxxxx>; STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx
Subject: RE: TGax CRC Teleconference 2020-08-18

Hi Osama

I’d like to present a slight update on DCN: 0717r11.

The update is to patch a missed equation change for the HE-SIG-A on the power normalization issue. Thanks.

BRs,

Xiaogang.

From: *** 802.11 TGax - HEW - High Efficiency WLAN *** <STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx> On Behalf Of Osama AboulMagd
Sent: Monday, August 17, 2020 5:23 AM
To: STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGAX] TGax CRC Teleconference 2020-08-18

Hello All,

I’ve uploaded a tentative agenda for the teleconference tomorrow. It is available at:

https://mentor.ieee.org/802.11/dcn/20/11-20-1169-08-00ax-tgax-crc-teleconference-agendas-august-september-2020.pptx

Please let me know if you plan a submission.

Regards;

Osama.

From: *** 802.11 TGax - HEW - High Efficiency WLAN *** [mailto:STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx] On Behalf Of Osama AboulMagd
Sent: Thursday, August 13, 2020 3:21 PM
To: STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGAX] TGax CRC Teleconference 2020-08-18

Hello All,

TGax CRC has a conference call scheduled for Tuesday August 18 @ 17:00 ET; for 2 hours.

Please let me know if you have a submission. I’ll send an agenda later.

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

Meeting number: 129 360 6457

Meeting password: wireless (94735377 from phones and video systems)

Join by phone: Tap to call in from a mobile device (attendees only) +1-408-418-9388 USA Toll
Global call-in numbers

Access code: 129 360 6457

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)