A thorough technical explanation of "recharge" as a telecommunications infrastructure concept — exploring how subscriber service entitlements are provisioned, how online charging systems track usage, and how policy control functions enforce and restore data access in mobile networks.
In the context of mobile network infrastructure, the term "recharge" refers to the process by which a subscriber's service entitlements are replenished or reset within the operator's charging and policy systems. This is fundamentally a network provisioning event — a set of coordinated updates that propagate through multiple backend systems to modify a subscriber's active service profile, restore data quota, and update Quality of Service (QoS) policies.
The word "recharge" is widely used across the telecommunications industry, particularly in regions where prepaid mobile services are predominant, including much of the Middle East, Asia, Africa, and Latin America. Technically, however, the concept of replenishing service entitlements applies equally to postpaid subscribers through billing cycle resets, add-on bundle activations, and plan upgrades — all of which trigger the same underlying network provisioning mechanisms.
A recharge event in network infrastructure triggers a coordinated update across the Business Support System (BSS), Online Charging System (OCS), Unified Data Management (UDM) or Home Subscriber Server (HSS), and the Policy Control Function (PCF) or Policy and Charging Rules Function (PCRF) — collectively restoring a subscriber's data quota, validity period, and QoS entitlements.
To understand recharge at a technical level, it is first necessary to understand the operational support architecture that governs subscriber management in a mobile network. This architecture is typically divided into Business Support Systems (BSS) and Operations Support Systems (OSS), each serving distinct but complementary roles.
BSS encompasses the software systems that manage the commercial and customer-facing aspects of a telecom operator's business. Key BSS components relevant to recharge include the Billing System, which processes charges and generates invoices; the CRM (Customer Relationship Management) system, which holds subscriber account records; the Product Catalogue, which defines the parameters of available service plans and add-on bundles; and the Revenue Management system, which tracks monetary balances for prepaid subscribers.
OSS covers the technical systems that manage network resources, service fulfilment, and network inventory. When a recharge event is processed by the BSS, the OSS handles the translation of commercial plan parameters into technical provisioning instructions that are sent to the network elements — the UDM, OCS, and PCF.
Telecommunications support system stack — a recharge event propagates from BSS through OSS to network layer systems
The Online Charging System (OCS) is the real-time charging infrastructure that tracks subscriber data usage and enforces quota limits as data is consumed. Unlike an offline charging system, which generates billing records for post-processing, the OCS operates in-session — it directly controls whether data packets are allowed to pass through the network based on the subscriber's remaining quota balance.
The OCS operates using the Diameter Gy interface (in 4G/LTE) or the 5G equivalent CHF (Charging Function using the Nchf service-based interface). When a subscriber starts a data session, the UPF (or PGW in 4G) sends a credit request to the OCS. The OCS grants a quota — a specific number of bytes or a time-based credit — and the UPF tracks usage against this grant. When the quota is nearly exhausted, the UPF sends another request for more credit. If the OCS finds that the subscriber has no remaining balance, it returns a termination action, causing the UPF to block or throttle further data traffic.
The fundamental message exchange in online charging is the Credit Control Request (CCR) and Credit Control Answer (CCA), defined in RFC 4006 and extended by 3GPP specifications. Three types of CCR exist: CCR-Initial (sent at session start), CCR-Update (sent to request additional quota or report usage), and CCR-Terminate (sent when the session ends). The OCS responds with a CCA containing the granted quota, validity time, and any result codes indicating the account status.
In prepaid models, the subscriber maintains a monetary balance or a bundle of service entitlements that are consumed as services are used. A recharge event replenishes this balance. The OCS enforces the balance in real-time — when the balance reaches zero, the OCS instructs the network to restrict or terminate the data session immediately.
In postpaid models, the subscriber's entitlements are reset at the end of the billing cycle (typically monthly). This is technically equivalent to a recharge — the UDM quota is reset, the OCS grants fresh credit, and the PCF updates QoS policies from throttled back to full speed. Data overage charges may be applied based on recorded usage data.
When a recharge event occurs — whether triggered by a prepaid top-up, bundle purchase, or postpaid cycle renewal — a coordinated sequence of system updates takes place across the operator's infrastructure. The following describes this flow in technical detail.
The recharge event is triggered by an external action recorded in the BSS Revenue Management system. The BSS validates the event, confirms the plan parameters from the Product Catalogue, and initiates a service activation/modification request to the OSS Service Fulfilment system. This triggers a downstream cascade of provisioning updates.
The OSS sends an update to the Unified Data Management (UDM) in 5G or the Home Subscriber Server (HSS) in 4G/LTE. This update modifies the subscriber's service profile — specifically the subscribed data quota, plan type, AMBR (Aggregate Maximum Bit Rate) limits, and the validity period of the entitlements. The UDM stores this as the subscriber's authoritative service record.
The Online Charging System (OCS) receives the recharge parameters — typically the new data volume (e.g., 10 GB), the validity window (e.g., 30 days), and any time-of-day restrictions. The OCS updates its internal subscriber account record. If the subscriber has an active data session, the OCS may proactively send a re-authorisation request (RAR) to the network to immediately restore the subscriber's full data entitlement without requiring a session restart.
The Policy Control Function (PCF) in 5G, or the Policy and Charging Rules Function (PCRF) in 4G, receives notification of the subscriber's updated entitlements. It generates new Policy and Charging Control (PCC) rules reflecting the restored data quota and full-speed QoS parameters. These rules are pushed to the Session Management Function (SMF) via the N7 interface (5G) or the Gx interface (4G).
The SMF translates the new PCC rules into Packet Detection Rules (PDRs) and Forwarding Action Rules (FARs) and sends them to the User Plane Function (UPF) via the N4 interface (PFCP protocol). The UPF immediately applies the new enforcement rules — removing any throttling or blocking actions that were in place due to quota exhaustion. Data now flows at full speed through the UPF.
If the subscriber's data session was terminated (rather than merely throttled) due to quota exhaustion, the subscriber's device must re-establish the PDU session. The AMF and SMF coordinate this re-establishment, with the UDM providing the updated subscription data. The new session inherits the fresh quota from the OCS and the restored QoS from the PCF.
At the application layer (outside the 3GPP core network), the operator's BSS may send an SMS, push notification, or in-app message to the subscriber confirming the successful recharge and the new entitlement details. This is a BSS/application function, separate from the network-level provisioning that has already been completed in the preceding steps.
Once a recharge has been processed and a data quota is active, the OCS tracks usage in real-time as the subscriber consumes data. The granularity and accuracy of this tracking depends on the operator's OCS implementation and the rating mechanism used.
The most common form of data quota tracking is volume-based charging, where each byte of uplink and downlink data transferred through the UPF is metered and reported to the OCS. The UPF maintains per-subscriber counters and reports usage in the CCR-Update messages sent to the OCS. The OCS deducts the reported usage from the subscriber's quota balance and returns a new credit grant (or a termination action if the quota is exhausted).
Modern OCS systems implement quota threshold notifications — when the subscriber's remaining balance drops below a configured threshold (e.g., 20% remaining, or specific absolute values like 500 MB, 100 MB, 10 MB), the OCS triggers a notification event. This event can be used to send an SMS or push notification to the subscriber alerting them of their low balance, and can also initiate pre-emptive throttling in some operator configurations.
| Quota State | OCS Action | UPF/PCF Action | Subscriber Experience |
|---|---|---|---|
| Full Quota | Grant full credit block | Apply full-speed AMBR | Maximum available speed |
| Low Quota (<20%) | Grant reduced credit block, trigger notification | Continue full-speed enforcement | Normal speed, low balance alert |
| Quota Exhausted | Return termination action or throttle grant | Apply reduced AMBR or block session | Throttled speed or no data access |
| Post-Recharge | Grant new full credit block via RAR | Remove throttle, restore full AMBR | Full speed restored immediately |
It is important to distinguish between the network-infrastructure concept of recharge described on this page and the various application-level or user-interface concepts that use the same word. In network infrastructure, recharge is a provisioning event that modifies subscriber records in the UDM, OCS, and PCF systems. This is entirely separate from any financial transaction processing, payment gateway interaction, or user-interface workflow.
The network layer receives only the outcome of any upstream processing — a provisioning instruction that says, in effect, "subscriber X now has Y gigabytes of data valid for Z days at speed tier W." How that instruction was generated — whether through an operator's app, a self-service portal, an automated cycle renewal, or any other mechanism — is irrelevant to the network infrastructure, which simply processes the provisioning instruction and updates its systems accordingly.
Understand the 5G core network functions — AMF, SMF, UPF, PCF — that recharge events interact with.
Learn how PDU sessions, QoS flows, and policy enforcement govern real-time data access on mobile networks.
Deep-dive into how data access is provisioned, managed, and metered across 4G and 5G network generations.