Estimate online charging TPS, daily CDR volume and mediation storage for a subscriber base.
Charging load is driven by event count rather than bandwidth. Concentrating the busy-hour fraction of the daily events into 3600 seconds gives the sustained credit-control rate, and the same event count multiplied by record size and retention gives the mediation platform's disk bill. An OCS that cannot keep up either blocks revenue-generating sessions or, worse, lets them run unrated, and CDR storage growth is one of the most commonly under-budgeted lines in an operator's OSS.
Charging Session
busy-hour TPS = (subscribers × events per day × busy-hour share) ÷ 3600; storage = events per day × CDR size × retention.
busy-hour TPS = (subscribers × events per day × busy-hour share) ÷ 3600; storage = events per day × CDR size × retention. Charging load is driven by event count rather than bandwidth. Concentrating the busy-hour fraction of the daily events into 3600 seconds gives the sustained credit-control rate, and the same event count multiplied by record size and retention gives the mediation platform's disk bill.
An OCS that cannot keep up either blocks revenue-generating sessions or, worse, lets them run unrated, and CDR storage growth is one of the most commonly under-budgeted lines in an operator's OSS.
This calculator takes 6 inputs: Subscribers, Chargeable events per subscriber per day, Average CDR size, Share of events in the busy hour, Rated capacity per charging node, CDR retention period. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.