A.54 Monitoring of NF service registration and update

28.5523GPP5G performance measurementsManagement and orchestrationRelease 18TS

The NRF maintains the information of available NF instances and their supported services, and each NF instance informs the NRF of the list of NF services that it supports.

The NF instance may make this information available to NRF when the NF instance becomes operative for the first time (registration) or upon individual NF service instance activation/de-activation within the NF instance (update operation) e.g. triggered after a scaling operation. The NF instance while registering the list of NF services it supports, for each NF service, may provide a notification endpoint information for each type of notification service that the NF service is prepared to consume, to the NRF during the NF instance registration. The NF instance could also update or delete the NF service related parameters (e.g. to delete the notification endpoint information). Registration with the NRF includes capacity and configuration information of the NF instances and at time of instantiation.

The failed NF service registration or update would result in that 1) the NF service cannot be discovered or consumed by the consumer, and 2) the NF service may not be able to receive the notifications for the other NF services it needs to consume, such failures would impact many users who need to be supported by the NF services. Therefore, the performance of the NF service registration or update need to be monitored, especially for the failure cases which need to trigger trouble shooting.