5G Network Deployment: Monetization, Policy, and Migration

A successful standalone 5G network deployment involves three things: the radios, the core, and the business systems that turn the network’s capabilities into revenue. The radios are the towers and antennas that send and receive the signal. The core is the central system that routes traffic and enforces rules for each user or device. The business systems layered on top set those rules and run the commercial side. But when these three things don’t arrive at the same time, an operator ends up with a network that runs but leaves money on the table.

An operator can run its fast 5G radios on an old 4G core (called non-standalone, or NSA), or build a new standalone core (SA) made just for 5G. The difference is huge: the 4G core was built as specialized telecom hardware, while the 5G core was designed from the start as software running on cloud servers. That shift—from fixed hardware to flexible software—is what lets a 5G core do things a 4G core can’t: slice the network, prioritize performance, and price each service differently.

When an operator has both—5G radios and a 5G core—it can finally charge for more than basic data and calls. Without a standalone 5G core, an operator has fast radios and a network that works, but no way to charge for what 5G makes valuable. Closing that gap is what this guide is about—monetization, policy control, and migration from 4G to standalone 5G.

What does 5G network deployment require beyond radio buildout?

Say "network deployment" and most people picture the radios—the towers, antennas, and small cells (the radio access network, or RAN) that carry the signal. But a network that runs isn't a business any more than a car that runs is a taxi service. Beyond the radios and the core that runs them, a deployment needs a fare system: the business systems that charge for the ride. That's the part most 5G deployments are missing. The rest of this guide is about that fare system, starting with charging.

BY THE NUMBERS: As of early 2026, global 5G subscriptions had passed 3 billion—about one-third of all mobile subscriptions—per the June 2026 edition of the Ericsson Mobility Report, which projects it will be two-thirds by 2031. But most operators can’t yet monetize that growth. Of the roughly 390 providers that have launched 5G, only about 90 have launched standalone 5G. The rest run on an old 4G core: fast service, but not the software core that makes new revenue possible.

How does 5G change charging and monetization?

Charging is the fare system operators rely on to track what customers use and work out what they owe. Standalone 5G handles it differently from 4G: it merges 4G's two charging systems—prepaid and postpaid—into one, swaps older telecom-only signaling for standard web interfaces the rest of the software industry uses, and lets operators charge for more than data and minutes.

The merge: Standalone 5G replaces 4G’s two charging systems with one

4G kept prepaid and postpaid on separate systems for a reason—they worked in opposite ways:

• The 4G prepaid system checked balances in real time, counted them down as the customer used the network, and stopped the service when the balance reached zero.

• The 4G postpaid system recorded usage and billed it at month-end, with no real-time tracking.

Standalone 5G merges the two. An operator can provide real-time control over postpaid accounts to accommodate enterprises that need live spending caps, alerts tied to department budgets, or usage quotas for a fleet of connected devices. Real-time control like that presents itself in three ways:

• A customer feels it: Their phone hotspot slows when they pass their data cap—the network meters them in real time and acts the moment they cross the line (according to the operator’s policy).

• A business feels it: A field crew's connected inspection camera, which uploads video all day, can trigger an alert or pause when it’s reached its quota. This can help the company stop overages before they happen, or at least see them coming instead of waiting until the bill arrives.

• An operator sells it: A standalone 5G plan that lets enterprises monitor and cap individual devices starts a new revenue stream that wasn’t practical with 4G.

UNDER THE HOOD: 3GPP—the global body that sets mobile standards—defines these in spec terms. The prepaid system is the online charging system (OCS, real-time), and postpaid is the offline charging system (OFCS, record-then-bill). Standalone 5G merges them into the Converged Charging System (CCS), with the Charging Function (CHF) replacing both.

The bridge: 5G changes how the network talks to the charging system

In 4G, the network told the charging system how much data and time each customer used via a protocol called Diameter, which only telecom equipment speaks. Standalone 5G uses a new language called Nchf—the “N” marks it as a 5G interface and the “chf” points to the Charging Function it connects to. Built on the same web standards that regular software runs on, Nchf lets an operator add and start billing a new service quickly, instead of waiting on special telecom signaling like Diameter.

The payoff: 5G can charge for more than data

In 4G, the charging meter mostly tracked two things: how much data was used and how long a call lasted. In 5G, the meter sees four things about each connection—for example: how it’s being used, which device it’s on, the quality it requires (steady and low-lag versus standard), and which network slice it’s running on. These details let the charging system price each connection on its specifics, not just the total usage.

