DNN

Data Network Name

Identifier
Introduced in Rel-15
The Data Network Name identifies an external packet data network that a UE connects to, such as the internet or an IMS service. It is the 5G System (5GS) and Evolved Packet System (EPS) equivalent of the APN, used for session management, policy control, and charging.

Description

The Data Network Name (DNN) is a fundamental identifier in the 5G System (5GS) and Evolved Packet System (EPS). It is a string (e.g., "internet", "ims") that uniquely identifies a Packet Data Network (PDN) or Data Network (DN) external to the 3GPP network. When a UE establishes a Protocol Data Unit (PDU) Session in 5GS or a PDN Connection in EPS, it must specify a DNN. This DNN is a key parameter used by the network to select the appropriate User Plane Function (UPF) in 5GS or Packet Data Network Gateway (PGW) in EPS that provides connectivity to that external network.

Architecturally, the DNN is used in conjunction with other identifiers like the Single Network Slice Selection Assistance Information (S-NSSAI). Upon receiving a PDU Session Establishment Request with a DNN, the Access and Mobility Management Function (AMF) interacts with the Session Management Function (SMF). The SMF uses the DNN, along with subscription data from the Unified Data Management (UDM) and policies from the Policy Control Function (PCF), to select a specific UPF instance. The DNN determines the external network's point of interconnection and influences the session's QoS characteristics, charging policies, and security requirements.

The DNN's role extends beyond simple gateway selection. It is integral to policy and charging control. The PCF may apply different policy and charging control (PCC) rules based on the DNN. For example, traffic destined for the DNN "internet" might have one set of QoS rules, while traffic for a DNN associated with a low-latency enterprise service would have another. The DNN is also used in network exposure; when a third-party application function (AF) requests specific traffic handling, it often references the DNN. Furthermore, the DNN is a critical parameter for network slicing, as a slice can be configured to support only specific DNNs, enabling service-specific network partitions.

Purpose & Motivation

The DNN was introduced to fulfill the same essential purpose as the Access Point Name (APN) in earlier systems but within the new service-based architecture of 5GS. It solves the problem of unambiguously identifying the external data network to which a user's session should be connected. This is a fundamental requirement for routing user plane traffic correctly and applying appropriate network policies.

In the context of 5G's support for diverse services (eMBB, URLLC, mMTC), the DNN provides a clear handle for the network to differentiate between service types. For instance, a UE might use one DNN for regular internet browsing and a different DNN for accessing a mission-critical industrial IoT service, even though both sessions might be served by the same UE. This allows for simultaneous connectivity to multiple data networks with independent policy treatment.

The evolution from APN to DNN reflects architectural simplification and alignment with IP networking principles. While APN had a structure that included network and operator identifiers, the DNN is a more straightforward label. Its purpose is deeply integrated with 5G's core tenets: network slicing, where a DNN may be mapped to a specific slice instance; service-based architecture, where the DNN is a common parameter across Nsmf, Npcf, and other service-based interfaces; and support for edge computing, where a DNN can point to a local area data network (LADN). It addresses the limitations of the older APN model by being more flexible and better suited for automated management and orchestration in cloud-native 5G cores.

Key Features

  • Uniquely identifies an external packet data network (e.g., internet, IMS, enterprise network)
  • Key parameter for PDU Session establishment in 5GS and PDN Connection in EPS
  • Used by SMF (5GS) / MME (EPS) to select the appropriate UPF / PGW
  • Determines the point of interconnection to the external DN
  • Influences policy and charging control rules applied by the PCF
  • Can be associated with specific network slices and edge computing locations (LADN)

Evolution Across Releases

Defining Specifications

SpecificationTitle
TS 22.874 3GPP TS 22.874
TS 23.180 3GPP TS 23.180
TS 23.228 3GPP TS 23.228
TS 23.501 3GPP TS 23.501
TS 23.558 3GPP TS 23.558
TS 23.700 3GPP TS 23.700
TS 23.758 3GPP TS 23.758
TS 24.229 3GPP TS 24.229
TS 24.483 3GPP TS 24.483
TS 24.484 3GPP TS 24.484
TS 24.501 3GPP TS 24.501
TS 24.526 3GPP TS 24.526
TS 24.549 3GPP TS 24.549
TS 24.575 3GPP TS 24.575
TS 24.890 3GPP TS 24.890
TS 26.501 3GPP TS 26.501
TS 26.512 3GPP TS 26.512
TS 26.847 3GPP TS 26.847
TS 26.891 3GPP TS 26.891
TS 26.927 3GPP TS 26.927
TS 26.941 3GPP TS 26.941
TS 28.538 3GPP TS 28.538
TS 28.828 3GPP TS 28.828
TS 28.833 3GPP TS 28.833
TS 28.836 3GPP TS 28.836
TS 29.122 3GPP TS 29.122
TS 29.502 3GPP TS 29.502
TS 29.503 3GPP TS 29.503
TS 29.505 3GPP TS 29.505
TS 29.507 3GPP TS 29.507
TS 29.508 3GPP TS 29.508
TS 29.512 3GPP TS 29.512
TS 29.514 3GPP TS 29.514
TS 29.519 3GPP TS 29.519
TS 29.520 3GPP TS 29.520
TS 29.521 3GPP TS 29.521
TS 29.522 3GPP TS 29.522
TS 29.523 3GPP TS 29.523
TS 29.525 3GPP TS 29.525
TS 29.532 3GPP TS 29.532
TS 29.541 3GPP TS 29.541
TS 29.543 3GPP TS 29.543
TS 29.549 3GPP TS 29.549
TS 29.554 3GPP TS 29.554
TS 29.558 3GPP TS 29.558
TS 29.581 3GPP TS 29.581
TS 29.890 3GPP TS 29.890
TS 31.111 3GPP TR 31.111
TS 32.255 3GPP TR 32.255
TS 32.256 3GPP TR 32.256
TS 32.899 3GPP TR 32.899
TS 33.501 3GPP TR 33.501
TS 33.739 3GPP TR 33.739
TS 33.749 3GPP TR 33.749