Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.288  Word version:  19.1.0

Top   Top   Up   Prev   Next
1…   4…   5…   5A…   6…   6.1.3   6.1.4…   6.1.4.4…   6.1.5…   6.1A…   6.1B…   6.1B.2.3…   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.2.8…   6.2.9…   6.2.13…   6.2A…   6.2B…   6.2B.3   6.2B.4…   6.2C…   6.2D…   6.2E…   6.2F…   6.2H…   6.2H.2.2…   6.2H.2.3…   6.2H.2.4…   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…   6.16…   6.17…   6.18…   6.19…   6.20…   6.21…   6.22…   6.23…   7…   7.4…   7.7…   7.9…   8…   9…   10…

 

6.23  QoS and Policy Assistance Analytics |R19|p. 313

6.23.1  Generalp. 313

Clause 6.23 describes how NWDAF can provide predictions of QoS and policy assistance analytics, based on the consumer request. The consumer can either subscribe to analytics notifications (i.e. a Subscribe-Notify model) or request a single notification (i.e. using a Request-Response model).
The service consumer may be a PCF.
The QoS and policy assistance analytic provides predictions of the QoE associated to a set of QoS parameters. When the service consumer needs assistance information to determine QoS or policy, it may send an Analytics request or subscription to NWDAF with one or multiple sets of QoS parameters and optional a requested QoE. NWDAF provides the candidate set(s) of QoS parameters and the corresponding derived predicted QoE that is expected to be achieved by applying the candidate set(s) of QoS parameters (the candidate set(s) of QoS parameters are within the sets of QoS provided by the consumer (i.e. PCF)).
The NWDAF shall include only the parameter(s) and the corresponding value(s) that are provided in the consumer request (i.e. PCF) in the output QoS parameter set(s).
The QoS and policy assistance analytic may be provided for individual UE or group of UEs (e.g. the QoE is for the application ID(s) associated to one or more QoS flow(s) of the UE(s)), or for an application (e.g. the QoE is for the service flow of the application ID).
The consumer of these analytics indicates the following information in the request or subscription:
  • Analytics ID = " QoS and Policy Assistance".
  • Target of Analytics Reporting as defined in clause 6.1.3.
  • A list of one or more QoS parameter set(s) and optionally each associated with a QoS parameter set ID. Based on PCF decision, the QoS parameter set(s) include one or a list of the following individual parameters and non-empty value list(s) for individual parameter(s) in every QoS parameter set(s):
    • 5QI (standardized or pre-configured) or QoS Characteristics attributes (as defined in clause 5.7.3 of TS 23.501): Resource Type, Priority Level, PDB, PER, Averaging Window, Maximum Data Burst Volume;
    • For GBR flows: GFBR and MFBR.
  • Optionally, a requested QoE to indicate NWDAF to only provide the QoS parameter set(s) and their corresponding value(s) for which the predicted QoE is equal or higher than the requested QoE.
  • Analytics Filter Information optionally includes:
    • DNN;
    • Application ID or SDF template;
    • Area of Interest (AOI(s));
    • S-NSSAI and NSI ID;
    • List of analytics subsets that are requested, (see clause 6.23.3), e.g. parameter(s) in QoS parameter set(s).
  • An Analytics target period indicates the time period over which the analytics are requested.
  • In a subscription, the Notification Correlation Id and the Notification Target Address are included.
  • Preferred order of results for the list of candidate QoS parameter sets and the predicted QoE associated to the candidate QoS parameter sets:
    • ordering criterion: "QoE" (i.e. QoE that is associated to candidate QoS parameter set) or "usage duration" or "number of usages" of a QoS flow,
    • order: ascending or descending.
  • Reporting Thresholds, which apply only for subscriptions and indicate conditions on the levels to be reached for the respective analytics subsets (see clause 6.23.3).
  • Maximum number of objects and maximum number of SUPIs.
  • Preferred granularity of location information: TA level or cell level or "longitude and latitude level".
Up

6.23.2  Input Datap. 314

The NWDAF supporting QoS and policy assistance analytics shall be able to collect information from AF, OAM and 5GC NFs.
The following specified input data might be reused by QoS and policy assistance analytics:
  • The input data defined for Observed Service Experience related network data analytics as defined in clause 6.4.2, e.g. the information of the application, Service Experience and QoE metrics.
