Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.288  Word version:  18.4.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.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…   7…   7.4…   7.7…   7.9…   8…   9…   10…

 

6.6  Network Performance Analyticsp. 179

6.6.1  Generalp. 179

With Network Performance Analytics, NWDAF provides either statistics or predictions on the gNB status information, gNB resource usage, communication performance and mobility performance in an Area of Interest; in addition, NWDAF it may provide statistics or predictions on the number of UEs located in that Area of Interest.
The service consumer may be an NF (e.g. PCF, NEF, AF), or the OAM.
The consumer of these analytics may indicate in the request:
  • Analytics ID = "Network Performance";
  • Target of Analytics Reporting: either a single UE (SUPI ), or a group of UEs (an Internal Group ID that refers to the group for which the analytics on the number of UEs that are located in the Area of Interest at the time indicated in the Analytics target period is requested) or any UE;
  • Analytics Filter Information:
    • Area of Interest (list of TA or Cells) which restricts the area in focus (mandatory if Target of Analytics Reporting is set to "any UE", optional otherwise);
    • Optionally, Traffic type of interest (overall traffic, GBR traffic or Delay-critical GBR traffic);
    • Optionally, a list of analytics subsets that are requested among those specified in clause 6.6.3;
  • Optionally, a preferred level of accuracy of the analytics;
  • Optionally, preferred level of accuracy per analytics subset (see clause 6.6.3);
  • Optionally, preferred order of results for the list of Network Performance information:
    • ordering criterion: "number of UEs", "communication performance" or "mobility performance";
    • order: ascending or descending;
  • Optionally, Reporting Thresholds, which apply only for subscriptions and indicate conditions on the level to be reached for respective analytics information (see clause 6.6.3) in order to be notified by the NWDAF;
  • An Analytics target period indicates the time period over which the statistics or prediction are requested; and
  • Optionally, maximum number of objects.
  • In a subscription, the Notification Correlation Id and the Notification Target Address are included.
  • Optionally, Spatial granularity size (if an Area of Interest is provided) and Temporal granularity size.
The NWDAF notifies the result of the analytics to the consumer as indicated in clause 6.6.3.
Up

6.6.2  Input Datap. 180

The NWDAF collects Load and Performance information in an Area of Interest from the sources listed in Table 6.6.2-1 and number of UEs within Area of Interest from the sources listed in Table 6.6.2-2.
Load information Source Description
Status, load and performance informationOAMStatistics on RAN status (up/down), load (i.e. Radio Resource Utilization) and performance per Cell Id for the traffic type of interest and in the Area of Interest as defined in TS 28.552.
NF Load informationNRFLoad per NF
Number of UEs information Source Description
Number of UEsAMFNumber of UEs in an Area of Interest
The NWDAF shall be able to collect UE mobility information as stated in clause 6.7.2.2.
Up

6.6.3  Output Analyticsp. 180

