| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Xiaogang,Thanks for your effort.There are typos,in page 5, Futher —> Furtherin page 6, capble —> capablechange CoBF and CoSR to Co-BF and Co-SRin page 7 and 8, ELR validate —> ELR Validatein page 7, CoBF/CoSR indication —> Co-BF/Co-SR Indicationin page 9, octetsand —> octets andin page 9, andpossible —> and possibleIn page 7, what is ELR-detection?Second, for intended BSS color indication is only for Co-BF based on motion 214,So, maybe we can update your suggested text as (based on the intended BSS color indication if Co-BF is used).I also noticed that motion 214 is not captured in D0.2. I have contacted PoC of the UHR-SIG, Mengshi, regarding this issue.So, the name “intended BSS color indication” may be updated. Or we can suggest to use that name to Mengshi.Lastly, regarding spatial reuse, I am not sure whether it is a good idea to allow spatial reuse on Co-BF/Co-SR and ELR PPDU.I think we need to have further discussion on it.— If the CRC protecting ELR-SIG1 is valid, the UL/DL does not contain an intended value, the PHY entity shall issue a PHY-RXSTART.indication(RXVECTOR) then issue a PHY-RXEND.indication(Filtered). The PHY shall maintain PHY- CCA.indication(BUSY, channellist) primitive for the predicted duration of the transmitted PPDU derived from the LENGTH field in ELR-SIG1 as defined in Equation (38-110)
unless it receives a PHY- CCARESET.request primitive before the end of the PPDU for instance during spatial reuse operation as described in 37.10 (UHR Spatial reuse operation).— If the CRC protecting ELR-SIG1 is valid and the UL/DL contains an intended value, the PHY shall continue to check CRC of ELR-SIG2
— If the CRC protecting ELR-SIG2 is not valid, the PHY shall issue the error condition PHY-RXEND.indication(FormatViolation) primitive and maintain PHY- CCA.indication(BUSY, channellist) primitive for the predicted duration of the transmitted PPDU derived from the LENGTH field in ELR-SIG1 as defined in Equation (38-110)
unless it receives a PHY- CCARESET.request primitive before the end of the PPDU for instance during spatial reuse operation as described in 37.10 (UHR Spatial reuse operation).— If the CRC protecting ELR-SIG2 is valid, the STA-ID in ELR-SIG2 does not match the 11 LSBs of the AID of a STA in theAP’s BSS, then the PHY entity shall issue a PHY-RXSTART.indication(RXVECTOR) then issue a PHY-RXEND.indication(Filtered). The PHY shall maintain PHY- CCA.indication(BUSY, channellist) primitive for the predicted duration of the transmitted PPDU derived from the LENGTH field in ELR-SIG1 as defined in Equation (38-110)
unless it receives a PHY- CCARESET.request primitive before the end of the PPDU for instance during spatial reuse operation as described in 37.10 (UHR Spatial reuse operation).Best regards,Wook Bong LeeOn Apr 29, 2025, at 10:04 AM, Xiaogang Chen <xiaogang.g.chen@xxxxxxxxx> wrote:Hi PHY folks,Thanks for the discussions yesterday.As agreed on the call, please find the updated version as attached. I have cleaned up the "track change" and only keep the ones in Page 7 regarding the BSS color match in UHR-SIG. As I mentioned yesterday, BSS color filter has been done in U-SIG. Page 7 deals with STA-ID match in UHR-SIG. "Intended STA-ID" should be good enough IMO, but to accommodate other members I modified the current text to "an intended STA-ID (based on the intended BSS color indication if CoBF/CoSR is used) is detected" to cover CoBF/CoSR. Hope we can converge on the current version.If I don't hear a different opinion by Thursday, the attached R2 will be uploaded to the server. Thanks.--BRs,Xiaogang.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