This feature has the following limitation:

• The SMF includes first-configured DNN profile in "dnnSmfInfoList" of NFProfile during registration with NRF.

To configure the subscriber policy, use the following sample configuration:

config 
   policy subscriber subscriber_policy_name 
      precedence precedence_value 
         cc-start-range cc_start_range_value 
         cc-stop-range cc_stop_range_value 
         gpsi-start-range gpsi_start_range_value 
         gpsi-stop-range gpsi_stop_range_value 
         imsi { mcc mcc_value | mnc mnc_value | msin  msin_value } 
         imsi-start-range imsi_start_value 
         imsi-stop-range imsi_stop_value 
         operator-policy operator_policy_name 
         pei-start-range pei_start_range_value 
         pei-stop-range pei_stop_range_value 
         sdt sdt_value 
         serving-plmn { mcc mcc_value | mnc mnc_value | mnc-list  mnc_list_value } 
         serving-plmn  serving_plmn_value 
         sst sst_value 
         supi-start-range supi_start_range_value 
         supi-stop-range supi_stop_range_value 
         instance-start-range start_range_value 
         instance-stop-range stop_range_value 
         end 

NOTES:

• precedence precedence_value: Specify the precedence value associated with the subscriber policy.

  The maximum limit for precedence is 2048.

• cc-start-range cc_start_range_value : Specify the charging characteristics start range value associated with the subscriber policy. cc_start_range_value must be a 1 to 4 digit hexadecimal string in the range of 0x1 to 0xffff. For example, 0001.

• cc-stop-range cc_stop_range_value : Specify the charging characteristics end range value associated with the subscriber policy. cc_stop_range_value must be a 1 to 4 digit hexadecimal string in the range of 0x1 to 0xffff. For example, 12AB.

• gpsi-start-range gpsi_start_range_value : Specify the GPSI start range value to be associated with the subscriber policy. gpsi_start_range_value must be an integer in the range from 1000000000 through 999999999999999.

• gpsi-stop-range gpsi_stop_range_value : Specify the GPSI stop range value to be associated with the subscriber policy. gpsi_stop_range_value must be an integer in the range from 1000000000 through 999999999999999.

• imsi { mcc mcc_value | mnc mnc_value | msin msin_value} : Specify the IMSI value by providing the MCC, MNC, or MSIN value that is to be associated with the subscriber policy.

• imsi-start-range imsi_start_value : Specify the IMSI start range value. imsi_start_value must be an integer in the range from 1000000000 through 999999999999999.

• imsi-stop-range imsi_stop_value : Specify the IMSI stop range value. imsi_stop_value must be an integer in the range from 1000000000 through 999999999999999.

• operator-policy operator_policy_name : Specify the operator policy to be associated with the subscriber policy.

  The maximum limit for operator policy is 2048.

• pei-start-range pei_start_range_value : Specify the PEI start range value. pei_start_range_value must be an integer in the range from 1000000000 through 999999999999999.

• pei-stop-range pei_stop_range_value : Specify the PEI stop range value. pei_stop_range_value must be an integer in the range from 1000000000 through 999999999999999.

• sdt sdt_value : Specify the SDT value be associated with the subscriber policy. sdt_value must be a 6-digit octet string in the [0-9a-fA-F]{6} - 000000 - ffffff format. For example, 1A2B3c.

• serving-plmn { mcc mcc_value mnc mnc_value mnc-list mnc_list_values} : Specify the 3-digit Mobile Country Code (MCC), 2- or 3-digit Mobile Network Code (MNC), or the list of MNC values of the serving PLMN. mcc_value and mnc_value must be a string. mnc_list_values must be a string, such as [580 660].

• sst sst_value : Specify the Slice/Service Type (SST) value. sst_value must be a 2-digit octet string in the [0-9a-fA-F]{2} - 00 to FF format. For example, A8.

• supi-start-range supi_start_range_value : Specify the SUPI start range value. supi_start_range_value must be an integer in the range from 1000000000 through 999999999999999.

• supi-stop-range supi_stop_range_value : Specify the SUPI stop range value. supi_stop_range_value must be an integer in the range from 1000000000 through 999999999999999.

• instance-start-range start_range_value : Specify the SMF instance start range value. start_range_value must be an integer in the range from 1 to 8.

