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

Re: [STDS-802-11-TGBP] PDT Request

Hi Sam,

 

Thanks for the feedback.

As you rightly pointed, this normative behaviour is optional (may). I do still believe it is important to specify it, as an SP Interval of 7 minutes, can have an AMP STA waking up 4.2s ahead of the start of the SP (with 10,000ppm clock accuracy). I think it is reasonable therefore to allow AMP STAs to enter doze state if they don’t support channel sensing for 4s (which maybe unlikely for small capacitors). This also does not preclude AMP STAs from staying in the awake state till the start of the SP. As you mentioned this is up to the AMP STA.

The main point here is if the AMP STA enters doze state before the start of the SP, it should enter awake state at the start of the SP. This is in line with the normative behaviour for the doze state during the SP Interval.

Hope that provides more clarity.

 

Kind Regards

Ian

 

From: Sam Shi <Sam.Shi@xxxxxxxxxxxxxxxx>
Sent: Tuesday, 10 March 2026 7:49 am
To: STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx; Ian Bajaj <ian.bajaj@xxxxxxxxxx>
Subject: Re: [STDS-802-11-TGBP] PDT Request

 

Hi Ian and all,

 

Thanks for the PDT. Regarding 0463 (PDT AMP Service period), I am still looking at the first sentence of the last paragraph:

 

If the Active Tx non-AP AMP STA receives the SP Advert frame indicating the start of the intended AMP SP is later than the current time, the Active Tx non-AP AMP STA may enter the doze state till the start of the AMP SP, at which time it should enter the awake state. 

 

Of course it's nothing wrong for this STA behavior. However, this (behavior) should be completely up to STA. A STA may choose to stay awake, and another may choose to doze. It's not necessary to specify this in the spec, although it uses the wording "may". I also want to hear opinions from other members.

 

Thanks,

Sam

From: Ian Bajaj <0000340c29b22c99-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Monday, March 2, 2026 10:07 PM
To: STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-11-TGBP] PDT Request

 

Hi Sebastian,

 

Thanks again for the feedback. While I agree with the suggested modifications, I think we cannot equate it to TWT in that AMP STAs do not have the luxury to remain in channel sensing indefinitely. So the onus in providing the AMP SP service should be on the AMP AP, particularly in ensuring AMP STAs with significant clock drift can still be pointed to the start of the AMP SP (with a deterministic schedule of SP Advert transmission).

 

I have modified the first nested sentence to include “within a time interval less than or equal to the SP Minimum Wake up duration” to reflect MM-35, and to improve the readability. The description of the first and subsequent SP Advert frames have been changed to tasks descriptions as suggested.

 

Revision 1 has been uploaded to mentor (https://mentor.ieee.org/802.11/dcn/26/11-26-0463-01-00bp-pdt-amp-service-period.docx), please let me know if there is any other feedback from the group.

 

Kind Regards

Ian

 

From: Sebastian Max <sebastian.max@xxxxxxxxxxxx>
Sent: Monday, 2 March 2026 9:55 pm
To: Ian Bajaj <ian.bajaj@xxxxxxxxxx>; STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBP] PDT Request

 

Hello Ian,

 

Some comments from me on this PDT:

 

 

 Especially the paragraph following Figure 39-1:

 

In the maximum clock drift period, prior to the start of a configured AMP Service Period, the AMP AP shall schedule for transmission one or more SP Advert frames. The transmission of the first SP Advert frame should be within a time interval less than or equal to the SP Minimum Wake Duration, from the start of the maximum clock drift period. The transmission of any subsequent SP Advert frames within the maximum clock drift period, should be within a time interval less than or equal to the SP Minimum Wake Duration, from the start of the previous SP Advert frame. The definition of the maximum clock drift period is TBD.

 

First, for more clarity, the first nested sub-sentences could be simplified:

 

In the maximum clock drift period the AMP AP shall schedule for transmission one or more SP Advert frames prior to the start of a configured AMP Service Period.

 

Then, you are using „should“ in the following sentences. Is this intentional, as the channel might be busy at this time? Probably we could here take the 11ax TWT operation as an example, where also the first frame of the TWT SP is not guaranteed to be transmitted at the start of the SP (see IEEE 802.11-2024 26.8.2, below Figure 26-9, for example). Then it would be written as

 

The AMP AP transmits the first SP Advert frame within a time interval less than or equal to the SP Minimum Wake Duration from the start of the maximum clock drift period. 

 

And similar for the second sentence – so not as a „should“ or „shall“, but simply as a description of tasks.

 

BR,

Sebastian

 

To unsubscribe from the STDS-802-11-TGBP list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBP&A=1

To unsubscribe from the STDS-802-11-TGBP list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBP&A=1