Block ACK
Understanding Block ACK
In legacy Wi-Fi, each data frame requires an individual ACK after a SIFS interval (10-16 μs). For high-rate transmissions, the ACK overhead becomes significant: at 1 Gbps PHY rate, a 1500-byte frame takes only 12 μs, but each ACK adds 44 μs of overhead (SIFS + ACK + DIFS + backoff). Block ACK eliminates this by batching acknowledgments.
A Block ACK session is established with an ADDBA (Add Block ACK) request/response exchange. Once established, the transmitter sends A-MPDUs (Aggregated MPDUs) and the receiver responds with a single Block ACK bitmap indicating which MPDUs were received correctly.
Efficiency = Tdata/(Tdata + TACK + Toverhead)
≈ 50-60% at high PHY rates
With Block ACK (64 MPDUs):
Efficiency = 64×Tdata/(64×Tdata + TBA + Toverhead)
≈ 90-95%
ACK Mechanism Comparison
| Mechanism | Standard | Frames/ACK | Efficiency |
|---|---|---|---|
| Normal ACK | 802.11a/g | 1 | ~50% |
| Block ACK | 802.11n | 64 | ~90% |
| Multi-STA BA | 802.11ax | 256 per STA | ~95% |
Frequently Asked Questions
How does it improve throughput?
64 MPDUs acknowledged by 1 frame vs 64 individual ACKs. MAC efficiency jumps from ~50% to 90%+. Up to 40% throughput gain.
Block ACK bitmap?
64 or 256-bit bitmap. Bit=1: received OK. Bit=0: missing. Sender retransmits only failed MPDUs next burst.
Immediate vs Delayed?
Immediate: sent within SIFS, standard in 802.11n+. Delayed: adds latency, rarely used in practice.