4.3 Nnwdaf_AnalyticsInfo Service

29.5203GPP5G SystemNetwork Data Analytics ServicesRelease 18Stage 3TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

4.3.1 Service Description

4.3.1.1 Overview

The Nnwdaf_AnalyticsInfo service as defined in 3GPP TS 23.501 [2], 3GPP TS 23.288 [17] and 3GPP TS 23.503 [4], is provided by the Network Data Analytics Function (NWDAF).

This service:

– allows NF service consumers to request and get different type of analytic event information; and

– allows NF service consumers to request and get context information related to analytics subscriptions.

The types of observed events include:

– Slice load level information;

– Network slice instance load level information;

– Service experience;

– NF load;

– Network performance;

– Abnormal behaviour;

– UE mobility;

– UE communication;

– User data congestion;

– QoS sustainability;

– SM congestion control experience;

– Dispersion;

– Redundant transmission experience;

– WLAN performance; and

– DN performence.

4.3.1.2 Service Architecture

The 5G System Architecture is defined in 3GPP TS 23.501 [2]. The Network Data Analytics Exposure architecture is defined in 3GPP TS 23.288 [17]. The Network Data Analytics signalling flows are defined in 3GPP TS 29.552 [25], the Policy and Charging related 5G architecture is also described in 3GPP TS 23.503 [4] and 3GPP TS 29.513 [5].

The Nnwdaf_AnalyticsInfo service is part of the Nnwdaf service-based interface exhibited by the Network Data Analytics Function (NWDAF).

Known consumers of the Nnwdaf_AnalyticsInfo service are:

– Policy Control Function (PCF)

– Network Slice Selection Function (NSSF)

– Access and Mobility Management Function (AMF)

– Session Management Function (SMF)

– Network Exposure Function (NEF)

– Application Function (AF)

– Operation, Administration, and Maintenance (OAM)

– Network Data Analytics Function (NWDAF)

– Data Collection Coordination Function (DCCF)

The PCF accesses the Nnwdaf_AnalyticsInfo service at the NWDAF via the N23 Reference point. The NSSF accesses the Nnwdaf_AnalyticsInfo service at the NWDAF via the N34 Reference point.

Figure 4.3.1.2-1: Reference Architecture for the Nnwdaf_AnalyticsInfo Service; SBI representation

Figure 4.3.1.2-2: Reference Architecture for the Nnwdaf_AnalyticsInfo Service: reference point representation

4.3.1.3 Network Functions

4.3.1.3.1 Network Data Analytics Function (NWDAF)

The Network Data Analytics Function (NWDAF) provides specific analytics information for different analytic events and, if the "AnaCtxTransfer" feature is supported, context information related to analytics subscriptions to NF service consumers.

4.3.1.3.2 NF Service Consumers

The Policy Control Function (PCF):

– supports taking analytics information for slice load level information from the NWDAF;

– supports taking analytics information for service experience related network data from the NWDAF;

– supports taking analytics information for network performance from the NWDAF;

– supports taking analytics information for abnormal UE behaviour from the NWDAF;

– supports taking analytics information for user data congestion from the NWDAF.

– supports taking analytics information for dispersion from the NWDAF;

– supports taking analytics information for WLAN performance from the NWDAF; and

– supports taking one or more above input from NWDAF into consideration for policies on assignment of network resources and/or for traffic steering policies.

NOTE: How this information is used by the PCF is not standardized in this specification.

The Network Slice Selection Function (NSSF):

– supports taking slice load level information or network slice instance load level information from the NWDAF into consideration for slice selection;

– supports taking analytics information for service experience related network data from the NWDAF; and

– supports taking analytics information for dispersion at the slice from the NWDAF.

The Access and Mobility Management Function (AMF):

– supports taking SMF load information from the NWDAF into consideration for SMF selection;

– supports taking expected UE behaviour information (UE mobility and/or UE communication) from the NWDAF into consideration for monitoring UE behaviour;

– supports taking abnormal UE behaviour information from the NWDAF into consideration for adjustment of UE mobility related network parameters to solve the abnormal risk;

– supports taking slice load level information or network slice instance load level information from NWDAF into consideration for slice selection;

– supports taking analytics information for service experience related network data from the NWDAF; and

– supports taking analytics information for dispersion at the slice from the NWDAF.

The Session Management Function (SMF):

– supports taking UPF load information from the NWDAF into consideration for UPF selection;

