Online Charging System Built for Mission-Critical Networks
Production-grade OCS platform for telecom operators who cannot afford authorization failures, revenue leakage, or network downtime. Process millions of charging events with sub-second response times.
What Is an Online Charging System?
An Online Charging System (OCS) is a real-time billing and authorization platform used by telecom operators to charge subscribers for prepaid and usage-based services.
Unlike offline charging systems; which process usage records after the fact; an OCS makes charging decisions in real time, before and during service consumption. When a prepaid subscriber initiates a voice call, starts a data session, or sends an SMS, the network component queries the OCS to validate balance and authorize usage.
This real-time capability is what distinguishes OCS from traditional billing systems. The OCS does not simply record what happened; it actively controls whether usage can happen at all.
Real-Time Authorization
Validate balance and authorize service before usage begins
Session Monitoring
Track consumption throughout the session lifecycle
Revenue Protection
Prevent revenue leakage with accurate balance decrements
Core OCS Functions
A production-grade OCS performs several interconnected functions that must work together seamlessly, at scale, under load. A failure in any one of them can cascade into network authorization issues.
Balance Validation
Before any service is granted, the OCS checks whether the subscriber's account has sufficient balance or quota. This validation must happen in milliseconds to avoid impacting network performance.
Real-Time Authorization
Based on balance status, the OCS returns an allow or deny decision to the network. This decision directly controls whether the subscriber can make a call, use data, or send a message.
Usage Monitoring
For session-based services, the OCS continuously tracks consumption through interim updates, adjusting balance and quota throughout the session lifecycle.
Quota Enforcement
The OCS enforces prepaid limits, plan quotas, and expiry rules; ensuring subscribers cannot consume beyond their entitlement.
CDR/UDR Generation
After each session or event, the OCS generates Call Data Records (CDRs) or Usage Data Records (UDRs) for downstream billing, mediation, and reporting systems.
Why OCS Architecture Matters
In telecom networks, the OCS is not a peripheral billing component. It sits directly in the service authorization path. Every prepaid voice call, data session, and messaging event passes through the OCS before the network grants service.
Network Authorization
The network component (UGW) cannot authorize usage without an OCS response. If the OCS is slow, the network waits. If the OCS is unavailable, authorization fails entirely.
Customer Experience
Subscribers expect instant service activation. When a prepaid customer recharges, they expect to make calls immediately; not after synchronization delays.
Revenue Protection
An OCS that fails to decrement balance accurately creates revenue leakage. Over thousands or millions of sessions, even small errors compound into significant revenue loss.
Service Continuity
When an OCS experiences downtime, prepaid services across the network can be affected. OCS downtime is not a backend billing issue; it is a service outage.
The performance of the OCS system meant that we could double or even triple our existing customer base with the existing system and hardware and there would be no issues.
OCS Problems Engineering Teams Face
Through our work with telecom operators across different regions and scales, we have observed recurring architectural problems in OCS implementations that manifest under production load.
Latency During Balance Validation
Many OCS platforms perform adequately during normal traffic but degrade under peak load. Balance validation requests that normally complete in 10-20 milliseconds start taking 200-500 milliseconds or more. This latency compounds across the network, causing subscriber delays and timeout errors.
Inconsistent Session Control Under Load
Session-based charging requires maintaining state across multiple interim updates. Under load, some OCS implementations lose track of session state, fail to process interim updates, or terminate sessions incorrectly.
Revenue Leakage from Charging Failures
When charging events fail to process; due to system errors, network interruptions, or race conditions; revenue leaks. The subscriber consumes service, but the balance is not decremented. Detecting these failures requires effective reconciliation processes.
Fragile Integrations
An OCS must integrate with multiple external systems: AAA servers, UGW components, Diameter and RADIUS message sources, MVNO billing stacks, mediation platforms, and banking systems. Each integration point is a potential failure mode that requires careful isolation.
Cloud Latency for On-Premise Workloads
Additional network latency between cloud and on-premise network equipment can make real-time charging impractical. For operators with strict latency requirements, on-premise deployment remains the appropriate model.
Session-Based vs Event-Based Charging
OCS platforms must handle two fundamentally different charging models. Understanding the technical differences between these models is essential for evaluating OCS architecture.
Session-Based Charging
Applies to services where usage occurs over time: voice calls, mobile data sessions, broadband connections. The charging flow begins when the network component initiates a session and sends an Access Request or Diameter CCR-Initial to the OCS.
Event-Based Charging
Applies to discrete service events: SMS messages, MMS messages, content purchases, API-triggered transactions. Unlike session-based charging, there is no ongoing state to maintain. The charging decision is made once, at the moment the event occurs.
Key Architecture Considerations
When evaluating or designing an OCS, engineering teams should assess several architectural factors that determine production readiness. These considerations separate systems that work in demos from those that survive production traffic.
High Availability
Support redundant servers with automatic failover, session state replication, and health monitoring that detects and responds to failures without manual intervention.
Horizontal Scalability
Add processing capacity by deploying additional listener nodes behind a load balancer, scaling specific components independently to match actual demand.
Response Time Consistency
Consistent response times are more important than averages. Evaluate performance under sustained load with attention to percentile latencies (p95, p99).
Multi-Protocol Support
Native support for both Diameter and RADIUS protocols, accepting messages from either source and processing through unified charging logic.
Integration Isolation
Properly isolated integrations with upstream network components and downstream systems, ensuring failures don't cascade across the system.
Wallet Management
Robust prepaid wallet capabilities with atomic balance updates, multiple balance type support, and immediate top-up processing without synchronization delays.
What EarnBill OCS Delivers
Our commitment to production-grade OCS infrastructure translates into specific technical capabilities that engineering teams can verify and measure. These are proven capabilities from deployed systems.
Millisecond Response Times Under Load
Balance validation completes in 10-20ms even during peak traffic periods, with p99 latencies remaining below 50ms.
Proven High Availability Architecture
Redundant server configurations with automatic failover, session state replication, and health monitoring.
Native Multi-Protocol Support
Native support for both Diameter and RADIUS protocols through unified charging logic.
On-Premise Deployment for Low Latency
Install within your data center, adjacent to network equipment, eliminating round-trip latency of cloud-based solutions.
Seamless Banking Integration
Integration with banking systems for recharge processing. Balance updates occur immediately without delays.
Operational Simplicity
Automated health monitoring, self-healing capabilities, comprehensive logging, and simplified maintenance windows.
The Cost of OCS Failure
Understanding the business impact of OCS failures helps justify investment in production-grade systems. When an OCS fails or performs poorly, the consequences extend far beyond technical metrics.
During OCS downtime for mid-sized operators with prepaid services blocked
Following repeated service authorization failures or charging errors
Beyond which subscribers experience noticeable delays in call setup
From charging failures and session tracking errors in poorly designed systems
See EarnBill OCS in Action
If you are evaluating an Online Charging System; whether for a new deployment or to replace an existing platform; the most effective way to assess EarnBill is through a focused technical walkthrough.
Live System Demo
See real-time balance validation and session control
Architecture Deep Dive
Walk through high availability and scalability
Integration Discussion
Discuss your specific network infrastructure
Technical Q&A
Answer detailed engineering questions