Data Network Name

In Release 15, the DNN (Data Network Name) function was enhanced with new capabilities including wildcard DNN subscriptions and the selection of the same SMF and UPF for PDU sessions using the same DNN within a network slice. It also introduced specific handling for emergency services, local area data networks (LADN), and invalid DNNs, along with clarifications on subscription checks and SMF selection procedures.

• Addition of DNN object in PDU session establishment parameters TS 31.111CR0705
• Wildcard DNN subscription TS 23.501CR0021
• Select the same SMF+UPF for PDU sessions of the same DNN within one slice TS 23.501CR0187
• Correction to DNN subscription TS 23.501CR0251
• Clarification on a wildcard DNN TS 23.501CR0465
• DNN Usage Clarification TS 23.501CR0500

+ 16 more changes

In Release 16, key enhancements for the DNN function included the introduction of DNN replacement procedures within the 5G Core network and more deterministic PCF selection rules, mandating the same PCF be selected for multiple PDU Sessions associated with the same combination of UE ID, S-NSSAI, and DNN. These changes provided greater control for network operators in managing user data traffic and ensured consistent policy application for sessions with identical service profiles.

• 23.501 part of PCF selection for PDU sessions with same DNN and S-NSSAI TS 23.501CR1375
• DNN replacement TS 29.507CR0081
• Completion of DNN replacement functionality TS 29.507CR0102
• Correction to the DNN replacement TS 29.507CR0112
• Add DNN and Slice filter TS 29.508CR0087
• Same PCF selection for the same UE ID, S-NSSAI and DNN combination TS 29.512CR0383

+ 30 more changes

In Release 17, the DNN function was enhanced to support new operational scenarios and service integrations. Key additions included explicit support for DNN and S-NSSAI usage in procedures for Standalone Non-Public Network (SNPN) and Public Network Integrated Non-Public Network (PNI-NPN) onboarding, UAS (Unmanned Aircraft System) service fallback, and integration with APIs like ChargeableParty and AsSessionWithQoS. The release also introduced clarifications for handling Local Area Data Network (LADN) DNNs, DNN replacement with URSP rules, and the optional use of DNN for emergency sessions during interworking with EPS.

• DNN setting in the 5GSM sublayer TS 24.501CR2860
• DNN/S-NSSAI providing in PDU session establishment for SNPN onboarding TS 24.501CR3322
• PDU session establishment with the DNN/S-NSSAI for UAS service from the UE whch has valid aerial subscription but UUAA-MM is failed abnormally TS 24.501CR3792
• Update DNN and S-NSSAI in ChargeableParty API TS 29.122CR0347
• Update DNN and S-NSSAI in AsSessionWithQoS API TS 29.122CR0348
• Update DNN and S-NSSAI in MonitoringEvent API TS 29.122CR0488

+ 23 more changes

In Release 18, enhancements for DNN focused on its interaction with network slicing (S-NSSAI), particularly for Local Area Data Network (LADN) services. Key updates included enabling LADN provisioning and AMF enforcement per combined DNN and S-NSSAI, refining UE policy and URSP rules for subscribed DNN/S-NSSAI, and clarifying procedures for DNN selection with an Alternative S-NSSAI. These changes provided more granular service management by treating DNN and network slice as an integrated pair.

• General updates for LADN per DNN & S-NSSAI TS 24.501CR5011
• 5GMM procedure updates for LADN per DNN & S-NSSAI TS 24.501CR5012
• 5GSM procedure updates for LADN per DNN & S-NSSAI TS 24.501CR5013
• AMF enforcement for LADN per DNN & S-NSSAI TS 24.501CR5213
• LADN per DNN & S-NSSAI handling for legacy UE TS 24.501CR5370
• URSP updates for LADN per DNN & S-NSSAI TS 24.526CR0167

+ 21 more changes

In Release 19, the DNN (Data Network Name) function was enhanced to support its explicit association with network slice information (S-NSSAI) in specific procedures. This included defining how DNN and slice data are provided in Terminal Response commands for PLI (Packet Loss Information) and in Communication Failure Event reporting. Additionally, specifications were corrected for the coding of the DNN within the SOR-CMCI (Steering of Roaming - Connectivity and Mobility Control Information) rule and for ensuring slice info and DNN selection mode are properly included where required.

• DNN association for served S-NSSAI in Terminal Response for PLI - list of slices information and Envelope (Event Download slice status) command TS 31.111CR0871
• DNN and Slice information for Communication Failure Event TS 29.503CR1362
• Rel-19 CR 32.255 Correction of missing the Slice Info and the DNN Selection Mode TS 32.255CR0602
• Coding of the DNN in SOR-CMCI rule of SOR transparent container IE TS 24.501CR6778