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

Re: [STDS-802-11-TGBN] TGbn PHY Motion Request

Hi Julia,

 

Thanks for the motion text.

 

I have a friendly editorial amendment suggestion to it below. I hope that is ok with you.

 

Regards,

Sameer

 

From: Julia Feng <feng.julia.shuling@xxxxxxxxx>
Sent: Wednesday, September 17, 2025 1:22 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] TGbn PHY Motion Request

 

WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.

Hi, Alfred, 

 

Thanks for pointing that out. Could you please add the following modified motion text to PHY motion list?

 

Move to insert the following rules to determine MAPC Co-BF sync-reference and sync-follower roles at P223.L15  in 37.15.2.1.2 (Co-BF negotiation) of 11bn D1.0:

 

When a Co-BF MAPC agreement is established or updated, the MAPC requesting AP determines and indicates explicitly its sync-reference / sync-follower role in the MAPC Scheme Request Set field of the Co-BF profile in the MAPC Negotiation Request frame. The MAPC responding AP assumes the sync-follower / sync-reference role left by the requesting AP if it accepts the agreement establishment or agreement update.

  

Note: It’s recommended to keep a Co-BF AP’s sync-reference/follower role semi-static and only changes change it in the Co-BF MAPC agreement update when necessary.

 

Supporting Doc: 11-25/1608r0

SP was passed without objections

 

Best regards

 

Shuling (Julia) Feng

 

On Wed, Sep 17, 2025 at 9:11 AM Alfred Asterjadhi <asterjadhi@xxxxxxxxx> wrote:

Hi Julia,

 

Could you please adapt the proposed text of the motion so that it is actionable for draft inclusion purposes?

 

Regards,


Alfred

 

On Tue, Sep 16, 2025 at 4:40 PM Julia Feng <feng.julia.shuling@xxxxxxxxx> wrote:

Dear Alfred, 

 

Could you please add the following motion to the motion queue?

 

Do you support to use the following procedure to determine MAPC Co-BF sync-reference and sync-follower roles when Co-BF MAPC agreement is established or updated in 11bn?

•A MAPC requesting AP indicates explicitly its sync-reference / sync-follower role in the MAPC Scheme Request Set field of the Co-BF profile in the MAPC Negotiation Request frame.

•A MAPC responding AP assumes the sync-follower / sync-reference role left by the requesting AP if it accepts the agreement establishment or agreement update.

Note: It’s recommended to keep a Co-BF AP’s sync-reference/follower role semi-static, only changes it in Co-BF MAPC agreement update when necessary.

 

Supporting Doc: 11-25/1608r0 

SP result: No objection

 

Thanks

Shuling (Julia) Feng

 

On Tue, Sep 16, 2025 at 11:33 PM Sameer Vermani <000039a3734fa32e-dmarc-request@xxxxxxxxxxxxxxxxx> wrote:

Hi Alfred,

Please add the following two motions to the PHY motions queue:

  1. Move to add the following rules for Co-BF in the TGbn spec in 37.15.2.1.4 Co-BF transmission procedure?
    • If the minimum number of data OFDM symbols of the Co-BF transmission indicated in the Co-BF Invite frame corresponds to Navbits > 3888 bits for a user of the coordinated AP, then the coordinated AP may indicate that 2xLDPC will be used for the user in the Co-BF Response frame.
    • If the minimum number of data OFDM symbols of the Co-BF transmission indicated in the Co-BF Invite frame corresponds to Navbits ≤ 3888 bits for a user of the coordinated AP, then the coordinated AP shall not indicate that 2xLDPC will be used for the user in the Co-BF Response frame.
    • A coordinating AP shall not choose a value for the Length field in the L-SIG field of the Co-BF PPDU in the Co-BF Trigger frame that corresponds to a number of OFDM symbols in the Data field which is smaller than the minimum number of data OFDM symbols the coordinating AP had indicated in the Co-BF Invite frame

                Note: These changes for the TGbn editor are reflected in the word document below

                https://mentor.ieee.org/802.11/dcn/25/11-25-1670-00-00bn-2x-ldpc-related-spec-text-changes-for-cobf.docx

               Supporting documents: 11-25/1609r2 and 11-25/1670r0

               SP result:  Passed unanimously

 

  1. Move to add the following recommendation for Co-BF to the TGbn spec in 37.15.2.1.4 Co-BF transmission procedure?
    • To help the coordinated AP choose an appropriate LDPC codeword length, the minimum number of data OFDM symbols of the Co-BF transmission indicated in the Co-BF Invite frame should be greater than or equal to 0.5 times the maximum number of data OFDM symbols of the Co-BF transmission indicated in the Co-BF Invite frame.

                Note: These changes for the TGbn editor are reflected in word document below

                https://mentor.ieee.org/802.11/dcn/25/11-25-1670-00-00bn-2x-ldpc-related-spec-text-changes-for-cobf.docx

                Supporting documents: 11-25/1609r2 and 11-25/1670r0

                SP result:  Passed unanimously

Thanks,

Sameer

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


 

--

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