How Mobile Data Systems Work

Contents

01Mobile Data Architecture
02SIM Authentication
03Packet Routing
04Data Availability
05Charging Systems
06Recharge Concept
07Policy Enforcement
08System Summary

Section 01

Mobile Data Architecture Overview

Mobile data systems are among the most complex distributed computing infrastructures in existence. To understand how data travels from a webpage server to your smartphone screen, it helps to understand the layered architecture through which that data passes — a series of distinct but tightly integrated subsystems, each serving a specific function in the overall connectivity chain.

At the highest level, a modern mobile network (4G LTE/5G) consists of three major domains: the User Equipment (UE) — the device itself; the Radio Access Network (RAN) — the wireless infrastructure connecting devices to the network; and the Core Network — the intelligent packet-handling and service management layer that connects the RAN to the internet.

Mobile Network Architecture — 4G LTE Reference Model

User Domain

Mobile Device (UE)

SIM / UICC Card

Modem / Baseband Chip

RF Antenna Module

Radio Access Network

eNodeB (Base Station)

Backhaul Link

Mobility Mgmt Entity

S-GW (Serving Gateway)

Core Network (EPC)

P-GW (Packet Gateway)

HSS (Subscriber Store)

PCRF (Policy Control)

OCS (Online Charging)

This architecture has been refined over multiple network generations. While 5G introduces a more flexible Service-Based Architecture (SBA) with cloud-native network functions, the fundamental principle — radio access feeding into a policy-aware core — remains consistent. Understanding these components individually allows us to then understand how data flow and access management actually function in practice.

Section 02

SIM Authentication and Network Registration

Before any data can flow, a mobile device must prove its identity to the network. This is accomplished through the SIM (Subscriber Identity Module) card — a secure cryptographic element storing the subscriber's IMSI (International Mobile Subscriber Identity) and a set of cryptographic keys used for authentication.

When a device powers on or enters network coverage, it initiates an Attach Procedure with the nearest base station. The network's Mobility Management Entity (MME) queries the Home Subscriber Server (HSS) to retrieve authentication vectors for that subscriber. A challenge-response protocol (EPS-AKA — Evolved Packet System Authentication and Key Agreement) is used to mutually authenticate the device and the network.

Attach Request

The device broadcasts an Attach Request containing its IMSI (or a temporary GUTI) to the nearest eNodeB, which forwards it to the MME.

Authentication Vector Retrieval

The MME queries the HSS (Home Subscriber Server) via the S6a interface using Diameter protocol to fetch the subscriber's authentication vectors.

Challenge-Response (EPS-AKA)

The MME issues an Authentication Request (RAND + AUTN) to the device. The SIM uses its stored key (Ki) to compute an expected response (XRES) and returns RES.

Security Mode & Bearer Setup

If RES matches XRES, authentication succeeds. NAS and AS security contexts are established, and default EPS bearers are activated for data transport.

Key Concept

The HSS also stores the subscriber's service profile — including their subscription tier, allowed data services, and current plan status. This profile is used downstream by the PCRF to determine policy rules for the session.

Section 03

Packet Routing Through the Core Network

Once authenticated and attached, a device's data traffic flows through a carefully managed packet-routing path. In LTE networks, this path traverses two gateways: the Serving Gateway (S-GW) and the Packet Data Network Gateway (P-GW).

The S-GW functions as the local mobility anchor — it handles handovers between base stations and manages the user plane data path within the operator's network. The P-GW is the policy enforcement and routing node that connects the mobile network to external packet data networks (PDNs), including the public internet.

Data Packet Flow — User Plane Path

Device (UE)

LTE Modem

eNodeB

Base Station

S-GW

Serving GW

P-GW / PCEF

Policy Enforcer

Internet

Public PDN

The P-GW performs Deep Packet Inspection (DPI), Quality of Service (QoS) enforcement, and crucially — quota enforcement. Every packet that passes through the P-GW is counted against the subscriber's data allocation. This accounting happens in real time via the Diameter Gy interface connecting the P-GW to the Online Charging System.

Section 04

Understanding Data Availability

Data availability is the operational state in which a subscriber's account is authorized to transmit and receive data packets across the network. This state is not permanently fixed — it is a dynamic property that the network actively monitors and can change based on usage, time, or plan status.

The concept of data availability maps directly to what users experience as their "mobile data balance". When a user queries their balance on a prepaid plan, they are effectively querying the OCS quota counter — the remaining byte allocation stored in the charging system for their IMSI.

States of Data Availability

Data availability exists on a spectrum of operational states, each carrying different implications for how the network treats the subscriber's traffic:

State	OCS Quota	PCEF Policy	User Experience
Fully Available	> 20% remaining	Full access granted	Normal speeds, all services active
Low Balance	1–20% remaining	Warning threshold triggered	Notification sent, full speed maintained
Fair Use Throttled	Near zero	Speed restriction applied	Reduced speeds (e.g., 128kbps)
Exhausted	Zero / Negative	Block or redirect enforced	Data access suspended or portal redirect
Restored (Post-Recharge)	Reset to plan maximum	Full access re-granted	Immediate restoration of data services

Technical Note

