Hypertext Transfer Protocol

Description

The Hypertext Transfer Protocol (HTTP) is a stateless application-layer protocol within the Internet protocol suite, defined by the IETF (RFC 9110 et seq.) and ubiquitously referenced in 3GPP specifications. It operates on a client-server model, where a client (typically a web browser on User Equipment) sends requests to a server, which then returns responses. In a 3GPP network, HTTP messages are carried as payload within IP packets. These IP packets are transported over the network's data bearers, which are established and managed by the core network's Packet Data Network (PDN) connectivity procedures—using protocols like GTP between the gateway (PGW/UPF) and the radio access network.

HTTP works through a series of request methods (GET, POST, PUT, DELETE, etc.) and status codes (200 OK, 404 Not Found). A GET request for a web page initiates a TCP connection (or uses an existing one via HTTP/1.1 persistent connections or HTTP/2 streams), which is transported over the mobile network's IP layer. The server's response contains headers with metadata and the message body, often an HTML document. The protocol itself is unaware of the underlying mobile network intricacies; however, the network implements various functions around HTTP traffic. These include Policy and Charging Control (PCC) to apply rules based on traffic detection, Deep Packet Inspection (DPI) for service awareness, and Traffic Flow Templates (TFTs) for bearer binding.

3GPP specifications reference HTTP in numerous contexts: as the transport for configuration protocols like OMA DM for device management, for service capability exposure (SCEF/NEF), in the Ut interface for provisioning, and as the protocol for numerous northbound APIs (e.g., Nnrf, Nudm in 5GC) which are based on HTTP/2. The shift to a Service-Based Architecture (SBA) in the 5G Core Network explicitly uses HTTP/2 with JSON payloads for communication between network functions (NFs). Furthermore, HTTP is central to content delivery optimization techniques discussed in 3GPP, such as transparent caching and video streaming adaptation (DASH), which aim to improve efficiency and user experience over the radio interface.

Purpose & Motivation

HTTP is integral to 3GPP standards because mobile networks are designed to provide IP connectivity, and the web (via HTTP) constitutes a massive portion of IP traffic. The protocol's purpose within 3GPP is twofold: first, as the carrier of end-user application data (web browsing, video streaming, app updates), and second, as a protocol for network internal and management interfaces. Its inclusion ensures the network architecture can efficiently handle request/response traffic patterns, manage sessions, apply appropriate quality of service, and charge for data usage.

The historical context is the convergence of telecommunications and the internet. Early mobile data services used specialized protocols. The adoption of HTTP signaled a shift towards an all-IP network that seamlessly integrates with the internet. This addressed limitations of previous circuit-switched data and proprietary protocols, which were inefficient for bursty web traffic. Standardizing around HTTP allowed for a vast ecosystem of internet applications to work on mobile devices without modification. In later releases, using HTTP/2 for 5G core interfaces solved problems of signaling efficiency and flexibility compared to earlier binary telecom protocols (like Diameter), enabling a more agile, cloud-native network architecture.

Key Features

• Client-server request/response model with defined methods (GET, POST)
• Stateless protocol, with state managed via cookies or sessions at the application layer
• Uses TCP for reliable transport, with HTTP/3 introducing QUIC over UDP
• Supports content negotiation, caching directives, and persistent connections
• Foundation for RESTful APIs and the 5G Service-Based Architecture (SBA)
• Extensible via headers and can carry any type of digital content as payload

Evolution Across Releases

Defining Specifications