Content for  TS 23.288  Word version:  17.2.0

The NWDAF can provide user data congestion related analytics, by one-time reporting or continuous reporting, in the form of statistics or predictions or both, to another NF. User Data Congestion related analytics can relate to congestion experienced while transferring user data over the control plane or user plane or both. A request for user data congestion analytics relates to a specific area or to a specific user. If the consumer of these analytics provides a UE ID, the NWDAF determines the area where the UE is located. The NWDAF then collects measurements per cell and uses the measurements to determine user data congestion analytics. The request for user data congestion related analytics indicates the location area information where congestion related analytics is desired or indicates a UE Identity that can be used by the NWDAF to determine the location area information where congestion related analytics is desired. When requesting user data congestion, the consumer may request the identifiers of the applications that contribute the most to the traffic in the area. The consumer may indicate how many applications should be reported by providing the maximum number of applications in the request or subscription. When the consumer of user data congestion related analytics subscribes to user data congestion related analytics, it may indicate a threshold and the NWDAF will provide analytics to the consumer when the congestion level crosses the threshold. The consumer can indicate an S-NSSAI in the request when congestion analytics are needed on a per slice level. The service consumer may be an NF (e.g. NEF, AF, PCF). The consumer of these analytics may indicate in the request or subscription the following parameters, its content is described in the clause 6.1.3:

• Analytics ID set to "User Data Congestion".
• Target of Analytics Reporting containing either a UE id (i.e. SUPI or GPSI), or "any UE".
• Analytics Filter Information containing:
  • Area of Interest (i.e. list of TAIs or CellIDs) which restricts the area in focus (mandatory if Target Of Analytics Reporting is set to "any UE", optional otherwise);
  • an optional list of analytics subsets that are requested, (see clause 6.8.3);
  • Optional S-NSSAI, in order to obtain congestion analytics only on a given slice.
• Analytics target period.
• Optional Reporting Threshold, which applies only for subscriptions and indicates conditions on the congestion level (Network Status Indication, see clause 6.8.3) to be reached in order to be notified by the NWDAF.
• Preferred level of accuracy of the analytics;
• Preferred order of results for the list of User Data Congestion statistics or predictions:
  • ordering by Applicable Time Window, chronological or reverse chronological order; or
  • ordering by Network Status Indication, ascending or descending;
• Optional maximum number of objects;
• An Analytics target period indicates the time period over which the statistics or prediction are requested, either in the past or in the future.
• In a subscription, the Notification Correlation Id and the Notification Target Address are included.

The NWDAF notifies the result of the analytics to the consumer as indicated in clause 6.8.3.

The detailed information collected by the NWDAF is defined in Table 6.8.2-1.

 

 

The NWDAF outputs the user data congestion analytics for transfer over the user plane, for transfer over the control plane, or for both. The output may consist of statistics, predictions, or both. The detailed information provided by the NWDAF is defined in Table 6.8.3-1 for statistics and in Table 6.8.3-2 for predictions.

 

The following list shows the applicability of the analytics subsets per consumer:

• Analytics subset "List of top applications in UL (0..NU)" and "List of top applications in DL (0..ND)" are applicable to any consumer (e.g. PCF, AF, NEF), The NWDAF decides if these Analytics subset is provided to an AF.