ATM Adaptation Layer type 5

Description

ATM Adaptation Layer type 5 (AAL5) is a specific protocol layer within the broader ATM (Asynchronous Transfer Mode) protocol stack, defined by the ITU-T and adopted by 3GPP for early releases. Its primary function is to adapt higher-layer protocols, particularly connectionless protocols like IP (Internet Protocol), to the underlying ATM layer, which operates using fixed-size 53-byte cells (48-byte payload plus 5-byte header). AAL5 resides above the ATM layer and below layers such as the Service-Specific Convergence Sublayer (SSCS) or directly below IP. It is classified as a 'simple and efficient' AAL (SEAL), optimized for data traffic where error recovery and sequencing are handled by higher layers.

Architecturally, AAL5 consists of two sublayers: the Segmentation and Reassembly (SAR) Sublayer and the Convergence Sublayer (CS). The Convergence Sublayer further divides into the Common Part Convergence Sublayer (CPCS) and the Service-Specific Convergence Sublayer (SSCS), though AAL5 often operates with a null SSCS for basic data transport. The CPCS is responsible for preparing the Protocol Data Unit (PDU) from the higher-layer packet. It adds a CPCS trailer to the end of the PDU, which includes a Length field (indicating the size of the CPCS payload), a CRC-32 checksum for error detection over the entire CPCS PDU, and a CPCS User-to-User indication field. The entire structure—payload plus trailer—must be padded to be an integer multiple of 48 bytes to align with ATM cell payloads.

The Segmentation and Reassembly Sublayer then fragments this prepared CPCS PDU into a series of 48-byte segments. Each segment is placed into the payload field of a standard ATM cell. All cells for a single CPCS PDU, except the final one, have the Payload Type (PT) field in the ATM header set to indicate a cell that is not the last in a sequence. The final cell carries the PT bit set to '1', signaling the end of the AAL5 frame. This mechanism allows the receiver to identify the frame boundary without explicit length fields in every cell. The receiver's SAR sublayer collects cells belonging to the same Virtual Channel Connection (VCC) until it detects the end-of-frame cell. It then passes the reassembled byte stream to the CPCS, which uses the CRC-32 to verify data integrity and the Length field to strip off any padding and deliver the original higher-layer packet.

In the 3GPP architecture, AAL5 was specified as a transport option for several critical interfaces, particularly in the packet-switched (PS) domain during the 3G era (UMTS). It was used over Iu-PS (between RNC and SGSN), Gn (between SGSNs, and between SGSN and GGSN), and Gi (between GGSN and external packet data networks) interfaces when these were based on ATM physical infrastructure. Its role was to provide a standardized, efficient method for carrying IP-based control plane (e.g., GTP-C) and user plane (e.g., GTP-U) traffic over the reliable, connection-oriented ATM backbone networks that were prevalent in early 3G deployments. AAL5's design minimized protocol overhead compared to earlier AAL types like AAL3/4, making it well-suited for the bursty, variable-length nature of IP traffic in mobile core networks.

Purpose & Motivation

AAL5 was created to address the specific need for efficiently transporting connectionless, variable-length data packets (primarily IP) over connection-oriented ATM networks, which were the dominant high-speed backbone technology in the late 1990s and early 2000s. Prior to AAL5, ATM adaptation layers like AAL3/4 were more complex, incorporating sequence numbers, multiplexing identifiers, and per-cell CRC, which introduced significant overhead for data applications that did not require these features. The telecommunications industry, including 3GPP for its initial UMTS specifications, needed a leaner adaptation method to make effective use of ATM's quality of service (QoS) and switching capabilities for data services without unnecessary protocol bloat.

The historical context is the convergence of telephony and data networks. ATM was selected for early 3G core networks due to its strengths in supporting multiple traffic types with guaranteed QoS, which aligned with the vision for multimedia mobile services. However, the core user payload was increasingly IP-based. AAL5 solved the mismatch by providing a simple segmentation mechanism with end-to-end error checking (via CRC-32) but leaving retransmission and flow control to higher-layer protocols like TCP. This design philosophy recognized that for data traffic, efficiency and lower processing overhead were more critical than the robust, cell-level error recovery mechanisms in AAL3/4.

By adopting AAL5, 3GPP enabled equipment vendors and operators to leverage existing ATM infrastructure investments for building early 3G packet cores. It provided a standardized, reliable transport for GTP tunnels carrying user data and signaling, ensuring interoperability between network elements from different vendors. While later 3GPP releases migrated towards all-IP transport (Ethernet/IP), eliminating the need for ATM adaptation, AAL5 was a crucial bridging technology that allowed the industry to deploy high-speed packet-switched mobile data services on the network technology available at the time.

Key Features

• Efficient segmentation of variable-length packets into 48-byte ATM cell payloads
• Low overhead compared to AAL3/4, using only an 8-byte trailer per CPCS PDU
• Strong error detection via a 32-bit CRC (CRC-32) computed over the entire CPCS PDU
• Use of the ATM cell header Payload Type bit to delimit frame boundaries without explicit length fields in every cell
• Support for connection-oriented transport over ATM Virtual Channel Connections (VCCs)
• Alignment padding to ensure the CPCS PDU is a multiple of 48 bytes for efficient cell segmentation

Evolution Across Releases

Defining Specifications