NFStatusNotify

[free5gc]

NFStatusNotify

[free5gc-org]

Hi,
As we implementing this piece of code, we referencing from R15.3 for SBI.
It's welcome to PR if there is any problem if you find. :D

[jpestima]

Greetings,

I looked up the R15.3 version for SBI, and it still references the NFStatusNotify as part of the consumer subscriptions and not of the the registration of profiles.

It seems that it has been like that for a while.

Best Regards.

[free5gc-org]

Hi,

When it comes to NFRegistration, we'll find the subscription and check ValidityTime.
Maybe you can provide your subscribe data?

[jpestima]

Greetings,

This is my SubscriptionData,

Request:

{"nfStatusNotificationUri":"https://localhost:8001/test","reqNfInstanceId":null,"subscrCond":{"serviceName":"namf_evts"},"subscriptionId":"76bb8c75-0406-4ac5-bb2a-d71cb397c9cd","validityTime":"2020-04-08T14:24:22Z","reqNotifEvents":null,"plmnId":null,"nid":null,"notifCondition":null,"reqNfType":"AMF","reqNfFqdn":null,"reqSnssais":null,"reqPlmnList":null}

Response:

Response code: 201, Response body: {"nfStatusNotificationUri":"https://localhost:8001/test","reqNfType":"AMF","subscrCond":{"serviceName":"namf_evts"},"subscriptionId":"14","validityTime":"2020-04-08T14:24:22Z"}

Later there are no notifications arriving at the specified nfStatusNotificationUri.

Best Regards.

[free5gc-org]

hi @jpestima ,
Can you please provide your pcap file and NRF keylog (nrfsslkey.log)?
We have test your subscription but it seems no problem on our test.

BR

[jpestima]

Hello @free5gc-org , I don't think you guys understood the question. Like I previously mentioned, the problem is not on the SubscriptionData, it is in the NotificationData that should arrive at the "nfStatusNotificationUri":"https://localhost:8001/test", whenever there are changes in a NFProfile, which does not seem to happen.

Imagine the following scenario:

1. NF A Producer Registers in NRF (PUT to the NRF)
2. NF B Consumer subscribes to NF A (PUT to the NRF)
3. NF A Producer Deregisters from NRF (DELETE to the NRF)
4. NRF notifies NF B that the producer has been deregistered. (POST from the NRF)

Steps 1-3 work perfectly fine, however, the 4th step does not happen.

Our NRF has been up for a week with multiple usages, however the mentioned file is empty.

[free5gc-org]

@jpestima this issue is fixed in 3.0.2 and the "serviceName" attribute should be "namf-evts".