How it Works
The following figure illustrates a call flow representing the complete NF profile replacement.

Step |
Description |
---|---|
1 |
The NF Service Consumer sends a PUT request to the resource URI representing the NF instance. The payload body of the PUT request contains an update operation on the NF Profile of the NF instance |
2a |
On success, if the NF Profile changes, the NRF returns "200 OK" along with the full NF Profile data in the response body. |
2b |
If the NF instance, identified by the "nfInstanceID", is not found in the list of registered NF instances in the NRF database, the NRF returns 4xx or 5xx status code with the ProblemDetails IE providing details of the error. |
The following figure illustrates the call flow representing the NF registration and NF update messaging from NRF client library on NF profile change trigger from SMF-rest-ep.

-
The SMF rest-ep, on start-up, reads the SMF profile configuration and accordingly populates the NF management Profile. The rest-ep then triggers NRF-LIB to indicate the NF Profile change.
-
NRF library (NRF-LIB) maintains the NF registration status and the registered profile in an external cache pod. The NRF client detects whether the NF registration with NRF is completed. If the NRF client detects that the registration is not completed during NF profile change handling, perform Step 3. If the NF registration is complete, perform Step 4.
-
The NRF-LIB sends NF Register to NRF. It allows an NF Instance to register its NF profile in the NRF. It includes the registration of the general parameters of the NF Instance along with the list of services exposed by the NF Instance.
-
NRF-LIB fetches the registered NF profile and then compares it with the new profile.
-
The NRF-LIB NF sends NF update (PUT) request to the NRF when any of the parameters in the NF management profile changes due to SMF profile configuration change.
-
The NRF-LIB ignores the trigger if there is no change detected.
ImportantThe NF update is sent only from the elected master.
Load parameter is not set as part of NF update PUT message. Heartbeat is set as the current active heartbeat interval.