Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.288  Word version:  17.5.0

Top   Top   Up   Prev   Next
1…   4…   5…   5A…   6…   6.1.4…   6.1.4.4…   6.1A…   6.1B…   6.1C   6.2…   6.2.3…   6.2.6…   6.2.6.2   6.2.6.3…   6.2.6.3.3   6.2.6.3.4   6.2.6.3.5   6.2.6.3.6   6.2.7…   6.2A…   6.2B…   6.3…   6.4…   6.5…   6.6…   6.7…   6.7.3…   6.7.4…   6.7.5…   6.8…   6.9…   6.10…   6.11…   6.12…   6.13…   6.14…   7…   8…   9…   10…

 

6.4  Observed Service Experience related network data analyticsp. 104

6.4.1  Generalp. 104

This clause specifies how NWDAF can provide Observed Service Experience (i.e. average of observed Service MoS and/or variance of observed Service MoS indicating service MOS distribution for services such as audio-visual streaming as well as services that are not audio-visual streaming such as V2X and Web Browsing services) analytics, in the form of statistics or predictions, to a service consumer.
The Observed Service Experience analytics may provide one or more of the following outputs:
  • Service Experience for a Network Slice: Service Experience for a UE or a group of UEs or any UE in a Network Slice;
  • Service Experience for an Application: Service Experience for a UE or a group of UEs or any UE in an Application or a set of Applications;
  • Service Experience for an Edge Application over a UP path: Service experience for a UE or a group UEs or any UE in an Application or a set of Applications over a specific UP path (UPF, DNAI and EC server);
  • Service Experience for an Application over a RAT Type or Frequency or both: Service experience for a UE or a group of UEs in an Application or a set of Applications over a RAT Type or over a Frequency or both as defined in Table 6.4.1-1.
Therefore, Observed Service experience may be provided as defined in clause 6.4.3. For example, individually per UE or group of UEs, or globally, averaged per Application or averaged across a set of Applications on a Network Slice.
The service consumer may be an NF (e.g. PCF, NSSF, AMF), AF, or the OAM.
The consumer of these analytics shall indicate in the request or subscription:
  • Analytics ID = "Service Experience";
  • Target of Analytics Reporting: one or more SUPI(s) or Internal Group Identifier(s), or "any UE";
  • Analytics Filter Information as defined in Table 6.4.1-1;
  • optionally, maximum number of objects and maximum number of SUPIs;
  • optionally, preferred level of accuracy of the analytics;
  • optionally, a list of analytics subsets that are requested (see clause 6.4.3)
  • optionally, preferred level of accuracy per analytics subset;
  • optionally, preferred order of results for the list of Application Service Experiences and/or Slice instance service experiences: "ascending" or "descending"; and
  • optionally, preferred granularity of location information: TA level or cell level.
Information Description Mandatory
Application Network Slice Edge Applications over a UP path Application over RAT Type and frequency
Application ID (0...max)The identification of the application(s) for which the analytics information is subscribed or requested.YNYY
S-NSSAIWhen requesting Service Experience for a Network Slice: identifies the Network Slice for which analytics information is subscribed or requested.
When requesting Service Experience for an Application: identifies the S-NSSAI used to access the application together with the DNN listed below.
NYNN
NSI ID(s)Identifies the Network Slice instance(s) for which analytics information is subscribed or requested.NNNN
Area of InterestIdentifies the Area (i.e. set of TAIs), as defined in TS 23.501 for which the analytics information is subscribed or requested.NNNN
DNNWhen requesting Service Experience for an Application, this is the DNN to access the application.NNNN
DNAI
(NOTE 1)
Identifier of a user plane access to one or more DN(s) where applications are deployed as defined in TS 23.501.NNYN
RAT Type
(NOTE 2)
Identifies the RAT type.NNNY
Frequency
(NOTE 2)
Identifies the Frequency value(s) (e.g. high, low).NNNY
Application Server Address(es) (NOTE 1)List of IP address(s)/FQDN(s) of the Application Server(s) that a UE, group of UEs, or 'any UE' has a communication session for which Service Experience Analytic information is requested.NNYN
UPF anchor ID (NOTE 1)Identifies the UPF where a UE has an associated PDU sessionNNNN
NOTE 1:
These parameters can be provided when a consumer requires analytics for an edge application over a UP path.
NOTE 2:
A service consumer can provide either a RAT Type or a Frequency or a specific combination of RAT Type and Frequency. A service consumer can also provide multiple instances of RAT Type or multiple instances of Frequency or multiple combinations of RAT type and Frequency. A service consumer can also provide "any" RAT type indication "any" Frequency value indication or "any" indication for all the RAT type and Frequency value the NWDAF has received for the application.
  • An Analytics target period that indicates the time window for which the statistics or predictions are requested;
  • In a subscription, the Notification Correlation Id and the Notification Target Address;
  • Optionally, Reporting Thresholds, which apply only for subscriptions and indicate conditions on the Service Experience to be reached in order to be notified by the NWDAF (see Table 6.4.3-1 and Table 6.4.3-2).
