Common Part Convergence Sublayer

Description

The Common Part Convergence Sublayer (CPCS) is a fundamental component of the transport network layer within the 3GPP-defined Iub interface architecture, which connects the Radio Network Controller (RNC) and Node B in UMTS networks. As part of the ATM adaptation layer type 2 (AAL2) protocol stack, CPCS operates above the Service Specific Convergence Sublayer (SSCS) and below the Segmentation and Reassembly (SAR) sublayer. Its primary function is to provide a standardized interface for higher-layer protocols to access AAL2 transport services, abstracting the underlying ATM cell transmission details while ensuring reliable data delivery.

Architecturally, CPCS resides within the AAL2 protocol layer defined in ITU-T Recommendation I.363.2 and adapted by 3GPP for mobile network interfaces. It handles the encapsulation of user data from various SSCS entities into CPCS Protocol Data Units (PDUs) that are then passed to the SAR sublayer for segmentation into ATM cells. The CPCS PDU structure includes a header containing length indication and sequence number fields, a payload field for user data, and a trailer with padding and cyclic redundancy check (CRC) for error detection. This structured approach allows multiple logical connections (AAL2 channels) to share a single ATM virtual circuit through statistical multiplexing.

In operation, CPCS receives service data units from SSCS entities that have been classified by service type (such as voice, circuit-switched data, or packet-switched data). It adds the necessary CPCS header and trailer information, performs length indication to delineate PDU boundaries, and implements sequence numbering to maintain packet order. The CRC mechanism in the trailer provides error detection capabilities, allowing corrupted packets to be identified and potentially retransmitted by higher layers. CPCS also handles padding to ensure the PDU aligns with the requirements of the SAR sublayer, which segments the CPCS PDUs into 48-byte ATM cell payloads.

Within the 3GPP network architecture, CPCS plays a critical role in the Iub interface's user plane transport, particularly for dedicated channels (DCH) and common channels. It enables efficient bandwidth utilization by allowing multiple low-bit-rate services (like voice calls) to share the same transport resources through AAL2 multiplexing. The standardization of CPCS in 3GPP specifications ensures interoperability between equipment from different vendors and provides a consistent transport mechanism for various radio access bearer services, from circuit-switched voice to packet-switched data connections.

Purpose & Motivation

The Common Part Convergence Sublayer was created to address the need for efficient transport of multiple low-bit-rate services over ATM-based interfaces in early 3G UMTS networks. Before its standardization, different services required separate transport connections, leading to inefficient bandwidth utilization and complex network management. CPCS, as part of the AAL2 protocol stack, enabled statistical multiplexing of multiple services over a single ATM virtual circuit, significantly improving transport efficiency for voice and other delay-sensitive traffic with variable bit rates.

Historically, the development of CPCS was motivated by the requirements of UMTS Release 99, which needed to support both circuit-switched and packet-switched services over a common transport infrastructure. Traditional ATM adaptation layers like AAL1 and AAL5 were inefficient for the mixed traffic patterns expected in mobile networks—AAL1 was optimized for constant bit rate services but wasted bandwidth for variable rate traffic, while AAL5 provided efficient packet transport but introduced excessive delay for real-time services. CPCS within AAL2 provided the optimal compromise, offering low delay for real-time services while maintaining efficient bandwidth utilization through multiplexing.

The creation of CPCS specifically for 3GPP networks addressed the limitations of previous transport approaches by providing a standardized mechanism that could handle the diverse QoS requirements of mobile services. It solved the problem of transporting multiple concurrent services (voice calls, video calls, and data sessions) from different users over the same physical interface between RNC and Node B. By defining a common convergence layer, 3GPP ensured vendor interoperability and enabled network operators to optimize their transport infrastructure for the specific traffic patterns characteristic of mobile networks, where many low-bit-rate connections need to be efficiently aggregated over high-capacity backbone links.

Key Features

• Provides common transport services for multiple SSCS entities over AAL2
• Enables statistical multiplexing of multiple low-bit-rate services on single ATM VCC
• Implements sequence numbering for packet order preservation
• Includes CRC-based error detection in CPCS PDU trailer
• Supports variable length PDUs with length indication field
• Handles padding to meet SAR sublayer requirements

Evolution Across Releases

Defining Specifications