– supports taking expected UE behaviour information (UE mobility and/or UE communication) from the NWDAF into consideration for monitoring UE behaviour;

– supports taking UE mobility information from the NWDAF into consideration for UPF selection;

– supports taking abnormal UE behaviour information from the NWDAF into consideration for adjustment of UE mobility related network parameters to solve the abnormal risk;

– supports taking analytics information for SM congestion control experience from the NWDAF into consideration for determining back-off timer provided to UE;

– supports taking analytics information for redundant transmission experience from the NWDAF to consider whether redundant transmission shall be performed, or (if it had been activated) shall be stopped; and

– supports taking analytics information for DN performance from the NWDAF into consideration for user plane performance.

The Network Exposure Function (NEF):

– supports forwarding UE mobility information from the NWDAF to the AF when it is untrusted;

– supports forwarding UE communication information from the NWDAF to the AF when it is untrusted;

– supports forwarding expected UE behavioural information (UE mobility and/or UE communication) from the NWDAF to the AF when it is untrusted;

– supports forwarding abnormal behaviour information from the NWDAF to the AF when it is untrusted;

– supports forwarding user data congestion information from the NWDAF to the AF when it is untrusted;

– supports forwarding network performance information from the NWDAF to the AF when it is untrusted;

– supports forwarding QoS Sustainability information from the NWDAF to the AF when it is untrusted;

– supports forwarding Dispersion information from the NWDAF to the AF when it is untrusted;

– supports forwarding DN performance information from the NWDAF to the AF when it is untrusted; and

– supports forwarding Observed Service Experience information from NWDAF to the AF when it is untrusted.

The Application Function (AF):

– supports receiving UE mobility information from the NWDAF or via the NEF;

– supports receiving UE communication information from the NWDAF or via the NEF;

– supports receiving expected UE behavioural information (UE mobility and/or UE communication) from the NWDAF or via the NEF;

– supports receiving abnormal behaviour information from the NWDAF or via the NEF;

– supports receiving user data congestion information from the NWDAF or via the NEF;

– supports receiving network performance information from the NWDAF or via the NEF;

– supports receiving QoS Sustainability information from the NWDAF or via the NEF;

– supports receiving Dispersion information from the NWDAF or via the NEF;

– supports receiving DN performance information from NWDAF or via the NEF; and

– supports receiving Observed Service Experience information from NWDAF or via the NEF.

The Operation, Administration, and Maintenance (OAM):

– supports receiving slice load level information from the NWDAF;

– supports receiving observed service experience from the NWDAF;

– supports receiving NF load information from the NWDAF;

– supports receiving network performance information from the NWDAF;

– supports receiving UE mobility information from the NWDAF;

– supports receiving UE communication information from the NWDAF;

– supports receiving expected UE behaviour information (UE mobility and/or UE communication) from the NWDAF; and

– supports receiving abnormal UE behaviour information from the NWDAF.

The Network Data Analytics Function (NWDAF):

– supports receiving information for all types of network data analytics from the NWDAF; and

– supports receiving context information related to analytics subscriptions from the NWDAF.

The Data Collection Coordination Function (DCCF):

– supports receiving information for all types of network data analytics from the NWDAF.

4.3.2 Service Operations

4.3.2.1 Introduction

Table 4.3.2.1-1: Operations of the Nnwdaf_AnalyticsInfo Service

Service operation name	Description	Initiated by
Nnwdaf_AnalyticsInfo_Request	This service operation is used by an NF to request and get specific analytics from NWDAF.	NF consumer (PCF, NSSF, AMF, SMF, NEF, AF, OAM, NWDAF, DCCF)
Nnwdaf_AnalyticsInfo_ContextTransfer	This service operation is used by an NF to request and get context information related to analytics subscriptions from NWDAF.	NF consumer (NWDAF)

4.3.2.2 Nnwdaf_AnalyticsInfo_Request service operation

4.3.2.2.1 General

The Nnwdaf_AnalyticsInfo_Request service operation is used by an NF service consumer to request and get specific analytics information from the NWDAF.

4.3.2.2.2 Request and get from NWDAF Analytics information

Figure 4.3.2.2.2-1 shows a scenario where the NF service consumer (e.g. PCF) sends a request to the NWDAF to request and get from the NWDAF analytics information (as shown in 3GPP TS 23.288 [17]).

Figure 4.3.2.2.2-1: Requesting a NWDAF Analytics information

