NFStatus Notify Call Flow

Issuing a POST request to each callback URI of the various subscribed NF Instances, initiates the NFStatus Notify operator.

Notification from NRF in the Same PLMN
Call Flow Description for Notification from NRF in the Same PLMN
StepDescription
1

The NRF sends a POST request to the callback URI.

The request body for a profile change notification request includes the following:

  • event: This attribute indicates the notification type. It can be one of the following:

    • NF_REGISTERED

    • NF_DEREGISTERED

    • NF_PROFILE_CHANGED

  • nfInstanceUri: Uniform Resource Identifier (URI) of the NF Instance associated to the notification event.

  • nfProfile: Indicates the new or updated NF profile.

  • profileChanges: This attribute identifies changes on the profile of the NF Instance associated to the notification event. This attribute is available when the event notification type is "NF_PROFILE_CHANGED".

2a

When the notification is successful, the NRF sends a "204 No content" response.

2b

The SMF returns a "404 Not Found" status code with the problem details if the SMF disregards the "nfStatusNotificationURI" as a valid notification URI. For example, if the URI does not belong to any of the existing subscriptions that the SMF has created in the NRF.