Tech-invite  3GPPspecsRELsGlossariesSIP
Info21222324252627282931323334353637384‑5x

full Contents for  TS 23.288  Word version:   16.3.0

Top   Up   Prev   Next
1…   4…   6…   6.2…   6.3…   6.4…   6.5…   6.6…   6.7…   6.7.3…   6.7.4…   6.7.5…   6.8…   6.9…   7…

 

6.4  Observed Service Experience related network data analytics
6.4.1  General
This clause specifies how NWDAF can provide Observed Service Experience (i.e. average observed Service MoS) analytics, in the form of statistics or predictions, to a service consumer.
The Observed Service Experience analytics may provide one or both of the following:
  • Service Experience for a Network Slice: Service Experience for UEs (for a UE or a group of or any UE) for a given Application or a set of Applications or any Application (i.e. all Applications) in a Network Slice;
  • Service Experience for an Application: Service Experience (i.e. for a UE or a group of UEs or any UE) in an Application.
Therefore, Observed Service experience may be provided 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), or the OAM.
The consumer of these analytics shall indicate in the request or subscription:
  • Analytics Id set to "Service Experience";
  • The 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 and, optionally, maximum number of objects and maximum number of SUPIs;
Information
Description

Application ID (1..n) (NOTE 1)
The identification of the application(s) for which the analytics information is subscribed or requested.
S-NSSAI (NOTE 2)
Identifies the Network Slice for which analytics information is subscribed or requested.
Area of Interest
Identifies the Area (i.e. set of TAIs), as defined in TS 23.501 where the analytics information is subscribed or requested.
Media/application bandwidth
Identifies the Media/application bandwidth requirement of the application.
DNN
DNN to access the application.
DNAI
Identifier of a user plane access to one or more DN(s) where applications are deployed as defined in TS 23.501

NOTE 1:
If no Application ID is provided, the Analytics Filter information applies to any application (i.e. all applications) in the Network Slice.
NOTE 2:
The S-NSSAI is mandatory if the NWDAF Service Consumer subscribes or requests the Service Experience in a Network Slice. Optionally, when multiple Network Slice instances of the same Network Slice (i.e. S-NSSAI) are deployed, associated NSI ID is used in addition to S-NSSAI.

 
  • 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.
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 provides statistics and predictions on the observed service experience to a consumer NF or to OAM.
Up
6.4.2  Input DataWord-p. 22
The service data collected from 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-2 and Table 6.4.2-3, respectively.
Information
Source
Description

Application ID
AF
To identify the service and support analytics per type of service (the desired level of service)
IP filter information
AF
Identify a service flow of the UE for the application
Locations of Application
AF/NEF
Locations 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 Experience
AF
Refers 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
Timestamp
AF
A time stamp associated to the Service Experience provided by the AF, mandatory if the Service Experience is provided by the ASP.

NWDAF subscribes to the service data from AF in the Table 6.4.2-1 either directly by invoking Naf_EventExposure_Subscribe service (Event ID = Service Data, Event Filter information = Application ID, Area of Interest) as defined in TS 23.502, or via NEF by invoking Nnef_EventExposure_Subscribe service.
Information
Source
Description

Timestamp
5GC NF
A time stamp associated with the collected information.
Location
AMF
The UE location information.
SUPI(s)
AMF
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.
DNN
SMF
DNN for the PDU Session which contains the QoS flow
S-NSSAI
SMF
S-NSSAI for the PDU Session which contains the QoS flow
Application ID
SMF
Used by NWDAF to identify the application service provider and application for the QoS flow
IP filter information
SMF
Provided 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
QFI
SMF
QoS Flow Identifier
QoS flow Bit Rate
UPF
The observed bit rate for UL direction; and
The observed bit rate for DL direction
QoS flow Packet Delay
UPF
The observed Packet delay for UL direction; and
The observed Packet delay for the DL direction
Packet transmission
UPF
The observed number of packet transmission
Packet retransmission
UPF
The observed number of packet retransmission

NOTE 1:
How NWDAF collects QoS flow Bit Rate, QoS flow Packet Delay, Packet transmission and Packet retransmission information from UPF is not defined in this Release of the specification.
NOTE 2:
Care shall be taken with regards to load and major signaling caused when requesting Any UE.
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

Timestamp
OAM
A time stamp associated with the collected information.
Reference Signal Received Power
OAM
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 Quality
OAM
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 ratio
OAM
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

NWDAF subscribes the network data from OAM in the Table 6.4.2-3 by using the services provided by OAM as described in clause 6.2.3.
The Event Filter for the service data collection from AF is defined in Table 6.4.2-4.
Information
Presence
Description

