DNN Profile

DNN Profile defines the various parameters for a DNN.

The following table describes if the configuration change can be dynamically allowed or if you must set the DNN to an offline mode.

Configuration Parameters Dynamic Change Impact on Existing Sessions
DnsServers Allowed No impact
DnnInfo Allowed New values are used after database reload of the session
NetworkElementProfile Not recommended (See NOTES)
Timeout Allowed No impact
ChargingProfile Not recommended (See NOTES)
RemoteVmac Allowed No impact
PcscfProfile Allowed No impact
PpdProfile Allowed Immediate (new values are used)
DefaultSscMode Allowed No impact
DefaultPduSession Allowed No impact
AllowedPduSession Allowed No impact
QosProfile Allowed Immediate (new values are used)
UpfApn Allowed No impact
SecondaryAuthen Allowed No impact
LocalAuthorization Allowed No impact
Note
  • In this release, we do not recommend changing (modify or delete) the NetworkElementProfile and ChargingProfile configuration parameters. If they are changed, the behavior for:

    • NetworkElementProfile: Messages for the existing sessions may be sent on new servers.

    • ChargingProfile: There may be some inconsistency between SMF and UPF related to URRs.

  • For modifying the DNN Profile mapping, the DNN Profile must be in the offline mode.

  • The SMF may report a warning when the configurations are modified. These modifications may have an impact on the ongoing calls. We recommend that you review the warning messages and take the appropriate action.

  • You can switch the DNN profile to an offline mode when dynamically configuring the parameters. This step avoids the network impact, which is caused by the configuration changes.