Internet Protocol Stack

Description

The Internet Protocol Stack (IPS) in 3GPP refers to the complete set of protocol layers, as defined by IETF standards and profiled by 3GPP, that are implemented in User Equipment (UE) and network nodes to support IP-based services. It is not a single protocol but a framework encompassing layers such as the physical layer, data link layer (e.g., PPP, Ethernet adaptations), network layer (IPv4, IPv6), transport layer (TCP, UDP, SCTP), and application layer protocols. The 3GPP specifications, particularly TS 33.108, detail the security and functional requirements for this stack's implementation within the mobile ecosystem.

Architecturally, the IPS is integrated into the Protocol Data Unit (PDU) Session establishment in the 5G Core or PDP Context in the EPC. It works by allowing the UE to request an IP address and negotiate the supported protocol suites with the network. Once established, user plane data is encapsulated according to the stack's layers, traversing the Radio Access Network (RAN), transport network, and core network gateways (like the UPF or PGW) before reaching external data networks. Key components include the IP stack in the UE's modem, the corresponding stack in the serving gateway (e.g., SGW-U/UPF), and the control plane functions (SMF/MME) that manage the session parameters.

Its role is fundamental: it is the conduit for all packet data. Whether for web browsing, video streaming, or IoT telemetry, the IPS provides the standardized 'language' for data exchange. The stack's configuration, including support for IP version (v4/v6), header compression (ROHC), and Quality of Service (QoS) markings, is controlled by the network to optimize performance and resource usage. In essence, the IPS is the technical realization of the 'bearer' concept, translating service requests into actionable data flows across the heterogeneous network infrastructure.

Purpose & Motivation

The Internet Protocol Stack was standardized within 3GPP to facilitate the transition from circuit-switched, voice-centric 2G networks to packet-switched, data-centric 3G and 4G networks. Prior to its formal profiling in 3GPP, early mobile data services used proprietary or limited protocols. The IPS was created to solve the critical problem of interoperability, ensuring that a mobile device from any vendor could connect seamlessly to the global Internet and other IP-based services through any compliant 3GPP network.

The motivation stemmed from the explosive growth of the Internet and the need for mobile networks to become an integral part of it. By adopting and profiling the well-established IETF IP suite, 3GPP avoided reinventing the wheel and leveraged a robust, scalable, and universally understood protocol family. This addressed the limitations of previous approaches, which were often siloed and inefficient for general data services. The IPS enabled the 'always-on' connectivity model, supporting a wide range of applications beyond simple messaging, and laid the groundwork for advanced services like the IP Multimedia Subsystem (IMS). Its specification ensures security considerations, like firewall traversal and trusted IP point-of-presence, are integrated from the start.

Key Features

• Profiles IETF standards (IPv4, IPv6, TCP, UDP) for mobile environments
• Supports dual-stack IP (IPv4v6) operation for transition scenarios
• Integrates with 3GPP-specific mechanisms like PDP Context/PDU Session management
• Enables header compression (ROHC) to save radio resources
• Provides the foundation for all packet data services and IMS
• Defines security architecture interfaces for trusted IP connectivity

Evolution Across Releases

Defining Specifications