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

Re: [STDS-802-11-TGBN] [EXT] Re: [STDS-802-11-TGBN] moving forward of 11-26/711



Hi Alfred and Kiseon,

 

The HT, VHT, EHT, UHR PPDU being used to carry Beacon and group addressed frames are excluded since “with the restrictions of in non-HT (duplicate) PPDU” exists.

 

Best Regards,

Liwen

 

From: Kiseon Ryu <kiseon.ryu@xxxxxxxxxxxxxx>
Sent: Wednesday, May 13, 2026 4:53 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: [EXT] Re: [STDS-802-11-TGBN] moving forward of 11-26/711

 

Caution: This is an external email. Please take care when clicking links or opening attachments. When in doubt, report the message using the 'Report this email' button

 

What about other PPDU types such as HT, VHT, EHT, UHR PPDU? Are they allowed to be transmitted for group addressed frames?

 

Regards,

Kiseon

 

From: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
Date: Wednesday, May 13, 2026 at 1:14
PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-11-TGBN] moving forward of 11-26/711

I think this still has issues. Perhaps it is simpler to state that the AP shall not transmit Beacons and group-addressed frames in an HE PPDU if at least one associated DPS STA is present. By exclusion the non-HT counterparts become the only viable option.

 

Regards,

 

Alfred

 

On Tue, May 12, 2026 at 8:32AM Liwen Chu <liwen.chu@xxxxxxx> wrote:

Hi all,

 

Per the offline discussion, the following text is added for the resolution of CID 11433 etc.

37.20 Enhanced multi-link single-radio (EMLSR) operation for a non-AP UHR MLD

TGbn editor: please add the following paragraph at the end of 37.20:

If the UHR STA affiliated with at least one UHR non-AP MLD associated with an UHR AP MLD is in the EMLSR mode, the UHR AP affiliated with the UHR AP MLD in the same link as the UHR STA shall transmit its Beacons and group-addressed frames as defined in subclause 10.6.5 (Rate selection for Data and Management frames) and 26.17.2.2 (Beacons in the 6 GHz band) with the restrictions of in non-HT (duplicate) PPDU using a rate of 6 Mb/s, 12 Mb/s and 24 Mb/s. (#11433, 4330, 6180, 6527, 8405, 10213)

 

Best Regards,

Liwen

 

From: Liwen Chu
Sent: Tuesday, May 12, 2026 2:08 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: moving forward of 11-26/711

 

Hi all,

 

The following are the CIDs that require further discussion in 11-26/711. If you have comments, please let me know.

 

Best Regards,

Liwen

 

CID 6412

Comments received in the meeting: the DBE should be combined with the other methods in one sentence.

Justification of using the separate sentences: The reason to separate DE from the other operations in the bullet is that the DBE case is not applicable to “if different from the DPS non-AP STA’s EHT Capabilities element” that is highlighted.

 

 

CID 11433 etc.

Comments received in the meeting: non-HT duplicate PPDU is missing. The non-HT duplicate PPDU should not be applicable to the band other than 6GHz band.

I can change the text to

If  there is at least one associated non-AP STA in DPS mode, the UHR AP shall transmit its Beacons and group-addressed frames as defined in subclause 10.6.5 (Rate selection for Data and Management frames) and 26.17.2.2 (Beacons in the 6 GHz band) with the restrictions of non-HT (duplicate) PPDU using a rate of 6 Mb/s, 12 Mb/s and 24 Mb/s. (#11433, 4330, 6180, 6527, 8405, 10213)

With such changes, the baseline’s non-HT or non-HT duplicate PPDU is followed.

 

CID 11774

Comments received in the meeting: the DPS non-AP STA with ICF Required field set to 0 is ok to enable DUO although the ICF is required for each TXOP the DPS non-AP STA is the TXOP responder.

Justification of CID 11774 change in 11-26/711: the EMLSR link should follow the same criteria.

 

CID 5411

Comments received in the meeting: the current RTS/CTS CCA sensing rules should be applied.

Justification of CID 5411 changes in 11-26/711: for a DPS STA with HC mode BW more than 20MHz that uses 20MHz for the CCA in LC mode, the current RTS/CTS rules are not enough. One way moving forward is to separate the RTS/CTS  to case 1 with same BW of LC and HC mode and case 2 with HC mode BW wider than LC mode BW. Case 1 uses the baseline RT/CTS rules while case 2 uses the new rules.

 

CID 11062

Comments received in the meeting: “decoding the PPDUs” is not applicable to ICF Required equal to 0 where the frame transmission is missing.

Justification of CID 11062 changes in 11-26/711: the case of ICF Required equal to 1 doesn’t require the transmission of the frame case.

One option to move forward is to separate the description to ICF Required equal to 1 from ICF Required equal to 0.

 

 

  

 

 

 

 

 

 


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

 

 

--

Alfred Asterjadhi, PhD

IEEE802.11 TGbe/TGbn Chair,

Qualcomm Technologies Inc.

Cell #:    +1 858 263 9445

Office #: +1 858 658 5302


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


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


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