Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi, Yuki and Yuxin, Thanks for your SPs and comments. Here’s my question on SP3. SP3: Do you agree to include the following into the 11bn SFD? * An NPCA STA shall indicate in the NPCA mode that NPCA operation is disabled when the operating channel width of the NPCA STA is changed from channel width more than TBD MHz
to equal or less than TBD MHz Do you have a vision that the NPCA Supported BW can be variant for different NPCA STAs implementation?
For example, a non-AP operating with 160MHz announces that its NPCA supported BW is 80MHz, while another 2nd non-AP operating with 320MHz announces that its NPCA supported BW is
160MHz, and at the same time a 3rd non-AP operating with 320MHz announces that its NPCA supported BW is 80MHz, like the table list below?
If so, I am wondering if it makes the transmission scheduler of AP more complicated? And a further signaling overhead is required for non-AP to indicate their NPCA supported BW. Basically I guess it is good to define a unified NPCA Supported BW for all UHR NPCA STAs for implementation simplicity. Or, do you have any other considerations? Best Regards! -------------------------------------------------- Junbin Chen
发件人: Jay Yang <yang.zhijie@xxxxxxxxxx>
Hi Yuki, Thanks for your SPs. Regarding your SP4, I'm not sure which the TBD frames meaning, it's too broad. Based on Liwen's contribution, I think the group address frame and Beacon frame shall be not transmitted
in NPCA primary channel, but I'm not sure about other frames. Could you change "TBD frames" to "Beacon frame and the group addressed frames" in the SP text? SP4: Thanks Best Regards Jay Yang (杨志杰)
Original From: yuxin.lu <eeluyx@xxxxxxxxx> Date: 2025年02月27日 18:05 Subject: Re: [STDS-802-11-TGBN] NPCA straw polls Hi Yuki, Thanks for preparing those SPs, for SP3, below are some comments for your consideration Would you clarify whether this NPCA STA includes both AP and non-AP? . if it includes AP, we have an agreement (Motion #134) that says that [An AP shall not allow the use of NPCA within its BSS if the BSS operating bandwidth is less than or equal
to TBD MHz, where TBD = 40 MHz or 80 MHz] . if it includes non-AP, non-AP can simply indicate its NPCA Supported BW with other operation parameters to clarify its NPCA operating capability to AP, instead of performing disabling
NPCA which introduces additional signaling overhead; for example, if non-AP indicates NPCA Supported BW=80 MHz, then its operating channel width is changed from 80MHz to 40MHz (should notify this change to AP via OMI/OMN), non-AP automatically
disables NPCA since it can no longer support 80MHz, or it can update its NPCA operating capability to AP with a new NPCA Supported BW value Best Regards Yuxin TCL On Thu, 27 Feb 2025 at 15:15, Yuki Yoshikawa <00003a6e12a10726-dmarc-request@xxxxxxxxxxxxxxxxx> wrote:
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
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 |