The NF service consumer (e.g. PCF) shall invoke the Nnwdaf_AnalyticsInfo_Request service operation when requesting the NWDAF analytics information. The NF service consumer shall send an HTTP GET request on the resource URI "{apiRoot}/nnwdaf-analyticsinfo/<apiVersion>/analytics" representing the "NWDAF Analytics" (as shown in figure 4.3.2.2.2-1, step 1), to request analytics data according to the query parameter value of the "event-id" attribute. In addition, the following information may be provided:

– common reporting requirement in the "ana-req" attribute as follows:

1) identification of time window for the requested analytics data applies via identification of date-time(s) in the "startTs" and "endTs" attributes;

2) preferred level of accuracy of the analytics in "accuracy" attribute;

3) percentage of sampling among impacted UEs in the "sampRatio" attribute;

4) maximum number of objects in the "maxObjectNbr" attribute;

5) maximum number of SUPIs expected for an analytics report in the "maxSupiNbr" attribute;

6) identification of time when analytics information is needed in the "timeAnaNeeded" attribute if the feature "EneNA" is supported;

7) indication of which analytics metadata is requested to be delivered with the response in the "anaMeta" attribute if the feature "Aggregation" is supported;

8) requested values for the analytics metadata information to be used for the generation of the analytics in the "anaMetaInd" attribute if the feature "Aggregation" is supported; and/or

9) preferred accuracy level per analytics subset in the "accPerSubset" attribute if the "listOfAnaSubsets" attribute is present and the EneNA feature is supported.

For different event types:

– if the event is "LOAD_LEVEL_INFORMATION", it shall provide the event specific filter information within "event-filter" attribute including identification(s) of the network slice via:

1) identification of network slice(s) in the "snssais" attribute; or

2) any slices indication in the "anySlice" attribute;

– if the feature "NsiLoad" is supported and the event is "NSI_LOAD_LEVEL", it shall provide the event specific filter information within "event-filter" attribute including identification(s) of the network slice via:

1) identification of network slice(s) and the optionally associated instance(s) if available, in the "nsiIdInfos" attribute; or

NOTE 1: The network slice instance of a PDU session is not available in the PCF.

2) any slices indication in the "anySlice" attribute;

and may include:

1) a list of analytics subsets carried by "listOfAnaSubsets" attribute with value(s) only applicable to "NSI_LOAD_LEVEL" event, if the "EneNA" feature is supported;

– if the feature "NfLoad" is supported and the event is "NF_LOAD", it shall provide:

1) identification of target UE(s) to which the request applies by "supis" or "anyUe" in the "tgt-ue" attribute; and

NOTE 2: Only NF instances of type AMF and SMF which are serving the UE can be determined using a SUPI in "supis" attribute.

NOTE 3: If a list of the NF Instance IDs (or respectively of NF Set IDs) is provided, the NWDAF needs to provide the analytics for each designated NF instance (or respectively for each NF instance belonging to each designated NF Set). In such case the target UE(s) of the Analytics Reporting need be ignored.

– the "event-filter" attribute may provide:

a) either list of NF instance IDs in the "nfInstanceIds" attribute or list of NF set IDs in the "nfSetIds" attribute if the identification of target UE(s) applies to all UEs;

b) list of NF instance types in the "nfTypes" attribute;

c) identification of network slice(s) in the "snssais" attribute;

d) optional area of interest by "networkArea" attribute; and/or

e) an optional list of analytics subsets by "listOfAnaSubsets" attribute with value(s) only applicable to NF_LOAD event, if the "EneNA" feature is supported;

– if the feature "UeMobility" is supported and the event is "UE_MOBILITY", it shall provide:

1) identification of target UE(s) to which the request applies by "supis" or "intGroupIds" attribute in the "tgt-ue" attribute;

– and may provide:

1) event specific filter information in the "event-filter" attribute:

a) identification of network area to which the request applies via identification of network area by "networkArea" attribute; and/or

b) if the feature "UeMobilityExt" is supported,

i) identification of LADN DNN in the "ladnDnns" attribute;

ii) visited Area(s) of Interest as the "visitedAreas" attirbute;

NOTE 1: For LADN service, the consumer (e.g. SMF) provides the LADN DNN to refer the LADN service area as the AOI.

– if the feature "UeCommunication" is supported and the event is "UE_COMM", it shall provide:

1) identification of target UE(s) to which the request applies by "supis" or "intGroupIds" attribute in the "tgt-ue" attribute;

