| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hello Girish: See inline below. Cheers -- ganesh From: *** 802.11 TGaz - NGP - Next Generation Positioning *** <STDS-802-11-TGAZ@xxxxxxxx>
On Behalf Of Girish Madpuwar Hi, I am referring to section "11.22.6.3 Fine timing measurement procedure negotiation" of REVmd_D1.0. Seeking some clarification regarding ASAP negotiation as documented below: — An initiating STA performing a FTM procedure with a responding STA that is an AP shall support non-ASAP operation. — A responding STA that is an AP shall support and select non-ASAP operation when so requested by an initiating STA. — An initiating STA performing a FTM procedure with a responding STA that is not an AP shall support ASAP operation. — A responding STA that is not an AP shall support and select ASAP operation when so requested by an initiating STA. — If the responding STA is ASAP capable, the responding STA’s selection of ASAP should be the same as that requested by the initiating STA. 1) Its seems that the negotiations is biased towards making handshake ASAP if exchange is happening between non-AP STA. Whereas if one party is AP then decision of ASAP/non-ASAP is left to
AP based on its capability. Is this intent right? What is the motivation behind this? [[gv]] some non-AP STAs may not be able to support ASAP operation – the intent is to allow for non-AP STAs that are not ASAP-capable to negotiate non-ASAP FTM sessions with the responding STA. Since NAN (Wi-Fi Aware) uses FTM for
Ranging in ASAP mode, additional conditions were added to the bulleted list (you quote above). 2) How is this relevant for TB and non-TB based negotiation of 11az? [[gv]]
There is no ASAP for TB/non-TB ranging. We instead have immediate and delayed response. 3) Is there further gain for ASAP other than reduction of two frame exchange i.e. 'initial FTM-ACK' and 'FTM request (trigger)-ACK' handshake? [[gv]] With ASAP, the only gain is that the first burst starts with IFTM (there is no need for a FTM request (trigger)-ACK handshake). However, the subsequent bursts require a FTM request(trigger)-ACK exchange. Regards, Girish To unsubscribe from the STDS-802-11-TGAZ list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGAZ&A=1 To unsubscribe from the STDS-802-11-TGAZ list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGAZ&A=1 |