The NWDAF shall notify the result of the analytics to the consumer as specified in clause 6.4.3.
NWDAF collects the network data from AF (directly or via NEF) and from other 5GC NF(s) in order to calculate and provide statistics and predictions on the observed service experience to a consumer NF or to OAM.
Based on the Analytics Filter information in Table 6.4.1-1 and the Target of Analytics Reporting provided by the service consumer in the analytics subscription or request, NWDAF determines whether service experience analytics should be delivered for:
  1. Application(s);
  2. Network Slice;
  3. both Application(s) and Network Slice;
  4. Edge Applications over a UP path;
  5. Application(s) over RAT Type(s) and/or Frequency value(s).
If NWDAF is unable to differentiate based on the analytics subscription or request, it provides service experience analytics for both Application(s) and Network Slice.
If service experience for both Application(s) and Network Slice is desired but the Target of Analytics Reporting or Analytics Filter information values (e.g. Area of Interest) need to be different, separate subscriptions/requests may be provided by the service consumer.
Up

6.4.2  Input Datap. 106

The service data and performance data collected from the AF (including the service data collected from the UE through the AF), the network data from other 5GC NFs and the network data from OAM for observed service experience are defined in Table 6.4.2-1, Table 6.4.2-1a, Table 6.4.2-2, Table 6.4.2-3 and Table 6.4.2-4 respectively.
Information Source Description
Application IDAFTo identify the service and support analytics per type of service (the desired level of service)
IP filter informationAFIdentify a service flow of the UE for the application
Locations of ApplicationAF/NEFLocations of application represented by a list of DNAI(s). The NEF may map the AF-Service-Identifier information to a list of DNAI(s) when the DNAI(s) being used by the application are statically defined.
Service ExperienceAFRefers to the QoE per service flow as established in the SLA and during on boarding. It can be either e.g. MOS or video MOS as specified in ITU-T P.1203.3 [11] or a customized MOS for any kind of service including those not related to video or voice.
UE IDAFThe list of UE ID(s) that are associated with the Service Experience value(s). When the AF is untrusted, GPSI(s) will be provided. When the AF is trusted SUPI(s) will be provided.
QoE metricsUE (via AF)QoE metrics observed at the UE(s). QoE metrics and measurement as described in TS 26.114, TS 26.247, TS 26.118, TS 26.346, TS 26.512 or ASP specific QoE metrics, as agreed in the SLA with the MNO, may be used.
TimestampAFA time stamp associated to the Service Experience provided by the AF, mandatory if the Service Experience is provided by the ASP.
Application Server InstanceAFThe IP address or FQDN of the Application Server that the UE had a communication session when the measurement was made.
NWDAF subscribes to the service data from AF in the Table 6.4.2-1 either directly for trusted AFs by invoking Naf_EventExposure_Subscribe service (Event ID = Service Experience information, Event Filter information = Area of Interest, Application ID) as defined in TS 23.502, or indirectly for untrusted AFs via NEF by invoking Nnef_EventExposure_Subscribe service (Event ID = Service Experience information, Event Filter information = Area of Interest, Application ID) where NEF translates the Area of Interest into geographic zone identifier(s). For the information whose source is UE (via AF), the AF collects data from the UE as defined in clause 6.2.8.
Information Source Description
UE identifierAFIP address of the UE at the time the measurements was made.
UE locationAFThe location of the UE when the performance measurement was made.
Application IDAFTo identify the service and support analytics per type of service (the desired level of service).
IP filter informationAFIdentify a service flow of the UE for the application.
Locations of ApplicationAF/NEFLocations of application represented by a list of DNAI(s). The NEF may map the AF-Service-Identifier information to a list of DNAI(s) when the DNAI(s) being used by the application are statically defined.
Application Server Instance addressAF/NEFThe IP address/FQDN of the Application Server that the UE had a communication session when the measurement was made.
Performance DataAFThe performance associated with the communication session of the UE with an Application Server that includes: Average Packet Delay, Average Loss Rate and Throughput.
TimestampAFA time stamp associated to the Performance Data provided by the AF.
NWDAF subscribes to the performance data from AF in the Table 6.4.2-1a either directly for trusted AFs by invoking Naf_EventExposure_Subscribe service (Event ID = Performance Data, Event Filter information = Area of Interest, Application ID) as defined in TS 23.502, or indirectly for untrusted AFs via NEF by invoking Nnef_EventExposure_Subscribe service (Event ID = Performance Data, Event Filter information = Area of Interest, Application ID) where NEF translates the Area of Interest into geographic zone identifier(s).
Information Source Description
Timestamp5GC NFA time stamp associated with the collected information.
LocationAMFThe UE location information, e.g. cell ID or TAI.
UE IDAMF(list of) SUPI(s). If UE IDs are not provided as Target of Analytics Reporting for slice service experience, AMF returns the UE IDs matching the AMF event filters.
DNNSMFDNN for the PDU Session which contains the QoS flow.
S-NSSAISMFS-NSSAI for the PDU Session which contains the QoS flow.
Application IDSMFUsed by NWDAF to identify the application service provider and application for the QoS flow.
UPF info (NOTE 1)SMFUPF ID/address/FQDN information for the UPF serving the UE.
DNAISMFIdentifies the access to DN to which the PDN session connects.
IP filter informationSMFProvided by the SMF, which is used by NWDAF to identify the service data flow for policy control and/or differentiated charging for the QoS flow.
QFISMFQoS Flow Identifier.
QoS flow Bit RateUPFThe observed bit rate for UL direction; and The observed bit rate for DL direction.
QoS flow Packet DelayUPFThe observed Packet delay for UL direction; and The observed Packet delay for the DL direction.
Packet transmissionUPFThe observed number of packet transmission.
Packet retransmissionUPFThe observed number of packet retransmission.
NOTE 1:
The UPF info may indicate information of an anchor UPF of the PDU session containing the QoS flow.
NWDAF subscribes to the network data from 5GC NF(s) in the Table 6.4.2-2 by invoking Nnf_EventExposure_Subscribe service operation with the following Event IDs as input parameters:
  • AMF Source: Namf_EventExposure_Subscribe (Event IDs = Location Changes, Area of Interest).
  • SMF Source: Nsmf_EventExposure_Subscribe (Event ID = QFI allocation).
