5.7.4 NF load Analytics

29.5523GPP5G SystemNetwork Data Analytics signalling flowsRelease 17Stage 3TS

This procedure is used by the NWDAF service consumer (may be an NF, or the OAM) to obtain the NF load analytics which are calculated by the NWDAF based on the information collected from the NRF and/or the OAM, may also collect UE input data via the AF (for the untrusted AF via the NEF). If target NF type is UPF, the NWDA may collect the information from UPF.

Figure 5.7.4-1: Procedure for NF load Analytics

1a. In order to obtain the NF load analytics, the NWDAF service consumer may invoke Nnwdaf_AnalyticsInfo_Request service operation as described in clause 5.2.3.1, the requested event is set to "NF_LOAD" with the supported feature "NfLoad".

1b-1c. In order to obtain the NF load analytics, the NWDAF service consumer may invoke Nnwdaf_EventsSubscription_Subscribe service operation as described in clause 5.2.2.1, the subscribed event is set to "NF_LOAD" with the supported feature "NfLoad".

2a-2b. The NWDAF may invoke Nnrf_NFDiscovery_Request service operation as described in clause 5.3.2.2 of 3GPP TS 29.510 [26] for each NF, to obtain the initial NF profile which contains NF status and may contains NF load information. The NRF responds to the NWDAF an HTTP "201 Created" response.

3. The NWDAF may invoke "Data collection service" to the OAM to get the NF resource usage information as described in clause 5.7 of 3GPP TS 28.552 [27] and/or the NF resource configuration information as described in clause 5.2 of 3GPP TS 28.533 [28]. The NWDAF may also collect the MDT data information for UE as described in 3GPP TS 37.320 [29].

4a-4b. The NWDAF may invoke Nnrf_NFManagement_NFStatusSubscribe service operation as described in clause 5.2.2.5 of 3GPP TS 29.510 [26] to subscribe to the NF status and/or NF load information. The NRF responds to the NWDAF an HTTP "201 Created" response.

5a-5b. If step 4a and step 4b are performed, the NRF may invoke Nnrf_NFManagement_NFStatusNotify service operation as described in clause 5.2.2.6 of 3GPP TS 29.510 [26]. The NWDAF responds to the NRF an HTTP "204 No Content" response.

6. If the target NF type is UPF, the NWDAF may collect traffic usage report information from UPF.

NOTE 1: How the NWDAF collects UPF information is not defined in this release of the specification.

7a-7b. If the AF is trusted, the NWDAF may invoke Naf_EventExposure_Subscribe service operation to the AF directly by sending an HTTP POST request targeting the resource "Application Event Subscriptions" to collect the Collective Behaviour of UEs. The AF responds to the NWDAF an HTTP "201 Created" response.

8a-8b. If step 7a and step 7b are performed, the AF invokes Naf_EventExposure_Notify service operation by sending an HTTP POST request to the NWDAF identified by the notification URI received in step 7a. The NWDAF responds to the AF an HTTP "204 No Content" response.

9a-9d. If the AF is untrusted, the NWDAF may invoke Nnef_EventExposure_Subscribe service operation to the NEF by sending an HTTP POST request targeting the resource "Network Exposure Event Subscriptions" and then the NEF invokes Naf_EventExposure_Subscribe service operation by sending an HTTP POST request targeting the resource "Application Event Subscriptions" to collect the Collective Behaviour of UEs. The AF responds to the NEF an HTTP "201 Created" response and then the NEF responds to the NWDAF an HTTP "201 Created" response.

10a-10d. If step 9a to step 9d are performed, the AF invokes Naf_EventExposure_Notify service operation by sending an HTTP POST request to the NEF identified by the notification URI received in step 9b and the NEF invokes Nnef_EventExposure_Notify service operation by sending an HTTP POST request to the NWDAF identified by the notification URI received in step 9a. The NWDAF responds to the NEF an HTTP "204 No Content" response and then the NEF responds to the AF an HTTP "204 No Content" response.

11. The NWDAF calculates the NF load analytics based on the data collected from NRF, OAM, UPF and/or AF.

12a. If step 1a is performed, the NWDAF responds to the Nnwdaf_AnalyticsInfo_Request service operation as described in clause 5.2.3.1.

12b-12c. If step 1b and step 1c are performed, the NWDAF invokes Nnwdaf_EventsSusbcription_Notify service operation as described in clause 5.2.2.1.

13. The same as step 3.

14a-14b. The same as step 5a and step 5b.

15. The same as step 6.

16a-16b. The same as step 8a and step 8b.

17a-17d. The same as step 10a to step 10d.

18. The same as step 11.

19a-19b. The same as step 12b and step 12c.

NOTE 2: For details of Naf_EventExposure_Subscribe/Notify service operations refer to 3GPP TS 29.517 [12].

NOTE 3: For details of Nnef_EventExposure_Subscribe/Notify service operations refer to 3GPP TS 29.591 [11].

NOTE 4: For details of Nnwdaf_EventsSubscription_Subscribe/Unsubscribe/Notify or Nnwdaf_AnalyticsInfo_Request service operations refer to 3GPP TS 29.520 [5].