Feature Description
This section describes the NF management procedures and their configurations that SMF supports. These procedures are NF registration, NF deregistration, NF heartbeat, and NF Update. The NF registration, update, and heartbeat are sent from only one of the rest-ep pods, which is the elected primary node. After this nodes is elected, the instance remains as primary node for the NF management activities till the pod crashes or is removed.
NF management supports dynamic configuration change. With this feature, if the configurations were modified in the middle of the transaction or procedure, the ongoing transactions are not impacted.
The dynamic configuration change feature supports the following:
-
NRF transaction or procedure picks a configuration version (v1) and uses the same version until the NRF transaction or procedure completes.
-
If you change the configuration during an ongoing NRF transaction, then a new configuration version (v2) is created. However, the new configuration is applied in the new transaction.
The dynamic configuration changes apply to the following data structures:
-
NrfFailureProfileSt
-
NrfClntProfileSt
-
NrfGrpSt
-
NrfPairProfileSt
-
NrfMgmtGrpSt