Information Source Description
TimestampOAMA time stamp associated with the collected information.
Reference Signal Received PowerOAM
(see NOTE 1)
The per UE measurement of the received power level in a network cell, including SS-RSRP, CSI-RSRP as specified in clause 5.5 of TS 38.331 and E-UTRA RSRP as specified in clause 5.5.5 of TS 36.331
Reference Signal Received QualityOAM
(see NOTE 1)
The per UE measurement of the received quality in a network cell, including SS-RSRQ, CSI-RSRQ as specified in clause 5.5 of TS 38.331 and E-UTRA RSRQ as specified in clause 5.5.5 of TS 36.331
Signal-to-noise and interference ratioOAM
(see NOTE 1)
The per UE measurement of the received signal to noise and interference ratio in a network cell, including SS-SINR, CSI-SINR, E-UTRA RS-SINR, as specified in clause 5.1 of TS 38.215
The mapping information between cell ID and frequencyOAMThe mapping information between cell ID and frequency (NOTE 2).
Cell Energy Saving StateOAMList of the cells which are within the area of interest and are in energy saving state, as specified in clauses 3.1 and 6.2 of TS 28.310.
NOTE 1:
Per UE measurement for a specific UE from OAM (via MDT), is as captured in clause 6.2.3.1.
NOTE 2:
The MDT measurement report provides the cell identity and carrier frequency information for UE's serving cell and neighbour cell(s). The NWDAF can get the mapping information between cell ID and frequency using OAM service as described in clause 6.2.3.
Information Source Description
Timestamp5GC NFA time stamp associated with the collected information.
LocationAMFThe UE location information, e.g. cell ID or TAI.
UE ID AMF(list of) SUPI(s).
RAT TypeSMFThe RAT type the UE camps on.
The Event Filters for the service data collection from SMF, AMF and AF are defined in TS 23.502.
The timestamps are provided by each NF to allow correlation of QoS and traffic KPIs. The clock reference is able to know the accuracy of the time and correlate the time series of the data retrieved from each NF.
Up