– and may provide:

1) event specific filter information in the "event-filter" attribute:

a) identification of the application as "appIds" attribute;

b) identification of network area to which the request applies via identification of network area by "networkArea" attribute;

c) identification of DNN in the "dnns" attribute;

d) identification of network slice(s) in the "snssais" attribute; and/or

e) a list of analytics subsets carried by "listOfAnaSubsets" attribute with value(s) only applicable to "UE_COMM" event, if the "EneNA" feature is supported;

– if the feature "NetworkPerformance" is supported and the event is "NETWORK_PERFORMANCE", it shall provide:

1) identification of target UE(s) to which the request applies by "supis", "intGroupIds" or "anyUe" attribute in the "tgt-ue" attribute;

2) event specific filter information in the "event-filter" attribute which shall provide:

a) the network performance types via "nwPerfTypes" attribute;

the "event-filter" attribute may provide:

a) identification of network area to which the request applies via identification of network area(s) by "networkArea" attribute (mandatory if "anyUe" attribute is set to true); and/or

b) a list of analytics subsets carried by "listOfAnaSubsets" attribute with value(s) only applicable to "NETWORK_PERFORMANCE" event, if the "EneNA" feature is supported;

– if the feature "ServiceExperience" is supported and the event is "SERVICE_EXPERIENCE", it shall provide:

1) identification of target UE(s) to which the request applies by "supis", "intGroupIds" or "anyUe" attribute in the "tgt-ue" attribute;

2) event specific filter information in the "event-filter" attribute which shall provide:

a) any slices indication in the "anySlice" attribute or identification of network slice(s) together with the optionally associated network slice instance(s) if available, via the "nsiIdInfos" attribute; and

NOTE 4: The network slice instance of a PDU session is not available in the PCF.

the "event-filter" attribute may provide:

a) identification of application(s) to which the request applies via "appIds" attribute;

b) identification of DNN via identification of Dnn(s) by "dnns" attribute;

c) identification of user plane accesses to one or more DN(s) where applications are deployed via "dnais" attribute;

d) identification of network area to which the request applies via identification of network area(s) by "networkArea" attribute (mandatory if "anyUe" attribute is set to true);

e) if "appIds" attribute is provided, the bandwidth requirement of each application by "bwRequs" attribute;

f) identication of all the RAT types and/or all the frequencies that the NWDAF received for the application or specific RAT type(s) and/or frequency(ies) and the service experience threshold value(s) for the RAT Type(s) and/or Frequency value(s) where the UE camps on by "ratFreqs" attribute if the feature "ServiceExperienceExt" is also supported;

g) a list of analytics subsets carried by "listOfAnaSubsets" attribute with value(s) only applicable to "SERVICE_EXPERIENCE" event, if the "EneNA" feature is supported;

h) the identification of the UPF as the "upfInfo" attribute if the feature "ServiceExperienceExt" is also supported; and/or

i) IP address(s)/FQDN(s) of the Application Server(s) as the "appServerAddrs" attribute if the feature "ServiceExperienceExt" is also supported;

– if the feature "QoSSustainability" is supported and the event is "QOS_SUSTAINABILITY", it shall provide:

1) event specific filter information in the "event-filter" attribute which shall provide:

a) identification of network area to which the request applies via identification of network area by "networkArea" attribute; and

b) QoS requirements via "qosRequ" attribute;

2) identification of target UE(s) to which the request applies by "anyUe" in the "tgt-ue" attribute;

the "event-filter" attribute may provide:

a) identification of network slice(s) by "snssais" attribute;

– if the feature "AbnormalBehaviour" is supported and the event is "ABNORMAL_BEHAVIOUR", it shall provide:

1) identification of target UE(s) to which the request applies by "supis", "intGroupIds" or "anyUe" attribute in the "tgt-ue" attribute; and

2) event specific filter information in the "event-filter" attribute which shall provide

a) either the expected analytics type via "exptAnaType" attribute or a list of exception Ids via "excepIds" attribute. If the expected analytics type via "exptAnaType" attribute is provided, the NWDAF shall derive the corresponding Exception Ids from the received expected analytics type as follows:

– if "exptAnaType" attribute sets to "MOBILITY", the corresponding list of Exception Ids are "UNEXPECTED_UE_LOCATION", "PING_PONG_ACROSS_CELLS", "UNEXPECTED_WAKEUP" and "UNEXPECTED_RADIO_LINK_FAILURES";

