Mobile Internet Fundamentals

What Is Mobile Internet?

Mobile internet refers to internet access delivered through a cellular mobile network rather than through a physical wired connection. Instead of Ethernet cables or fibre optic lines running to a fixed location, mobile internet uses radio frequency signals transmitted between your device and a base station to carry data.

From the perspective of the applications you run, mobile internet is functionally identical to any other internet connection — your browser makes HTTP requests, your apps communicate with their servers, and DNS lookups resolve domain names to IP addresses. The underlying transport mechanism, however, is fundamentally different from fixed broadband and involves a complex series of radio, authentication, and policy systems described throughout this guide.

The mobile internet operates at Layer 3 (IP layer) of the OSI model, just like any internet connection. What differs is everything below Layer 3 — the radio access layer, the bearer management, and the policy enforcement mechanisms described in our Core Systems Guide.

Mobile Internet vs. Fixed Broadband

While both deliver internet access via the IP protocol suite, mobile and fixed broadband differ significantly in their physical transmission medium, latency characteristics, capacity management, and how access is charged and managed.

The volume-based charging model of mobile internet is perhaps the most practically significant difference for users. Because mobile spectrum is a finite shared resource managed by the operator's policy system, data consumption is metered and quota-gated — concepts explored in depth in our Understanding Data Limits guide.

APN Configuration Explained

The Access Point Name (APN) is one of the most fundamental — yet least understood — configuration parameters in mobile internet. The APN tells the mobile network which external network (Packet Data Network) to connect your device to, and which P-GW to use for routing your traffic.

When a device initiates a Packet Data Network Connection (PDN Connection) — which happens automatically on attach — it includes an APN in the request. The MME selects the appropriate P-GW based on this APN, and the P-GW establishes the data bearer to the corresponding external network.

IP Address Assignment on Mobile Networks

When a P-GW establishes a PDN context, it assigns an IP address to the device. This address is used for all internet communication during that data session. Mobile networks use two mechanisms for IP assignment: dynamic assignment from a P-GW address pool, and static assignment from a pre-provisioned address (used primarily for enterprise subscribers).

Due to the scarcity of IPv4 address space, most mobile operators deploy Carrier-Grade NAT (CGNAT). Under CGNAT, devices receive private IPv4 addresses (e.g., 10.x.x.x or 100.64.x.x), which the P-GW translates to a smaller pool of public IPv4 addresses shared across many subscribers.

IPv6 is increasingly deployed on mobile networks, where each device can receive a unique public IPv6 prefix — eliminating the need for CGNAT and enabling true end-to-end connectivity. Dual-stack configurations (IPv4 + IPv6 simultaneously) are common in modern deployments.

DNS Resolution on Mobile Networks

Domain Name System (DNS) resolution on mobile networks functions similarly to fixed broadband, but with some operator-specific variations. When your device connects to the internet APN, the P-GW typically provides DNS server addresses as part of the PDN Context Activation response.

Operators run their own DNS resolvers, which provide several advantages: lower latency (resolvers are close to the subscriber), traffic visibility for lawful interception compliance, and the ability to apply DNS-based filtering policies. In some jurisdictions, operators are required to block certain domain names at the DNS layer.

Modern devices and applications increasingly use DNS over HTTPS (DoH) or DNS over TLS (DoT) to encrypt DNS queries, bypassing operator DNS resolvers and sending queries directly to services like Cloudflare (1.1.1.1) or Google (8.8.8.8). This has implications for network management and parental control features that rely on DNS inspection.

Data Session Lifecycle

Understanding the full lifecycle of a mobile data session — from device power-on to a completed web request — illustrates how all the components described in this guide work together.