Sub-Network Dependent Convergence Protocol

Description

The Sub-Network Dependent Convergence Protocol (SNDCP) is the concrete protocol specification that realizes the functions of the SubNetwork Dependent Convergence (SNDC) layer. It is a peer-to-peer protocol operating between the Mobile Station (MS) and the Serving GPRS Support Node (SGSN) in GPRS and UMTS networks. Defined across a vast array of 3GPP specifications (e.g., TS 23.060, 24.065, 44.065), SNDCP provides the detailed mechanisms for adapting network layer protocols to the underlying Logical Link Control (LLC) layer and the radio interface.

Architecturally, SNDCP sits atop the LLC layer and below network layer protocols like IP. It manages multiple SNDCP contexts, each linked to an active Packet Data Protocol (PDP) context. The protocol's operation is centered on the processing of Network layer Protocol Data Units (N-PDUs). Key components of the SNDCP protocol include the compression entities, the segmentation/reassembly function, and the protocol control logic. The compression entity can implement multiple compression algorithms, such as V.42bis for general data compression and specific header compression schemes (e.g., for TCP/IP headers). These algorithms are negotiated during PDP context activation. The segmentation function breaks down an N-PDU, after possible compression, into SNDCP Data Units that fit the Maximum Transmission Unit (MTU) supported by the underlying LLC layer.

The protocol works through the exchange of SNDCP PDUs, which consist of a header and a payload. The SNDCP header contains critical control information, including the Network Layer Protocol Identifier (NLPI), which identifies the protocol of the encapsulated N-PDU (e.g., IPv4, IPv6), and a Data Compression Protocol (DCP) field indicating the compression algorithm used. For segmented PDUs, the header includes sequence numbers and more flags to allow correct reassembly at the receiver. The process flow begins when the network layer submits an N-PDU. SNDCP selects the appropriate context, applies negotiated compression, segments the data if necessary, prepends the SNDCP header, and passes the SNDCP-PDU to the LLC layer. On the receiving side, SNDCP uses the NLPI to route the decompressed and reassembled N-PDU to the correct network layer entity. This entire process is transparent to the upper layers and is crucial for maintaining efficiency and reliability across the radio link, which has higher latency and lower bandwidth compared to fixed networks.

Purpose & Motivation

SNDCP was created to provide a standardized, implementable protocol for the convergence functions required in GPRS. While SNDC defined the architectural layer and its responsibilities, SNDCP provides the exact packet formats, state machines, and procedures needed for vendors to build interoperable mobile stations and network equipment. The problem it solves is the lack of a detailed protocol to efficiently map arbitrary network traffic onto the GPRS transmission mechanisms.

Its development was motivated by the need for a robust protocol that could handle the heterogeneity of user data and optimize performance. Prior to GPRS, data services over cellular used circuit-switched connections or simple packet protocols without sophisticated convergence features. SNDCP introduced mandatory and optional compression techniques to tackle the overhead of network protocol headers, which is significant for small packets common in web browsing and messaging. The segmentation function addresses the mismatch between typical IP packet sizes (e.g., 1500 bytes) and the much smaller radio blocks (e.g., a few hundred bits). By standardizing these procedures in SNDCP, 3GPP ensured that different manufacturers' devices and networks could work together seamlessly to deliver efficient packet data services, enabling the mobile data revolution. It laid the groundwork for the always-on internet connectivity that later evolved into HSPA and LTE.