6.4.3  Output Analyticsp. 108

The NWDAF services as defined in the clause 7.2 and clause 7.3 are used to expose the analytics.
  • Service Experience statistics information is defined in Table 6.4.3-1.
  • Service Experience predictions information is defined in Table 6.4.3-2.
Information Description
Slice instance service experiences (0..max)List of observed service experience information for each Network Slice instance.
> S-NSSAIIdentifies the Network Slice
> NSI ID (NOTE 2)Identifies the Network Slice instance within the Network Slice.
> Network Slice instance service experienceService experience across Applications on a Network Slice instance over the Analytics target period (average, variance).
> SUPI list (0..SUPImax) (NOTE 3)List of SUPI(s) for which the slice instance service experience applies.
> Ratio (NOTE 3)Estimated percentage of UEs with similar service experience (in the group, or among all UEs).
> Spatial validity (NOTE 6)Area where the Network Slice service experience analytics applies.
> Validity periodValidity period for the Network Slice service experience analytics as defined in clause 6.1.3.
Application service experiences (0..max)List of observed service experience information for each Application.
> S-NSSAIIdentifies the Network Slice used to access the Application.
> Application IDIdentification of the Application.
> Service Experience TypeType of Service Experience analytics, e.g. on voice, video, other.
> UE location (NOTE 1, NOTE 5)Indicating the UE location information (e.g. TAI list, gNB ID, etc) when the UE service is delivered.
> UPF Info (NOTE 4)Indicating UPF serving the UE.
> DNAIIndicating which DNAI the UE service uses/camps on.
> DNN (NOTE 4)DNN for the PDU Session which contains the QoS flow.
> Application Server Instance AddressIdentifies the Application Server Instance (IP address of the Application Server) or FQDN of Application Server.
> Service ExperienceService Experience over the Analytics target period (average, variance).
> SUPI list (0..SUPImax) (NOTE 3)List of SUPI(s) with the same application service experience.
> Ratio (NOTE 3)Estimated percentage of UEs with similar service experience (in the group, or among all UEs).
> Spatial validity (NOTE 6)Area where the Application service experience analytics applies.
> Validity periodValidity period for the Application service experience analytics as defined in clause 6.1.3.
> RAT Type
(NOTE 7)
Indicating the list of RAT type(s) for which the application service experience analytics applies.
> Frequency
(NOTE 7)
Indicating the list of carrier frequency value(s) of UE's serving cell(s) where the application service experience analytics applies.
NOTE 1:
This information element is an Analytics subset that can be used in "list of analytics subsets" that are requested.
NOTE 2:
The NSI ID is an optional parameter. If not provided the Slice instance service experience indicates the service experience for the S-NSSAI.
NOTE 3:
The SUPI list and Ratio in the service experience information for an application can be omitted, if the corresponding parameter(s) is/are provided and are assigned with the same value(s) in the service experience information for the slice instance which the application belongs to. Otherwise, the SUPI list and Ratio are mandatory to be provided for an application service experience.
NOTE 4:
If the consumer NF is an AF, the item "DNN" and "UPF info" shall not be included, and the NEF is responsible for translation of SUPI to GPSI, internal group identifiers to external ones, and UE location to geographical area, by querying UDM, prior to contacting the AF.
NOTE 5:
When possible and applicable to the access type, UE location is provided according to the preferred granularity of location information. UE location shall only be included if the Consumer analytics request is for single UE or a list of UEs. Inclusion of UE location requires user consent.
NOTE 6:
The Spatial validity is present in the output parameters if the consumer provided the Area of Interest as defined in Table 6.4.1-1.
NOTE 7:
When "any" value has been provided in the request (e.g. "any" RAT type, "any" frequency, or "any" for all the RAT type and frequency indication), the NWDAF provides an instance of the Application service experience per combination of RAT Type(s) and/or Frequency value(s) having the same Service Experience.
Information Description
Slice instance service experiences (0..max)List of observed service experience information for each Network Slice instance.
> S-NSSAIIdentifies the Network Slice
> NSI ID (NOTE 2)Identifies the Network Slice instance within the Network Slice.
> Network Slice instance service experienceService experience across Applications on a Network Slice instance over the Analytics target period (average, variance).
> SUPI list (0..SUPImax) (NOTE 3)List of SUPI(s) for which the slice instance service experience applies.
> Ratio (NOTE 3)Estimated percentage of UEs with similar service experience (in the group, or among all UEs).
> Spatial validity (NOTE 6)Area where the Network Slice service experience analytics applies.
> Validity periodValidity period for the Network Slice service experience analytics as defined in clause 6.1.3.
> ConfidenceConfidence of this prediction.
Application service experiences (0..max)List of predicted service experience information for each Application.
> S-NSSAIIdentifies the Network Slice used to access the Application.
> Application IDIdentification of the Application.
> Service Experience TypeType of Service Experience analytics, e.g. on voice, video, other.
> UE location (NOTE 1, NOTE 5)Indicating the UE location information (e.g. TAI list, gNB ID, etc) when the UE service is delivered.
> UPF Info (NOTE 4)Indicating UPF serving the UE.
> DNAIIndicating which DNAI the UE service uses/camps on.
> DNN (NOTE 4)DNN for the PDU Session which contains the QoS flow.
> Application Server Instance AddressIdentifies the Application Server Instance (IP address of the Application Server) or FQDN of Application Server.
> Service ExperienceService Experience over the Analytics target period (average, variance).
> SUPI list (0..SUPImax) (NOTE 3)List of SUPI(s) with the same application service experience.
> Ratio (NOTE 3)Estimated percentage of UEs with similar service experience (in the group, or among all UEs).
> Spatial validity (NOTE 6)Area where the Application service experience analytics applies.
> Validity periodValidity period for the Application service experience analytics as defined in clause 6.1.3.
> ConfidenceConfidence of this prediction.
> RAT Type
(NOTE 7)
Indicating the list of RAT type(s) for which the application service experience analytics applies.
> Frequency
(NOTE 7)
Indicating the list of carrier frequency value(s) of UE's serving cell(s) where the application service experience analytics applies.
NOTE 1:
This information element is an Analytics subset that can be used in "list of analytics subsets that are requested".
NOTE 2:
The NSI ID is an optional parameter. If not provided the Slice instance service experience indicates the service experience for the S-NSSAI.
NOTE 3:
The SUPI list and Ratio in the service experience information for an application can be omitted, if the corresponding parameter(s) is/are provided and are assigned with the same value(s) in the service experience information for the slice instance which the application belongs to. Otherwise, the SUPI list and Ratio are mandatory to be provided for an application service experience.
NOTE 4:
If the consumer NF is an AF, the item "DNN" and "UPF info" shall not be included, and the NEF is responsible for translation of SUPI to GPSI, internal group identifiers to external ones, and UE location to geographical area, by querying UDM, prior to contacting the AF.
NOTE 5:
When possible and applicable to the access type, UE location is provided according to the preferred granularity of location information. UE location shall only be included if the Consumer analytics request is for single UE or a list of UEs. Inclusion of UE location requires user consent.
NOTE 6:
The Spatial validity is present in the output parameters if the consumer provided the Area of Interest as defined in Table 6.4.1-1.
NOTE 7:
When "any" value has been provided in the request (e.g. "any" RAT type, "any" frequency, or "any" for all the RAT type and frequency indication), the NWDAF provides an instance of the Application service experience per combination of RAT Type(s) and/or Frequency value(s) having the same Service Experience.
The number of Service Experiences and SUPIs are limited respectively by the maximum number of objects and the Maximum number of SUPIs provided as part of Analytics Reporting Information by the NWDAF Service Consumer.
Up