– if "exptAnaType" attribute sets to "COMMUN", the corresponding list of Exception Ids are "UNEXPECTED_LONG_LIVE_FLOW", "UNEXPECTED_LARGE_RATE_FLOW", "SUSPICION_OF_DDOS_ATTACK", "WRONG_DESTINATION_ADDRESS" and "TOO_FREQUENT_SERVICE_ACCESS";

– if "exptAnaType" attribute sets to "MOBILITY_AND_COMMUN", the corresponding list of Exception Ids includes all above derived exception Ids.

The derived list of Exception Ids are used by the NWDAF to notify the NF service consumer when UE’s behaviour is exceptional based on one or more Exception Ids within the list.

If the "anyUe" attribute in the "tgt-ue" attribute sets to "true":

a) the expected analytics type via the"exptAnaType" attribute or the list of Exception Ids via "excepIds" attribute shall not be requested for both mobility and communication related analytics at the same time;

b) if the expected analytics type via the"exptAnaType" attribute or the list of Exception Ids via "excepIds" attribute is mobility related, at least one of identification of network area by "networkArea" attribute and identification of network slice(s) by "snssais" attribute should be provided; and

c) if the expected analytics type via the"exptAnaType" attribute or the list of Exception Ids via "excepIds" attribute is communication related, at least one of identification of network area by "networkArea" attribute, identification of application(s) by "appIds" attribute, identification of DNN(s) in the "dnns" attribute and identification of network slice(s) by "snssais" attribute should be provided;

the "event-filter" attribute may provide:

a) expected UE behaviour via "exptUeBehav" attribute;

– if the feature "UserDataCongestion" is supported and the event is "USER_DATA_CONGESTION", it shall provide one of the following attributes:

1) identification of target UE(s) via "supis" "gpsis" (if feature "UserDataCongestionExt" is supported) or "anyUe" attribute within "tgt-ue" attribute;

and may provide:

1) event specific filter information in the "event-filter" attribute which may provide:

a) identification of network slice(s) by "snssais" attribute;

b) identification of network area to which the request applies via identification of network area by "networkArea" attribute (mandatory if "anyUe" attribute is set to true);

c) if the feature "UserDataCongestionExt" is also supported, request a list of top applications with maximum number that contribute the most to the traffic in uplink and/or downlink directions bythe "maxTopAppUlNbr" attribute and/or the "maxTopAppDlNbr" attribute; and/or

d) a list of analytics subsets carried by "listOfAnaSubsets" attribute with value(s) only applicable to "USER_DATA_CONGESTION" event, if the "EneNA" feature is supported;

– if the feature "SMCCE" is supported and the event is "SM_CONGESTION", it shall provide:

1) event specific filter information in the "event-filter" attribute which shall provide:

a) identification of DNN in the "dnns" attribute; and/or

b) identification of network slice(s) in the "snssais" attribute; and

2) identification of target UE(s) via "supis" attribute in the "tgt-ue" attribute where the target UE(s) are one have the PDU Session for the DNN and/or S-NSSAI indicated by the event specific filter information;

and may include:

1) a list of analytics subsets carried by "listOfAnaSubsets" attribute with value(s) only applicable to "SM_CONGESTION" event, if the "EneNA" feature is supported;

NOTE 5: The predictions are not applicable for Session Management Congestion Control Experience analytics.

– if the feature "Dispersion" is supported and the event is "DISPERSION", shall provide:

1) identification of target UE(s) applies by "supis", "intGroupIds" or "anyUe" attribute within "tgt-ue" attribute, "anyUe" attribute is only supported in combination with "snssais" attribute, "networkArea" attribute and/or "disperClass" attribute;

and may include:

1) identification of network area applies via identification of network area by "networkArea" attribute;

2) identification of network slice(s) by "snssais" attribute;

3) application identifier(s) in "appIds" attribute;

4) dispersion analytics requirements in "disperReqs" attribute, which for the requested dispersion type may include dispersion class, ranking, ordering and/or accuracy requirments; and/or

5) an optional list of analytics subsets by "listOfAnaSubsets" attribute with value(s) only applicable to DISPERSION event;

– if the feature "RedundantTransmissionExp" is supported and the event is "RED_TRANS_EXP", shall provide:

1) identification of target UE(s) applies by "supis", "intGroupIds" or "anyUe" attribute within "tgt-ue" attribute;

and may include:

