Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Protocol

SNDCP

Sub-Network Dependent Convergence Protocol

Protocol →

SNDCP is the Sub-Network Dependent Convergence Protocol in GPRS and UMTS that handles data compression, segmentation, and protocol discrimination between the mobile station and SGSN to optimize radio interface efficiency.

Introduced
R97
Where
Radio Access Network
Specifications
14 specs
Also in
Core Network, Services, Management
SNDCP Description Purpose What changed Family Neighbours Detected Changes Specifications

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.

What changed in its specifications

The latest release-to-release comparison of specifications that define SNDCP. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 21.905 →
TS 23.060Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 23.060: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 23.060 →

Technology family

Radio user-plane layer 2 protocols · Radio Access Network

  1. Phase 1 RLP
  2. R97 LLC, SNDCP
  3. R99 UTRA MAC, UTRA PDCP, UTRA RLC
  4. Rel-8 E-UTRA MAC, E-UTRA PDCP, E-UTRA RLC
  5. Rel-15 NR MAC, NR PDCP, NR RLC, NR SDAP

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 7 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

R97 introduced

Introduced in R97 (release dating of the term; no individual change cited).

R99 specification text

The SNDCP specification (24.065) first appears in R99, defining SNDCP's services, functions, entities and its use of LLC and SM, alongside SNDCP handling in 23.060 procedures.

  • “The present document provides the description of the Subnetwork Dependent Convergence Protocol (SNDCP) for the General Packet Radio Service (GPRS).” TS 24.065 v3.1.0
  • “SNDCP shall perform the following functions (see Figure 3):” TS 24.065 v3.1.0
  • “The SNDCP entity handles the service functions provided by the SNDCP layer.” TS 24.065 v3.1.0
Rel-4 specification text

TS 44.065 first appears in this release as the SNDCP specification for GPRS, defining its functions, services, entities and N-PDU handling between the MS and the SGSN.

  • “The present document provides the description of the Subnetwork Dependent Convergence Protocol (SNDCP) for the General Packet Radio Service (GPRS).” TS 44.065 v4.3.0
  • “SNDCP shall perform the following functions (see figure 4):” TS 44.065 v4.3.0
  • “For unacknowledged data transfer, the SNDCP shall delete an N‑PDU immediately after it has been delivered to the LLC layer.” TS 44.065 v4.3.0
Rel-5 specification text

SNDCP XID negotiation changed in 44.065: SNDCP version number is now set to 1 with a new version negotiation clause, and unknown-algorithm rejection is no longer split by MS or SGSN.

  • “An SNDCP entity supporting this version of SNDCP shall set the version number in the originating SNDCP XID block to 1.” TS 44.065 v5.2.0
  • “6.8.1a Negotiation of SNDCP version” TS 44.065 v5.2.0
  • “NOTE: The current version of SNDCP is 1. The default value for the version number is 0.” TS 44.065 v5.2.0
Rel-6 specification text

SNDCP in TS 44.065 gained ROHC header compression support, feedback N-PDU handling and renumbering, and revised XID reset and recovery behaviour on LLC (re-)establishment.

  • “Robust Header Compression (ROHC) is a framework for header compression, on top of which compression schemes can be defined for the compression of various protocol headers.” TS 44.065 v6.6.0
  • “any feedback N-PDUs shall be removed from the buffered N‑PDUs.” TS 44.065 v6.6.0
  • “if the old XID indicator is set, keep the SNDCP XID parameters that were applicable before the receipt of the LL-RESET.indication” TS 44.065 v6.6.0
Rel-8 specification text

Rel-8 specifies that SNDCP acknowledged-mode NSAPIs and SNDCP sequence numbers are not used with S4-SGSNs, and the network must not configure them for E-UTRAN/S4-SGSN interworking.

  • “SNDCP N-PDU numbers are not relevant for S4-SGSNs as the network shall not configure usage of acknowledged mode NSAPIs (SNDCP)” TS 23.060 v8.17.0
  • “SNDCP and GTP sequence numbers are not relevant for a new S4-SGSN if provided by an old Gn/Gp SGSN” TS 23.060 v8.17.0
Rel-13 specification text

SNDCP segmentation limit changed so that SN-PDUs must be no longer than (N201-U – 4) when integrity protection is used, instead of simply N201.

  • “no longer than N201 (no longer than (N201-U – 4), if integrity protection is used)” TS 44.065 v13.1.1

Defining Specifications

3GPP specifications that define or reference SNDCP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 23.060 vj00 GPRS Stage 2 Service Description Rel-19 read
TR 23.923 v300 Mobile IP+ Feasibility Study for UMTS/GPRS R99 read
TS 24.065 v310 GPRS Subnetwork Dependent Convergence Protocol R99 read
TR 26.937 vj00 3GPP PSS Characterization Rel-19 read
TS 27.060 vj00 TE-MT Interworking for Packet Domain Rel-19 read
TS 32.401 vj00 Performance Management Concept & Requirements Rel-19 read
TS 43.129 vj00 PS Handover in GERAN A/Gb and GAN Modes Rel-19 read
TS 43.318 vj00 Generic Access Network (GAN) Stage 2 Rel-19 read
TR 43.902 vj00 GAN Enhancements Feasibility Study Rel-19 read
TS 44.065 vj00 GPRS SNDCP Specification Rel-19 read
TS 44.318 vj00 Generic Access Network (GAN) Interface Procedures Rel-19 read
TS 45.820 vd10 Cellular IoT Low Complexity Study Rel-13 read
TS 52.402 vj00 GSM Performance Management Measurements Rel-19 read