6.4.4  Procedures to request Service Experience for an Applicationp. 111

Reproduction of 3GPP TS 23.288, Fig. 6.4.4-1: Procedure for NWDAF providing Service Experience for an Application
Up
This procedure allows the consumer to request Analytics ID "Service Experience" for a particular Application. The consumer includes both the Application ID for which the Service Experience is requested and indicates that the Target of Analytics Reporting is "any UE". If the Target for Analytics Reporting is either a SUPI or an Internal-Group-Id the procedure in clause 6.4.6 applies. At the same time, for an Application ID, a set of initial QoS parameter combinations per service experience window (e.g. one is for 3<Service MOS<4 and another is for 4<Service MOS<5) is defined in PCF (e.g. by configuration of operator policies) that may be updated based on the Service Experience reported by NWDAF.
Step 1.
Consumer NF sends an Analytics request/subscribe (Analytics ID = Service Experience, Target of Analytics Reporting = any UE, Analytics Filter Information that may include one or more of the following as defined in Table 6.4.1-1 (Application ID, S-NSSAI, DNN, Application Server Address(es), Area of Interest, RAT type(s), Frequency value(s)), Analytics Reporting Information=Analytics target period) to NWDAF by invoking a Nnwdaf_AnalyticsInfo_Request or a Nnwdaf_AnalyticsSubscription_Subscribe.
Step 2a.
NWDAF subscribes the service data from AF in the Table 6.4.2-1 by invoking Nnef_EventExposure_Subscribe or Naf_EventExposure_Subscribe service (Event ID = Service Experience information, Application ID, Event Filter information), Target of Event Reporting = Any UE) as defined in TS 23.502.
Step 2b.
NWDAF subscribes the network data from 5GC NF(s) in the Table 6.4.2-2 by invoking Nnf_EventExposure_Subscribe service operation.
Step 2c.
With these data, the NWDAF estimates the Service experience for the application.
Step 3.
The NWDAF provides the data analytics, i.e. the observed Service Experience (which can be a range of values) to the consumer NF by means of either Nnwdaf_AnalyticsInfo_Request response or Nnwdaf_AnalyticsSubscription_Notify, depending on the service used in step 1, indicating how well the used QoS Parameters satisfy the Service MoS agreed between the MNO and the end user or between the MNO and the external ASP.
If the consumer NF is a PCF and it determines that the application SLA is not satisfied, it may take into account the Observed Service Experience and the operator policies including SLA and required Service Experience (which can be a range of values) to determine new QoS parameters to be applied for the service, as defined in clause 6.1.1.3 and clause 6.2.1.2 of TS 23.503.
If the consumer NF is an AF (e.g. MEC or other Application Server), it may use the Observed Service Experience related network data analytics to determine whether the user experience can be satisfied. If not, the AF may determine to adjust service parameters, e.g. for a video service this may be bit rate, frame rate, codec format, compression parameter, screen size, etc., to better match the network conditions and achieve better user experience.
If the consumer NF is SMF, PCF or AF/Application Server, it may take into account the Observed Service Experience analytics per UP path (i.e. UPF and/or DNAI and/or AS instance address as defined in Table 6.4.3-1) to perform the following procedures:
  • The consumer SMF determines to (re)selects UP paths, including UPF and DNAI, as described in clause 4.3.5 of TS 23.502. In addition, the SMF may (re)configure traffic steering, updating the UPF regarding the target DNAI with new traffic steering rules.
  • The consumer AF/Application Server determines to adjust service parameters, e.g. service parameters of video for adjustment may be bit rate, frame rate, codec format, compression parameter, screen size, etc. In addition, the AF/ Application Server may provide an updated list of DNAI(s) for SMF to perform relocation when appropriate.
  • The consumer PCF may provide an updated list of DNAI(s) for SMF to perform relocation upon AF request.
