AAL

The ATM Adaptation Layer (AAL) is a set of protocols that sits between the ATM core network and the higher-layer services that use it. ATM itself is a fixed-cell switching fabric: it chops all data into 53-byte cells and routes them independently. But real applications need different things. Video streams need low latency and don't care if a few cells drop. File transfers need every byte intact. The AAL's job is to package diverse traffic types into ATM cells on the transmit side and reassemble cells into usable data on the receive side.

Four main variants emerged and remain standardized. AAL1 handles constant-bit-rate services: circuit emulation, DS1/E1 voice, video. It adds a simple header tracking cell sequence and a convergence sublayer that maps timing. AAL2 handles variable-bit-rate real-time traffic like compressed voice and video; it multiplexes multiple logical connections into one ATM connection to save bandwidth. AAL3/4 (unified into a single spec) is used for data services requiring ordered delivery; it adds sequence numbering and error detection. AAL5, the simplest and most widely deployed, just pads the data, appends a CRC, segments into cells, and trusts the network to get the cells through in order.

Why the complexity matters

An ATM cell has 48 bytes of payload and 5 bytes of header. If you're carrying a voice sample that arrives every 125 microseconds, you can't just wait for 48 bytes. AAL1 lets you flush incomplete cells on a clock tick so delay stays predictable. If you're moving a file across a network, you need to know which cells belong to which message and detect corruption; AAL5 adds a per-PDU CRC. Different AALs waste different amounts of bandwidth: AAL1 has per-cell overhead even for small payloads, while AAL5 can pack more efficiently if the application tolerates slight latency variance.

The term 'adaptation layer' reflects the OSI model thinking of the 1980s and 1990s, when ATM was designed as the universal transport. In practice, AAL implementations live in chipsets, driver firmware, and switching hardware. Network operators provisioned separate 'virtual circuits' with different AAL types for voice, video, and data. Errors in AAL implementations, particularly in AAL5 reassembly, caused real operational issues: cells arriving out of order due to network faults could cause the receive side to misalign and corrupt data. Most modern networks have moved away from ATM, but AAL terminology persists in some carrier environments and in legacy equipment documentation.