DNN Profile
DNN profile defines various parameters for a particular DNN.
The following table describes if the dynamic configuration change is allowed or if the DNN must be set 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 |
|
NetworkCapability |
Allowed |
No impact |
|
PolicyProfile |
Allowed |
No impact |
NOTES:
-
It’s recommended not to modify or delete the NetworkElementProfile and ChargingProfile configuration parameters. If the parameters are changed, then the behavior for:
-
NetworkElementProfile: Messages for the existing sessions may be sent on new servers.
-
ChargingProfile: There may be some inconsistencies related to Usage Reporting Rules (URRs) between SMF and UPF.
-
-
For modifying the DNN profile mapping, the DNN profile must be in the offline mode.
-
It’s recommended to review the messages shown in the help string before executing the CLI commands.
-
Switch the DNN profile to an offline mode when configuring the parameters dynamically. This step avoids the network impact, which is caused by the configuration changes.