Data Network Name

In Release 15, the DNN (Data Network Name) was formally introduced as a core subscription and session management parameter. Key new capabilities included support for a wildcard DNN in subscriptions, the ability to select the same SMF and UPF for all PDU sessions of the same DNN within a network slice, and clarified procedures for handling invalid or unsubscribed DNNs during PDU session establishment. The release also defined specific use cases like emergency DNNs and Local Area Data Network (LADN) DNNs, integrating the DNN into SMF selection and EPS to 5GS interworking.

• 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 granular policy control, such as ensuring the same PCF is selected for multiple PDU Sessions sharing the same combination of UE ID, S-NSSAI, and DNN. These changes provided operators with greater flexibility in managing network resource mapping and policy enforcement for specific data networks.

• 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 (Data Network Name) function was enhanced with new capabilities for Standalone Non-Public Networks (SNPN) and onboarding procedures, including the provisioning of DNN and S-NSSAI during PDU session establishment for SNPN onboarding. It also introduced updates to network exposure APIs like ChargeableParty, AsSessionWithQoS, and MonitoringEvent to include DNN and S-NSSAI information. Furthermore, Release 17 specified new behaviors for LADN DNNs, such as extensions for UE Mobility Analytics and handling for rejected LADN DNNs, and clarified the use of DNN as an optional parameter during interworking with EPS for emergency sessions.

• 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, the DNN function was enhanced primarily through the introduction of LADN (Local Area Data Network) support per DNN & S-NSSAI pair, requiring updates to 5GMM and 5GSM procedures, AMF enforcement, and URSP rules. This release also introduced updates for DNN and S-NSSAI specific group parameters, additional Shared DNN Config IDs in subscription data, and clarified DNN selection for Alternative S-NSSAI. Furthermore, it defined the use of UE local configuration for the default DNN and S-NSSAI and added DNN and S-NSSAI as an authorization indication for certain procedures.

• 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, enhancements for the DNN (Data Network Name) function introduced new capabilities for associating a DNN with a served network slice (S-NSSAI) in terminal procedures, including within the Terminal Response for PLI list and the Envelope command for event download. The release also specified the inclusion of DNN and slice information for reporting communication failure events and refined the coding of the DNN within specific steering of roaming rules.

• 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