Answers
What Is an Online Charging System (OCS) in Telecom?
An online charging system (OCS) is the part of a mobile network that decides, in real time, whether a subscriber can use a service and charges for it as it is used. Before a data session, call or SMS goes through, the network asks the OCS for permission. The OCS checks the subscriber's balance or allowance, reserves a slice of it, and grants that slice as quota. As the quota is consumed, the network reports usage and asks for more, and the OCS debits the account. When the balance runs out, the OCS stops granting quota and the service is stopped or redirected.
The architecture is defined by 3GPP, mainly in TS 32.240 (charging architecture) and TS 32.296 (the OCS itself).
How the OCS charging loop works
A data session on a 4G network is the clearest example.
- Session starts. The packet gateway, acting as the charging trigger, sends an initial credit-control request to the OCS.
- OCS checks and reserves. The OCS looks up the subscriber's account, prices the service, and reserves units against the balance, for example 50 MB.
- Quota granted. The OCS returns the granted quota. The gateway lets traffic flow until that quota is close to used.
- Update. The gateway reports what was actually consumed and requests more. The OCS debits the used units and grants a new reservation if the balance allows it.
- Session ends. The gateway sends a final report. The OCS debits the last usage and releases anything reserved but unused.
What happens when the balance runs out
If the update step finds no remaining balance, the OCS returns a final unit indication and the gateway ends or redirects the session, often to a top-up page.
This exchange runs over Diameter credit control. The interface is called Gy for data from the packet core and Ro for IMS and other service elements. The same logic applies to voice minutes and to other session types.
Some services are charged as single events rather than sessions. An SMS is the usual case: the OCS either debits immediately (immediate event charging) or reserves first and confirms after delivery (event charging with unit reservation).
What is inside an OCS
Vendors package these differently, but the split between authorising usage, pricing it and holding the balance is consistent.
| Function | What it does |
|---|---|
| Online Charging Function (OCF) | Handles credit-control requests from the network. Split into a session-based function (data sessions, calls) and an event-based function (SMS, content purchases). |
| Rating Function (RF) | Works out the price of the requested units using the subscriber's tariff. |
| Account Balance Management Function (ABMF) | Holds the subscriber's balances, allowances and counters. |
| Charging Gateway Function (CGF) | Optional. Collects charging data records for online-charged subscribers, for operators that also want records for billing, reporting or reconciliation. |
OCS, offline charging and billing are different things
Online charging affects service delivery. The OCS can refuse or cut off a session in real time.
Offline charging does not. The network records usage in charging data records after the fact and sends them to the billing domain in files. Nothing is blocked while usage happens.
Billing is a separate system again. It takes rated usage, recurring charges, discounts and taxes, and produces invoices and account statements. An OCS keeps balances correct as usage happens; it does not issue bills.
A common misconception is that an OCS is only for prepaid. Prepaid depends on it, but postpaid plans use it too, for hard spending limits, data caps, fair-use throttling triggers and bill-shock alerts. IoT connectivity uses it to stop a faulty device from running up unlimited usage.
OCS and the PCRF
The OCS and the Policy and Charging Rules Function (PCRF) work together but do different jobs. The OCS answers "can this subscriber pay for this, and how much is left?" The PCRF answers "how should this traffic be treated?", setting speed, priority and access rules. When a balance or allowance crosses a threshold, the OCS can tell the PCRF, which then changes the policy, for example slowing a subscriber to a lower speed once a monthly allowance is used.
Does an MVNO run its own OCS?
It depends on the MVNO model. An MVNO that relies heavily on its host network often uses the host's charging, with the host enforcing balances and caps. An MVNO that controls more of its own core and customer experience typically runs its own OCS, connected to the host network's gateways over the credit-control interfaces described above. Running your own OCS gives full control over plan design, balance logic and real-time offers, at the cost of more integration and operational responsibility.
In 5G standalone networks, the OCS role is taken over by the Charging Function (CHF), which combines online and offline charging behind a service-based interface. The OCS concepts described here, quota grants, reservation and balance control, still apply.
Related Pages
FAQs
Is an OCS the same as a billing system?
No. The OCS controls and charges usage as it happens. The billing system produces invoices. Many BSS platforms include both, but they are separate functions.
What protocol does an OCS use?
In 4G and earlier networks, Diameter credit control, over the Gy interface for packet data and Ro for IMS and service elements. Older circuit-switched networks also used CAMEL. 5G standalone networks use HTTP-based service interfaces to the CHF instead.
Why does real-time charging matter for revenue?
Because it closes the gap between usage and charging. With offline charging, usage that cannot be collected later, from a prepaid customer with no balance or a device that should have been capped, is lost revenue. An OCS refuses that usage before it happens.