Description
TCP/IP is not a single protocol but a layered suite of protocols that governs all internet communication. In the context of 3GPP, it is the fundamental protocol stack used for data transport over the Packet Switched (PS) domain. The suite is typically described using a four-layer model: the Link Layer (e.g., Ethernet, PPP), the Internet Layer (IP), the Transport Layer (TCP, UDP), and the Application Layer (HTTP, FTP, etc.). The Internet Protocol (IP) is responsible for the logical addressing (IP addresses) and routing of datagrams across different networks. It is a connectionless, best-effort delivery protocol, meaning it does not guarantee delivery, order, or error-checking of packets. The Transmission Control Protocol (TCP), operating at the transport layer, builds upon IP to provide a reliable, connection-oriented, byte-stream service. It establishes a virtual connection between endpoints, sequences data packets, provides flow control, and performs error recovery through acknowledgments and retransmissions. Within a 3GPP network, user equipment (UE) uses TCP/IP to communicate with application servers on the internet or within an operator's IP Multimedia Subsystem (IMS). The Gateway GPRS Support Node (GGSN) in earlier releases, or the Packet Data Network Gateway (PGW) in the Evolved Packet Core (EPC), acts as the interface between the mobile network's internal packet routing and the external IP networks, performing functions like IP address allocation (via DHCP) and policy enforcement. The integration of TCP/IP allows mobile networks to be seamlessly connected to the global internet, supporting a vast array of services from web browsing to real-time communications.
Purpose & Motivation
The purpose of TCP/IP in 3GPP is to provide a standardized, universal, and interoperable method for data communication, enabling mobile networks to connect to and become part of the global Internet. Prior to the full adoption of all-IP architectures, mobile networks like GSM primarily used circuit-switched connections for voice and limited data services (e.g., GPRS), which were inefficient for bursty internet traffic. The motivation for integrating TCP/IP was to leverage the existing, massively successful internet ecosystem, allowing mobile subscribers to access the same services available on fixed networks. It solved the problem of network heterogeneity by providing a common language for communication between vastly different network technologies (e.g., radio access networks and fiber backbones). Its creation was driven by the need for scalable, flexible, and cost-effective data services, moving beyond proprietary or telephony-centric protocols. The adoption of TCP/IP as the core transport protocol was a fundamental shift that enabled the mobile broadband revolution, transforming cellular networks from voice-centric systems to general-purpose data networks.
Classification
Evolution Across Releases
Introduced as the foundational protocol suite for the new all-IP Evolved Packet System (EPS). It was mandated for all user plane data transport, replacing older GPRS tunneling protocols for external connectivity. The architecture centered on the PGW as the IP anchor point, allocating IP addresses to UEs and routing traffic to external IP networks like the internet.
Explore further
Broader topics and technologies where TCP/IP plays a role.
Defining Specifications
3GPP specifications that define or reference TCP/IP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 26.938 vj00 | DASH Deployment Guidelines for 3GPP Networks | Rel-19 |
| TS 32.101 vj00 | Management principles and high-level requirements | Rel-19 |