Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
SP1: harmonization between SPs in [23/1873, 23/2003, 23/1965]
• Initial Control frame is TBD
SP2: harmonization between SPs in [23/1875, 23/2003, 23/1965, 23/1936]
Do you agree 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)
• Initial Control frame is TBD
• Whether that applies for a non-mobile AP is TBD
SP3: harmonization between SPs in [23/1875, 23/2003, 23/1965, 23/1936]
Do you agree that, in 11bn, a STA can request its peer STA to initiate TXOPs/frame exchanges with the STA with an initial control frame
• Initial control frame is TBD
SP4: harmonization between SPs in [23/2040, 23/2002, 23/1103, 24/0097]
Do you agree to define in 11bn a mechanism to allow a STA to optionally indicate or update a periodic unavailability in time to its peer STA
• Expectation is to use existing protocols
• Applies when the peer STA(s) supports the mechanism
Hi Alfred,
There’s been harmonization between the authors of the contributions on power save (per-link) topic.
Here’s the list of SPs with common wording that result from this harmonization, tagged with the related contributions.
Please queue these SPs.
Thanks
Laurent
SP1: harmonization between SPs in [23/1873, 23/2003]
Do you agree to define a way in 11bn to include in an initial control frame an intermediate FCS for UHR STA(s) that precedes padding and the FCS field
SP2: harmonization between SPs in [23/1875, 23/2003, 23/1965, 23/1936]
Do you agree 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)
• Initial Control frame is TBD
• Whether that applies for a non-mobile AP is TBD
SP3: harmonization between SPs in [23/1875, 23/2003, 23/1965, 23/1936]
Do you agree that, in 11bn, a STA can request its peer STA to initiate TXOPs/frame exchanges with the STA with an initial control frame
• Initial control frame is TBD
SP4: harmonization between SPs in [23/2040, 23/2002, 23/1103, 24/0097]
Do you agree to define in 11bn a mechanism to allow a STA to optionally indicate or update a periodic unavailability in time to its peer STA
• Expectation is to use existing protocols
• Applies when the peer STA(s) supports the mechanism
From: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
Sent: Wednesday, January 17, 2024 10:53 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBN] Handling Similar SPs for MAC/Joint topics
Hello all,
In order to save some time in running SPs that are similar to each other (noticed several of them in multiple topics in MAC and Joint) I would suggest that members with SPs that are similar in nature to work offline with other members, that have SPs on that same topic, to converge on common wording that is satisfactory and send a single SP request as opposed to multiple SP requests that are similar. This way we can optimize the time used in the TGbn.
When you send such a request please also include the contributions that are used for preparing the converged SP, and we will add a note to the SP slide which refers to these contributions, and the MAC ad-hoc chair/TGbn chair will show the SP text with the above mentioned note.
Let me know if you have any questions and/or suggestions on this approach.
Regards,
Alfred
--
Alfred Asterjadhi, PhD
IEEE802.11 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
---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters:
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
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