Configuring a Virtual DNN under a DNN Profile

The SMF provides flexibility to send Virtual-DNN value on all northbound interfaces. Virtual DNN to be send on each interface can be configured as follows. The Resource Manager (RMGR) virtual DNN is used to map IP pool to DNN.

To configure a virtual DNN under a DNN profile, use the following sample configuration:

config 
   profile dnn profile_name 
      dnn dnn_name network-function-list [ chf | ocs | pcf | pcrf | radius | upf ] 
   profile profile_name 
   end 

NOTES:

  • dnn dnn_name : Specify the DNN name. dnn_name must be an alphanumeric string.

  • network-function-list : Specify the network functions. The DNN profile goes to these network functions. Supported values are CHF, OCS, PCF, PCRF, RADIUS and UPF.

Configuring Override Command

In addition to the preceding CLI, SMF has the capability to override the access DNN with the vDNN received from the RADIUS server.

RADIUS-ep is upgraded to decode Starent VSA attribute “SN-Virtual-APN-Name (Type: 94) “ and application is enhanced to support this attribute.

RADIUS Server sends vDNN to SMF in access accept and SMF includes this DNN in N4 messages to UPF. A new configuration is added on the SMF to decide whether to override the DNN sent on specific interfaces with the value received from RADIUS server.

Override keyword is added to support virtual DNN from the Radius Server.

config 
   profile dnn profile_name 
      dnn override network-function-list [ chf | ocs | pcf | pcrf | radius | upf ] 
      dnn override rmgr 
      end 

Details of attribute used for receiving virtual DNN on RADIUS interface is as follows:

  • SN: Virtual-APN-Name

  • Syntax: Opaque Value

  • Length: 1-64

  • Type: 26

  • Vendor ID: 8164

  • VSA Type: 94

  • Override keyword takes priority over the locally configured value.

  • Override keyword is present but RADIUS isn’t providing any vDNN then SMF uses the locally configured value (if present) or gnDNN.

  • If for an interface, there’s no configuration (either override or local-dnn-name), it takes the gnDNN.

    Override vDNN isn’t applicable for UDM network-function.

  • The framed-ip received from the RADIUS server must be a part of the IP pool associated to the vDNN received from the RADIUS server. If there’s mismatch, session creation fails.

  • with this feature, different RMGR vDNN can be assigned to the same UE for same DNN for dynamic and static ip allocation case and hence IP can be assigned from dynamic or static pool.