| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Chris, I also have similar opinions to Ali. If the polling phase does not exist, the user field containing the partial TSF field is not sent by AP. and, I think that we don't need to constrain the STA type to apply the TSF field. Best regards, Dongguk. From: Ali Raissinia [mailto:alirezar@xxxxxxxxxxxxxxxx] Correct, when there is a polling phase a capture of TSF has been done and should be conveyed to any device that intends to synchronize, in any form of sounding (at least one exists) or even if the device decides not to participate as it considers this measurement unnecessary, but can benefit from tracking AP’s clock for next cycle(s). From: Chris Beg <chris.beg@xxxxxxxxxxxxxxxxxxxx> WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Hi Ali, Just to confirm, is your preference to make it mandatory for the TB Exchange to include these additional User/STA Info fields containing the Partial TSF every time a polling phase is present? Then the only way an AP would be able to exclude those fields would be to not start the exchange with a polling phase? This would apply to the SR2SI Sounding Trigger, SR2SR Sounding Trigger, and Sensing NDPA – and there wouldn’t be a case where it is present in the SR2SI Sounding Trigger, but not the Sensing NDPA? Thanks and regards, -Chris From: Ali Raissinia <alirezar@xxxxxxxxxxxxxxxx> My preference is to either include the Partial TSF and make it reserved (keep implementation the same) or do NOT send User Info field of AID=2008/STA Info field with AID=2044 when polling phase is absent in each TB measurement exchange and not mention about ‘unassociated STA’. This way even associated devices can benefit from the TSF update for an improved clock tracking. We can either add a NOTE or a normative text in TB General (11.55.1.5.2.1) section which is the section that Dongguk is adding the new normative text. Regards, Ali From: Chris Beg <chris.beg@xxxxxxxxxxxxxxxxxxxx> WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. HI Dongguk and Chaoming, Thanks for the comments and discussion. I have a similar CID (#3296/#3297) that I’m working on, however it covers the section 11.55.1.5.2.4 text identified by Chaoming, and the equivalent NDPA text in 11.55.1.5.2.3. The partial TSF is required when there are unassociated STAs participating, since it saves them having to keep coming back to receive the beacon. There is also a constraint that un unassociated STA shall set the Poll Required bit (section 11.55.1.3 P137.49), and therefore a Polling phase will be present. The suggestion by Chaoming of ONLY including it for unassociated responders would indeed be the easiest resolution. Are there any cases where we may want to provide the Partial TSF to associated STAs (e.g., long sleep interval between receiving beacons)? Another simple option could be to make the Partial TSF mandatory when unassociated STAs are participating, but not exclude the option of adding it for exchanges that begin with a polling phase. What are your thoughts? Thanks and regards, -Chris From: stds-802-11-tgbf@xxxxxxxxxxxxxxxxx <stds-802-11-tgbf@xxxxxxxxxxxxxxxxx> On Behalf Of ???(Chaoming Luo) Hi Dongguk, Thanks for the contribution! I do have a question per CID 3204 and I don’t think the issue got resolved. The CID raises such a case: the measurement exchange does not contain a polling phase (e.g., no unassociated non-AP responders). In such a case, how should the Partial TSF field in the SR2SI Sounding Trigger frame be set? Keep in mind in the current 11.55.1.5.2.4 TF sounding phase - SR2SI variant, it looks like the SR2SI Sounding Trigger frame always includes a the User Info field with the AID12/USID12 field equal to 2008. If the Partial TSF field is used by unassociated non-AP only, I’d suggest we add text (may be in clause 11) to clarify the SR2SI Sounding Trigger frame includes the User Info field with the AID12/USID12 field equal to 2008 only when there is unassociated non-AP responder(s), otherwise it does not include that User Info field. BR, Chaoming 发件人: stds-802-11-tgbf@xxxxxxxxxxxxxxxxx <stds-802-11-tgbf@xxxxxxxxxxxxxxxxx> 代表 Dongguk Lim
Hi All, I would like to share CR contribution, which provides resolutions for 5 CIDs related to SR2SI Sounding Trigger frame. I plan to upload it to the server after hearing your opinions. So, I would appreciate it if you could share your thoughts. Best regards, Dongguk. To unsubscribe from the STDS-802-11-TGBF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBF&A=1 To unsubscribe from the STDS-802-11-TGBF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBF&A=1 To unsubscribe from the STDS-802-11-TGBF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBF&A=1 To unsubscribe from the STDS-802-11-TGBF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBF&A=1 To unsubscribe from the STDS-802-11-TGBF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBF&A=1 |