Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Alfred,
Please add the following motion request in the queue:
- Move to add the following into 11bn SFD.
- When Co-SR Invite frame indicates 2x LTF type and indicates the intended number of LTF symbols in Co-SR Invite frame, then in the Co-SR Response frame, AP2 could reject the invitation due to the number of LTF limitation.
- The existence of a rejection reason in the CO-SR Response frame is TBD and if a rejection reason field is adopted in TGbn, the presence of a specific rejection reason for LTF limitation is also TBD
[11/25-1182r1]
No objections.
Regards
Ross Jian Yu 于健
Huawei Technologies
发件人: You-Wei Chen <ywchen77115@xxxxxxxxx>
发送时间: 2025年7月23日 20:30
收件人: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
主题: 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
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