AAL5

AAL5 is the adaptation layer that sits between user data and the ATM (Asynchronous Transfer Mode) cell structure, converting variable-length packets into fixed 53-byte cells for transmission and reassembling them at the destination. It handles the mismatch between how applications generate data in irregular chunks and how ATM networks require 53-byte cells: 48 bytes of payload plus 5 bytes of header.

AAL5 wraps outgoing data with a trailer containing a length field and CRC-32 checksum, then pads the result to a multiple of 48 bytes before segmentation into cells. The receiving end extracts this trailer from the last cell to recover the original message length and verify integrity. This approach, called message mode operation, makes AAL5 suitable for connection-oriented protocols like TCP/IP running over ATM, as well as for LAN emulation and circuit emulation of video or voice streams.

AAL5 became the dominant adaptation layer in deployed ATM networks during the 1990s and early 2000s, particularly in carrier backbones and enterprise WANs. Its efficiency compared to earlier AAL3/4 (which carried its own length and CRC in each cell, wasting 4 bytes per cell) and its simplicity made it the default choice. ATM switches did not need to understand AAL5 semantics; they simply moved cells along virtual circuits defined at layer 2.

The CRC-32 catches single-cell corruption but cannot correct it, so any detected error forces the entire message to be discarded and retransmitted at a higher layer. Padding overhead varies: a 100-byte packet becomes 144 bytes (three 48-byte payloads plus trailer), adding 44 percent; a 1500-byte Ethernet frame becomes 1536 bytes. Long messages suffer less relative overhead.

AAL5 requires that cells belonging to the same message arrive in order and without interleaving from other messages on the same virtual circuit. This constraint simplified hardware but limited multiplexing flexibility. As IP over ATM declined and Ethernet dominated, AAL5 infrastructure was gradually retired, though implementations remain in legacy carrier networks and in some industrial real-time systems where deterministic cell delivery is valued.