Mobile Core Integration (4G / 5G)
Last updated 14 Oct 2026
At a glance
5G core network functions are cloud-native software running on Kubernetes. The orchestrator does not configure devices here: it configures subscribers, data networks, policy and slices, and asks MANO for capacity. This part covers the 4G EPC and 5GC functions and where each piece of service intent actually lands.
The picture
Service intent becomes changes to subscribers, data networks, policy and slices, in different functions per generation
1 · Service intent
From SOM
Mobile CFS items: who the subscriber is, which data networks, what policy, which slice
No device, no CLI, no container detail.
2 · Object and where it lives
Subscriber profile
Provision this SIM with an enterprise voice and data profile
4G: HSS
5GC: UDM / UDR
APN / DNN
Enable a corporate data network for this group
4G: P-GW + PCRF
5GC: SMF + UPF + PCF
QoS profile
Apply a bandwidth and priority class
4G: PCRF (QCI, ARP)
5GC: PCF (5QI, ARP, AMBR)
Policy rule (PCC)
Throttle after a usage threshold
4G: PCRF · Gx
5GC: PCF
Slice
Serve this group on a dedicated slice
4G: n/a
5GC: NSSF + slice-aware NFs
EPC: a different Diameter application per interface. 5GC: one service-based interface family, discovered through NRF.
3 · Below the service line
AMF, SMF, UPF, MME, gateways
Built capacity. Not reconfigured per subscriber.
MANO
Scales NF instances; new instances register with NRF
How it works
Two generations in production
4G EPC has control and user plane often co-resident, and is integrated through Diameter and GTP. 5GC is a service-based architecture with strictly separated control and user planes, integrated through HTTP/2 service-based interfaces (SBI). Many operators run both: EPC carries LTE, VoLTE and non-standalone 5G; 5GC carries standalone 5G.
| Function | Gen | Role |
|---|---|---|
| HSS | 4G | Subscriber data: IMSI, profiles, authentication keys |
| MME | 4G | Control plane: attach, mobility, bearer setup |
| S-GW / P-GW | 4G | User plane: session anchor, forwarding; APNs configured here |
| PCRF | 4G | Policy and charging rules, pushed to the gateway over Gx |
| UDM / UDR | 5G | Subscriber data and authentication |
| AMF | 5G | Registration, mobility, NAS termination; slice-aware |
| SMF | 5G | Session setup, IP allocation, UPF selection; DNN and S-NSSAI bindings |
| UPF | 5G | Forwarding and QoS enforcement, controlled by the SMF |
| NRF / NSSF / AUSF / PCF | 5G | Discovery, slice selection, authentication, policy |
What SBI changes, and what it does not
In EPC each interface between functions (S6a, Gx, Gy, Sh) is a different Diameter application with different semantics. In 5GC the functions talk to each other over the same family of HTTP/2 services and register with the NRF. SBI is that runtime control plane, not the orchestrator's way in: functions are configured through OAM (the 3GPP network resource model, TS 28.541, over NETCONF/YANG or the vendor EMS), and subscriber data goes in through the HSS or UDM/UDR provisioning interface. What 5GC adds for orchestration is a standard management model, not a new configuration protocol.
What the orchestrator configures
| Object | Lives in (4G / 5GC) | Example intent | Underlying change |
|---|---|---|---|
| Subscriber profile | HSS / UDM-UDR | Provision this SIM with an enterprise profile | Subscriber record, key material, policy class binding |
| APN / DNN | PCRF + P-GW / SMF + UPF + PCF | Enable a corporate APN for this group | APN or DNN config, IP pool, QoS binding |
| QoS profile | PCRF / PCF | Apply a bandwidth and priority class | QCI or 5QI, ARP, AMBR, GBR profiles |
| Network slice | NSSF and slice-aware NFs (5GC) | Serve this group on a dedicated slice | Slice template realised across core functions, plus a transport slice request |
| Policy rule (PCC) | PCRF / PCF | Throttle video after a usage threshold | Policy rule push; charging key updates |
| NF capacity | MANO (NFVO + VNFM) | Add UPF capacity in a region | Scale-out; new instances register with the NRF |
Per order, the work lands mostly in the subscriber data and policy functions. The control-plane and user-plane functions are configured when capacity is built, and scaled through MANO (9.7). Slices span more than the core and are covered in 9.6.
Three levels, kept apart
- Service intent: what SOM asks for (subscriber, data network, policy, slice).
- 3GPP operations: the changes to UDM, PCF, SMF and the other functions that realise it.
- Infrastructure lifecycle: the instances, managed by MANO underneath.
SOM payloads that carry Kubernetes namespaces, Helm chart versions, image references or VIM identifiers have mixed the first and third levels. That detail belongs in the network function and network service descriptors.
Who owns what
| Entity | System of Record | System of Engagement | System of Reference | Notes |
|---|---|---|---|---|
| Subscriber profile (IMSI / SUPI, keys, policy class) | HSS (4G) / UDM-UDR (5GC) | SOM / ROM (provisioning) | Service Inventory | The main per-order target in the mobile core. |
| APN / DNN and QoS profiles | PCRF and P-GW (4G) / PCF and SMF (5GC) | — | Service Catalog | Mostly defined when capacity is built; bound to subscribers per order. |
| Policy rules (PCC) | PCRF / PCF | — | Service Catalog | Rule templates designed once; per-subscriber binding at order time. |
| Network function instances | MANO (NFVO / VNFM) | — | Resource Inventory | Instances scale and move; inventory is fed from MANO. |
In practice
Mobile-core orchestration is the domain where vendor stacks are most mature, partly because operators co-developed slicing and 5GC orchestration with their core vendors, and partly because the reliability bar is highest here. Where one vendor supplies the core, its orchestration tends to come with it, with deep but consistent coupling.
A common failure is to treat 5GC functions like routers: per-function configuration pushed through a generic domain controller, in a vendor-specific shape. It works until a function is replaced, scaled or sliced.
The trade-off
What it solves
Working at the level of subscribers, data networks, policy and slices lets mobile services be ordered by intent while functions are scaled, replaced or moved underneath.
What it does not solve
- Running EPC and 5GC side by side, with two provisioning paths.
- Legacy subscriber profiles that have no catalog equivalent.
- Cross-domain slice SLAs, which the core cannot guarantee alone.
What it adds
- A clean boundary between service intent and infrastructure detail has to be held in every payload.
- Service state and infrastructure state are independent: a function can be healthy while the service is not yet active, and the reverse.
- Generation-specific mapping (HSS and PCRF provisioning for EPC, UDM/UDR and PCF provisioning plus the 28-series management model for 5GC) has to be maintained during the overlap.
Architecture decision
How should mobile-core provisioning be integrated while EPC and 5GC both run?
One service model, generation-specific adapters
Choose when the same products are sold on both generations and the catalog can describe intent without naming the generation.
Separate provisioning paths per generation
Choose when 5GC serves a distinct product set (for example enterprise standalone) and EPC is on a dated decline.
Converged subscriber data first
Choose when the core vendor supports a combined HSS/UDM data layer, so one subscriber record serves both.
Breaks if the service catalog carries generation or infrastructure detail. Every core change then forces SOM and catalog rework.
Takeaways
Key Takeaways
- Mobile core is software, not boxes; the orchestrator configures subscribers, data networks, policy and slices.
- EPC integration is per-interface Diameter; 5GC offers one family of service-based interfaces with NRF discovery.
- Per-order work lands mostly in HSS/UDM and PCRF/PCF; control- and user-plane functions are built capacity.
- Keep service intent, 3GPP operations and infrastructure lifecycle apart; container detail never belongs in SOM.
Check yourself
A SOM payload for a new enterprise APN includes a Helm chart version. What is wrong, and where should it go?Show answerHide
Infrastructure detail has leaked into the service layer. Chart versions belong in the network function or network service descriptor that MANO uses. SOM should ask for the APN and its policy, nothing about how the function is deployed.
A 5G customer’s order is "complete" but they cannot get a data session. The UPF pods are all healthy. Where do you look?Show answerHide
Service state, not infrastructure state: the subscriber record in UDM/UDR, the DNN and S-NSSAI bindings, and PCF policy. Healthy functions say nothing about whether this subscriber was provisioned correctly.