[ns] backoff decrement and transmission in 802.11e tkn code

According to section 9.9.1.3 in the IEEE 802.11e standard, one and only one of the following actions is allowed at slot boundaries: - decrement of backoff timer, or - initiate transmission, or - backoff procedure due to internal collision, or - do nothing. So, 1. Backoff counter is

Re: [ns] backoff decrement and transmission in 802.11e tkn code

On Mar 15, 2006, at 1:40 PM, Jongman Heo wrote: According to section 9.9.1.3 in the IEEE 802.11e standard, one and only one of the following actions is allowed at slot boundaries: - decrement of backoff timer, or - initiate transmission, or - backoff procedure due to internal

Re: [ns] backoff decrement and transmission in 802.11e tkn code

I have no knowledge about the TKN implementation. However, I don´t agree with the interpretation of item 2. Because, when the backoff counter reach 0, the station can transmit immediately, i.e., in the next slot time. The station doesn´t wait for another AIFS interval. According to section

Re: [ns] backoff decrement and transmission in 802.11e tkn code

No. The operation of backoff decrement in 802.11e EDCA is significantly different from 802.11 DCF. In DCF, transmission occurs whenever the backoff counters reach zero. In EDCA, however, transmission occurs on the first slot boundary after the backoff counter has reached zero. STAs wait for a