Use case: One operator, many ways to charge

With standalone 5G, a single carrier can bill a range of enterprise customers on terms that fit their needs:

• A logistics company with thousands of low-data tracking devices is billed a flat rate per device, not per byte.

• A brick-and-mortar retailer is charged per transaction for their payment terminals, with guaranteed uptime so a sale doesn’t fail because the connection drops.

• A connected-vehicle service buys priority connections on demand and is charged per use, like a toll lane that only charges when you go through it.

• An operator’s own consumer plans run on the same system—standard data and calls, billed by usage.

Same operator, one charging system, four ways to charge—because 5G can tell each kind of traffic apart.

UNDER THE HOOD: 5G charging and billing can be based on access, API calls, or device and event—not just data volume. The Charging Function (CHF) generates the charging data records (CDRs) that these services are billed from.

How do you bridge 4G and 5G during migration?

No operator can go from 4G to 5G overnight. Instead, they run the two side by side: old and new systems operate at the same time, a translator converts traffic between them, and the switchover happens in phases.

The approach: A translator lets 4G and 5G run side by side

“Big bang” migration—switching everything over at once—is something most operators avoid because the 4G systems still carrying live revenue can’t be taken offline to make the change. So 4G and 5G run in parallel: 4G keeps doing its job while 5G comes online next to it, and a connector lets them work together.

That connector is the interworking function (IWF)—the translator between Diameter (the language 4G speaks) and the web-based signaling 5G uses. With the IWF, a 5G session—a phone call, video stream, or a connected device’s data upload—can be charged by the 4G charging systems an operator already runs, while those same systems keep handling their own traffic.

UNDER THE HOOD: In 4G, charging runs on the online charging system (OCS) and policy runs on the policy and charging rules function (PCRF)—and both speak Diameter. The IWF translates 5G's HTTP/2 and JSON signaling into Diameter and back, so the OCS and PCRF keep working through the migration.

The mapping: Charging and policy connections have 4G equivalents

Running side by side is only half of it—eventually each function has to move from 4G to 5G. That's possible because 4G and 5G carry the same kind of information, just in different languages. Because the jobs match, an operator can move them over one function at a time—charging first, then policy, then the rest—with the IWF translating between the old 4G language and the new 5G language.

[IMAGE]

UNDER THE HOOD: Each of these connections has an official name set by 3GPP, the standards body. The 5G names start with "N"; their 4G counterparts use older letter-based names.

The sequence: Monetization migrates in phases

Monetization comes online the same way the charging and policy systems do—in stages, each one adding something new to sell.

Phase 1: 5G runs on 4G billing. The operator sets up the 5G charging function and an interworking function, so 5G runs but is billed by the 4G charging and policy systems it already trusts. 5G speeds are live and for sale, but still limited to data and minutes.

Phase 2: Real-time charging goes live. The operator brings its Converged Charging System (CCS) online—the single 5G system that prices usage and tracks balances, replacing the two systems that the 4G core kept separate. Now it can charge in real time: enterprise spending caps, IoT quotas, and usage-based plans. It typically rolls these out to part of the subscriber base first, so the new system proves itself under real traffic before everyone depends on it.

Phase 3: The full model goes live. All subscribers move to standalone 5G charging and policy—the CCS plus a policy control function, or PCF—and the legacy OCS and PCRF retire. Now the operator can sell the full range: quality tiers, guaranteed slices, per-event pricing—everything the 4G core couldn't bill for. The migration is done, and the network finally earns from everything it can do.

Why does policy control matter for standalone 5G?

Policy control decides what each connection—a user or device—is allowed to do, moment to moment. It’s what lets an operator charge more for better service. In standalone 5G, that authority belongs to the Policy Control Function.

The control: The PCF makes premium tiers possible

The PCF sets the rules for a connection's quality (priority and speed), its service type, whether it counts against a data cap, and which network slice it runs on. Those controls let an operator offer different levels of service—priority lanes, prioritized performance, plans matched to what each connection needs—and charge for the difference. Without the PCF, a hospital monitor, a video stream, and a fleet of sensors all look the same to the network, so there's no way to charge them differently. So the PCF isn’t optional—it’s what makes premium service possible.

UNDER THE HOOD: A "premium tier" is a price attached to a specific class of service. 5G is designed around three broad service categories, and the PCF is what lets an operator charge each differently:

