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

Re: [STDS-802-11-TGBN] CC50 PDT-CR on Trigger frame

Hi Alice,

 

Thanks for the updates.

11-25/442r4 Part 1: The RA field is set as follows:

—    For a Trigger frame that is not a GCR MU-BAR, NFRP or MU-RTS Trigger frame, and that has one User Info field that is not a Special User Info field (see 9.3.1.22.3 (Special User Info field)) and is not a Feedback User Info field (see 9.3.1.22.6a (Feedback User Info field)) and the AID12 subfield of the User Info field contains the AID of a STA, the RA field is set to the address of that STA

 

My comment was/are

  1. For AP to AP case, when the STA is an AP belonging to a multiple BSSID set, the RA field should be set to the transmitted BSSID of that AP.
  2. What about User Info fields with AID12 2011, 2012, etc? You may need to exclude these User Info fields as well.

 

Thanks,

Kaiying

 

 

From: Alice Jialing Li Chen <jialing.li.phd2@xxxxxxxxx>
Sent: Wednesday, May 14, 2025 12:47 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] CC50 PDT-CR on Trigger frame

 

External email : Please do not click links or open attachments until you have verified the sender or the content.

Dear All,

 

The latest PDT-CR documents on Trigger frame are the following. Part 2 is new. Parts 1, 3, 4, 5, 6 were revised based on dicussion in the Monday TGbn Joint call.

· 11-25/442r4 Part 1 to resolve CIDs in 9.3.1.22 and 9.3.1.22.1

· 11-25/633r0 Part 2 to resolve CIDs in 9.3.1.22.2

· 11-25/634r2 Part 3 to resolve CIDs in 9.3.1.22.3

· 11-25/635r0 Part 4 to resolve CIDs in 9.3.1.22.6

· 11-25/636r4 Part 5 to resolve CIDs in 9.3.1.22.7 – 9.3.1.22.9

· 11-25/637r4 Part 6 to resolve CIDs in 9.3.1.22.10 – 9.3.1.33.16

 

Regards,

Alice Chen

Qualcomm

 

PS: The following comments in the chat window have been addressed.

  • Part 1
    • Mark: In "B39 is set to 0 for an HE variant User Info field by an EHT or UHR AP", "or UHR AP" has been deleted, but only "or UHR" should be deleted, otherwise the sentence doesn't work
    • Dibakar/Juan's comment
  • Part 3
    • Mark: Isn't an UHR AP an EHT AP?
    • Mark: "MURTS" should be "MU-RTS". "MU RTS" should be "MU-RTS"
    • Mark: Field name should not include "/Reserved"
    • Mark: "Not-applicable" should be "Not applicable"
    • Yongho Seok Apple: "The UL Bandwidth Extension subfield, together with the UL BW subfield in the Common Info field, indicates the bandwidth of the solicited TB PPDU (i.e., the bandwidth in the U-SIG field of the EHT TB PPDU or UHR TB PPDU) if the Trigger frame is not an MU-RTS Trigger frame (see 9.3.1.22.11 (MU RTS Trigger frame format))[#3643]" If it is BSRP GI3, the solicited PPDU is not TB PPDU.
    • Laurent: For NPCA Primary Channel indication, a more accurate description would be: The NPCA Primary Channel Indication is set to 1 if the Trigger frame is transmitted by an NPCA STA that has switched to the NPCA primary channel (see 37.11 (Non-primary channel access (NPCA))) and is set to 0 otherwise.
  • Part 4
    • Mark: "a EHT" should be "an EHT" (Alice: not found)
    • Mark: "of PS160" should be "of the PS160"
    • Mark: "DRU Size" should be "DRU size" (assuming not a field name)
    • (Alice: Rename fields. They're not the same field.) Mark: I don't think we can have a field with two names
  • Part 5
    • Liwen: should Location Indication User Info field follow the style of I-FCS USer Info field (B12 to B15 being reserved)?
    • Change I-FCS to IFCS per editor’s input
    • Mark: “up to … and excluding …” is enough. Remove “any other …”
  • Part 6
    • Mark: "is defined as a BSRP non-trigger based (NTB) Trigger frame" should be "is called a BRSP NTB Trigger frame", no?
    • Mark: missing comma in "UL Spatial Reuse field the UHR P160 field"
    • Mark: delete "always" in "is always set to 0"

 

 

 

 

 

 

On Sat, May 10, 2025 at 12:11 PM Alice Jialing Li Chen <jialing.li.phd2@xxxxxxxxx> wrote:

Dear All,

 

One more PDT-CR document on the Trigger frame has been uploaded. Your timely feedback is much appreciated!

·       11-25/635r0 Part 4 to resolve CIDs in 9.3.1.22.6

 

Regards,

Alice Chen

 

 

On Mon, May 5, 2025 at 12:16 PM Alice Jialing Li Chen <jialing.li.phd2@xxxxxxxxx> wrote:

Dear all,

 

The following PDT-CR documents on the Trigger frame will be presented in a TGbn Joint call in the IEEE May meeting. Could you please review and let me know if you have any comments and questions? Your timely feedback is much appreciated!

  • 11-25/442r2 Part 1 to resolve CIDs in 9.3.1.22 and 9.3.1.22.1
  • 11-25/634r0 Part 3 to resolve CIDs in 9.3.1.22.3
  • 11-25/636r2 Part 5 to resolve CIDs in 9.3.1.22.7 – 9.3.1.22.9
  • 11-25/637r2 Part 6 to resolve CIDs in 9.3.1.22.10 – 9.3.1.33.16

 

Two more PDT-CR documents on the Trigger frame are under preparation. Will let you know when they are ready.

  • 11-25/633r0 Part 2 to resolve CIDs in 9.3.1.22.2
  • 11-25/635r0 Part 4 to resolve CIDs in 9.3.1.22.6

 

Best Regards,

Alice Chen

Qualcomm 

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