Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.288  Word version:  17.1.0

Top   Top   Up   Prev   Next
1…   4…   5…   5A…   6…   6.1.4…   6.1A…   6.1B…   6.2…   6.2.3…   6.2.6…   6.2.6.3…   6.2.7…   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.15…   7…   8…   9…   10…

 

6.14  DN Performance Analytics |R17|Word‑p. 162

6.14.1  General

This clause specifies how an NWDAF can provide DN Performance Analytics which provides analytics for user plane performance (i.e. average traffic rate, average packet delay) in the form of statistics or predictions to a service consumer.
The DN Performance Analytics may provide one or a combination of the following information:
  • User plane performance analytics for a specific Edge Computing application for a UE, group of UEs, or any UE over a specific serving anchor UPF.
  • User plane performance analytics for a specific Edge Computing application for a UE, group of UEs, or any UE over a specific DNAI.
  • User plane performance analytics for a specific Edge Computing application for a UE, group of UEs, or any UE over a specific Edge Application Server Instance.
The service consumer may be an NF (e.g. SMF, EASDF) or an AF.
The consumer of these analytics shall indicate in the request or subscription:
  • Analytics ID set to "DN Performance Analytics";
  • 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.14.1-1; and
  • optionally, a preferred level of accuracy of the analytics;
  • optionally, Accuracy level per analytics subset (see clause 6.14.3);
  • optionally, preferred order of results for the list of Network Performance information:
    • ordering criterion: one of the analytics subset (see clause 6.14.3);
    • order: ascending or descending;
  • optionally, Reporting Thresholds, which apply only for subscriptions and indicate conditions on the level to be reached for respective analytics subsets (see clause 6.14.3) in order to be notified by the NWDAF;
  • optionally, maximum number of objects and maximum number of SUPIs.
Information Description
Application ID (0...max)The identification of the application(s) for which the analytics information is subscribed or requested.
S-NSSAIIdentifies the Network Slice for which analytics information is subscribed or requested.
NSI ID(s)Identifies the Network Slice instance(s) for which analytics information is subscribed or requested.
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.
UPF anchor identityIdentifies the UPF where a UE has an associated PDU session.
DNNDNN to access the application.
DNAIIdentifier of a user plane access to one or more DN(s) where applications are deployed as defined in TS 23.501.
Application Server Address(es)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 with for which DN Performance Analytic information is requested.
List of analytics subsetsList of analytics subsets that are requested among those specified in clause 6.14.3.
NOTE:
All parameters are optional.
Up

6.14.2  Input DataWord‑p. 163

The data collected from the AF are defined in Table 6.14.2-1.
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.
 
The data collected by the SMF are described in Table 6.4.2-2 with additional data as described in Table 6.14.2-2
Information Source Description
DNAISMFIdentifies the access to DN to which the PDN session connects.
Anchor UPF IDSMFThe anchor UPF of the PDU session containing the QoS flow.
 
The NWDAF subscribes to network data as defined in clause 6.4.2.
Data may be collected from OAM as described in Table 6.4.2-3 by using the services provided by OAM as described in clause 6.2.3.
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.14.3  Output AnalyticsWord‑p. 164

The DN performance analytics is shown in Table 6.14.3-1 and Table 6.14.3-2.
Information Description
Application IDIdentifies the application for which analytics information is provided.
S-NSSAIIdentifies the Network Slice for which analytics information is provided. See note 1.
DNN Identifies the data network name (e.g. "internet") for which analytics information is provided. See NOTE 1.
DN performance (0-x)List of DN performances for the application.
> Application Server Instance AddressIdentifies the Application Server Instance (IP address/FQDN of the Application Server).
> Serving anchor UPFThe involved anchor UPF. See NOTE 2.
> DNAIIdentifier of a user plane access to one or more DN(s) where applications are deployed as defined in TS 23.501.
> PerformancePerformance indicators.
>> Average Traffic rateAverage traffic rate observed for UEs communicating with the application. See NOTE 3.
>> Maximum Traffic rateMaximum traffic rate observed for UEs communicating with the application. See NOTE 3.
>>Average Packet DelayAverage packet delay observed for UEs communicating with the application. See NOTE 3.
>>Maximum Packet DelayMaximum packet delay for observed for UEs communicating with the application. See NOTE 3.
>> Average Packet Loss RateAverage packet loss observed for UEs communicating with the application. See NOTE 3.
> Spatial Validity ConditionArea where the DN performance analytics applies.
> Temporal Validity ConditionValidity period for the DN performance analytics.
NOTE 1:
The item "DNN" and "S-NSSAI" shall not be included if the consumer NF is an untrusted AF.
NOTE 2:
The item "Serving anchor UPF" shall not be included if the consumer is an AF.
NOTE 3:
Analytics subset that can be used in "list of analytics subsets that are requested", "Accuracy level per analytics subset" and "Reporting Thresholds".
 
