How it Works
This section describes the Maintenance Operational Procedure and how dynamic change in configuration works for the supported SMF configurations.
Maintenance Operational Procedure
-
Shutdown (offline) SMF by executing mode offline CLI command under SMF Profile.
SMF sends NFUpdate with Method PUT and NFStatus as “UNDISCOVERABLE”
-
Clean up the sessions using clear subscriber sess all CLI command.
-
Change the configurations and remove mode offline CLI command.
SMF sends NFUpdate with Method PUT and NFStatus as “Registered”.
SMF Profile and SMF-Service Profile
The following table describes how dynamic change in configuration works for the supported SMF configurations.
Configuration parameters | Dynamic Change | Impact on Existing Sessions | NRF Update | Maintenance Operational Procedure |
---|---|---|---|---|
locality |
Allowed |
Sessions will start using the newer values. |
Not Required |
Allowed |
node-id |
Not Applicable |
No Impact |
Not Applicable |
Not Applicable |
fqdn |
Allowed |
SMF always fetches the latest FQDN value for sessions while interacting with UDM. |
Allowed |
Allowed |
allowed-nssai |
Allowed |
Sessions will start using the newer values. |
Allowed |
Allowed |
plmn-id |
Allowed |
Sessions will start using the newer values. |
Allowed |
Allowed |
service name, schema, service-id, version |
Allowed |
Sessions will start using the newer values. |
Allowed |
Allowed |
http-endpoint |
Allowed |
Sessions will start using the newer values. |
Allowed |
Allowed |
icmpv6-profile |
Allowed |
Sessions will start using the newer values. |
Not Required |
Not Required |
compliance-profile |
Allowed |
SMF might perform parse-failure because of incompatibility issues between SMF and other NFs for various SBI interfaces. |
Not Required |
Not Required |
access-profile |
Allowed |
Sessions will start using the newer values. |
Not Required |
Not Required |
subscriber-policy |
Allowed |
Sessions will start using the newer values. |
Not Required |
Not Required |