Online Charging System

Description

The Online Charging System is a real-time charging node in the 3GPP charging architecture. It authorizes service usage before resources are granted and continues to monitor credit availability while a session or transaction is active. In legacy 3GPP architectures, the OCS is typically connected to a Charging Collection Function through the Ro interface and to a Policy and Charging Rules Function or Policy Control Function through the Sy interface. In 5G deployments, the OCS may be represented or fronted by a Charging Function and service-based interfaces, but its core role remains the same: it decides whether a subscriber has sufficient balance or credit for a requested service.

Architecturally, the OCS contains several logical components. A rating engine converts usage events into chargeable units using tariffs, service identifiers, rating groups, and subscriber class rules. A balance manager maintains account balances, service units, and reservation states. A credit-control application handles Diameter Credit Control Application messages, including Credit-Control-Request and Credit-Control-Answer procedures. The system also supports event-triggered reauthorization, unit reservation, final unit handling, and reporting of consumed units. It may interact with a Subscriber Profile Repository or equivalent subscriber data source to retrieve prepaid or postpaid charging profiles.

The operational flow begins when a network node needs to authorize a service. The Charging Collection Function, Policy and Charging Rules Function, or Policy Control Function sends a credit-control request that identifies the subscriber, service, event type, requested units, and charging context. The OCS checks the subscriber profile, applies rating rules, verifies available balance, and reserves units if the request is acceptable. It returns granted units, a validity time, and optional conditions. During the session, the network may send interim requests or reauthorization requests when the validity time expires, the service changes, or the reserved units are exhausted. If the OCS cannot grant additional units, it can instruct the network to terminate, downgrade, or gate the service. At the end of the session, a final request reconciles the actual usage and updates the account balance.

The OCS is important because it converts charging from a post-event accounting function into a real-time control point. It enables prepaid services, credit control for postpaid subscribers, convergent charging across voice, messaging, data, and content, and tight coupling between policy and charging. When integrated with PCC, the OCS can ensure that QoS levels, gating decisions, and charging outcomes are consistent with subscriber entitlements. This supports operator monetization, fraud prevention, and customer control over spending. In modern 3GPP systems, the OCS remains a key element for online charging even as transport interfaces migrate from Diameter-based signaling to service-based HTTP/2 and JSON interactions.

From a standards perspective, the OCS is described in charging specifications such as TS 32.251 and related architecture documents. Its behavior is defined in terms of charging events, service units, credit-control states, and interaction with policy control. The OCS may be deployed as a centralized platform supporting many network nodes, or as a distributed set of charging capabilities embedded in operator systems. Regardless of deployment form, the glossary definition refers to the logical online charging system that performs real-time authorization and balance management for 3GPP services.

Purpose & Motivation

The OCS exists because offline charging alone cannot protect operator revenue or support prepaid services in real time. Traditional charging systems often collected usage records after the fact and settled accounts later. That model works for postpaid billing, but it cannot prevent a subscriber from consuming more than their balance, and it cannot immediately apply credit limits, unit reservations, or spending caps. As mobile data, messaging, and content services grew, operators needed a way to authorize each service usage event while the session was still active.

R99-era packet and charging architectures introduced the online charging concept to address these limitations. The OCS enabled prepaid voice, data, and messaging, as well as credit control for postpaid accounts. It solved problems such as fraud exposure, bill shock, and the inability to offer flexible service plans. By interacting with the Charging Collection Function and policy nodes, the OCS could reserve units, track balance, and instruct the network to stop or modify a service when credit ran out. It also allowed operators to combine multiple services into a single account and to apply real-time promotions, quotas, and parental controls.

In later releases, the motivation expanded to support convergent charging across radio access technologies and service domains. The OCS became a central element of PCC because policy decisions and charging decisions need to be consistent: a subscriber should not receive high QoS if the charging system has not authorized it, and a change in balance should be able to trigger policy updates. In 5G, the need for online charging remains, especially for network slices, edge services, and application-specific pricing, even though the interfaces and deployment models have moved toward service-based architectures.