• instance-stop-range stop_range_value : Specify the SMF instance stop range value. stop_range_value must be an integer in the range from 1 to 8.

To configure the operator policy, use the following sample configuration:

config 
   policy operator operator_policy_name 
      policy dnn dnn_policy_name [  [ secondary secondary_dnn_policy_name ] [   network-capability network_capability ]  ] 
      end 

NOTES:

• policy dnn dnn_policy_name [ [ secondary secondary_dnn_policy_name ] [ network-capability network_capability] ] : Specify the parameters of primary DNN policy to be associated with the operator policy. dnn_policy_name must be a string.

  • secondary secondary_dnn_policy_name : If the parameters of DNN policy to be associated with the operator policy don't match with the primary policy, specify the secondary DNN policy for fallback. secondary_dnn_policy_name must be a string.

  • network-capability network_capability : Specify the network capability configuration details for the respective operator policy that you have selected. The network_capability value must be a string.

To configure the DNN policy, use the following configuration:

config 
   policy dnn dnn_policy_name 
      dnn dnn_name profile dnn_profile_name dnn-list dnn_list 
   exit 
exit 

NOTES:

• policy dnn dnn_policy_name : Specify the DNN policy. dnn_policy_name must be an alphanumeric string.

  The maximum limit for DNN policy is 2048.

• dnn dnn_name : Specify the virtual DNN profile to map with the specified network DNN profile. dnn_name must be an alphanumeric string.

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

• profile dnn_profile_name : Specify the network DNN profile. dnn_profile_name must be an alphanumeric string.

  The maximum limit for DNN profile is increased from 512 to 2048.

• dnn-list dnn_list : Specify the list of DNNs supported by the UPF node.

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 | cgf ] 
   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, UPF, and CGF.

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 | cgf ] 
      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.

• 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.

To associate a subscriber policy under SMF service, use the following sample configuration:

config 
   profile smf smf_profile_name 
      service name service_name 
         subscriber-policy subscriber_policy_name 
         end 

NOTES:

• subscriber-policy subscriber_policy_name : Specify the subscriber policy name. subscriber_policy_name must be an alphanumeric string.

During the subscriber session creation, SMF selects operator policy based on the SMF instance IDs configured in the Subscriber Policy Configuration mode. For each subscriber, SMF associates the selected operator policies with different DNN profiles, virtual DNNs, IP pools, and UPF profiles.

SMF provides the flexibility to choose appropriate DNN profiles corresponding to the SMF instances.

For example, in an active-standby Geo Redundancy (GR) deployment scenario, assume that there are two racks (Rack 1 and Rack 2) with each rack comprising two regions (Region 1 and Region 2), two active and standby SMF instances (SMF instance 1 and SMF instance 2), IP pools (Pool 1 and Pool 2), virtual DNNs (vdnn 1 and vdnn 2), and two UPF sets (UPF Set 1 (UPF 1 and UPF 3) and UPF Set 2 (UPF 2 and UPF 4)).

SMF is configured in such a way that vdnn 1 is associated to SMF Instance 1, Pool 1, and UPF Set 1, and vdnn 2 is associated to SMF Instance 2, Pool 2, and UPF Set 2. When the subscriber attempts to establish PDU connection, SMF instance is selected based on the Virtual IP (VIP) of the session it lands. If SMF instance 1 in one region is active and selected, SMF chooses vdnn1, Pool 1, and UPF Set 1 even though the SMF instances have the same DNN in both the regions.

SMF subsequently distributes the IP pools from Pool 1 only to the UPFs in UPF Set 1. If the SMF instance IDs are not configured, SMF allocates the available IP addresses to the UPFs associated to both the SMF instances.

To configure the SMF instances, use the following sample configuration:

Note	It is recommended to add this configuration at runtime. A new operator policy selection post configuration change uses new configuration.

config 
   policy subscriber subscriber_policy_name 
      precedence precedence_value 
         instance-start-range start_range_value 
         instance-stop-range stop_range_value 
         operator-policy operator_policy_name 
         end 

NOTES:

• precedence precedence_value: Specify the precedence value associated with the subscriber policy.

  The maximum limit for precedence is 2048.

• instance-start-range start_range_value : Specify the SMF instance start range value. start_range_value must be an integer in the range from 1 to 8.

