9 | | The 802.11 standard specifies the Timing Synchronization Function (TSF) for maintaining a common timebase among nodes in a network. The TSF requires every node implement a 64-bit counter which increments every microsecond. Each node maintains its own TSF timer and derives the microsecond clock from its own local oscillator. |
10 | | |
11 | | In an infrastructure network, the TSF synchronization scheme designates the microsecond timer at the AP as the authoritative time for the network. As part of its normal operation the AP transmits beacon frames at some pre-defined interval (typically 102400 µsec). Every beacon frame contains the 64-bit value of the AP's TSF timer at the instant the transmission occurs. Critically, the beacon's timestamp field must be set at the time of transmission, ''not'' the time of packet creation or enqueuing. This guarantees the timestamp value accurately reflects any transmission delays due to medium activity. Every STA in the network which receives a beacon from the AP must update the its local microsecond timer with the value of the timestamp contained in the beacon payload. With high probability this scheme provides a common timebase across the network, with inter-node time offsets bounded by the maximum oscillator drift in one beacon interval. In other words, with the TSF synchronization already in place as part of the 802.11 Reference Design, we do not need to worry about any kind of explicit synchronization in our fast hopping approach. We can just base out frequency selection on the TSF timer and trust that the value in that timer is synchronized with the other nodes in the network. |
| 9 | The 802.11 standard specifies the Timing Synchronization Function (TSF) for maintaining a common timebase among nodes in a network. The TSF requires every node implement a 64-bit counter which increments every microsecond. Each node maintains its own TSF timer and derives the microsecond clock from its own local oscillator. In an infrastructure network, the TSF synchronization scheme designates the microsecond timer at the AP as the authoritative time for the network. As part of its normal operation the AP transmits beacon frames at some pre-defined interval (typically 102400 µsec). Every beacon frame contains the 64-bit value of the AP's TSF timer at the instant the transmission occurs. Critically, the beacon's timestamp field must be set at the time of transmission, ''not'' the time of packet creation or enqueuing. This guarantees the timestamp value accurately reflects any transmission delays due to medium activity. Every STA in the network which receives a beacon from the AP must update the its local microsecond timer with the value of the timestamp contained in the beacon payload. With high probability this scheme provides a common timebase across the network, with inter-node time offsets bounded by the maximum oscillator drift in one beacon interval. |
| 10 | |
| 11 | In other words, with the TSF synchronization already in place as part of the Mango 802.11 Reference Design, we do not need to worry about any kind of explicit synchronization in our fast hopping approach. We can just base our frequency selection on the TSF timer and trust that the value in that timer is synchronized with the other nodes in the network. |