Information Description
Application IDIdentifies the application for which analytics information is provided.
S-NSSAIIdentifies the Network Slice for which analytics information is provided. See NOTE 1.
DNNIdentifies the data network name (e.g. internet) for which analytics information is provided. See NOTE 1.
DN performance (0-x)List of DN performance for the application.
> Application Server Instance AddressIdentifies the Application Server Instance (IP address/FQDN of the Application Server).
>Serving anchor UPFThe involved anchor UPF. See NOTE 2.
> DNAIIdentifier of a user plane access to one or more DN(s) where applications are deployed as defined in TS 23.501.
>PerformancePerformance indicators
>> Average Traffic rateAverage traffic rate predicted for UEs communicating with the application . See NOTE 3.
>> Maximum Traffic rateMaximum traffic rate predicted for UEs communicating with the application. See NOTE 3.
>>Average Packet DelayAverage packet delay predicted for UEs communicating with the application. See NOTE 3.
>>Maximum Packet DelayMaximum packet delay for predicted for UEs communicating with the application. See NOTE 3.
>> Average Packet Loss RateAverage packet loss predicted for UEs communicating with the application. See NOTE 3.
>Spatial Validity ConditionArea where the DN performance analytics applies.
>Temporal Validity ConditionValidity period for the DN performance analytics.
>ConfidenceConfidence of this prediction.
NOTE 1:
The item "DNN" and "S-NSSAI" shall not be included if the consumer is an untrusted AF.
NOTE 2:
The item "Serving anchor UPF" shall not be included if the consumer is an AF.
NOTE 3:
Analytics subset that can be used in "list of analytics subsets that are requested", "Accuracy level per analytics subset" and "Reporting Thresholds".
Up

6.14.4  Procedures to request DN Performance Analytics for an ApplicationWord‑p. 165

Reproduction of 3GPP TS 23.288, Figure 6.14.4-1: Procedure for NWDAF providing DN Performance analytics for an Application
Up
The procedure illustrated in Figure 6.14.4-1 allows an analytics consumer to request Analytics ID "DN Performance" for a particular Application. The analytics consumer includes the Application ID for which DN Performance is requested. The consumer indicates the Target of Analytics Reporting (e.g. "any UE") and may include as Analytic Filter information the UPF anchor ID, DNAI, or Application Server instance that DN performance analytics are requested.
Step 1.
Analytics consumer sends an Analytics request/subscribe (Analytics ID = DN Performance Target of Analytics Reporting, Analytics Filter information = (Application ID, Analytics target period S-NSSAI, DNN, Area of Interest, UPF anchor ID, DNAI, Application Server Address(es))) to NWDAF by invoking a Nnwdaf_AnalyticsInfo_Request or a Nnwdaf_AnalyticsSubscription_Subscribe service.
Step 2a.
NWDAF subscribes to the performance data from AF defined in Table 6.14.2-1 by invoking Nnef_EventExposure_Subscribe or Naf_EventExposure_Subscribe service (Event ID = Performance Data, Application ID, Event Filter information), Target of Event Reporting = Any UE) as defined in TS 23.502.
Step 2b.
NWDAF subscribes to the network data from 5GC NF(s) defined in Table 6.14.2-2 by invoking Nnf_EventExposure_Subscribe service.
Step 2c.
With the collected data, the NWDAF estimates the DN Performance for the application.
Step 3.
NWDAF provides the data analytics, to the analytics consumer by means of either Nnwdaf_AnalyticsInfo_Request response or Nnwdaf_AnalyticsSubscription_Notify, depending on the service used in step 1.
If the analytics consumer is an SMF, the SMF may use the analytics to determine the UPF and DNAI that offers the best user plane performance.
If the analytics consumer is an AF, the AF may use the analytics to determine the DNAI that has the best user plane performance if Application Server relocation is required.
If the analytics consumer is an EASDF, the EASDF uses DN performance analytics to determine a Local DNS server in the Edge network to route a UE DNS request.
Up

Up   Top   ToC