| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Thanks Ali and Dibakar, a SP is a good idea. In terms of the section 11 text, here is a way we can potentially describe the behaviour. Open to all suggestions – Option A seems to require a bit more of a change compared to the original text. Option A: A STA Info field with the AID11 field
set to 2044 shall be present in all transmitted Sensing NDP Announcement frames as part of a TB sensing measurement exchange.
When transmitting a Sensing NDP Announcement frame as part of a TB sensing measurement exchange beginning with a polling phase,
the fields of the STA Info field with AID11
equal to 2044 shall be set as follows:
When transmitting a Sensing NDP Announcement
frame as part of a TB sensing measurement exchange not beginning with a polling phase, the
Partial TSF and Token fields of the STA Info field with AID11 equal to
2044
shall be reserved. Option B: When transmitting a Sensing NDP Announcement frame as part of a TB sensing measurement exchange
beginning with a polling phase, an AP shall include a value in the Partial TSF field in the STA Info field with the AID11 field equal to 2044, that equals
From: stds-802-11-tgbf@xxxxxxxxxxxxxxxxx <stds-802-11-tgbf@xxxxxxxxxxxxxxxxx>
On Behalf Of Das, Dibakar Agree to this.
From: Ali Raissinia <alirezar@xxxxxxxxxxxxxxxx>
Thanks Chris, like Chaoming correctly have understood my point! We could keep the ‘User Info/STA Info’ in the relevant frames at all TB exchanges any declare the Partial TSF field is
‘reserved’ when there’s no polling phase, which make the transmitter design essentially the same across both cases. This is actually my preference although we could run a SP and decide if we should adopt a text like yours below. Either one would work. 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/Chaoming/Ali, Ok, great, I also feel it is perfectly reasonable to always include the Partial TSF when there is a polling phase, and exclude it when there is no polling phase. I have a few CIDs referencing this problem in the normative text from sections 11.55.1.5.2.3, 11.55.1.5.2.4, and 11.55.1.5.2.5. The text is very similar in all three sections. Given the discussion,
I was thinking to revise as follows (e.g., 11.55.1.5.2.3): When transmitting a Sensing NDP Announcement frame
as part of a TB sensing measurement exchange beginning with a polling phase, an AP shall include a value in the Partial TSF field in the STA Info field with the AID11
field equal to 2044, that equals to the AP’s TSF[21:6] at the time of transmission of the preceding Sensing Polling Trigger frame. Specifically, the time of transmission is defined as when the first data symbol of the PSDU of the frame was transmitted to the
PHY plus the AP’s delays through its local PHY from the MAC-PHY interface to its interface with the WM. Additionally, the AP shall set the Token field in the STA Info field with the AID11 field equal to 2044 in the Sensing NDP Announcement frame to the same
trigger poll counter value as the Token field in the Sensing Polling Trigger frame whose partial TSF time is carried in the Sensing NDP Announcement frame. Would this clarification help with Chaoming’s concerns? Thanks and regards, -Chris From:
stds-802-11-tgbf@xxxxxxxxxxxxxxxxx <stds-802-11-tgbf@xxxxxxxxxxxxxxxxx>
On Behalf Of ???(Chaoming Luo) Hi Dongguk, Please see my follow up inline. BR, Chaoming 发件人: Dongguk Lim <dongguk.lim@xxxxxxx>
Hi Chaoming, Thanks for sharing your opinions and questions.
As described in 11bf D2.0, the partial TSF field is set to AP’s
TSF time at the timing of transmitting the preceding sensing polling Trigger frame.
I think that it is obvious that if there is no transmission of the sensing polling trigger
frame in the sensing measurement exchange, the partial TSF field does not exist.
[cm] It’s
not obvious. As you see, Ali pointed out two options: 1. The partial TSF field does not exist (or the user info with 2008 not exist?) when polling not exist; 2. The TSF filed is reserved when polling not exist. We need text to clarify which one is the group’s
preference. In addition, as commented by Ali, I think that we don’t
restrict the use case of the partial TSF to specific STA beacon by this information, any STA can get the benefits.
[cm] This means when partial TSF exists it applies to both A-STA and U-STA. Sounds OK to me for this point. After discussion, I added the related text as a note in the resolution to indicate that.. Best regards, Dongguk. From:
罗朝明(Chaoming Luo) [mailto:000015d97e832564-dmarc-request@xxxxxxxxxxxxxxxxx]
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
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 |