Hi Alfred,
Please add the following motions in the TGbn joint session, following SP in TGbn MAC group:
Motion 1
Move to define in 11bn a power save mode for a STA that is a UHR Mobile AP or a UHR non-AP STA wherein the STA may transition from a lower capability mode to a higher capability mode upon reception of an initial control frame
- Lower capability mode (e.g., 20 MHz BW, one SS, limited data rates, PPDU format)
- Higher capability mode (e.g., operating BW, NSS and MCSs, with at least one higher capability than that in the lower power capability mode)
- Initial Control frame is TBD
- Whether that applies for a non-mobile AP is TBD
Note: Discussed in several sessions and several submissions discuss similar concept, ref:
23/1875,
23/2003,
23/1965,
23/1936
Result in MAC ad hoc: 101Y/11N/23A
Motion 2
Do you agree to define cross link power save signaling mechanism
- Allowing a non-AP MLD to indicate to its associated AP MLD that supports the mechanism, in a frame sent on
one enabled link, the power management mode for one or more of its affiliated non-AP STAs
- Whether support for the mechanism is mandatory or optional is TBD
[23/2003, 24/0602]
Result in MAC ad hoc: 122Y/23N/32A
Thanks,
Laurent
From: Binita Gupta <bingupta.ieee@xxxxxxxxx>
Sent: Thursday, March 14, 2024 12:56 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] TGbn Planned Motions
Hi Alfred,
Could you please add the following joint motion on roaming in the TGbn joint session. The SP for this was run in Tuesday’s AM2 TGbn session with the following result.
SP result: 100Y, 28N, 18A
Move to add the following text to the TGbn SFD.
11bn defines a mechanism that when a non-AP MLD roams from one AP MLD to another AP MLD, the context related to the non-AP MLD is transferred from the one AP MLD to the other AP
MLD such that it preserves the data exchange context for the non-AP MLD.
–Details of the context (ex security association context) that can be transferred are TBD
–Framework to transfer the context is TBD.
Note: Discussed in several sessions and several submissions discuss similar concept, ref: 23/1908r2, 23/1884r2, 23/2157r2, 23/1996r0, 23/0322r0, 23/1937r1, 23/1897r0, 23/1971r2
Thanks,
Binita
Hello all,
Please let me know of any planned motions for today (Thursday) PM2 TGbn Joint session. Please send the request to the TGbn reflector no later than the end of the PM1 session so that I have time to prepare and upload the motion deck.
--
IEEE802.11 TGbe/TGbn Chair,
Qualcomm Technologies Inc.
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
---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: 90-92 route de la Reine, 92100 Boulogne, France
Registration Number: 302 456 199 R.C.S. NANTERRE
Capital: 5 208 026.16 Euros
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
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
|