AAL2

ATM Adaptation Layer type 2

Protocol
Introduced in R99
AAL2 is a protocol layer that adapts variable-bit-rate, delay-sensitive traffic like voice and video for transport over an Asynchronous Transfer Mode (ATM) network. It enables efficient multiplexing of multiple low-bit-rate connections into a single ATM Virtual Channel Connection (VCC), optimizing bandwidth usage. It was crucial for early 3GPP UMTS networks where ATM was the primary transport technology for the lu and lub interfaces.

Description

ATM Adaptation Layer type 2 (AAL2) is a critical protocol defined by the ITU-T and adopted by 3GPP for the transport of real-time, variable-bit-rate traffic in the early releases of the UMTS network architecture. It operates as a sublayer within the ATM protocol stack, sitting between the service-specific higher layers (e.g., voice codecs, signaling protocols) and the core ATM layer. Its primary function is to segment and reassemble the data streams from multiple users or applications into the fixed-size cells (53-byte) used by ATM, while preserving timing relationships and minimizing packetization delay, which is essential for conversational services.

Architecturally, AAL2 is divided into two sublayers: the Common Part Sublayer (CPS) and the Service Specific Convergence Sublayer (SSCS). The CPS is the core, responsible for multiplexing multiple AAL2 connections, called Channel Identifiers (CIDs), into a single ATM Virtual Channel Connection (VCC). It does this by packing variable-length CPS-Packets from different sources into the 48-byte payload of ATM cells. Each CPS-Packet consists of a 3-byte header (containing the CID, Length Indicator, and User-to-User Indication) and a payload of up to 45 or 64 bytes (depending on the mode). This packing mechanism, known as mini-cell multiplexing, allows for very low delay as cells can be sent before being completely filled, unlike AAL1 or AAL5, making it highly efficient for sporadic, low-bit-rate traffic.

Within the 3GPP context, AAL2 was specified as the primary transport for user plane traffic (e.g., AMR voice, circuit-switched data) and control plane signaling across critical interfaces in the UTRAN. Specifically, it was used on the lub interface between the Node B and the Radio Network Controller (RNC), the lur interface between RNCs, and the lu-CS interface between the RNC and the Core Network's Circuit-Switched domain (MSC). The SSCS part of AAL2 was further specialized for these roles; for example, the Service Specific Connection Oriented Protocol (SSCOP) and Service Specific Coordination Function (SSCF) were used for signaling transport, while a null SSCS or a segmentation and reassembly SSCS was often used for user data. This layered approach provided a reliable, low-latency pipe that was fundamental to the Quality of Service (QoS) guarantees of early 3G services.

AAL2 works by establishing AAL2 connections end-to-end between network elements. When a user plane data packet (like a voice frame) arrives from the higher layer, the AAL2 layer at the source (e.g., Node B) encapsulates it into a CPS-Packet with a specific CID corresponding to that user's bearer. Multiple such CPS-Packets from different CIDs are then sequentially packed into the payload of an ATM cell. The cell is transmitted once a timer expires or the payload is nearly full, ensuring a compromise between delay and efficiency. At the receiving end (e.g., RNC), the CPS extracts the CPS-Packets based on the CID and length indicator, reassembles the original data units, and delivers them to the correct higher-layer entity. This process, managed by the AAL2 signaling protocol (Q.2630.1/Q.2150.1 in 3GPP), allowed for dynamic establishment and release of these low-bandwidth channels, aligning perfectly with the call setup and release procedures in UMTS.

Purpose & Motivation

AAL2 was created to address the specific challenge of efficiently transporting bursty, low-bit-rate, and delay-sensitive traffic over ATM networks, which were the dominant high-speed backbone technology in the late 1990s and early 2000s. Prior approaches like AAL1 were designed for constant-bit-rate traffic (e.g., E1/T1 circuit emulation) and were inefficient for voice, which has silent periods, while AAL5 was optimized for large, bursty data packets but introduced significant packetization delay unsuitable for real-time communication. The telecommunications industry, moving towards integrated networks, needed a method to carry compressed voice (e.g., using AMR codecs) and other real-time services without wasting the fixed bandwidth of ATM cells.