In addition, more information collected by the NWDAF from relevant 5GC NFs (i.e. UPF, SMF, AMF, PCF) is defined in Table 6.23.2-1.
Information Source Description
QoS binding events (1..max)SMFSMF provides such event when specific QoS parameters are applied to some QoS flows.
> Used QoS parameter set(s)SMFThe QoS parameter set(s) that have been already applied by SMF.
As detailed in clause 6.23.1, the QoS parameter set includes QoS parameters and QoS characteristics attributes (as defined in TS 23.501).
> Used QoS profileSMFThe QoS profile associated to the used QoS parameter set(s).
> Traffic descriptorSMFOne of Application Identifier or IP Packet Filter Set or Ethernet Packet Filter Set.
..> S-NSSAISMFSlice used to transport the QoS flow.
> DNNSMFDNN associated with the QoS flows.
> Application IDSMFIdentifies the application service provider and application for the QoS Flow(s).
> DNAISMFIdentifies the access to the DN to which the PDU Session connects.
> PDU Session TypeSMFType of PDU Session.
> SSC ModeSMFSSC Mode of the PDU Session(s).
UE identifierSMF, AMFThe identifier of UE, e.g. SUPI, UE IP address, etc.
UE LocationAMFThe UE location information, e.g. cell ID or TAI.
Time stampSMF, AMFThe time stamp associated to the collected data.
Up

6.23.3  Output Analyticsp. 315

The NWDAF shall be able to provide prediction on QoS and Policy Assistance to consumer NFs, i.e. PCF, as defined in Table 6.23.3-1.
Information Description
Time slot entry (1..max)List of time slots during the Analytics target period.
> Time slot startTime slot start within the Analytics target period.
> DurationDuration of the time slot.
> QoS and Policy Assistance information (1…max) (NOTE 1)List of QoS and Policy Assistance information.
Max. is the number of the candidate QoS parameter set(s), if applicable.
>> QoS parameter set identifierIdentifies the QoS set for which the entry applies.
>> DNNDNN for the PDU Session which contains the QoS flow.
>> Application ID(s)Identifies the application(s) that associated to the QoE or QoS parameter set.
>> Predicted QoE (NOTE 7)The predicted QoE or the service experience (e.g. QoE, MOS) of the corresponding QoS parameter set, e.g. average, variance, maximum, minimum of QoE.
>> QoS parameter values (NOTE 5)The parameters and corresponding values for the QoS parameter set associated to the predicted QoE,
>>> 5QIThe reference to 5G QoS characteristics and QoS parameters.
>>> ARPThe QoS parameter ARP contains information about the priority level, the pre-emption capability and the pre-emption vulnerability, as defined in TS 23.501.
>>> Resource typeThe resource type of the corresponding QoS flow, e.g. GBR QoS flow, non-GBR QoS flow, delay-critical QoS flow.
>>> Packet Delay BudgetPacket Delay Budget (PDB) indicates the upper bound for the time that a packet may be delayed between the UE and the N6 termination point at the UPF, as defined in TS 23.501.
>>> Packet Error RatePacket Error Rate (PER) defines an upper bound for a rate of non-congestion related packet losses, as defined in TS 23.501.
>>> Flow Bit Rates (NOTE 2)The flow bit rates only applies to GBR QoS Flow.
>>>> GFBRGuaranteed Flow Bit Rate (GFBR) for UL and/or DL.
>>>> MFBRMaximum Flow Bit Rate (MFBR) for UL and/or DL.
>>> Packet Loss Rate (NOTE 2)The Maximum Packet Loss Rate (UL, DL) indicates the maximum rate for lost packets of the QoS Flow that can be tolerated in the uplink and downlink direction.
This is provided to the QoS Flow if it is compliant to the GFBR.
>>> Averaging Window (NOTE 2)The Averaging window is applied when the resource type is GBR QoS.
The Averaging window represents the duration over which the GFBR and MFBR shall be calculated (e.g. in the (R)AN, UPF, UE), as defined in TS 23.501.
>>> Maximum Data Burst Volume (NOTE 3)The Maximum Data Burst Volume (MDBV) applies to GBR QoS Flow with Delay-critical resource type.
The MDBV denotes the largest amount of data that the 5G-AN is required to serve within a period of 5G-AN PDB, as defined in TS 23.501.
>> Applicable duration of QoS and Policy Assistance informationThe applicable duration/ time window of the QoS and Policy Assistance information.
>> Validity periodThe validity period within the time slot for the analytics on service experience associated to QoS in clause 6.1.3.
>> Spatial validityArea where the analytics on service experience associated to QoS applies.
>> Traffic descriptorOne of Application Identifier or IP Packet Filter Set or Ethernet Packet Filter Set.
>> Usage Duration information (NOTE 6)Maximum/Minimum/Average usage duration of QoS Flows associated to Candidate QoS parameter set.
>> Number of usage (NOTE 6)The number of times that the QoS Flows associated to Candidate QoS parameter set to be used.
> ConfidenceConfidence of this prediction.
NOTE 1:
Analytics subset that can be used in "list of analytics subsets that are requested" and "Reporting Thresholds".
NOTE 2:
The output analytics only applies to GBR QoS Flow.
NOTE 3:
The output analytics only applies to GBR QoS Flow with Delay-critical resource type.
NOTE 4:
Only the parameters that have more than one candidate values provided by the consumer shall be included in the NWDAF output and only the values provided by the consumer are allowed.
NOTE 5:
The usage duration and number of usage of QoS Flow is determined by NWDAF using the SMF Events QoS Flow establishment (i.e. QFI Change) or QoS Flow termination (i.e. QFI deallocation) or Traffic binding of QoS Flow events. For example, the duration equals to the time period between the timestamp of QoS Flow establishment and QoS Flow termination events.
NOTE 6:
The predicted QoE is reported for the entire QoS set if only one parameter value has been provided for each parameter and otherwise separately for each combination of parameter values.
Up

