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.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (121 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the HTTP function introduced specific procedures for creating resources via HTTP POST for the Npcf_SMPolicyControl and Npcf_AMPolicyControl services, along with detailed HTTP error handling procedures and the use of the HTTP response code 204 for QoS notifications. It also added support for background data transfer and clarified the use of HTTP custom headers and the PATCH method. These enhancements standardized the application protocol interactions for service-based interfaces within the core network.
- Using HTTP POST to create resources for the Npcf_SMPolicyControl Service. TS 29.890CR0003
- Using HTTP POST to create resources for the Npcf_AMPolicyControl Service. TS 29.890CR0005
- HTTP Error responses TS 29.508CR0028
- HTTP error handling procedure TS 29.512CR0010
- Backgroud data transfer support TS 29.512CR0065
- HTTP custom headers TS 29.512CR0133
+ 7 more changes
In Release 16, the HTTP function was enhanced to include a message transfer failure notification mechanism. Furthermore, support for background data transfer was added, with accompanying editorial updates to the specification. These additions introduced new procedures for managing the success or failure of data transfer operations.
In Release 17, the primary updates for the HTTP function involved updating the specifications for HTTP Digest Access Authentication and refreshing the normative reference to the underlying HTTP/1.1 protocol. These changes ensured the authentication mechanisms and core protocol references remained current. Additionally, new procedures for analytics and subscription context transfer operations were defined, extending the framework for managing and transferring analytical data.
- Add call transfer for MCPTT private calls TS 23.379CR0229
- MCPTT private call transfer to a functional alias as a target TS 23.379CR0263
- Update of HTTP Digest Access Authentication and reference update for HTTP/1.1 protocol TS 24.109CR0069
- Update of HTTP Digest Access Authentication and reference update for HTTP/1.1 protocol TS 24.141CR0119
- Reference update for HTTP/1.1 protocol TS 24.259CR0055
- Reference update for HTTP/1.1 protocol TS 24.481CR0052
+ 44 more changes
In Release 18, the HTTP function was enhanced to support End-to-end data volume transfer time analytics across several Network Data Analytics Function (NWDAF) services and APIs, including Nnwdaf_EventsSubscription, Nnwdaf_AnalyticsInfo, and Nnwdaf_MLModelProvision. These updates introduced new capabilities for reporting this transfer time with corresponding data volume, support for a list of UEs, and the addition of a confidence attribute to the analytics. Furthermore, the release added protocol description support in the Npcf_SMPolicyControl API and enabled analytics and ML model accuracy context transfer.
- Clarification regarding the protocol used on new reference points TS 23.280CR0313
- Private call transfer between several MCPTT systems TS 23.379CR0313
- Input data support of End-to-end data volume transfer time analytics TS 29.508CR0230
- Updates to support E2E data volume transfer time analytics TS 29.508CR0270
- Protocol description support in Npcf_SMPolicyControl API TS 29.512CR1086
- Protocol description update TS 29.512CR1149
+ 39 more changes
In Release 19, key HTTP enhancements included the introduction of HTTP/2 support for identity management procedures (MCLoc), the addition of a specific HTTP header parameter to extend the registration timer, and alignments for HTTP-3. The release also updated references to obsoleted HTTP standards and defined the use of HTTP status code 422.
- MC Recording procedures using Session Recording Protocol TS 23.280CR0630
- MCLoc HTTP/2 support in identity management specification TS 24.482CR0021
- HTTP status code 422 TS 29.500CR0476
- HTTP header parameter to extend registration timer TS 29.500CR0479
- Providing Expedited Transfer Indication in the PCC rules TS 29.512CR1348
- Update the description for the expedited transfer indicator TS 29.512CR1411
+ 5 more changes
Explore further
Broader topics and technologies where HTTP plays a role.
Defining Specifications
3GPP specifications that define or reference HTTP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TS 22.112 v1800 | USAT Gateway System Specification | Rel-8 |
| TS 22.242 vj00 | DRM Service Requirements | Rel-19 |
| TS 23.057 vj00 | Mobile Execution Environment (MExE) Specification | Rel-19 |
| TS 23.125 v1700 | Flow Based Charging Architecture | Rel-7 |
| TS 23.140 v1600 | MMS Non-Realtime Service Definition | Rel-6 |
| TS 23.141 vj00 | Presence Service Stage 2 Architecture | Rel-19 |
| TS 23.179 vd50 | MCPTT Functional Architecture | Rel-13 |
| TS 23.207 vj00 | End-to-End QoS Framework for GPRS | Rel-19 |
| TS 23.280 vk10 | Common Architecture for Mission Critical Services | Rel-20 |
| TS 23.281 vk10 | MCVideo Functional Architecture and Flows | Rel-20 |
| TS 23.379 vk00 | MCPTT Functional Architecture | Rel-20 |
| TS 23.722 vf10 | Common API Framework (CAPIF) for 3GPP Northbound APIs | Rel-15 |
| TS 23.802 v1700 | Enhanced End-to-End QoS Architecture | Rel-7 |
| TS 24.109 vj00 | HTTP Digest AKA & GAA Stage 3 | Rel-19 |
| TS 24.141 vj00 | Presence Service Protocol Details | Rel-19 |
| TS 24.147 vj00 | IMS Conferencing Protocol Details | Rel-19 |
| TS 24.229 vj50 | IMS call control protocol based on SIP and SDP | Rel-19 |
| TS 24.259 vj00 | Personal Network Management (PNM) Protocol Details | Rel-19 |
| TS 24.322 vj00 | IMS Tunneling over Restrictive Networks | Rel-19 |
| TS 24.423 v850 | PSTN/ISDN Simulation Services XCAP Protocol | Rel-8 |
| TS 24.481 vj20 | Mission Critical Services (MCS) group management | Rel-19 |
| TS 24.482 vj00 | Mission Critical Services Identity Management | Rel-19 |
| TS 24.484 vj30 | MCS Configuration Management | Rel-19 |
| TS 24.549 vj10 | SEAL Network Slice Capability Enablement Protocol | Rel-19 |
| TS 24.623 vj00 | XCAP Protocol for Supplementary Services | Rel-19 |
| TS 24.819 v1700 | IMS Services via Fixed Broadband Access | Rel-7 |
| TS 24.841 v1600 | Presence Service IP Multimedia Subsystem | Rel-6 |
| TR 24.930 vj00 | IMS Session Setup Signalling Flows | Rel-19 |
| TS 26.117 vj00 | 5G Media Streaming Speech/Audio Capabilities | Rel-19 |
| TS 26.118 vj00 | Virtual Reality Media Formats | Rel-19 |
| TS 26.142 vj00 | 3GPP TS 26.142: Dynamic and Interactive Multimedia Scenes (DIMS) | Rel-19 |
| TS 26.234 vj00 | 3GPP PSS Protocols and Codecs Specification | Rel-19 |
| TS 26.244 vj00 | 3GPP File Format (3GP) Specification | Rel-19 |
| TS 26.247 vj00 | 3GPP Progressive Download & DASH over HTTP | Rel-19 |
| TS 26.501 vj30 | 5G Media Streaming (5GMS) Architecture | Rel-19 |
| TS 26.517 vj10 | 5G MBS User Service Protocols and Formats | Rel-19 |
| TS 26.802 vj20 | Multicast Enhancements for 5G Media Streaming | Rel-19 |
| TS 26.804 vj10 | 5G Media Streaming Extensions Study | Rel-19 |
| TS 26.849 vc10 | MBMS Operation on Demand (MooD) | Rel-12 |
| TS 26.851 vb20 | Enhancements to Multimedia (EMM) for PSS, MMS, MBMS | Rel-11 |
| TR 26.857 vi00 | Technical Report on Media Service Enablers | Rel-18 |
| TR 26.905 vj00 | Study on Mobile 3D Video Services | Rel-19 |
| TR 26.926 vj00 | Traffic Models & Quality Evaluation for Media/XR in 5G | Rel-19 |
| TR 26.927 vj00 | AI/ML in 5G Media Services Study | Rel-19 |
| TR 26.928 vj00 | Study on eXtended Reality (XR) in 5G | Rel-19 |
| TR 26.937 vj00 | 3GPP PSS Characterization | Rel-19 |
| TR 26.938 vj00 | DASH Deployment Guidelines for 3GPP Networks | Rel-19 |
| TR 26.953 vj00 | Study on Service Interactivity for Streaming & Download | Rel-19 |
| TR 26.955 vj00 | Video Codec Analysis for 5G Services | Rel-19 |
| TR 26.956 vj01 | Beyond 2D Video Formats & Codecs Study | Rel-19 |
| TR 26.998 vj00 | 5G AR/MR Glasses Integration Study | Rel-19 |
| TS 29.116 vj00 | REST-based protocol for xMB reference point | Rel-19 |
| TS 29.201 vj00 | RESTful Rx Interface for AF-PC Communication | Rel-19 |
| TS 29.433 v1811 | ETSI TISPAN Endorsement of 3GPP Cx/Dx Interfaces | Rel-8 |
| TS 29.500 vj50 | 5GC Service Based Architecture Specification | Rel-19 |
| TS 29.508 vj40 | 5G Session Management Event Exposure Service | Rel-19 |
| TS 29.512 vj40 | 5G Session Management Policy Control Service | Rel-19 |
| TS 29.520 vj40 | 5G Network Data Analytics Services Stage 3 | Rel-19 |
| TS 29.521 vj40 | 5G Binding Support Management Service Stage 3 | Rel-19 |
| TS 29.523 vj20 | 5G Policy Control Event Exposure Service | Rel-19 |
| TS 29.524 vj00 | 5G Cause Code Mapping Specification | Rel-19 |
| TS 29.525 vj40 | 5G UE Policy Control Service Stage 3 | Rel-19 |
| TS 29.817 vc10 | Study on XML-based Rx interface for PCC | Rel-12 |
| TS 29.890 vg00 | CT3 5G System Technical Report | Rel-16 |
| TS 29.891 vg00 | CT4 Aspects of 5G System Phase 1 | Rel-16 |
| TS 31.112 v1800 | USAT Interpreter System Architecture | Rel-8 |
| TS 32.102 vj00 | Telecom Management Physical Architecture Framework | Rel-19 |
| TS 32.158 vk00 | Management and Orchestration REST Solution Sets | Rel-20 |
| TS 32.296 vj00 | Online Charging System (OCS) Architecture | Rel-19 |
| TS 32.316 vj00 | Generic IRP Management Solution Set Definitions | Rel-19 |
| TS 32.317 v910 | Generic IRP management SOAP Solution Set | Rel-9 |
| TS 32.583 vj00 | HNB OAM&P Procedure Flows for Type 1 Interface | Rel-19 |
| TS 32.593 vj00 | HeNB OAM&P Procedure Flows for Type 1 Interface | Rel-19 |
| TS 32.808 v1800 | Common User Profile Storage Framework | Rel-8 |
| TS 32.821 v1900 | SON OAM Architecture for Home NodeB | Rel-9 |
| TS 32.824 v900 | SOA and IRP Gap Analysis | Rel-9 |
| TS 32.866 vf00 | REST, HTTP, JSON for Management Interfaces | Rel-15 |
| TS 33.141 vj00 | Security for Presence Service (Ut reference point) | Rel-19 |
| TS 33.222 vj00 | Secure HTTP Access in GAA | Rel-19 |
| TS 33.823 vc20 | GBA Web Browser Integration Study | Rel-12 |
| TS 33.835 vg10 | Study on authentication and key management for apps | Rel-16 |
| TR 37.901 vf10 | UE Application Layer Data Throughput Performance | Rel-15 |
| TR 37.976 vj00 | MIMO OTA Test Methodology Study | Rel-19 |
| TR 37.977 vj00 | MIMO OTA Test Methodology | Rel-19 |
| TS 43.802 vc00 | GERAN Enhancements for Mobile Data Applications | Rel-12 |
| TR 43.901 vj00 | Generic Access to A/Gb Interface Feasibility Study | Rel-19 |