• Enhanced mobile broadband (eMBB): Speed—high-bandwidth data for people; streaming, video calls, browsing on a phone.

• Massive machine-type communication (mMTC): Scale—small amounts of data from huge numbers of low-power devices; sensors, smart meters.

• Ultra-reliable low-latency communication (uRLLC): Reliability—connections that can’t fail or lag; remote surgery, connected vehicles.

The continuity: Policy migrates the same way charging does

Policy follows the same path as charging. The 4G version was the Policy and Charging Rules Function (PCRF); the 5G version is the PCF, and the two run side by side until the PCRF can retire. Why this matters: a customer moves between 4G and 5G constantly, so policy has to enforce their plan on both—or a premium tier stops working the moment they leave 5G.

UNDER THE HOOD: The 4G PCRF and 5G PCF are often combined into a single dual-mode PCF/PCRF engine. That combined engine:

• Coordinates policy with charging across the N28 interface, so policy decisions (like a speed cap) and their billing stay aligned for one session—a single connection, like a video stream or a call.

• Keeps each session matched to its own rules through the Nbsf, so a session gets only the policy and charging rules set for it.

• Adjusts policy in real time—if the network gets congested, it can use live performance data to decide what each connection gets, so the connections that paid for priority keep it.

Network slicing is a monetization problem, not just a network feature

A network slice is a dedicated portion of the 5G standalone network built to deliver committed speed, latency, and reliability for a specific user or device. Slicing is possible because the 5G core is software: one physical network can be divided into many virtual ones, each tuned and priced differently—something a fixed-hardware 4G core can't do.

The problem: A slice only earns if you can charge for it

If an operator builds a slice but can't bill for it, it’s spending money on something that earns nothing back. The money comes from selling it with a promise attached: a service-level agreement (SLA), a written guarantee of the speed, latency, or uptime that the customer pays a premium for. Delivering that guarantee takes charging and policy working together—policy enforces the performance the SLA promises, and charging meters it, prices it, and bills for it.

BY THE NUMBERS: Operators are starting to sell slices, not just demonstrate them. Commercial 5G standalone slicing offerings rose from 65 to 84 in six months, per the June 2026 Ericsson Mobility Report. The furthest along is fixed wireless access (FWA): Opensignal reports that operators including Odido, Elisa, and Cosmote are using standalone 5G capacity and slicing to sell tiered home broadband—an early example of charging for differentiated performance rather than flat access.

The model: Charging in a slice, across slices, and through resellers

Once a slice is metered, an operator can charge for it in several different ways:

• Within a slice: For traffic running on one slice, the carrier can meter it per device, per use, or per event. For example, a utility company’s smart meters can be billed per device for their everyday reporting, while a one-off firmware update pushed to all of them is billed once as a one-time charge—both on the same slice.

• Across slices: One enterprise might run several slices at once, each on a different plan but on the same bill. A logistics company could put its offices on one slice, its warehouses on another, and its truck fleet on a third—each with the performance that part of the business requires.

• Through a reseller (B2B2X): Business-to-business-to-anyone is when an operator sells a slice to a business, which builds its own service on top and resells it to its customers. For example, a cloud-gaming company buys a low-latency slice and resells guaranteed performance to players at a premium—the operator bills the gaming company, and the gaming company bills the players.

The market: Who buys slices?

Typical slice buyers are customers who can’t run on a “best-effort” connection—the kind with no performance promise. Hospitals, factories, emergency services: these are operations where the connection has to work every time.

• Hospitals: A hospital running remote patient monitoring or connected operating-room equipment needs guaranteed reliability because lives depend on it.

• Smart factory: Robotics and automated lines need guaranteed low latency, because a temporary pause can stop the line.

• Emergency services: First responders need guaranteed priority, staying connected even when a cell is jammed with everyone else's traffic during a crisis.

These buyers aren’t price-shopping—they're buying certainty, and a slice with an SLA is exactly what sells it. That's the commercial heart of slicing.

UNDER THE HOOD: Slicing also serves V2X (vehicle-to-everything—connected cars, traffic systems, road safety) and enterprise IoT (large connected-device fleets), across public and private 5G. Each slice carries its own SLA—policy enforces it, and charging meters it.

How do operators scale for 5G and IoT transaction volumes?

Every 5G service an operator sells generates charging events. A network of phones produces a manageable stream, but add millions of sensors, meters, and trackers all reporting at once, and the core charging systems can't keep up. They become the bottleneck that stalls the whole deployment.

