Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Management

OCS

Online Charging System

Management →

OCS is a 3GPP charging entity that authorizes service usage in real time by evaluating subscriber balances, rating rules, and credit availability before granting resources.

Introduced
Rel-5
Where
Core Network › Evolved Packet Core
Specifications
42 specs
Also in
Services, Management
OCS Description Purpose What changed Family Neighbours Detected Changes Specifications

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.

What changed in its specifications

The latest release-to-release comparison of specifications that define OCS. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 21.905 →
TS 23.003Rel-18 → Rel-19

Rel-19 adds clauses 31.1 to 31.7 to TS 23.003 defining identifier and information structures for Ambient IoT devices and areas, plus new normative references. It also adds SNPN support to ProSe identifiers, including an optional NID part in the PLMN ID and a revised temporary identity length.

Full comparison in TS 23.003 →

Technology family

Charging architecture · Core Network

  1. R99 CDR, CGF
  2. Rel-5 OCS
  3. Rel-6 ABMF, BD, CDF, CTF, EBCF, OCF, OFCS, RF, SBCF
  4. Rel-8 IMS-GWF
  5. Rel-15 CCS, CHF
  6. Rel-16 CEF
  • OCS decomposed into OCF (not stated verbatim in the specifications)

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 12 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

Rel-5 introduced

Introduced in Rel-5 (release dating of the term; no individual change cited).

Rel-6 specification text

The OCS is defined for the first time as the entity performing real-time credit control, covering transaction handling, rating, online correlation and subscriber account balance management, and authorising or declining resource usage.

  • “Online Charging System: the entity that performs real-time credit control. Its functionality includes transaction handling, rating, online correlation and management of subscriber account balances.” TS 32.251 v6.10.0
  • “For each charging event received during the session, the OCS decides whether to authorise the resource usage or whether to decline the request” TS 32.240 v6.4.0
Rel-7 specification text

OCS role in PS-domain online charging was specified: it arms quota re-authorisation triggers, supports tight online/offline interworking and tariff time change, and can provide termination actions and credit-control information to the PCEF.

  • “In a tight interworking between online and offline charging the specified quota re-authorisation triggers armed by OCS are supported.” TS 32.251 v7.8.0
  • “The OCS may specify the behaviour on consumption of the final granted units known as termination action.” TS 32.251 v7.8.0
  • “The OCS shall provide the termination action to the PCEF before denying credit; otherwise the PCEF default termination action will be performed.” TS 23.203 v7.14.1
Rel-9 specification text

