APN 4G to DNN 5G: What Actually Changes

An RF engineer decodes a PDU Session Establishment Accept on a freshly integrated 5G SA site. In the NAS trace, there is no APN field anywhere. The parameter is now called DNN — Data Network Name. A cosmetic rename or an architectural shift? The answer lies in the 3GPP specifications and in the operational reality of Standalone 5G deployments.

With 78 operators having launched 5G SA across 42 countries as of September 2025 (source: GSMA Intelligence) and over 2 billion 5G connections worldwide by end of 2024, the transition from APN to DNN is no longer a theoretical exercise. It is a daily operational concern for network engineering teams.

From APN to DNN: A Paradigm Shift

APN in the 4G/EPS Architecture

In the 4G network (EPS — Evolved Packet System), the Access Point Name (APN) plays a central role. It identifies the PDN Gateway (P-GW) to which subscriber traffic must be routed. Each APN corresponds to a specific data network: internet access, the IMS platform for voice services, or a private enterprise network.

The APN is carried in the Attach Request or the Activate Default EPS Bearer Context Request. The MME uses this information to select the appropriate S-GW and P-GW, then establishes one or more EPS Bearers between the UE and the P-GW.

The 4G QoS model is bearer-based: each bearer has a QCI (QoS Class Identifier) that determines its latency, packet loss, and priority characteristics. A subscriber connected to a given APN can have multiple dedicated bearers for different traffic types.

DNN in the 5G SA Architecture

The DNN, defined in 3GPP TS 23.501 (section 5.9), takes over the fundamental function of the APN: identifying the target data network. Internet, IMS, private LAN — the DNN points to the same logical destination as the APN.

But the similarity ends there. The DNN operates within a fundamentally different architecture, built on PDU Sessions and network slicing. The combination of DNN with S-NSSAI (Single Network Slice Selection Assistance Information) creates an addressing system far more granular than the APN alone.

At the NAS encoding level, the DNN uses the same format as the APN: a length-prefixed label sequence, as defined in 3GPP TS 24.501. This format compatibility eases interworking between 4G and 5G networks.

The PDU Session: Successor to the EPS Bearer

PDU Session Establishment

The session establishment mechanism is the most significant architectural difference between 4G and 5G. Defined in 3GPP TS 23.502, it replaces the bearer activation procedure with a more flexible process.

The UE sends a PDU Session Establishment Request carrying three essential pieces of information: the DNN, the requested S-NSSAI, and the PDU Session Type. This last point is a major 5G innovation: three session types are available — IPv4, IPv6, and Ethernet. The Ethernet type, absent in 4G, directly addresses the needs of industrial IoT and private networks.

The AMF (Access and Mobility Management Function) receives this request and selects the appropriate SMF (Session Management Function) based on the DNN + S-NSSAI pair. The SMF then queries the UDM (Unified Data Management) to retrieve the subscriber profile and the subscribed QoS for that specific DNN.

The SMF then selects the appropriate UPF (User Plane Function) and establishes the N3 tunnel (between the gNB and the UPF) and optionally N9 tunnels (between intermediate UPFs). The response — PDU Session Establishment Accept — returns to the UE the allocated PDU address, the confirmed DNN, the S-NSSAI, and the authorized QoS flow descriptions.

Flow-Based QoS: The End of the Bearer Model

In 4G, quality of service is managed at the bearer level. Each bearer has a fixed QCI, and modifying QoS requires creating or modifying a dedicated bearer. While functional, this model lacks flexibility.

5G introduces flow-based QoS within each PDU Session. The 5QI (5G QoS Identifier) replaces the QCI, and QoS Rules allow dynamic mapping of traffic flows to distinct QoS Flows within a single session. A subscriber can have one PDU Session toward an “internet” DNN with multiple different QoS flows: a best-effort flow for web browsing, a low-latency flow for gaming, and a guaranteed bit rate flow for a video call.

This granularity is critical for advanced 5G use cases. Traffic shaping becomes more precise, radio resource management more efficient, and enterprise SLAs easier to implement.

The Role of DNN in Network Slicing