1) identification of network area applies via identification of network area by "networkArea" attribute, if the "supis" attribute or "intGroupIds" attribute is included in the "tgt-ue" attribute;

2) identification of network slice(s) by "snssais" attribute;

3) identification of DNN in the "dnns" attribute;

4) other redundant transmission experience analysis requirements in "redTransReqs" attribute, which may include preferred order of results for the list of Redundant Transmission Experience; and/or

5) an optional list of analytics subsets by "listOfAnaSubsets" attribute with value(s) only applicable to RED_TRANS_EXP event, if the "EneNA" feature is supported;

– if the feature "WlanPerformance" is supported and the event is "WLAN_PERFORMANCE", shall provide:

1) identification of target UE(s) by "supis", "intGroupIds" or "anyUe" attribute in the "tgt-ue" attribute. If "anyUe" attribute is included in the "tgt-ue" attribute, then any of "networkArea" attribute, "ssIds" or "bssIds" attribute shall be present in the "wlanReqs" attribute;

and may include:

1) identification of network area to which the request applies via identification of network area by "networkArea" attribute;

2) other WLAN performance analytics requirements in "wlanReqs" attribute, which may include SSID(s), BSSID(s), preferred order of results for the list of WLAN performance information and/or accuracy per analytics subset; and/or

3) an optional list of analytics subsets by "listOfAnaSubsets" attribute with value(s) only applicable to WLAN_PERFORMANCE event, if the "EneNA" feature is supported;

– if the feature "DnPerformance" is supported and the event is "DN_PERFORMANCE", shall provide:

1) identification of target UE(s) to which the request applies by "supis", "intGroupIds" or "anyUe" attribute in the "tgt-ue" attribute;

and may include:

1) identification of network area to which the request applies via identification of network area by "networkArea" attribute;

2) identification of network slice(s) in the "snssais" attribute;

3) identification of network slice and the optionally associated network slice instance(s) if available, via the "nsiIdInfos" attribute or any slices indication in the "anySlice" attribute;

4) application identifier(s) in "appIds" attribute;

5) an identification of DNN in the "dnns" attribute;

6) identification of a user plane access to one or more DN(s) where applications are deployed by "dnais" attribute;

7) the identification of the UPF as the "upfInfo" attribute;

8) IP address(s)/FQDN(s) of the Application Server(s) as the "appServerAddrs" attribute;

9) DN performance analytics requirements in "dnPerfReqs" attribute, which may include the preferred order of results for the list of DN performance information and/or the reporting threshold of each analytics subset; and/or

10) an optional list of analytics subsets by "listOfAnaSubsets" attribute with value(s) only applicable to "DN_PERFORMANCE" event, if the "EneNA" feature is supported.

Upon the reception of the HTTP GET request, the NWDAF shall:

– analyse the requested analytic data according to the requested event.

If the HTTP request message from the NF service consumer is accepted, the NWDAF shall respond with "200 OK" status code with the message body containing the analytics with parameters as relevant for the requesting NF service consumer. The AnalyticsData data structure in the response body shall include:

– analytics with the corresponding information as described in clause 4.2.2.4.2.

If the requested NWDAF Analytics data does not exist, the NWDAF shall respond with "204 No Content" status code.

If the "timeAnaNeeded" attribute within EventReportingRequirement is provided during the request, if the time is reached but the requested analytics information is not ready, the consumer does not need to wait for the analytics information any longer, the NWDAF may send a "500 Internal Server Error" status code to the NF service consumer. In addition, if the EneNA feature is supported, the NWDAF may provide, within the ProblemDetailsAnalyticsInfoRequestdata in the response, the corresponding failure reason via a "problemDetails" attribute with the "cause" attribute set to "UNSATISFIED_REQUESTED_ANALYTICS_TIME" and a minimum time interval recommended by the NWDAF via a "rvWaitTime" attribute which is used by the NF service consumer to determine the time when analytics information is needed in similar future analytics requests.

If the analytics target period provided in the body of the HTTP GET request includes the start time in the past and the end time in the future, the NWDAF shall reject the request with an HTTP "400 Bad Request" response including the "cause" attribute set to "BOTH_STAT_PRED_NOT_ALLOWED".

If the statistics in the past are requested but the necessary data to perform the service is unavailable, the NWDAF shall reject the request with an HTTP "500 Internal Server Error" response including the "cause" attribute set to "UNAVAILABLE_DATA".