In the historical context of 3GPP Release 99, which standardized the first UMTS networks, ATM was selected as the transport technology for the new UTRAN due to its proven reliability, traffic management, and QoS capabilities. However, to make this viable for the myriad of low-rate radio access bearers, an adaptation layer was required that could statistically multiplex hundreds of voice calls onto a single ATM VCC while maintaining strict delay bounds. AAL2 solved this by allowing partial filling of cells and interleaving packets from multiple sources, dramatically improving bandwidth utilization compared to dedicating a full VCC per call. This efficiency was economically critical for mobile operators deploying 3G infrastructure.

Thus, the primary motivation for adopting AAL2 in 3GPP was to enable cost-effective, high-quality transport for circuit-switched services over a packet-oriented ATM core, bridging the gap between traditional telephony requirements and modern packet-switched backbone networks. It provided the necessary traffic engineering to support the QoS classes defined for UMTS, particularly the conversational and streaming classes, until the industry's eventual migration towards all-IP transport with technologies like IP over Ethernet in later releases.

Key Features

  • Statistical multiplexing of multiple low-bit-rate connections (CIDs) into a single ATM VCC
  • Low packetization delay via partial cell fill and timer-based transmission
  • Support for variable-size payloads (up to 45/64 bytes) per CPS-Packet
  • 3-byte header per CPS-Packet containing Channel Identifier (CID) and length
  • End-to-end signaling (Q.2630.1) for dynamic connection establishment and management
  • Segmentation and Reassembly capability for service data units larger than CPS-Packet payload

Evolution Across Releases

R99 Initial

Introduced AAL2 as the foundational transport protocol for UTRAN user and control planes. Specified its use on the lub, lur, and lu-CS interfaces for carrying circuit-switched voice (AMR) and data traffic. Defined the 3GPP-specific adaptations and SSCS functions required for interoperability between Node B, RNC, and MSC within the ATM-based network architecture.

Enhanced support for the evolved Core Network architecture with the separation of MSC into MSC Server and Media Gateway (MGW). Refined AAL2 transport requirements and signaling procedures for the lu interface to align with this split, ensuring consistent bearer handling between the RNC and the MGW.

Introduced IP Transport as an alternative to ATM in the UTRAN (Iu, Iub, Iur over IP). While AAL2 remained defined, this release began the transition towards all-IP networks, reducing the long-term centrality of AAL2. Specifications were updated to maintain AAL2 functionality in mixed or legacy transport scenarios.

Further solidified IP transport options. Work focused on interoperability and coexistence of ATM-based AAL2 and IP-based transport (using UDP/IP or RTP/IP). No major new AAL2 features were added, reflecting the industry shift away from ATM.

Continued maintenance of AAL2 specifications for backward compatibility. Enhancements were minimal, with primary development effort directed at High Speed Packet Access (HSPA) and IP-based transport optimizations, marking AAL2 as a legacy technology for existing deployments.

AAL2 specifications were maintained but functionally frozen. From Release 8 onwards, with the introduction of LTE and its all-IP, flat architecture based on Ethernet and IP transport (GTP-U), AAL2 became obsolete for new radio access networks. It remained specified only to support legacy UMTS/HSPA networks still utilizing ATM transport.

Defining Specifications

SpecificationTitle
TS 21.905 3GPP TS 21.905
TS 23.146 3GPP TS 23.146
TS 23.910 3GPP TS 23.910
TS 25.401 3GPP TS 25.401
TS 25.412 3GPP TS 25.412
TS 25.413 3GPP TS 25.413
TS 25.420 3GPP TS 25.420
TS 25.422 3GPP TS 25.422
TS 25.424 3GPP TS 25.424
TS 25.425 3GPP TS 25.425
TS 25.426 3GPP TS 25.426
TS 25.430 3GPP TS 25.430
TS 25.434 3GPP TS 25.434
TS 25.931 3GPP TS 25.931
TS 26.102 3GPP TS 26.102
TS 26.202 3GPP TS 26.202
TS 29.414 3GPP TS 29.414
TS 29.415 3GPP TS 29.415