World Wide Web

Description

Within the 3GPP architectural framework, the World Wide Web is not a network component but a dominant application-layer service that fundamentally shapes the design and capabilities of the mobile packet core. It is modeled as a key service in the IP Multimedia Subsystem (IMS) and Packet-Switched (PS) domain, requiring the network to provide reliable IP connectivity, session management, and policy control. The 3GPP specifications define service requirements for WWW access, including necessary Quality of Service (QoS) parameters for interactive and background traffic classes, security mechanisms for data integrity, and charging models for data usage.

The operation of WWW services relies on the underlying capabilities of the Evolved Packet Core (EPC) or 5G Core (5GC). Key network functions such as the Packet Data Network Gateway (PGW) or User Plane Function (UPF) provide the anchor point for IP connectivity to the public Internet, where web servers reside. The Policy and Charging Rules Function (PCRF) or Policy Control Function (PCF) enforces policies that may prioritize or shape web traffic. The Session Management Function (SMF) in 5GC manages the Protocol Data Unit (PDU) sessions that carry HTTP/HTTPS traffic.

From a protocol perspective, WWW traffic primarily uses HTTP and its secure variant HTTPS, which operate over TCP/IP. The mobile network's role is to transport these IP packets efficiently between the User Equipment (UE) and the internet. This involves radio resource scheduling in the RAN, tunneling through the core network using protocols like GTP-U, and applying traffic flow templates for filtering. The performance of WWW services is a critical metric for user experience, directly influenced by network latency, throughput, and reliability as specified in 3GPP service requirements.

Purpose & Motivation

The inclusion of WWW in 3GPP standards from Release 99 onward was driven by the explosive growth of internet-based services and the need to integrate mobile telecommunications with the global Internet. Prior to 3G, mobile networks were primarily circuit-switched, optimized for voice and low-speed data, which was ill-suited for the bursty, asymmetric nature of web browsing. The standardization of WWW service requirements ensured that 3GPP networks could natively support IP-based applications, making mobile devices true internet endpoints.

This formal recognition motivated the development of key packet-switched architectural elements like the GPRS core network and later the EPS. It created concrete technical requirements for always-on connectivity, dynamic IP address allocation, and efficient handling of numerous simultaneous, short-lived TCP connections typical of web pages. By defining WWW as a service, 3GPP ensured that network planning, QoS frameworks, and charging systems were designed to accommodate its traffic patterns, which remain a dominant portion of mobile data today.

Key Features

• Defines service requirements for hypertext document access over IP
• Drives need for interactive and background QoS class support
• Influences design of policy control for data service differentiation
• Requires support for standard Internet protocols (HTTP, HTTPS, TCP/IP)
• Forms basis for traffic model assumptions in network dimensioning
• Integrates with IMS for enriched web-based communication services

Evolution Across Releases

Defining Specifications