Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi, Matt, Thanks for your reply. For the section 2),
I’d like to discuss more on this part. 7) section 2) c) i) -- suggestion to remove the PHY header based qualifier I think that the qualifier needs to remain it is complicated by the assignments of the MAC variables, but I'll keep rereading it and probably have a nightmare about it tonight For section 2) c), currently the logical structure of the texts in r6 is: c) at least one of the following is true:
i)
If AP has enabled PHY header-based NPCA
only, => check NPCA_PPDU_REM_DUR of 3rd PPDU
ii)
If AP has enabled MAC header-based NPCA in addition, => check NPCA_CFRAME_TXOP_REM_DUR of 1st PPDU,
The mentioned PHY header-based qualifier makes i) and ii) mutually exclusive situations, the STA can only fit in one of i) and ii).
That is to say, if the AP set the “MAC Header-based NPCA bit” to 1, the STA will not check NPCA_PPDU_REM_DUR of 3rd PPDU. However, as your previous reply to Gaurang, a STA may still check the variable NPCA_PPDU_REM_DUR of 3rd PPDU, if the 1st PPDU is lost. As for the potential cases that PPDUs might lost, here are some of my considerations for your reference.
Based on the table presented above, I would recommend reorganizing the logical structure of the text as follows:
b)
at least one of the following is true:
i)
Check NPCA_PPDU_REM_DUR of the PPDU.
ii)
If the AP has enabled MAC header-based NPCA in addition, => Further check NPCA_CFRAME_TXOP_REM_DUR of the PPDU. Note – I am using the limitation “the PPDU is not an ICF-only PPDU” to exclude the situation that the PPDU is a (MU)RTS and no following CTS received.
c)
at least one of the following is true:
i)
If the 3rd PPDU is received => check NPCA_PPDU_REM_DUR of 3rd
PPDU.
ii)
If the AP has enabled MAC header-based NPCA in addition, => Further check NPCA_CFRAME_TXOP_REM_DUR of 1st PPDU (and/or 2nd PPDU).
Note – I am using the limitation “at least two of the mentioned PPDUs” to make sure that the TXOP is not failed.
BTW, it just came up to me that we may use the name “single PPDU triggered” for condition 1) and “multiple PPDU triggered” for condition 2), if you are ok to reorganize the
text as my suggestion. Of course I am also open to other better names. Hope my considerations help, thank you! Best Regards! Junbin Chen
-------------------------------------------------- 发件人: Matthew Fischer <matthew.fischer@xxxxxxxxx>
Junbin, Thanks for reviewing: 1) for UHR Link reconfig frame - agree 2) adding other NPCA parameters to the list of those that must be included in the frames, I think that the earlier paragraphs in this section already include mention of those other parameters, plus another comment suggested
adding one or two that were missing - so instead of a new bullet, the previous paragraph is modified to include them - ignoring the optional/mandatory question for now 3) names PHY header based and MAC header based - there have been many suggestions and none yet suitable, so we'll just stick with this one for a while and people can continue to come up with ideas for the next several months 4) does specifying EHT/HE/UHR mean that it must be a data frame no - it could be mgmt, it could also be a non-HT that is a data frame - no need to be that specific anyway 5) simplify the PHY header based conditions - agree 6) same as 5) - agree 7) section 2) c) i) -- suggestion to remove the PHY header based qualifier I think that the qualifier needs to remain it is complicated by the assignments of the MAC variables, but I'll keep rereading it and probably have a nightmare about it tonight 8) change above to a reference - agree 9) meaning of peers - still under discussion, looking for a consensus A revision will appear later. On Tue, Jun 17, 2025 at 5:21 AM
陈俊斌 <00003c9288e54ba2-dmarc-request@xxxxxxxxxxxxxxxxx> wrote:
--
Matthew Fischer 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 |