The NWDAF shall be able to provide both statistics and predictions on Network Performance.
Network performance statistics are defined in Table 6.6.3-1.
Information Description
List of network performance information (1..max)Observed statistics during the Analytics target period.
> Area subsetList of TA(s) or Cell ID(s) within the requested area of interest as defined in clause 6.6.1. If a Spatial granularity size was provided in the request or subscription, the number of elements of the list is smaller than or equal to the Spatial granularity size.
> Analytics target period subsetTime window within the requested Analytics target period as defined in clause 6.6.1. If a Temporal granularity size was provided in the request or subscription, the duration of the Analytics target period subset is greater than or equal to the Temporal granularity size.
> gNB status information (NOTE 1)Average ratio of gNBs that have been up and running during the entire Analytics target period in the area subset.
> gNB resource usage (NOTE 1) (NOTE 2)Usage of assigned resources (average, peak).
> gNB resource usage for GBR traffic (NOTE 1) (NOTE 2)Usage of assigned resources for GBR traffic (average, peak).
> gNB resource usage for Delay-critical GBR traffic (NOTE 1) (NOTE 2)Usage of assigned resources for Delay-critical GBR traffic (average, peak).
> Number of UEs (NOTE 1)Average number of UEs observed in the area subset.
> Communication performance (NOTE 1)Average ratio of successful setup of PDU Sessions.
> Mobility performance (NOTE 1)Average ratio of successful handover.
NOTE 1:
Analytics subset that can be used in "list of analytics subsets that are requested" and "Preferred level of accuracy per analytics subset".
NOTE 2:
The average and peak usage of uplink and downlink traffic are provided as percentage.
Network performance predictions are defined in Table 6.6.3-2.
Information Description
List of network performance information (1..max)Predicted analytics during the Analytics target period
> Area subsetList of TA(s) or Cell ID(s) within the requested area of interest as defined in clause 6.6.1. If a Spatial granularity size was provided in the request or subscription, the number of elements of the list is smaller than or equal to the Spatial granularity size.
> Analytics target period subsetTime window within the requested Analytics target period as defined in clause 6.6.1. If a Temporal granularity size was provided in the request or subscription, the duration of the Analytics target period subset is greater than or equal to the Temporal granularity size.
> gNB status information (NOTE 1)Average ratio of gNBs that will be up and running during the entire Analytics target period in the area subset.
> gNB resource usage (NOTE 1) (NOTE 2)Usage of assigned resources (average, peak).
> gNB resource usage for GBR traffic (NOTE 1) (NOTE 2)Usage of assigned resources for GBR traffic (average, peak).
> gNB resource usage for Delay-critical GBR traffic (NOTE 1) (NOTE 2)Usage of assigned resources for Delay-critical GBR traffic (average, peak).
> Number of UEs (NOTE 1)Average number of UEs predicted in the area subset.
> Communication performance (NOTE 1)Average ratio of successful setup of PDU Sessions.
> Mobility performance (NOTE 1)Average ratio of successful handover.
> ConfidenceConfidence of this prediction.
NOTE 1:
Analytics subset that can be used in "list of analytics subsets that are requested" and "Preferred level of accuracy per analytics subset".
NOTE 2:
The average and peak usage of uplink and downlink traffic are provided as percentage.
The number of network performance information entries is limited by the maximum number of objects provided as part of Analytics Reporting Information.
The NWDAF provides Network Performance Analytics to a consumer at the time requested by the consumer in the Analytics target period:
  • Analytics ID set to "Network Performance".
  • Notification Target Address including the address of the consumer.
  • Notification Correlation ID, for the consumer to correlate notifications from NWDAF if subscription applies.
  • Analytics specific parameters at the time indicated in the Analytics target period.
Up

6.6.4  Proceduresp. 182

Reproduction of 3GPP TS 23.288, Fig. 6.6.4-1: Procedure for subscription to network performance analytics
Up
Step 1.
The NF sends Nnwdaf_AnalyticsSubscription_Subscribe or Nnwdaf_AnalyticsInfo_Request (Analytics ID="Network Performance", Target of Analytics Reporting, Analytics Filter Information = "Area of Interest", Analytics Reporting Information = ("Reporting Thresholds" and Analytics target Period(s))) to the NWDAF.
Step 2a-2d.
The NWDAF discovers from NRF the AMF(s) belonging to the AMF Region(s) that include(s) the Area of Interest and subscribes to NF load and status information from NRF about these AMF(s).
Step 3a-3b.
The NWDAF subscribes to OAM services to get the status and load information and the resource usage on the Area of Interest in clause 6.6.2, following the procedure captured in clause 6.2.3.2.
Step 4a-4b.
The NWDAF collects the number of UEs located in the Area of Interest from AMF using Namf_EventExposure_Subscribe service, including the Target of Event Reporting provided as an input parameter (i.e. any UE or Internal Group Identifier).
Step 5.
The NWDAF derives the requested analytics.
Step 6.
The NWDAF sends Nnwdaf_AnalyticsSubscription_Notify or Nnwdaf_AnalyticsInfo_Request response (Network Performance analytics, Subscription Correlation Id, Confidence).
Step 7-8.
A change of network performance information, i.e. change in the gNB status information, gNB resource usage, communication performance and mobility performance in the area of interest at the observed period, is detected by OAM, or a change in the NF load information is reported by NRF and is notified to NWDAF.
Step 9.
The NWDAF derives new analytics taking into account the most recent data collected.
Step 10.
When relevant according to the Analytics target period and Reporting Thresholds, the NWDAF provides a notification using Nnwdaf_AnalyticsSubscription_Notify (Network Performance analytics, Subscription Correlation Id, Confidence).
Up

Up   Top   ToC