If the user consent has not been checked by the NF service consumer and is required for the requested analytics collection depending on local policy and regulations, then the NWDAF shall check user consent for the targeted UE(s) by retrieving the user consent subscription data via the Nudm_SDM service API of the UDM as described in clause 5.2.2 of 3GPP TS 29.503 [23]. If the NWDAF receive the response from the UDM that it is not granted for the impacted user(s), then the NWDAF shall send an HTTP "403 Forbidden" error response including the "cause" attribute set to "USER_CONSENT_NOT_GRANTED".

NOTE 6: When the target of reporting is a SUPI or a GPSI then the subscription can be rejected, e.g. because user consent is not granted, and the error is sent to the consumer. When the target of reporting is an Internal Group Id, or a list of SUPIs/GPSI(s) or any UE, and the user consent is not granted for a subset of the impacted users, then no error is sent, but a subset of the SUPIs/GPSIs is skipped if user consent is not granted.

If an error occurs when processing the HTTP GET request, the NWDAF shall send an HTTP error response as specified in clause 5.2.7.

4.3.2.3 Nnwdaf_AnalyticsInfo_ContextTransfer service operation

4.3.2.3.1 General

The Nnwdaf_AnalyticsInfo_ContextTransfer service operation is used by an NF service consumer to request and get context information related to analytics subscriptions from the NWDAF.

4.3.2.3.2 Request and get from NWDAF context of a subscription

Figure 4.3.2.3.2-1 shows a scenario where the NF service consumer (e.g. NWDAF) sends a request to the NWDAF to request and get from NWDAF context information related to analytics subscriptions (see also 3GPP TS 23.288 [17]).

Figure 4.3.2.3.2-1: Requesting NWDAF context information related to analytics subscriptions

The NF service consumer (e.g. NWDAF) shall invoke the Nnwdaf_AnalyticsInfo_ContextTransfer service operation when requesting context information related to analytics subscriptions. The NF service consumer shall send an HTTP GET request on the resource URI "{apiRoot}/nnwdaf-analyticsinfo/<apiVersion>/context" representing the "NWDAF Context" (as shown in figure 4.3.2.3.2-1, step 1), to request context information related to analytics subscriptions according to the query parameter values of the attributes "context-ids" and "req-context".

Upon the reception of the HTTP GET request, the NWDAF shall retrieve the context information for the requested context identifiers.

If the HTTP request message from the NF service consumer is accepted, the NWDAF shall respond with "200 OK" status code with the message body containing the retrieved context information. The ContextData data structure in the response body shall include for each of the context elements contained in the "contextElems" attribute:

– the context identifier that this context element refers to in the "contextId" attribute, which indicates among others the analytics subscription that this context element is associated with.

– the pending output analytics for the indicated analytics subscription in the "pendAnalytics" attribute if such analytics are available and the NF service consumer has indicated the "PENDING_ANALYTICS" context type in the "req-context" attribute of the request.

– the historical output analytics for the indicated analytics subscription in the "histAnalytics" attribute if such analytics are available and the NF service consumer has indicated the "HISTORICAL_ANALYTICS" context type in the "req-context" attribute of the request.

– a timestamp of the last provided output analytics in the "lastOutputTime" if the NF service consumer has indicated the "PENDING_ANALYTICS" and/or "HISTORICAL_ANALYTICS" context type in the "req-context" attribute of the request and output analytics had been provided to the analytics consumer.

– information about aggregation related analytics subscriptions that the NWDAF has with other NWDAFs in the "aggrSubs" attribute if such subscriptions exist and the NF service consumer has indicated the "AGGR_SUBS" context type in the "req-context" attribute of the request.

– historical data related to the indicated analytics subscription in the "histData" attribute if such data exists and the NF service consumer has indicated the "DATA" context type in the "req-context" attribute of the request.

– identifier of ADRF instance in the "adrfId" attribute if the NWDAF stores data in the ADRF.

– the types of data stored in the ADRF in the "adrfDataTypes" attribute if the "adrfId" attribute is provided.

– identifiers of NWDAF instances used when aggregating multiple analytics subscriptions in the "aggrNwdafIds" if such information is available and the NF service consumer has indicated the "AGGR_INFO" context type in the "req-context" attribute of the request.

– information about used ML models in the "modelInfos" attribute if such information is available and the NF service consumer has indicated the "ML_MODELS" context type in the "req-context" attribute of the request.

If the requested context information does not exist, the NWDAF shall respond with "204 No Content" status code.