The problem: IoT creates more charging events than the core can handle

The issue isn't the size of each transaction—it's the number of them. IoT devices are individually tiny (a sensor sends just a few bytes) but collectively huge (millions of them, generating events nonstop). And many of those events don't need metering at all—flat-rate devices billed the same no matter what they use, or zero-rated traffic the operator includes for free. Sending all of it to the core charging systems means scaling expensive systems just to process traffic that mostly doesn't need them.

The fix: Filter before the core

A high-throughput layer called mediation sits in front of the core charging systems and sorts the events. It passes through only the events that need pricing and billing, so the core sees a filtered stream instead of an avalanche of events—and never has to handle the full volume.

The proof: High volumes are already running on live networks

Processing billions of events a day sounds impossible, but live 5G networks already do it:

• A single mediation site can process 16.5 billion charging records per day.

• Real-time charging runs at 100,000 transactions per second with low latency.

UNDER THE HOOD: Mediation filters high-volume 5G and IoT traffic before it reaches the core charging functions—the rating function (RF), account balance management function (ABMF), and OCS. Flat-rate and zero-rated events are filtered at the mediation layer; only chargeable events pass through to be rated and recorded.

Service continuity matters in 5G deployments, too

Most 5G coverage is about the new things: new core, new charging, and new services. But a deployment also has to keep the old things working—calls connecting, texts arriving, a subscriber's service active the moment they sign up—across 3G, 4G, and 5G all at once. Continuity is the part of a deployment a customer only notices when it breaks.

The problem: A 5G network is really three networks at once

An operator runs 5G alongside 4G and 3G, and the customer never knows the difference:

• A call starts on 5G and hands to 4G as the subscriber drives out of 5G coverage.

• A text has to go through whether the phone is on 5G or an older network.

• A new device has to activate the moment it's switched on, on whatever network it finds.

The deployment has to make one seamless service out of three generations—and the systems holding that together (messaging, voice, provisioning) have to speak all three.

The handoff: A call can't drop when it moves between networks

Voice is the clearest example: A subscriber on a call walks out of a building, and their phone shifts from 5G to 4G—the call should keep going without them noticing. A 5G call uses one technology, a 4G call another, a Wi-Fi call a third, and the subscriber moves between them mid-conversation. If the systems handling voice can't pass a live call cleanly from one to the next, the call drops—and the customer blames the operator.

Messaging is the same: A text has to arrive whether the person receiving it is on 5G, 4G, or an older network in a weak-signal spot. Customers just expect it to work, but making that happen takes systems built to bridge every generation, so a message gets through no matter where each person is.

The activation: Service has to turn on the moment it’s sold

Continuity also means a new subscriber or device works the instant it's activated. In a 3G or 4G world, activations arrive as a steady, moderate stream. A 5G deployment with IoT changes that: activations can come in bursts when whole fleets of devices come online at once. The provisioning systems that turn service on have to keep up—because a slice, a plan, or a device that's sold but not working is something the customer paid for and can't use.

UNDER THE HOOD: Continuity spans systems beyond charging and policy:

