Feature Description

Important

The PGW-C term used in this chapter denote the EPS interworking functionality supported by SMF and must not be assumed as a standalone P-GW that is used in the LTE network.

The multi-DNN support enables the SMF to have multiple PDN connections for end users to provide different services including Internet and VoNR services.

The SMF fetches the locally configured profile-based Data Network Name (DNN) in PDU Session Establishment Request from the AMF. Then, the SMF maintains the PDN connections based on using SUPI and PDU Session ID. The SMF includes the received DNN in all SBI interfaces to authorize the end user to fetch subscription information, policy, and charging related information. The SMF provisions the forward path information to the UPF. The SMF integrates the multi-DNN support with the IP Address Management (IPAM) module to allocate address to the end user based on received DNN. The SMF maps the DNN profile that is derived from subscriber policies. The SMF also fetches DNN and IPv4 and IPv6 path information based on IPAM pool configuration and updates the UPF as part of node association interactions.

Note

Multiple DNN is supported only for 5GS procedures and is not qualified for EPS Session using SBI interfaces.

The SMF supports virtual DNN mapping based on a subscriber profile. It supports mapping of a UE-requested DNN to a configured DNN and sends the selected DNN profile towards the configured network interfaces.

DNN Case Insensitive Support

The DNN configuration in SMF is case insensitive. The configuration accepts a string from 1 through 62 alphanumeric characters, that is case insensitive. It can also contain dots (.) and/or dashes (-).

This feature is extended to support all DNN configurations and validations.