AAL2
Asynchronous Transfer Mode Adaption Layer Type 2, ATM Adaption Layer Type 2.
AAL2: ATM's adapter for voice and low-speed data
AAL2 is the second adaptation layer in the ATM (Asynchronous Transfer Mode) protocol stack, designed to carry voice, video, and low-speed data traffic across ATM networks. Where ATM itself handles the physical movement of fixed-size 53-byte cells through a network, AAL2 sits between the application layer and ATM, breaking incoming streams into cell payloads and reassembling them on the other end. It was standardized by the ITU-T to handle real-time, connection-oriented services that tolerate small delays but require guaranteed delivery.
AAL2 differs fundamentally from its predecessor AAL1 and sibling AAL5. AAL1 targets constant-bit-rate streams like uncompressed video; AAL5 handles data that arrives in variable-length chunks. AAL2 occupies the middle ground, accepting variable-length packets from sources like voice codecs (which may compress speech into 10 or 20 millisecond frames) and multiplexing multiple low-bandwidth channels into single ATM connections. This multiplexing efficiency made AAL2 the choice for telecom operators building VoIP backbones in the 1990s and 2000s.
Structure and cell format
An AAL2 cell contains a 3-byte header and 48 bytes of payload. The header includes a channel identifier (CID), length indicator (LI), and sequence number (SN). Because multiple logical channels can share one ATM virtual circuit, the CID field identifies which user or service the data belongs to. The length field tells the receiver how many bytes of actual payload are present; this matters because AAL2 does not pad short frames to fill the cell. A voice frame from a codec might occupy only 10 bytes; AAL2 can pack multiple such frames into a single 48-byte payload space and still track their boundaries.
Reassembly at the far end requires the receiver to buffer incoming AAL2 cells, extract the individual service data units (SDUs) using the length indicators, and hand them to the waiting application. Timing matters: if a cell is lost due to network congestion, the receiver must detect it (via the sequence number) and discard the rest of that channel's data in the current cell to prevent out-of-order delivery. This makes AAL2 less forgiving than AAL5 but more responsive than AAL1 for delay-sensitive applications.
AAL2 saw real deployment in carrier networks during the late 1990s, particularly in mobile backhauling and voice-over-ATM systems. However, the rise of IP-based infrastructure and Ethernet switching shifted demand away from ATM altogether. Today, AAL2 remains in legacy telecom equipment and embedded systems but has largely been displaced by RTP (Real-time Transport Protocol) over IP networks. Understanding AAL2 remains valuable for anyone maintaining or troubleshooting older circuit-switched voice systems, DSL backhaul networks, or hybrid ATM-Ethernet environments still operating in some carrier backbones.