• Messaging: SMSC for texts, USSD gateways for short-code services (the #123# menus).

• Voice: The service control point (SCP) helps to route calls, and VoLTE, VoWiFi, and VoNR (voice over 5G) coexist so a call holds up moving between 4G, Wi-Fi, and 5G.

• Activation: Scales from the steady volumes of 3G and 4G to whole device fleets switching on at once.

How CSG supports 5G network deployment

This guide opened on a promise: a 5G deployment pays off when monetization, policy, and migration come together—plus the continuity that keeps it all running. CSG builds the systems that support each one, and does so from a single platform instead of a patchwork of vendors.

For an operator that's built the network but hasn't turned it into revenue, here's where CSG fits in.

Monetization: Turn the 5G you’ve built into revenue

If your 5G is up and running but not earning revenue yet, chances are it’s because you haven’t set up a way to charge for it. CSG offers a converged charging system (CCS) that fills that gap.

Where 4G needed two separate systems—one for prepaid and one for postpaid—the CCS does both in one. It uses the Charging Function (CHF) to collect usage from the network and the Charging Gateway Function (CGF) to turn it into records billing can use, so you bill for things 4G couldn't: quality tiers, per-use plans, and slice-based SLAs.

More charging means more events to process. CSG’s mediation layer filters those events before they reach the core, so the CCS isn’t overwhelmed. It’s proven to handle 16.5 billion records a day and 100,000 transactions per second.

Policy: Sell premium tiers across 4G and 5G

Charging lets you bill for 5G service, but it's policy that decides what each connection is allowed to do. CSG's Policy Control Function (PCF) controls connection quality, mobility, charging control, and which slice a connection uses. It runs in dual mode across 4G and 5G, so you can sell premium tiers during the migration, not just after.

Migration: Add 5G without replacing your 4G stack

Running 4G and 5G side by side, moving over in phases without downtime—CSG's interworking function (IWF) is what makes that dual operation possible. It translates between Diameter (the language your 4G systems speak) and your 5G signaling, while a Diameter routing agent (DRA) directs traffic to the right place. So you can earn revenue during migration without disrupting the services your customers depend on.

Continuity: Keep every service running while you migrate

Calls, texts, and activations all have to keep working across 3G, 4G, and 5G at once. CSG covers those systems too—messaging (SMSC, USSD), voice routing (SCP) and real-time activation that keeps up when whole fleets of devices come online together. Because it all runs on one platform with charging and policy, nothing falls out of step while you migrate.

Frequently asked questions

Can operators launch 5G SA without replacing their 4G charging and policy stack on day one?

Yes. An interworking function (IWF) translates 5G signaling into the Diameter interfaces that 4G's OCS and PCRF already understand, so 5G traffic can be charged by the legacy systems while the carrier migrates in phases. The 4G and 5G systems run side by side, and each function moves over one at a time—no big-bang switchover.

How does CSG support 5G network slicing monetization?

A slice only earns if the carrier can meter and bill it. CSG's policy and charging systems work together to do that—policy enforces the performance an SLA promises, and charging meters and prices it—whether the carrier bills within a single slice, across several slices on one account, or through a reseller (B2B2X) model. That's what turns a network slice from reserved capacity into a sellable product.

How can operators protect legacy charging systems from 5G and IoT transaction volumes?

A high-throughput mediation layer sits in front of the core charging systems and filters the flow of events—settling flat-rate and zero-rated events that don't need billing, and passing only chargeable events through. The core sees a filtered stream instead of the full volume, so it never has to scale to peak device load. CSG's mediation runs at production scale: 16.5 billion records per day at a single site, and 100,000 transactions per second.

Why does 5G deployment rely so heavily on small cells?

It comes down to spectrum. mmWave—the high-band spectrum behind 5G's fastest speeds—doesn't travel far, and it struggles to get through walls and obstacles. To cover an area with it, a carrier may need five to ten times as many cell sites as 4G did. Those extra sites are small cells: compact radios placed close together to fill gaps and add capacity where traffic is heavy. Mid-band needs far less of this, which is why most carriers rely on it for everyday coverage. The radios, though, are only half the job. Turning that coverage into something a carrier can charge for is the other half—and the harder one.

How do low-band, mid-band, and mmWave spectrum compare?

They trade range for speed. Low-band (under 1 GHz) reaches a long way and gets through buildings, so it's good for rural and wide-area coverage, but it's the slowest of the three. mmWave (above 24 GHz) is fast and high-capacity but barely travels and is easily blocked, so carriers use it in packed places like stadiums and downtowns. Mid-band (roughly 1 to 6 GHz) lands in the middle—decent reach, strong speed—which is why it carries most everyday 5G. No single band does it all, so carriers run a mix.

What are the biggest challenges in a 5G deployment?

There are real ones on the radio side: securing the right spectrum, building out enough small cells to cover high-band areas, and paying for all of it. Those are hard, but they're well-understood—carriers have been solving coverage problems for decades. The challenge that catches more of them off guard is commercial. A network can be live, fast, and fully built and still earn nothing if there's no way to charge for what it does. Standalone 5G needs new charging, policy, and migration systems to turn what the network can do into revenue, and that's the piece deployments most often shortchange.

What changes when moving from a 4G core (EPC) to a 5G standalone core?

Quite a bit. The core stops being specialized hardware in a data center and becomes software running on cloud servers. That one change opens up the rest: a software core can be split into many virtual networks (slices), can commit to a specific level of performance per service, and can charge for far more than data and minutes. The two separate charging systems 4G kept—one prepaid, one postpaid—merge into one. And the old telecom-only signaling gives way to the same web standards regular software uses. Together, those shifts are what make standalone 5G worth deploying.