Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Thanks Rubayet, it is correct. It works well as long as the TSF offset compensation is done. 发件人: Rubayet Shafin [mailto:r.shafin@xxxxxxxxxxx]
Hi Abhi, Sure, no problem. I can share my understanding. Please see the below figures corresponding to the two cases you depicted. Case-1 (TSF Offset = -20): Case-2 (TSF Offset = +35): Basically, TSF offset information will be used to adjust the timing reference for SP on link 2 with respect to that on link 1 (see 11-22/305). I really hope it clarifies things a bit.
@Ming, sorry to jump in here. Please feel free to share your thoughts if the pictures you have in mind is different than the ones I illustrated above. Best Rubayet From: Abhishek Patil <appatil@xxxxxxxxxxxxxxxx>
Hi Rubayet, Ming, As requested, could you please draw the figures and provide an explanation for the timing/TSF on each link for the two scenarios that I described? Regards, Abhi From: Rubayet Shafin <r.shafin@xxxxxxxxxxx>
WARNING:
This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Hi Ming, Thank you for your contribution. I think the aligned SP is, in general, a good direction, and I don't see any technical difficulty in realizing it, especially since the group has already agreed on the TSF synchronization
across multiple links. As Minyoung suggested, we can work on refining the text for better clarity. Best Rubayet From: Abhishek Patil <appatil@xxxxxxxxxxxxxxxx> Hi Ming, Thank you for your email. Could you please provide figures that show the timing information (i.e., the TSF values) at the start of each SP on that link. You need to consider two cases:
?
Case 1 - TSF on transmitting link (L1) is greater than TSF on the other link (L2) - let's say TSF for L1 is 115 and TSF for L2 is 95 and Target Wake Time field along w/ other fields in the TWT parameter set
indicates start of first SP at TSF=125, periodicity of 15ms and the SP duration is 5ms
?
Case 2 - TSF on transmitting link (L1) is less than TSF on the other link (L2) - let's say TSF for L1 is 115 and TSF for L2 is 150 and fields in the TWT parameter set indicates start of first SP at TSF=125,
periodicity of 15ms and the SP duration is 5ms Regards, Abhi From: Ganming(Ming Gan) <000017d5b1a95115-dmarc-request@xxxxxxxxxxxxxxxxx>
Correct the following example Taking the following fig for example, an AP MLD and a non-AP MLD setup two TWT agreements through one TWT element on link 1, the target wake up time is in reference to the TSF of
link 1. If the target wake up time for link 1 is T, then target wake up time for link 2 is T-Delta, right? Here clock drift is ignored. 发件人: Ganming(Ming Gan) [mailto:000017d5b1a95115-dmarc-request@xxxxxxxxxxxxxxxxx]
Hello Abhi Could you elaborate why the case you mentioned can’t work. For the TSF topic, it is right, we discussed it several times. Fortunately, the group reached consensus on it. Each affiliated
AP shall do synchronization on TSF, and can ensure the clock drift to be within +-30us. Moreover TSF offset is also provided. In this case, there is no issue to reference the TSF of any link . Taking the following fig for example, an AP MLD and non-AP MLD setup two TWT agreements through one TWT element on link 1, the target wake up time is in reference to the TSF of link
1. If the target wake up time for link 1 is T, then target wake up time for link 1 is T-Delta, right? Here clock drift is ignored. Best wishes Ming Gan 发件人: Abhishek Patil [mailto:appatil@xxxxxxxxxxxxxxxx]
Hi Ming,
Hope this helps!
From: Ganming(Ming Gan) <000017d5b1a95115-dmarc-request@xxxxxxxxxxxxxxxxx>
Hello all This email is for the discussion of Individual TWT issue. If you have comments, please let me know. Best wishes Ming Gan To unsubscribe from the STDS-802-11-TGBE list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1
To unsubscribe from the STDS-802-11-TGBE list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1
To unsubscribe from the STDS-802-11-TGBE list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1
To unsubscribe from the STDS-802-11-TGBE list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1
To unsubscribe from the STDS-802-11-TGBE list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1
To unsubscribe from the STDS-802-11-TGBE list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1
To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 |