5.7.15 Redundant Transmission Experience Analytics

29.5523GPP5G SystemNetwork Data Analytics signalling flowsRelease 17Stage 3TS

This procedure is used by the NWDAF service consumer (may be an NF e.g. SMF) to obtain the Redundant Transmission Experience Analytics which are calculated by the NWDAF based on the information collected from the AMF, AF, SMF, UPF and/or OAM.

Figure 5.7.15-1: Procedure for Redundant Transmission Experience Analytics

1a. In order to obtain the Redundant Transmission Experience 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 "RED_TRANS_EXP" with the supported feature "RedundantTransmissionExp".

1b-1c. In order to obtain the Redundant Transmission Experience 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 "RED_TRANS_EXP" with the supported feature "RedundantTransmissionExp".

2a-2b. The NWDAF may invoke Namf_EventExposure_Subscribe service operation as described in clause 5.3.2.2.2 of 3GPP TS 29.518 [18] to retrieve the UE Mobility information. The AMF responds to the NWDAF an HTTP "201 Created" response.

3a-3b. If step 2a and step 2b are performed, the AMF may invoke Namf_EventExposure_Notify service operation as described in 3GPP TS 29.518 [18] clause 5.3.2.4. The NWDAF responds to the AMF an HTTP "204 No Content" response.

4a-4b. The NWDAF may invoke Nsmf_EventExposure_Subscribe service operation by sending an HTTP POST request targeting the resource "SMF Notification Subscriptions" to subscribe to the notification of Information related to PDU Session established with redundant transmission. The SMF responds to the NWDAF an HTTP "201 Created" response.

5a-5b. If step 4a and step 4b are performed, the SMF may invoke Nsmf_EventExposure_Notify service operation by sending an HTTP POST request to the NWDAF identified by the notification URI received in step 4a. The NWDAF responds to the SMF an HTTP "204 No Content" response.

6. The NWDAF may collect data related to packet delay measurement information from UPF, refer to clause 5.4 1 of TS 28.552 [27] for the performance measurement in UPF.

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

7. The NWDAF may invoke "Data collection service" to the OAM to get the packet drop and/or packet delay measurement refer to clause 5.1 of TS 28.552 [27] for the performance measurement in NG-RAN.

8a-8b. 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 service data related to UE mobility information. The AF responds to the NWDAF an HTTP "201 Created" response.

9a-9b. If step 8a and step 8b 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 8a. The NWDAF responds to the AF an HTTP "204 No Content" response.

10a-10d. 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 service data related to UE mobility information. The AF responds to the NEF an HTTP "201 Created" response and then the NEF responds to the NWDAF an HTTP "201 Created" response.

11a-11d. If step 10a to step 10d 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 10b 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 10a. 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.

12. The NWDAF calculates the Redundant Transmission Experience Analytics based on the data collected from AMF, AF SMF, UPF and/or OAM.

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

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

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

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

16. The same as step 6.

17. The same as step 7.

18a-18b. The same as step 9a and step 9b.

19a-18d. The same as step 11a and step 11d.

20. The same as step 12.

21a-21b. The same as step 13b and step 13c.

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

NOTE 3: For details of Nsmf_EventExposure_Subscribe/Notify service operations refer to 3GPP TS 29.508 [6].

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