| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Kumail, My comments are 1), in baseline, an AP may announce Responder PM Mode subfield is equal to 1 and might be no available outside the broadcast TWT SP. What you proposed should be for 11mf. 2), If 11bq should accept such enhancement, AP’s earlier ending of broadcast SP may not be enough. The reason is that a PUO AP needs to be available in TWT SP of individual TWT agreement ryc. Best Regards, Liwen From: Muhammad Kumail Haider <kumail.ieee@xxxxxxxxx>
Hi all, I am starting this thread to discuss CID#11686 in 25/2144 regarding TWT Termination provision for APPUO AP, discussed during 2/9/26 call. Here is the proposed text, under discussion:
(#11686)If a UHR APPUO AP receives the early termination indication (i.e., EOTSP subfield equal to 1 in a QoS Null frame) from all associated
STAs during an ongoing broadcast TWT SP, and the APPUO AP has also sent the TWT SP termination indication to all these STAs (as described in 26.8.5), the APPUO AP may become unavailable for the remaining duration of the broadcast TWT SP. Use case: Consider an APPUO AP (e.g., a mobile AP) with 2 associated STAs. The AP sets up 30TU SP with 300TU interval. And so it happens that the AP and all STAs are done with usage of the SP within the first 5ms. STAs send early
termination indication using EOTSP (new 802.11bn feature) and AP subsequently terminates the SP for both STAs, and STAs switch to DOZE to save power. However, as per baseline broadcast TWT and APPUO rules, the AP must stay awake until the scheduled end time
of SP, consuming more power. The above provision will allow the APPUO AP to also switch to sleep (or use that time to operate on another channel e.g.,). As such, it’s a valuable provision to add, to give APs this option. Note that this provision is providing APPUO AP with an “option” to become unavailable (may become unavailable), it is up to the implementation, and to me it’s a valuable addition to the spec. @Binita Gupta (binitag), @Liwen
Chu hope it clarifies the use case and addresses your comments during the meeting. Another clarification, I received a comment during the call that the APPUO AP may even become unavailable during a broadcast TWT SP, so the added provision is not needed. This is incorrect. Please refer to the following text. Even
when operating with Unavailability Mode set to 1, the APPUO AP may be unavailable for other types of SPs (e.g., individual TWT SPs, if they fall outside the bTWT SPs the AP announces). However, the AP must be available during the (entirety of) bTWT SPs it
sets up. As per 802.11bnD1.3, 37.18.4 AP PUO mode: "...The NDP Paging Indicator/Unavailability Mode subfield is set to 0 to indicate that the AP is unavailable outside of these broadcast TWT SPs, except within any other TWT SP that is setup with the AP or that is advertised by the AP (see
baseline subclause). The NDP Paging Indicator/Unavailability Mode subfield is set to 1 to indicate that the AP is unavailable outside of these broadcast TWT SPs, even if that time falls within any other TWT
SP that is setup with the AP or that is advertised by the AP (see baseline subclause)." Please let me know any further comments. Kumail 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 |