| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Gwangho,
Thanks for initiating this topic.
As i mentioned during your presentation, we can just add a note to clarify that the PHY-CCA.indication(Busy) is related to current operating channel. For example:
When an OBSS PPDU is detected on BSS PCH, a PHY-CCA.indication(Busy) primitive generates and indicates the BSS PCH is busy. And then the STA switches to NPCA PCH via PHY-CONFIG.request primitive indicating NPCA PCH. Since the previous PHY-CCA.indication(Busy) primitive only indicates the BSS PCH is busy other than the NPCA PCH. Therefore, the STA could access the channel without any limitation.
BTW, according to your contribution, it's a little bit confusing to send a PHY-CCARESET.request primitive during the OBSS PPDU, because BSS PCH is indeed busy and you do not indicate which PCH(BSS PCH or NPCA PCH) this primitive applies to
In genral, when you operates on BSS PCH, PHY-CCA.indication(Busy) primitive only indicates the BSS PCH is busy.
when you operates on NPCA PCH, PHY-CCA.indication(Busy) primitive only indicates the NPCA PCH is busy
Such primitive does not case any influence to the PCH on which the STA does not currently operate
Best Regards！
Yan Li
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