Hi Matthew,
I appreciate your effort in the CR documents, and I carefully checked your resolutions.
I have some opinions on my CIDs in the documents.
CID 7150, 7153 of 26/0319 (LB291 PDT CR MAC NPCA EASY):
- For CID 7150, my intention of the comment is not to transmit to a STA which is not operating in the NPCA Primary channel. Regarding the modification of your document, “12) An NPCA STA that is not allowed to transmit an MPDU on the NPCA primary channel when its backoff reaches zero because it does not have an MPDU in any transmission queue that meets all of the requirements for transmitting an MPDU that are specified in this subclause shall invoke the backoff procedure as specified in 10.23.2.2 (EDCA backoff procedure) item k).(#7150)”, I think “the requirements” do not include any rule for prohibiting transmission to the STA that does not operate in the NPCA Primary channel. Therefore, I suggest adding a transmission restriction rule for this case.
- For CID 7153, I generally agree with your resolution, but I think there should be more clarification to avoid misunderstanding. Regarding the modification of CR doc., “A STA should not transmit an MPDU to an intended recipient if the end of the MPDU transmission and/or the end of the acknowledgement for that transmission would occur beyond the time at which the NPCA_TIMER at the transmitter reaches zero.(#7153)”, my understanding is that the term “at the transmitter” includes both “a STA transmitting an MPDU” and “an intended recipient (which transmits the acknowledgement)”, but the current paragraph may lead to misunderstanding. So, I would like to clarify the paragraph as following: “A STA should not transmit an MPDU to an intended recipient if the end of the MPDU transmission, and, if an immediate response is solicited, the end of the immediate response for that transmission would occur beyond the time at which the NPCA_TIMER at the STA or the intended recipient reaches zero.(#7153)”
|
7150
|
258.15
|
37.18.4
|
An MSDU destined for a STA that does not use NPCA may exist in the transmission queue of an NPCA AP. When the NPCA AP operates on the NPCA Primary channel, it should be clarified how the MSDU destined for a non-NPCA STA is not transmitted. For example, similar to the NSTR operation in IEEE 802.11be, this could be described as removing such MSDUs from the transmission queue.
|
As in comment.
|
Revised – TGbn editor to make changes marked with CID 7150 as found in 11-26-0319r0 which add a requirement backoff is restarted whenever a frame is not transmitted.
|
|
7153
|
258.15
|
37.18.4
|
A rule should be specified requiring an NPCA STA to complete a frame exchange before the NPCA_TIMER of its peer NPCA STA expires. The current draft does not include this rule, nor does it provide a method for a STA to perform the necessary calculation.
For example, consider an NPCA AP with a longer NPCA switching delay than its peer NPCA non-AP STA. When the AP transmits to the non-AP STA, it only needs to ensure the transmission is completed before its own NPCA_TIMER expires, as its timer is the more restrictive of the two.
Conversely, when the non-AP STA (with the shorter switching delay) transmits to the AP, a different approach is required. The non-AP STA must estimate the expiration time of the AP's shorter NPCA_TIMER. It can do this indirectly by calculating the point at which its (remaining NPCA_TIMER + own NPCA switching delay - AP's NPCA switching delay) becomes zero. The non-AP STA must then terminate its frame exchange before this calculated time.
|
As in comment.
|
Revised – TGbn editor to make changes marked with CID 7153 as found in 11-26-0319r0 which add a recommendation for a STA to not transmit an MPDU beyond its own NPCA_TIMER zero endpoint. Commenter should note that the transmitter does not necessarily know the recipient’s NPCA_TIMER value and by using its own timer, the transmitter will at least get the right answer when both transmitter and recipient have observed the same OBSS event.
|
CID 7132 of 26/0323 (LB291 PDT CR MAC NPCA MEDMISSYNC):
This CID is currently assigned to Seongho, and a resolution for this CID is drafted in 25/1928r6 (https://mentor.ieee.org/802.11/dcn/25/11-25-1928-06-00bn-lb291-comment-resolution-for-npca-synchronization.docx). I agree to the draft resolution of 15/1928r6, so please remove my CID from your document.
|
7132
|
259.13
|
37.18.4
|
In the current NPCA operation, it is unclear how the operation period should be handled when an NPCA AP and an associated NPCA non-AP STA observe different OBSS information.
This can lead to a situation where the pair of peer NPCA STAs have different NPCA timers, so a method for synchronizing their operation periods is required. To ensure consistent behavior, the standard should specify which STA's calculation takes precedence. It is suggested that the operation period determined by the AP should be adopted by its associated non-AP STAs.
|
As in comment.
|
Rejected – while there can be different operating periods of time on the NPCA channel, it is imperative that each STA return to the BSS channel at the time that is based on their own observation of the CCA on the BSS channel. This ensures that each STA returning from the NPCA channel will return in synchronization with the medium state on the BSS channel as observed by that STA. See also CID 5057.
|
CID 7137 of 26/0328 (LB291 CR MAC NPCA DIFFICULT):
This CID is proposing the problem, which occurs in NPCA capable UHR STAs (dot11NPCAOptionImplemented is True) and NPCA non-capable UHR STAs (dot11NPCAOptionImplemented is False) are mixed in a BSS which MOPLEN NPCA mode is enabled. In the BSS, when an OBSS’s TXOP is detected and its duration exceeds NPCA Minimum Duration Threshold, NPCA capable STAs will switch its operating channel to the NPCA Primary channel while NPCA non-capable STAs won’t. If the OBSS’s TXOP is truncated, non-NPCA capable STAs will perform channel access in the BSS Primary channel, during the NPCA capable STAs (including AP of the BSS) are operating in the NPCA Primary Channel. Therefore, non-NPCA capable STAs’ channel access eventually fails and occurs non-necessary medium inefficiency. This problem is described in my previous submission, 25/0018 (https://mentor.ieee.org/802.11/dcn/25/11-25-0018-01-00bn-considerations-on-stas-without-npca-capability.pptx). I prefer that the non-NPCA capable UHR STAs will defer its uplink transmissions until its AP returns to the BSS Primary channel from the NPCA Primary channel.
|
7137
|
254.05
|
37.18.1
|
STAs, which do not support NPCA operation may exist. When a BSS(AP) of the STAs is supporting NPCA operation, the AP will switch to the NPCA primary channel due to an OBSS's TXOP. However, if the OBSS's TXOP is truncated, the STAs which do not support NPCA operation will try channel access and UL transmission. Please define a rule for STAs which does not support NPCA operation for the given scenario.
|
As in comment.
|
Rejected – the commenter does not provide any guidance as to the nature of the rule that he desires to become part of the draft and therefore, the comment is unactionable.
|
If you have further opinions, please let me know. Thank you.
Best Regards,
Juseong Moon
2026. 2. 11. 오전 6:16, Matthew Fischer <matthew.fischer@xxxxxxxxx> 작성:
Alfred,
Please queue the following documents within the MAC group:
--
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
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
|