Every Wi-Fi transmission pays a fixed price before any data moves: waiting for the channel, a preamble and an acknowledgement. Aggregation packs many packets into one transmission so that price is paid once. See how A-MSDU, A-MPDU and both together build a frame, what they save, and what happens when errors hit.
Sending one packet costs a contention wait, a preamble (fixed time, however fast the data rate), MAC headers and an ACK. At high data rates the packet itself takes only a few microseconds, so most of the airtime is overhead. Aggregation sends many packets per transmission:
A-MSDU puts several packets inside one MAC frame: one header, one checksum. A-MPDU sends several complete MAC frames back to back in one transmission, each with its own checksum, and the receiver answers with one Block Ack that confirms each frame separately. Modern Wi-Fi usually does both: A-MSDUs inside an A-MPDU.
A radio error corrupts a few bits somewhere in the transmission. The receiver checks each FCS (checksum): whatever that checksum covers is thrown away and has to be sent again. The difference is how much one checksum covers.
| Wi-Fi 4 (802.11n) | Wi-Fi 5 (802.11ac) | Wi-Fi 6 (802.11ax) | Wi-Fi 7 (802.11be) | |
|---|---|---|---|---|
| Largest A-MSDU | 7,935 bytes (3,839 on some devices) | about 11,400 bytes | about 11,400 bytes | about 11,400 bytes |
| Largest frame inside an A-MPDU | 4,095 bytes, so an A-MSDU there holds only 2 full-size packets | 11,454 bytes | 11,454 bytes | 11,454 bytes |
| Largest A-MPDU | 65,535 bytes | 1,048,575 bytes | 6,500,631 bytes | 15,523,200 bytes |
| Frames per Block Ack | 64 | 64 | 256 | 1,024 |
| Longest transmission | about 5.5 ms | about 5.5 ms | about 5.5 ms | about 5.5 ms |
Whichever limit is reached first ends the transmission. At high data rates it's usually the Block Ack window; at low rates it's the 5.5 ms time limit.
| A-MSDU | A-MPDU | Both (A-MSDU inside A-MPDU) | |
|---|---|---|---|
| Arrived in | Wi-Fi 4 (802.11n, 2009) | Wi-Fi 4 (802.11n, 2009), with the compressed Block Ack | Wi-Fi 4 (802.11n), but small (inner frame ≤ 4,095 bytes); practical from Wi-Fi 5 on |
| What it packs | Several packets inside one MAC frame | Several complete MAC frames in one transmission | Several A-MSDUs, each a complete MAC frame, in one transmission |
| Checksums (FCS) | One for all the packets | One per frame | One per A-MSDU |
| Header overhead | Lowest: one MAC header, one security header | Highest: a MAC header, security header and delimiter per packet | Low |
| What an error costs | Everything in the frame is resent | Only the damaged frames are resent (the Block Ack says which) | Only the damaged A-MSDUs are resent |
| Needs | Both sides to support it and agree a maximum size; a normal ACK | A Block Ack agreement set up first (ADDBA) | A Block Ack agreement that allows A-MSDUs |
| Pros | Least header overhead; less work for the radio and CPU (one frame for many packets); great for bundling small packets like TCP ACKs | Robust on noisy links; very long transmissions possible; each frame can be encrypted, checked and retried on its own | Combines both: few headers and little processing, with errors limited to one small A-MSDU |
| Cons | One bad bit loses every packet; limited to about 11 KB; its "A-MSDU present" flag was abused in the 2021 FragAttacks, fixed by stricter checks and SPP A-MSDU | More header bytes per packet; the Block Ack agreement adds setup; the receiver must buffer and reorder | More complex to schedule; big A-MSDUs bring back the error cost, so they're kept to 2–3 packets |
| Used today | Not on its own: every Wi-Fi 5/6/7 data transmission is an A-MPDU | Always, in Wi-Fi 5 and later | Common on fast links, with A-MSDUs of 2–3 packets |