Application ID (1..n)
Conditional (NOTE 1)
An identification of the application or a set of identifications of the applications.
Area of Interest
Conditional (NOTE 2)
Area of Interest which restricts the area in focus

NOTE 1:
If no Application ID is provided, the Event Filter information applies to any Application (i.e. all Applications).
NOTE 2:
Mandatory if Target Of Event Reporting is set to "any UE", optional otherwise.

The Event Filter for the service data collection from SMF and AMF 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 AnalyticsWord-p. 24
The NWDAF services as defined in the clause 7.2 and 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

S-NSSAI
Identifies the Network Slice for which analytics information is provided.
Service experiences (1…n) (NOTE)
List of observed service experience information for each Network Slice instance.
> NSI ID
Identifies the Network Slice instance within the Network Slice.
> Slice instance service experience
Service experience across Applications on a Network Slice instance instance over the Analytics target period (average, variance).
> Application ServiceExperiences (1..max)
List of observed service experience information for each Application.
>> Application ID
Identification of the application.
>> Service Experience Type
Type of Service Experience analytics, e.g. on voice, video, other.
>> Service Experience
Service Experience over the Analytics target period (average, variance).
>> SUPI list (0..SUPImax)
List of SUPI(s) for each application service experience.
>> Ratio
Estimated percentage of UEs with similar service experience (in the group, or among all UEs).
>> Spatial validity
Area where the estimated Service Experience applies.
If Area of Interest information was provided in the request or subscription, spatial validity should be the requested Area of Interest.
>> Validity period
Validity period as defined in clause 6.1.3.
Slice service experience
Service experience across applications on a Network Slice over the Analytics target period (average, variance).

NOTE:
If multiple Network Slice instances are not deployed for the S-NSSAI or NSI IDs are not available, only one Service experience entry is provided (i.e. n=1). In that case, the NSI ID is not provided and the Slice instance service experience indicates the service experience for the S-NSSAI.

 
Information
Description

S-NSSAI
Identifies the Network Slice for which analytics information is provided.
Service experiences (1…n) (NOTE)
List of observed service experience information for each Network Slice instance.
> NSI ID
Identifies the Network Slice instance within the Network Slice.
> Slice instance service experience
Service experience across Applications on a Network Slice instance instance over the Analytics target period (average, variance).
> Application ServiceExperiences (1..max)
List of predicted service experience information for each Application.
>> Application ID
Identification of the application.
>> Service Experience Type
Type of Service Experience analytics, e.g. on voice, video, other.
>> Service Experience
Service Experience over the Analytics target period (average, variance).
>> SUPI list (0..SUPImax)
List of SUPI(s) for each application service experience.
>> Ratio
Estimated percentage of UEs with similar service experience (in the group, or among all UEs).
>> Spatial validity
Area, where the estimated Service Experience applies.
If Area of Interest information was provided in the request or subscription, spatial validity should be the requested Areas of Interest.
>> Validity period
Validity period as defined in clause 6.1.3.
>> Probability assertion
Confidence of this prediction.
Slice service experience
Service experience across applications on a Network Slice over the Analytics target period (average, variance).

NOTE:
If multiple Network Slice instances are not deployed for the S-NSSAI or NSI IDs are not available, only one Service experience entry is provided (i.e. n=1). In that case, the NSI ID is not provided and the Slice instance service experience indicates the service experience for the S-NSSAI.

The number of Service Experiences and SUPIs are limited respectively by the maximum number of objects and the Maximum number of SUPIs provided as input parameter.
Up
6.4.4  Procedures to request Service Experience for an ApplicationWord-p. 25
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". 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 = (Application ID, Analytics target period S-NSSAI, DNN, Area of Interest)) 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, Event Filter information = (Application ID, Area of Interest), Target of Event Reporting = Any UE) as defined TS 23.502.
NOTE 1:
In the case of external AF, NEF translates the requested Area of Interest into a list of geographic zone identifier(s) as described in clause 5.6.7.1 of TS 23.501.
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.
NOTE 2:
QoE measurements from the applications are based on outcome of the ongoing SA5 Rel-16 WID "Management of QoE measurement collection" which addresses how to collect the QoE measurements from the applications in the UE.
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.
NOTE 3:
The call flow only shows a request-response model for the interaction of NWDAF and consumer NF for simplicity instead of both request-response model and subscription-notification model.
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.
NOTE 4:
The non-real time data information from AF includes the service experience data (see Table 6.4.2-1), which indicates the service quality during the service lifetime.
Up
6.4.5  Procedures to request Service Experience for a Network SliceWord-p. 27
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 "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). 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 a separate AF, 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 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

Up   Top   ToC