6.23.4  Proceduresp. 318

Figure 6.23.4-1 shows the procedure for the NWDAF to derive and provide the QoS and policy assistance analytics to a consumer 5GC NF (i.e. PCF).
Reproduction of 3GPP TS 23.288, Fig. 6.23.4-1: Procedure for QoS and Policy Assistance Analytics
Up
Step 1.
The Consumer NF, i.e. PCF, requests or subscribes to QoS and policy assistance analytics from NWDAF (via NEF in case the consumer NF is an untrusted AF) and provides the input information as specified in clause 6.23.1 to NWDAF.
Step 2a.
The NWDAF may subscribe to the service data from 5GC NFs, e.g. AMF, SMF, UPF, etc. as defined in clause 6.23.2 by invoking the corresponding NF event exposure service operation, e.g. using Namf_EventExposure_Subscribe service operation for collecting UE location(s); using Nsmf_EventExposure_Subscribe service operation (Event ID, parameters in QoS parameter set, QoS profile ID, SUPI(s) or Application ID), etc.
If the required UE location information is finer granularity than TA/cell level, then NWDAF collects the location data from GMLC instead of AMF by invoking the Ngmlc_Location service as defined in TS 23.273 and TS 29.515.
Step 2b.
The NWDAF collects data from the OAM, following the procedure captured in clause 6.2.3.2.
Step 2c.
The NWDAF may subscribe to the service data from AF as defined in Table 6.23.2-1 by invoking Nnef_EventExposure_Subscribe or Naf_EventExposure_Subscribe service (Event ID = QoS and Policy Assistance, Application ID, Event Filter information, Target of Event Reporting = UE ID(s)) as defined in TS 23.502.
Step 3.
The NWDAF derives the requested analytics on QoS and Policy Assistance based on NWDAF internal logic and based on operator policies, e.g. the NWDAF derives the analytics directly based on the input data as defined in clause 6.23.2 or the NWDAF may derive the analytics by consuming the output analytics of Observed Service Experience analytics and the input parameters in Table 6.23.2-1.
Step 4.
The NWDAF provides the requested QoS and Policy Assistance to the consumer NF, using either Nnwdaf_AnalyticsInfo_Request response or Nnwdaf_AnalyticsSubscription_Notify, depending on the service operation used in step 1.
Step 5-7.
If the consumer NF subscribes to QoS and Policy Assistance in step 1, once the NWDAF generates new analytics on QoS and Policy Assistance, it provides notification using Nnwdaf_AnalyticsSubscription_Notify to the Consumer NF.
Up

Up   Top   ToC