• instance-stop-range stop_range_value : Specify the SMF instance stop range value. stop_range_value must be an integer in the range from 1 to 8.

Configuration Example

The following is an example of a configuration show running-config policy subscriber command that describes SMF instances for DNN profile selection.

 [smf] smf# show running-config policy subscriber 
Wed Mar  6  05:09:45.143 UTC+00:00
policy subscriber polSub
 precedence 1
  sst                  02
  sdt                  Abf123
  serving-plmn mcc 123
  serving-plmn mnc 456
  supi-start-range     100000000000001
  supi-stop-range      999999999999999
  gpsi-start-range     100000000000001
  gpsi-stop-range      999999999999999
  instance-start-range 1
  instance-stop-range  1
  operator-policy      opPolHomer
 exit

SMF provides a way to configure common attributes in a parent DNN profile template and reuse it in other DNN profiles, for example, child DNN profiles as and when required. This feature optimizes the DNN profile configurations and improves the operational efficiency.

Note	The DNN Inheritance feature is currently qualified only for SMF (including legacy interfaces) and not for cnSGW-C.

This section provides details about how the network operators can perform the DNN profile configuration to inherit or reuse a parent DNN profile.

You can define all the common attributes in a separate DNN profile and then use this parent profile in other DNN profiles by using the CLI configuration.

To inherit the parent DNN profile with common attributes, use the following sample configuration:

config 
   profile dnn dnn_profile_name   
      inherit dnn_template_name 
       dnn rmgr  ims_pool_ipv6 
      end 

NOTES:

• inherit dnn_template_name : Specify the name of parent DNN profile to inherit to child profile(s).

Configuration Example

The following is an example configuration to inherit the attributes from a parent DNN profile and use them in a child profile.

// Parent DNN profile
profile dnn dnnprof-ims.epdg.prod
  dns primary ipv4 10.177.0.34
  dns primary ipv6 fd00:976a::9
  dns secondary ipv4 10.177.0.210
  dns secondary ipv6 fd00:976a::10
  network-element-profiles chf nfprf-chf1
  network-element-profiles amf nfprf-amf1
  network-element-profiles pcf nfprf-pcf1
  network-element-profiles udm nfprf-udm1
  dnn ims.epdg.prod network-function-list [ chf pcf udm upf ]
  timeout up-idle 3600 cp-idle 7320
  charging-profile           chgprof-1
  pcscf-profile              pcscf1
  ppd-profile                ppd-prof1
  ssc-mode 1 allowed [ 2 ]
  session type IPV6
  session skip-ind false
  upf apn ims.epdg.prod
  qos-profile                5qi-to-dscp-mapping-table-IMS
  always-on                  true
  dcnr                       true
  userplane-inactivity-timer 3600
  only-nr-capable-ue         false
exit

// Child DNN profile
profile dnn dnnprof-ims.prod
  inherit dnnprof-ims.epdg.prod
  dnn rmgr ims-pool-ipv6
exit

SMF supports IP pool allocation per slice with the same DNN. A slice is a logical end-to-end network that is created dynamically. A user equipent (UE) can access multiple slices over one access network, such as over the same radio interface.

SMF performs the following tasks:

• Register, discover, subscribe, and send traffic to all the external NFs based on the slice ID.

• Provide slice-based procedure and session statistics.

• Provide slice information on an EDR.

• Provide slice information on logs.

• Limit the maximum number of supported slices on SMF to 512.

SMF selects NFs, such as PCF, CHF, UDM, and AMF through the static configuration or NRF-based dynamic selection. In both these options, the messaging includes the slice information that is used in those interfaces.

SMF performs the following tasks:

• Register slice with NRF.

• Receive slice information on the N11 and N10 interfaces.

• Use slice for peer NF discovery and UPF selection.

• Send slice information on the N7 and N40 interfaces.

This section describes how to configure the IP pool allocation per slice and DNN.

Configuring this feature involves the following steps:

1. Configure tags. For details, see Configuring SMF Tags.

2. Perform the dynamic node selection with slice using the following tasks:

   • Register NRF. For details, see Registering NRF.

   • Configure allowed NSSAI values. For details, see Configuring Allowed NSSAI Values.

   • Discover NRF. For details, see Discovering NRF.

3. Configure NSSAI labels of smf_service_stats metrics for slice information on procedure and session statistice. For details, see Configuring Metrics Collection.