Understanding Data Limits

What Are Mobile Data Limits?

A mobile data limit — commonly referred to as a data cap, data allowance, or data quota — is a finite quantity of data (measured in megabytes or gigabytes) that an operator allocates to a subscriber for a defined period. Once this allocation is consumed, the network applies a policy that restricts or modifies the subscriber's data access until the allocation is renewed or augmented.

Data limits exist because mobile spectrum — the radio frequency resource that carries wireless data — is finite and shared among thousands of simultaneous users in each cell. Unlike fixed broadband where a dedicated physical connection runs to each premises, mobile network capacity must be divided dynamically among all active users. Data limits are a primary mechanism by which operators manage spectrum utilisation and ensure fair capacity distribution.

From a purely technical standpoint, a data limit is a quota counter stored in the Online Charging System (OCS). This counter is decremented in real time as the subscriber consumes data, and triggers policy changes at defined thresholds. The subscriber's subjective experience of having a "data balance" is a high-level representation of this OCS quota counter.

How Data Metering Works

Data metering is the process by which the network counts the volume of data consumed by each subscriber. This counting happens at the Policy and Charging Enforcement Function (PCEF) — implemented within the Packet Data Network Gateway (P-GW) — which sits at the boundary between the mobile core network and the public internet.

Every IP packet that traverses the P-GW is counted. The PCEF maintains per-service data flow (SDF) counters, tracking bytes transmitted in both uplink and downlink directions. These counters are reported to the OCS via the Diameter Gy interface using Credit Control Request (CCR) messages.

The Credit Control Cycle

Quota Enforcement Mechanisms

When a subscriber's quota reaches zero, the OCS returns a Quota Exhaustion Indication to the PCEF. The PCEF then applies one of several operator-configured enforcement actions, depending on the subscriber's plan and the operator's policy design:

Throttling vs. Hard Cutoff

Two primary enforcement models exist for managing quota exhaustion: throttling (speed reduction) and hard cutoff (complete suspension). Each has distinct technical implementations and user experience implications.

Fair Use Policy (FUP) Systems

Many operators implement Fair Use Policies (FUP) — particularly on nominally "unlimited" mobile plans — as a mechanism for managing network congestion and preventing a small number of high-consumption subscribers from degrading the experience of the majority.

Under a FUP, a subscriber may consume data without restriction up to a defined threshold (e.g., 40GB per month). Beyond this threshold, the PCRF applies a reduced-speed policy — typically throttling to 1–2 Mbps — for the remainder of the billing period. The subscriber retains data access throughout; only the speed is reduced.

FUP enforcement follows the same technical mechanism as standard quota enforcement: the OCS tracks consumption, and the PCRF pushes updated PCC Rules to the PCEF at the defined threshold. The distinction is that FUP typically triggers throttling rather than a hard block, reflecting the more permissive nature of unlimited plan designs.

Balance Restoration: The Recharge System

When a subscriber's data quota is exhausted and access is suspended or throttled, the mechanism for restoring full data availability is called a recharge or top-up. From a systems perspective, this is a billing and provisioning event — not a technical radio network event — that updates the subscriber's quota in the OCS.

The restoration process is remarkably fast in modern networks because the update path — from payment platform to BSS to OCS to PCEF — is entirely digital and highly automated. A successfully processed recharge transaction typically restores data access within 5 to 30 seconds in well-configured systems.

For a more comprehensive technical breakdown of the recharge event chain, including the BSS–OCS–PCEF interface interactions in detail, see our Core Concepts: Recharge and Connectivity guide.