Skip to main content
BSS/OSS Academy
🌐
Section 9.5

Mobile Core Integration (4G / 5G)

Last updated 14 Oct 2026

01

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.

02

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

Service intent from SOM becomes changes to subscriber profiles, APN/DNN, QoS, policy and slices, held in different functions in 4G EPC and 5GC. The control- and user-plane functions are built capacity, scaled through MANO.
03

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.

FunctionGenRole
HSS4GSubscriber data: IMSI, profiles, authentication keys
MME4GControl plane: attach, mobility, bearer setup
S-GW / P-GW4GUser plane: session anchor, forwarding; APNs configured here
PCRF4GPolicy and charging rules, pushed to the gateway over Gx
UDM / UDR5GSubscriber data and authentication
AMF5GRegistration, mobility, NAS termination; slice-aware
SMF5GSession setup, IP allocation, UPF selection; DNN and S-NSSAI bindings
UPF5GForwarding and QoS enforcement, controlled by the SMF
NRF / NSSF / AUSF / PCF5GDiscovery, 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

ObjectLives in (4G / 5GC)Example intentUnderlying change
Subscriber profileHSS / UDM-UDRProvision this SIM with an enterprise profileSubscriber record, key material, policy class binding
APN / DNNPCRF + P-GW / SMF + UPF + PCFEnable a corporate APN for this groupAPN or DNN config, IP pool, QoS binding
QoS profilePCRF / PCFApply a bandwidth and priority classQCI or 5QI, ARP, AMBR, GBR profiles
Network sliceNSSF and slice-aware NFs (5GC)Serve this group on a dedicated sliceSlice template realised across core functions, plus a transport slice request
Policy rule (PCC)PCRF / PCFThrottle video after a usage thresholdPolicy rule push; charging key updates
NF capacityMANO (NFVO + VNFM)Add UPF capacity in a regionScale-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.

04

Who owns what

EntitySystem of RecordSystem of EngagementSystem of ReferenceNotes
Subscriber profile (IMSI / SUPI, keys, policy class)HSS (4G) / UDM-UDR (5GC)SOM / ROM (provisioning)Service InventoryThe main per-order target in the mobile core.
APN / DNN and QoS profilesPCRF and P-GW (4G) / PCF and SMF (5GC)—Service CatalogMostly defined when capacity is built; bound to subscribers per order.
Policy rules (PCC)PCRF / PCF—Service CatalogRule templates designed once; per-subscriber binding at order time.
Network function instancesMANO (NFVO / VNFM)—Resource InventoryInstances scale and move; inventory is fed from MANO.
05

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.

Legacy reality
Existing subscribers were provisioned into HSS and PCRF through older workflows, often with profiles no catalog describes. Moving them to 5GC means mapping those profiles to UDM and PCF data, and EPC stays in service alongside 5GC for years, so both sets of provisioning paths have to be run and kept in step.
06

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.

07

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 answer

    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 answer

    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.