Up

6.4.5  Procedures to request Service Experience for a Network Slicep. 113

Reproduction of 3GPP TS 23.288, Fig. 6.4.5-1: Procedure for NWDAF providing Service Experience for a UE or a group of UEs in a Network Slice
Up
This procedure is similar to the procedure in clause 6.4.4, with the following differences. The consumer needs to request the Analytics ID "Service Experience" for all UEs or a group of UEs or a UE on a Network Slice, identified by an S-NSSAI. If multiple Network Slice instances of the same Network Slice are deployed, associated NSI ID(s) may be used in addition to S-NSSAI. If 'any UE' is the Target of Analytics Reporting, NWDAF may subscribe to UE mobility event notifications of AMF as described in clause 5.3.4.4 of TS 23.501 using event ID "UE moving in or out of Area of Interest" and Event Filters as described in Table 5.2.2.3.1-1 of TS 23.502 if it is needed to retrieve the list of SUPIs (and GPSIs if available) in the area of interest. The event exposure service request may also include the immediate reporting flag as Event Reporting Information as described in Table 4.15.1-1 of TS 23.502.
In addition, service experience data may need to be collected from multiple Applications. If each Application is hosted in different AFs, NWDAF subscribes the service data in the Table 6.4.2-1 from the different AFs by invoking Nnef_EventExposure_Subscribe or Naf_EventExposure_Subscribe services for each Application (Event ID = Service Experience information, Event Filter information, Application ID) as defined in TS 23.502. Figure 6.4.5-1 shows an example procedure with two AFs. If one AF provides the service experience data of multiple Applications, the set of Application IDs is provided by NWDAF to the AF with the Naf_EventExposure_Subscribe service operation, as defined TS 23.502.
The Observed Service Experience for a Network Slice when consumed by OAM could be used as described in Annex H of TS 28.550.
Up

6.4.6  Procedures to request Service Experience for a UE |R17|p. 113

Figure 6.4.6-1 depicts procedure for NWDAF providing Service Experience for an application for a UE or a group of UEs.
Reproduction of 3GPP TS 23.288, Fig. 6.4.6-1: Procedure for NWDAF providing Service Experience for an application for a UE or a group of UEs
Up
The procedure in clause 6.4.4 applies with the following additions. The consumer needs to request the Analytics ID "Service Experience" for a UE identified by a SUPI or a group of UEs identified by an Internal Group-Id. The consumer includes both the Application ID for which their Service Experience is requested and the Target of Analytics Reporting for a SUPI or an Internal-Group-Id. Analytic Filter Information can be set according to clause 6.4.1. When NEF is the NF service consumer, the NEF translates a GPSI into a SUPI or an External-Group-Id into an Internal-Group-Id then includes it in the Target of Analytics Reporting.
Up

Up   Top   ToC