Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
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 |
Attachment:
oledata.mso
Description: oledata.mso
Attachment:
image007.emz
Description: image007.emz