Rel-9 adds User CSG information change as a charging condition reported to the OCS via CCR update, and OCS reporting of CSG information follows OCS re-authorization triggers.

  • “When "User CSG Information change" occurs as a change of charging condition, how the changes (i.e. User entering/leaving a CSG cell” TS 32.251 v9.13.0
  • “the reporting of User CSG information to the OCS shall be done on the level of detail as requested by the OCS re-authorization triggers” TS 23.203 v9.14.0
Rel-10 specification text

The OCS's internal ABMF function and Rc reference point, previously unspecified or FFS, are now put in functional context with TS 32.296, and the OCS gains a proxy option for visited access.

  • “The Rc reference point allows the interaction between the OCF and an Account Balance Management Function (ABMF) in order to access the account of the subscriber on the OCS.” TS 32.240 v10.1.0
  • “For a visited access, the VPLMN may use an OCS proxy between the PCEF and the OCS.” TS 23.203 v10.10.0
  • “This reference point is FFS for future releases.” TS 32.240 v10.1.0
Rel-11 specification text

The OCS gained new responsibilities in Rel-11: maintaining policy counters for subscriber spending limits and reporting their status to the PCRF over the new Sy interface.

  • “The OCS shall maintain policy counter(s) to track spending for a subscription.” TS 23.203 v11.15.0
  • “The OCS shall make information regarding the subscriber's spending available to the PCRF using spending limit reports.” TS 23.203 v11.15.0
  • “Sy Reference point for policy enforcement between OCS and the PCRF” TS 32.240 v11.7.0
Rel-12 1 CR

In Rel-12 the OCS gained the ability to provide a Presence Reporting Area identifier and subscribe to UE presence changes in a PRA, and to perform credit control for TDF sessions.

  • “the OCS may provide, if not already determined by the PCRF, the "Presence Reporting Area identifier" identifying the PRA to be reported” TS 32.251 v12.13.0
  • “the OCS may subscribe to Change of UE presence in Presence Reporting Area at any time during the life time of the credit management session” TS 23.203 v12.11.0
  • Presence Reporting Area provided by OCS TS 23.060CR1834
Rel-13 1 CR

OCS interactions were extended: Gy/Gyn now run between a HPLMN OCS and visited PCEF/TDF (LBO, NSWO), the OCS proxy was removed, and new charging-condition triggers are sent to the OCS.

  • “Gy between OCS residing in HPLMN and PCEF located in PGW VPLMN, as per Evolved 3GPP Packet Switched Domain Roaming Architecture” TS 32.251 v13.6.1
  • Removal of OCS proxy in LBO roaming scenario TS 23.203CR0991
  • “all current counts are captured and sent towards the OCS with a Debit / Reserve Units Request[Update]” TS 32.251 v13.6.1
Rel-14 specification text

The OCS gained new roles: it handles ProSe restricted discovery Debit/Reserve operations, and it can provide, change and unsubscribe from Presence Reporting Areas and influence the Unused Quota timer.

  • “The OCS performs the Debit Units operation for "Restricted Match".” TS 32.277 v14.3.0
  • “The OCS may change (activate/modify/remove) the Presence Reporting Area(s) to be reported by providing the updated PRA Identifier(s) to PCEF.” TS 32.251 v14.4.0
  • “The OCS may in this case respond with a new value of the Unused Quota timer to the PCEF” TS 32.251 v14.4.0
Rel-15 1 CR

OCS behaviour changed: it may subscribe to and receive reports of UE presence in multiple Presence Reporting Areas, can terminate Sy sessions, and Rel-15 charging text extends OCS to the 5G CCS.

  • “By providing the corresponding above lists in Presence-Reporting-Area-Information AVP(s), the OCS subscribes to the notifications of change of UE presence status in the PRA(s)” TS 32.251 v15.5.0
  • “This clause describes the signalling flow for the OCS to terminate the Sy session of a subscriber.” TS 23.203 v15.5.0
  • Correction of OCS behaviour for unknown and unavailable Policy Counters TS 29.219CR0073
Rel-16 specification text

The OCS definition changed from performing real-time Credit-Control to performing quota management, and the ABMF is now located within the OCS or the CCS (Converged Charging System).

  • “Online Charging System: the entity that performs quota management.” TS 32.240 v16.5.0
  • “Online Charging System: the entity that performs real-time Credit-Control.” TS 32.240 v16.5.0
  • “is the location of the subscriber’s account balance within the OCS or the CCS.” TS 32.240 v16.5.0
Rel-17 specification text

TS 32240 text on OCS was revised to cover OCS/CCS and converged charging with the CHF, and event charging gained a Post Event Charging (PEC) option alongside ECUR and IEC.

  • “"Event Charging with Unit Reservation" (ECUR),"Immediate Event Charging" (IEC) or "Post Event Charging" (PEC), respectively” TS 32.240 v17.11.0
  • “the OCS/CHF is responsible to generate CDRs similar in scope to the ones described in offline chargin” TS 32.240 v17.11.0

Defining Specifications

3GPP specifications that define or reference OCS, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 23.003 vk10 Numbering, Addressing and Identification Rel-20 read
TS 23.060 vj00 GPRS Stage 2 Service Description Rel-19 read
TS 23.125 v700 Flow Based Charging Architecture Rel-7 read
TS 23.203 vk10 Policy and Charging Control Architecture Rel-20 read
TS 23.234 vd10 3GPP-WLAN Interworking Index Rel-13 read
TS 23.237 vj00 IMS Service Continuity (ISC) Stage 2 Rel-19 read
TS 23.401 vk10 Evolved Packet System Architecture Rel-20 read
TS 23.503 vk30 5G Policy and Charging Control Framework Rel-20 read
TR 23.979 vj00 PoC over 3GPP Systems Architectural Requirements Rel-19 read
TS 28.849 vj10 CAPIF Phase2 Charging Study Rel-19 read
TS 29.212 vk00 Diameter-Based PCC Reference Points Rel-20 read
TS 29.215 vj00 S9 Reference Point Stage 3 Specification Rel-19 read
TS 29.219 vj00 Sy Reference Point Stage 3 Specification Rel-19 read
TS 29.234 vb20 WLAN-3GPP Interworking Protocols Rel-11 read
TS 29.817 vc10 Study on XML-based Rx interface for PCC Rel-12 read
TS 29.890 vg00 CT3 5G System Technical Report Rel-16 read
TS 32.240 vk10 3GPP Charging Architecture and Principles Rel-20 read
TS 32.250 vj00 Circuit Switched Offline Charging Rel-19 read
TS 32.251 vj00 PS Domain Charging Management Rel-19 read
TS 32.255 vk30 5G Data Connectivity Converged Charging Rel-20 read
TS 32.260 vk10 IMS Charging Management Rel-20 read
TS 32.270 vj00 MMS Charging Management Specification Rel-19 read
TS 32.271 vj20 3GPP LCS Charging Management Spec Rel-19 read
TS 32.272 vj00 Charging for Push-to-Talk over Cellular (PoC) Rel-19 read
TS 32.273 vj00 MBMS Charging Management Rel-19 read
TS 32.276 vj00 VCS Online Charging from Proxy Function Rel-19 read
TS 32.277 vj20 Charging Management for Proximity Services (ProSe) Rel-19 read
TS 32.278 vj00 Monitoring Events Offline Charging Specification Rel-19 read
TS 32.280 vj00 Advice of Charge (AoC) Framework Rel-19 read
TS 32.281 vj00 Announcement Service for Online Charging Rel-19 read
TS 32.293 vj00 Proxy Function in Domestic Service Provider Rel-19 read
TS 32.295 vj00 3GPP Charging: CDR Transfer via GTP' Protocol Rel-19 read
TS 32.296 vj00 Online Charging System (OCS) Architecture Rel-19 read
TS 32.297 vj00 Charging Data Record File Transfer Rel-19 read
TS 32.299 vj00 Diameter Charging Applications for 3GPP Rel-19 read
TS 32.808 v800 Common Profile Storage Framework for User Data Rel-8 read
TS 32.825 va00 Rc Reference Point Study for ABMF Rel-10 read
TS 32.843 vd00 Inter-PLMN Online Charging for Roaming Rel-13 read
TS 32.849 vd00 VoLTE Roaming Charging Scenarios Rel-13 read
TS 32.850 ve00 IMS Charging Correlation Methods Study Rel-14 read
TS 32.869 vf00 Diameter Overload Control for Charging Interfaces Rel-15 read