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

Re: [STDS-802-11-TGBN] Motion request

Hello, Alfred

Please, help add the following to the PHY motion list. Thank you.

•     Move to include the following to the 11bn SFD

–    The user information in the Sync frame and in the UHR-SIG of CoBF DL PPDU corresponds to all the users that were listed, in the Invite as well as the Response frames

•       Nss for each user in the Invite/Response frame and the corresponding number of spatial streams for the same user interpreted from the spatial configuration in the Sync frame is consistent, i.e., the spatial stream allocation does not change.

•       The MCS and 2xLDPC bits for each user in the Sync frame should be consistent with those in the Response frame

•     Reference doc. 25/1186r2, 25/1191r1

 

Regards

 

From: You-Wei Chen [mailto:ywchen77115@xxxxxxxxx]
Sent: July 23, 2025 8:30 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] Motion request

 

Dear Alfred,

 

Please help to add the following passed SP to the PHY Motion list. Many thanks

 

  • Move to include the following text in the most updated 11bn draft in 37.12.3 (Rules for UHR Co-BF sounding protocol sequences) page 128 line 4 in D0.3?

           In a UHR Co-BF sounding sequence, the Starting Spatial Streams field in the UHR NDP Announcement shall be set to 0 in a UHR Co-BF sequential NDP sounding sequence and set to 1 in a UHR Co-BF joint NDP sounding sequence.


Ref doc: 11/25-1191r1, no objections

 

Best Regards,

You-Wei Chen 

 

 

 

Julia Feng <feng.julia.shuling@xxxxxxxxx> 於 2025年7月23日 週三 下午2:50寫道：

Hi Alfred,

 

Please use the corrected motion text in this updated message.

 

Please add the following SP from doc 1129r1 to the PHY motion list. It's passed unanimously in the PHY #3 ad-hoc session. 

 

Move to insert the following PDT at Page 319 Line 54 in 11bn D0.3:

A Co-BF AP shall be capable of being a sync-reference or a sync-follower. Co-BF APs’ sync-reference and sync-follower roles are determined when a Co-BF MAPC agreement is established using procedures described in Clause 37.13.1.3.2 (MAPC agreement establishment). The sync-reference and sync-follower roles can be changed when a Co-BF MAPC agreement is updated using procedure described in Clause 37.13.1.3.3 (MAPC agreement update).

 

Mover: Shuling (Julia) Feng

 

Thanks,

 

Shuling (Julia) Feng

 

On Wed, Jul 23, 2025 at 4:42 AM Julia Feng <feng.julia.shuling@xxxxxxxxx> wrote:

Hi Alfred,

 

Please add the following SP from doc 1129r1 to the PHY motion list. It's passed unanimously in the PHY #3 ad-hoc session. 

 

Do you support to insert the following PDT at Page 319 Line 54 in 11bn D0.3?

A Co-BF AP shall be capable of being a sync-reference or a sync-follower. Co-BF APs’ sync-reference and sync-follower roles are determined when a Co-BF MAPC agreement is established using procedures described in Clause 37.13.1.3.2 (MAPC agreement establishment). The sync-reference and sync-follower roles can be changed when a Co-BF MAPC agreement is updated using procedure described in Clause 37.13.1.3.3 (MAPC agreement update).

 

Thanks,

 

Shuling (Julia) Feng

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