DNN + S-NSSAI: The Fundamental Pair

Network slicing is arguably the most structurally significant innovation in 5G SA. Each network slice — identified by an S-NSSAI — constitutes an independent logical network with its own network functions, QoS policies, and dedicated resources.

The DNN alone is not enough to determine the complete traffic path. It is the DNN + S-NSSAI pair that allows the AMF to route the request to the correct SMF, and the SMF to select the appropriate UPF. The same “internet” DNN can be served by different slices: an eMBB slice for consumer broadband, a URLLC slice for critical applications, an mMTC slice for IoT sensors.

This mechanism is transparent to the end consumer. But for network engineering teams, it significantly increases the complexity of validation and troubleshooting. It is no longer sufficient to verify that an APN is correctly configured; the DNN + S-NSSAI + PDU Session Type triplet must be validated at every step of the chain.

SSC Modes: Session Continuity Reimagined

5G introduces three Session and Service Continuity (SSC) modes, which have no equivalent in 4G:

• SSC Mode 1: the anchor UPF remains fixed for the entire session duration. This is the behavior closest to 4G.
• SSC Mode 2: the network can release the session and establish a new one with a different UPF. Suited for services that tolerate brief interruptions.
• SSC Mode 3: the network can establish a new session before releasing the old one, ensuring seamless continuity. Ideal for streaming services or critical applications during mobility.

The SSC mode is negotiated per DNN and per slice. A single device can therefore exhibit different continuity behaviors depending on the service being used.

4G/5G Interworking: The DNN-to-APN Mapping

Coexistence of Two Worlds

Operational reality demands a prolonged coexistence of 4G and 5G networks. No operator can afford an abrupt cutover. The 3GPP has therefore defined interworking mechanisms that allow a device to move from a 4G network to a 5G network (and back) without losing connectivity.

At the heart of this interoperability sits the DNN-to-APN mapping. The HSS+UDM maintains a correspondence table between 5G DNNs and 4G APNs, associated with the FQDNs of the combined SMF+PGW-C nodes. When a device on 5G SA performs a handover to 4G, the network must translate the active DNN into its equivalent APN, convert QoS parameters (5QI to QCI), and maintain data session continuity.

This mapping is not trivial. Flow-based QoS policies must be converted back into bearers. Slicing information has no direct 4G equivalent. And Ethernet-type sessions, specific to 5G, simply cannot be maintained during a fallback to 4G.

Impact on Network Validation

For integration and validation teams, this duality means a doubling of test scenarios. Each DNN must be validated in a pure 5G SA context, but also in an interworking scenario with 4G. Test cases include:

• PDU Session establishment with a specific DNN in 5G SA
• Inter-RAT handover from 5G to 4G with session continuity
• DNN-to-APN mapping verification in HSS+UDM traces
• QoS conversion validation (5QI to QCI) during fallback
• SSC mode behavior during inter-system mobility

Drive test and protocol analysis tools must now natively support decoding of both signaling stacks. The ability to correlate a 5G DNN with its corresponding 4G APN within the same trace becomes a decisive selection criterion for validation tooling.

Preparing for the Migration: Practical Considerations

The migration from APN to DNN is not a simple parameter rename. It requires a rethinking of provisioning processes, an upgrade of supervision tools, and upskilling of field engineering teams.

GSMA Intelligence forecasts a fourfold rise in mobile data traffic between 2024 and 2030. This growth will be driven by 5G SA networks and their slicing capabilities. Operators who master the DNN + S-NSSAI mechanics today will be better positioned to monetize these new services.

The gap is widening between pioneer markets (GCC, Nordics, China, United States) and the rest of the world. For operators in the 5G SA deployment phase, the validation window is critical. Every DNN misconfiguration, every mapping inconsistency with the existing APN, every QoS flow defect translates into degraded subscriber experience — and into churn.

The question is no longer whether DNN will replace APN. It already has, in both the specifications and deployed networks. The real question is: are your network validation processes ready for this increased complexity?

For more on network migration challenges, see also our analysis on 2G shutdown in France 2026.