How 5G changes charging: the service-based architecture, the converged charging function, network slices and new ways to make money from the network.
In 5G standalone networks, network functions talk to each other through web-style APIs. Charging follows the same model: the session management function and other network functions call the Charging Function (CHF) over the Nchf interface. A single converged charging system (CCS) handles both real-time and after-the-event charging.
The bigger change is commercial. 5G lets operators sell guaranteed quality, private networks, network slices and programmable network capabilities, so the charging and catalog layers must price things that are not just minutes and megabytes.
Network functions such as SMF, PCF and NEF expose and consume APIs; charging is just another service on the bus.
Combines the CHF, rating, account balance management and charging record generation in one system.
The policy function (PCF) changes quality of service in real time, for example boosting or throttling when a bundle is bought or used up.
Logical networks with their own performance targets, for example for video, IoT or a factory, each with its own price plan and SLA.
APIs for location, quality on demand and SIM-swap checks, sold to developers and enterprises per call.
Compute close to the user; charged by capacity, latency tier or usage.
From network capability to revenue.
Package a network capability, such as a slice, quality on demand or location, as a product.
Model it in the product catalog with price, SLA, eligibility and bundling rules.
Enterprise or developer orders through a portal or API; the order is decomposed and provisioned.
The CHF rates usage per slice, per API call or per capacity tier, in real time if needed.
Invoice the enterprise, share revenue with partners and track SLA credits.
| Model | Charged on | Example |
|---|---|---|
| Volume / time | MB, minutes | Consumer data plans |
| Quality tier | Guaranteed bit rate, latency | Live video uplink for broadcasters |
| Slice subscription | Slice capacity and SLA | Factory private slice |
| API call | Per request | Fraud check via SIM-swap API |
| Event / outcome | Successful outcome | Per delivered drone flight or connected car |
Predict SLA breaches on a slice and trigger corrective actions before penalties apply.
Recommend offers and prices based on demand, network load and customer value.
Forecast traffic per cell, slice and edge site to plan investment.
This page describes generic industry practice and public standards. It is not based on, and does not describe, any particular vendor's product or operator's systems.