| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Matthew,My intention is that the exisitng mechanism in 10.23.2.2 should be reused to the NPCA channel, not intent to say the CW setting in the normal primary channel. For your explaination on storing and reuse the EDCA parameters on PCH, I think it is OK.If we see 10.23.2.2, the QSRC is only used in several cases, i.e. not always used.But in the PDT, the NPCA CW is always set by using the QSRC and the QSRC is from AP, which is defferent from 10.23.2.2.Why not just let CW = CWmin and QRSC = 0 each time the STA and AP switch to NPCA? If falure happens, then the exisiting CW and QRSC update in 10.23.2.2 can be used.
BRs,Haorui Yang(Rae)China Mobile---- Replied Message ----
From Matthew Fischer<matthew.fischer@xxxxxxxxx> Date 6/14/2025 07:15 To <STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx> Subject Re: [STDS-802-11-TGBN] 11-25-936r4 PDT NPCA update -- was: Reminder: Technical Submissions Queues Haorui,You said:I guess you are OK with reusing the exising mechanism in 10.23.2.2 where the CW update depends on the different events, e.g. a) to j) (even more).Yes, this is the intent.The PDT says that when switching to NPCA, the STA stores the CW and QSRC variables of the EDCAF that has been running on the primary channel and puts new values in their place, then on the NPCA channel operates EDCAF with the same rules as on the primary channel, but with these new values.When the STA switches back, it puts the old CW and QSRC values back into the EDCAF variables and then resumes backoff on the primary channel.So the same rules for backoff are performed on the NPCA channel.What you might be indicating as different is that the events that occur on the NPCA channel are not reflected in the EDCAF variables that were stored and then put back.This is what is intended, as the other devices on the primary channel do not experience those NPCA channel events and therefore, their EDCAF variables are not modified during that period of time.That is, any device that is competing on the primary channel during NPCA is simply watching and waiting for the OBSS TXOP that is occuring there and there would be no change to its EDCAF variables.So it does not make sense for an NPCA device to change the EDCAF variables that it is using for the primary channel during the NPCA channel excursion.So my understanding is that what specified in the PDT is different from the existing mechanism
I do not understand what it is that you are saying that is different in the PDT, unless it is what I mentioned above.Is it something else that you feel is different?
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