The transition between states is managed in real time. When a subscriber's quota drops to zero, the OCS issues a Quota Exhaustion Indication to the P-GW via the Gy interface. The P-GW applies the operator-configured exhaustion policy within milliseconds — making the state change nearly instantaneous from the user's perspective.

Section 05

Mobile Charging Systems Architecture

The charging infrastructure in mobile networks is a sophisticated real-time computing system responsible for tracking data consumption, applying tariffs, and enforcing financial policy rules. Modern 3GPP-compliant networks implement two parallel charging systems:

Online Charging System (OCS)

Real-time quota management for prepaid subscribers. The OCS communicates with the P-GW via the Diameter Gy interface, issuing quota grants and receiving usage reports in near real-time. When quota is exhausted, the OCS immediately instructs the network to modify the subscriber's session.

Diameter Gy Real-time Prepaid Quota-based

Offline Charging System (OFCS)

Batch-mode usage recording for postpaid subscribers. The OFCS collects Charging Data Records (CDRs) from network elements and processes them for end-of-period billing. Policy enforcement operates separately via the PCRF rather than a real-time quota counter.

CDR-based Batch Processing Postpaid Diameter Gz

In addition to these charging systems, the Policy and Charging Rules Function (PCRF) serves as the central intelligence layer. The PCRF defines the rules governing how data traffic is treated — including speed limits, service priorities, and access permissions. It communicates with the P-GW via the Gx interface, pushing policy updates dynamically as subscriber states change.

Section 06

How Recharge Relates to Connectivity (Conceptual)

The term "recharge" — also referred to as a top-up, credit replenishment, or data renewal — refers to the process by which a prepaid subscriber's data allocation is restored within the operator's charging system. From a systems perspective, a recharge event is a billing transaction that produces a network policy change.

It is important to understand that recharge is not a technical action performed on the radio network, the device, or the SIM card. It is an administrative and financial transaction that updates records in the operator's Business Support System (BSS) — which then propagates changes to the technical network systems.

The Recharge Event Chain

Payment Transaction Initiated

A recharge transaction is initiated through a payment channel. The payment platform validates the transaction and communicates with the operator's BSS (Business Support System).

BSS Subscriber Record Update

The BSS updates the subscriber record, augmenting or resetting the data quota associated with the subscriber's IMSI/MSISDN. This update is logged in the CRM and billing platform.

OCS Quota Restoration

The BSS triggers an OCS quota update via provisioning interfaces. The OCS resets the subscriber's quota counter to the new balance — either a fixed data amount or a time-based plan reset.

PCEF Policy Modification

The OCS communicates the new quota to the P-GW/PCEF. If the subscriber was previously blocked, the PCEF policy is updated to remove the block and restore full data access.

Subscriber Notification

The BSS triggers an SMS notification to the subscriber's MSISDN confirming the transaction. The device's data session — if interrupted — may automatically resume or require a manual reconnect.

Key Insight: Recharge as a Policy Trigger

A recharge event is, at its core, a policy trigger. The money paid does not flow into the radio network — it flows into a billing system. The billing system updates a database record. That database record change is what causes the network to re-enable data access. This is why recharge effects are almost instantaneous: no physical changes occur, only data records are updated in interconnected software systems.

Section 07

Policy and Charging Enforcement

The Policy and Charging Enforcement Function (PCEF) is the gatekeeper of data access in the mobile core network. Implemented within the P-GW, the PCEF executes policy rules received from the PCRF and applies them to every data session in real time.

Policy rules (called PCC Rules — Policy and Charging Control Rules) define:

Service Data Flow (SDF) Templates: Which IP flows the rule applies to (e.g., all traffic, video streaming only, etc.)
Gate Status: Whether the flow is permitted (OPEN) or blocked (CLOSED)
QoS Parameters: Maximum Bitrate (MBR), Guaranteed Bitrate (GBR), and QoS Class Identifier (QCI)
Charging Key: Links the traffic flow to a specific quota bucket in the OCS

When a subscriber's data balance reaches zero, the PCRF pushes an updated PCC Rule to the PCEF with the gate status set to CLOSED for data traffic. This is the technical mechanism behind what users experience as "data access suspended." The restoration that follows a recharge event is simply the PCRF pushing a new rule with the gate status set back to OPEN.

Section 08

System Summary

Mobile data systems are sophisticated layered architectures where radio access, authentication, packet routing, and policy enforcement work in concert to deliver internet connectivity to mobile devices. The key concepts covered in this guide can be summarized as:

Architecture

Three-domain model: User Equipment → Radio Access Network → Evolved Packet Core. Each domain has distinct functions but communicates through standardized 3GPP interfaces.

Authentication

SIM-based cryptographic identity proof via EPS-AKA, validated against the HSS. This establishes the subscriber's identity and retrieves their service profile before any data flows.

Data Availability

A dynamic state managed by the OCS (quota) and PCRF (policy). When quota is exhausted, the PCEF blocks data. When restored via recharge, data access resumes within seconds.

Recharge Concept

A billing-system transaction — not a physical network change — that restores quota in the OCS, triggering a PCEF policy update that re-enables data access for the subscriber.

Explore Network Infrastructure Connectivity Explained