6 OCNWDAF Subscription and Analytics Requests

This chapter describes consumer subscription and analytics request procedures.

6.1 Analytics Subscription Request to the OCNWDAF

This section describes how the OCNWDAF service consumers subscribe or unsubscribe to the OCNWDAF to obtain analytics information. The Nnwdaf_AnalyticsSubscription service is used to subscribe, unsubscribe, and modify existing subscriptions to the OCNWDAF.

Figure 6-1 OCNWDAF Consumer Subscription Request


OCNWDAF Consumer Subscription Request

  1. The OCNWDAF service consumer initiates or cancels a subscription to analytics information by invoking the Nnwdaf_AnalyticsSubscription_Subscribe or Nnwdaf_AnalyticsSubscription_Unsubscribe service operation. When a subscription to analytics information is received, the OCNWDAF determines whether triggering data collection is required. If the service invocation is for a subscription modification, the NF service consumer includes an identifier (Subscription Correlation ID) to be modified in the Nnwdaf_AnalyticsSubscription_Subscribe request.
  2. If the OCNWDAF service consumer subscribes to analytics information, the OCNWDAF notifies the service consumer with the analytics information by invoking the Nnwdaf_AnalyticsSubscription_Notify service operation, based on the request from the service consumer, for example, Analytics Reporting Parameters.

6.2 Analytics Information Request to OCNWDAF

This section describes how the OCNWDAF service consumers request and obtain analytics information from the OCNWDAF. The Nnwdaf_AnalyticsInfo service is used to request and obtain information from the OCNWDAF.

Figure 6-2 Analytics Request


Analytics Request

  1. The OCNWDAF service consumer requests analytics information by invoking the Nnwdaf_AnalyticsInfo_Request service operation.
  2. On receiving the request, the OCNWDAF determines if a data collection needs to be triggered. If the requested analytics information is not present, it triggers a data collection request.
  3. If the OCNWDAF has the requested information, it responds to the consumer with the requested analytics information.

Note:

The consumer sends an HTTP GET request to obtain analytics data based on the query parameter value of the "event-id" attribute. Along with event-id, the ana-req attribute can be specified. It contains the parameter timeAnaNeeded, which sets the time when the analytics information is needed. Once the time specified timeAnaNeeded is crossed, the consumer does not need to wait for the analytics information any longer, and the OC-NWDAF sends an error response to the consumer.

6.3 Correlation between Network Data and Service Data

The correlation information from each NF input data helps OCNWDAF correlate data from different NFs. The following table contains correlation information:

Note:

The correlation information is not listed in the input data per network data analytics.

Table 6-1 Correlation between network data and service data

Correlation Information Description
Timestamp, IP address 5-tuple To correlate data from AF and from UPF
Timestamp, AN Tunnel Info (Clause 9.3.2.2, 3GPP TS 38.413 [16]) To correlate UPF data and OAM data which are reported by the RAN
Timestamp, UE IP address To correlate data from UPF and SMF
Timestamp, SUPI To correlate data from SMF and AMF
Timestamp, SUPI, DNN, S-NSSAI or UE IP address To correlate data from SMF and PCF

Timestamp, RAN UE NGAP ID

(Clause 9.3.3.2, 3GPP TS 38.413 [16]) and Global RAN Node ID

To correlate AMF data and OAM data reported by the RAN
Timestamp, Application ID, IP filter information To correlate data from SMF and AF