Connectionless Network Protocol

Description

The Connectionless Network Protocol (CLNP) is an OSI (Open Systems Interconnection) network layer protocol, standardized as ISO/IEC 8473-1, which was adopted within 3GPP specifications for early General Packet Radio Service (GPRS) networks. As a connectionless protocol, CLNP operates by transmitting data in independent packets, or datagrams, each containing complete addressing and control information. This allows each packet to be routed independently through the network based on its destination address, without requiring a prior end-to-end connection setup phase. In the 3GPP context, CLNP was utilized as the network layer protocol within the GPRS backbone, specifically between GPRS Support Nodes (GSNs), to transport user data and signaling messages. It functioned alongside the Connectionless Network Protocol (CLNP) and the Subnetwork Dependent Convergence Protocol (SNDCP) at the network layer, enabling packet-switched communication over the GSM radio access network.

Architecturally, CLNP's role was integral to the GPRS core network, known as the GPRS backbone. This backbone interconnected Serving GPRS Support Nodes (SGSNs) and Gateway GPRS Support Nodes (GGSNs). CLNP packets, encapsulating user data from mobile stations, were routed between these nodes based on Network Service Access Point (NSAP) addresses, which are hierarchical addresses defined in the OSI model. The protocol provided essential services such as segmentation and reassembly for large packets, error detection through checksums, and a time-to-live (TTL) mechanism to prevent indefinite packet looping. It operated over various data link layer technologies, including Frame Relay and Ethernet, which were common in early mobile core networks. The use of CLNP allowed GPRS to offer a true packet-switched service, contrasting with the circuit-switched nature of traditional GSM voice calls.

In operation, when a mobile station initiated a packet data session, the SGSN would encapsulate the data units into CLNP packets. These packets were then forwarded through the GPRS backbone, potentially traversing multiple intermediate nodes, to the GGSN, which acted as the gateway to external packet data networks (PDNs). CLNP's connectionless nature meant that each packet's route could be determined dynamically by intermediate routers based on routing tables and network conditions, offering robustness and flexibility. However, CLNP did not guarantee delivery, order, or error-free transmission; these functions were left to higher-layer protocols, such as the Transport Protocol Class 4 (TP4) in the OSI stack or adaptations in the 3GPP architecture. Over time, as the internet protocol (IP) became ubiquitous, 3GPP evolved to adopt IP (initially IPv4, then IPv6) as the standard network layer protocol, phasing out CLNP due to IP's global dominance and simplified integration with the internet.

Purpose & Motivation

CLNP was introduced in 3GPP Release 4 to provide a standardized, connectionless network layer protocol for the GPRS packet-switched core network. Its creation was motivated by the need to enable mobile packet data services within GSM networks, which were originally designed solely for circuit-switched voice. Prior to GPRS, data services in GSM relied on circuit-switched data connections, which were inefficient for bursty, intermittent data traffic as they dedicated radio resources for the entire session duration, leading to poor resource utilization and higher costs. CLNP addressed this by offering a packet-switched approach, allowing statistical multiplexing of data from multiple users over shared network resources, thereby improving efficiency and enabling new services like mobile internet access.

The adoption of CLNP was driven by its alignment with the OSI reference model, which was influential in telecommunications standardization during the 1990s. It provided a well-defined, international standard for connectionless networking, ensuring interoperability between equipment from different vendors in the GPRS backbone. CLNP solved the problem of transporting packetized data across the core network between GSNs without requiring complex connection establishment procedures, which was suitable for the dynamic and mobile nature of user sessions. However, its purpose was ultimately transitional; as the internet and IP protocol suite gained overwhelming prevalence, the limitations of maintaining a separate OSI-based protocol stack became apparent, including increased complexity and lack of seamless integration with IP-based external networks. This led 3GPP to transition towards IP as the unifying network layer protocol in later releases.

Key Features

• Connectionless datagram service for independent packet routing
• Use of NSAP addresses for hierarchical network addressing
• Segmentation and reassembly of large protocol data units
• Error detection via header checksum for data integrity
• Time-to-live field to prevent packet looping in the network
• Operation over various data link layers like Frame Relay

Evolution Across Releases

Defining Specifications