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.8  User Data Congestion AnalyticsWord-p. 48
6.8.1  General
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 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).
The consumer of these analytics may indicate in the request or subscription:
  • Analytics ID set to "User Data Congestion".
  • Target of Analytics Reporting containing either a SUPI, or "any UE".
  • Analytics Filter Information containing:
    • Optional maximum number of objects;
    • Area of Interest (list of TA or Cells) which restricts the area in focus (mandatory if Target Of Event Reporting is set to "any UE", optional otherwise);
    • Optional S-NSSAI, in order to obtain congestion analytics only on a given slice.
  • 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.
  • 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.6.3.
Up
6.8.2  Input dataWord-p. 49
The detailed information collected by the NWDAF is defined in Table 6.8.2-1.
NOTE:
Performance Measurements defined in TS 28.552 represent resource utilisation but do not, by themselves, indicate the event of congestion or congestion levels. The NWDAF collects measurements from the OAM and how the NWDAF derives Network Status Indication (NSI) is not specified.
Information
Source
Description

UE Location
AMF
UE location information that NWDAF can use to derive the Area of Interest.
Measurements
OAM
Performance Measurements that will be used by the NWDAF to determine congestion levels.
Performance Measurements are related to information transfer over the user plane and/or the control plane (e.g. UE Throughput, DRB Setup Management, RRC Connection Number, PDU Session Management, and Radio Resource Utilization as defined in TS 28.552). The NWDAF may obtain measurements by invoking management services that are defined in TS 28.532 and TS 28.550.

Additionally, NWDAF may use statistics or predictions on service experience as specified in clause 6.4.3 as an input, e.g. for service experience in a given area or service experience for some specific applications such as high bandwidth applications.
Up
6.8.3  Output analytics
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.
Information
Description

Area of Interest
A list of TAIs or Cell IDs
List of user data congestion Analytics (1..max)
>Type
User Plane or Control Plane
>Applicable Time Window
The time period that the analytics applies to
>Network Status Indication
Congestion Level

 
Information
Description

Area of Interest
A list of TAIs or Cell IDs
List of user data congestion Analytics (1..max)
>Type
User Plane or Control Plane
>Applicable Time Window
The time period that the analytics applies to
>Network Status Indication
Congestion Level
> Confidence
Confidence of this prediction

The number of user data congestion analytics entries is limited by the maximum number of objects provided as input parameter.
Up
6.8.4  ProceduresWord-p. 50
6.8.4.1  Procedure for one-time or continuous reporting of analytics for user data congestion in a geographic area
The procedure as depicted in Figure 6.8.4.1-1 is used by an NF to retrieve congestion analytics for a specific geographic area. The procedure can be used to request a one-time or continuous reporting of congestion analytics.
Up
For one-time reporting:
Step 1.
The NF sends Nnwdaf_AnalyticsInfo_Request to NWDAF, indicating request for analytics for congestion in a specific location. The NF can request statistics or predictions or both. The type of analytics is set to user data congestion analytics for transfer over user plane, control plane, or both, Analytics Filter is set to a location (e.g. ECGI, TA).
Step 2-3.
If the request is authorized, and in order to provide the requested analytics, the NWDAF may request the measurement information for the requested location from OAM services following the data collection from OAM procedure as captured in 6.2.3.2. If the NWDAF already has information about the requested location, these steps are omitted. The NWDAF may obtain measurements by invoking management services that are defined in TS 28.532 and TS 28.550.
Step 4.
The NWDAF derives requested analytics.
Step 5.
The NWDAF provides the analytics for congestion to the NF.
For continuous reporting:
Step 6.
The NF sends Nnwdaf_AnalyticsSubscription_Subscribe Request to the NWDAF, indicating request for analytics for congestion in a specific location (e.g. ECGI, TA), possibly with thresholds. The NF can request statistics or predictions or both. The type of analytics is set to user data congestion analytics for transfer over user plane, control plane, or both.
Step 7-8.
The NWDAF subscribes to OAM services following the data collection from OAM procedure as captured in 6.2.3.2 to get measurement information for the requested location, possibly providing measurement thresholds. The NWDAF may obtain measurements by invoking management services that are defined in TS 28.532 and TS 28.550.
Step 9.
The NWDAF derives requested analytics.
Step 10.
The NWDAF provides the analytics for congestion to the NF.
Step 11.
A change of user data congestion status corresponding to crossing a threshold set by the NWDAF is detected by OAM and notified to NWDAF.
Step 12.
The NWDAF derives new analytics.
Step 13.
The NWDAF provides a notification for analytics for the user data congestion to the NF.
Up
6.8.4.2  Procedure for one-time or continuous reporting of analytics for user data congestion for a specific UEWord-p. 51
The procedure as depicted in Figure 6.8.4.2-1 is used by an NF to retrieve user data congestion analytics for a specific UE. The procedure can be used to request a one-time or continuous reporting of user data congestion analytics.
Up
For one-time reporting:
Step 1.
The NF sends Nnwdaf_AnalyticsInfo_Request to NWDAF, requesting for analytics for user data congestion for a specific UE id. The NF can request statistics or predictions or both. The type of analytics is set to user data congestion analytics for transfer over user plane, control plane, or both, the Target of Analytics Reporting is set to UE id.
Step 2-5.
The NWDAF may already know the UE location. If not, the NWDAF checks the UE location by first retrieving the AMF serving the UE (steps 2-3) and then by interrogating the AMF about the UE location.
Step 6-7.
The NWDAF requests measurement information for the UE location from OAM services (as captured in 6.2.3.2). These steps are omitted if the NWDAF already has the information. The NWDAF may obtain measurements by invoking management services that are defined in TS 28.532 and TS 28.550.
Step 8.
The NWDAF derives requested analytics.
Step 9.
The NWDAF provides the analytics for congestion to the NF.
For continuous reporting:
Step 10.
The NF sends Nnwdaf_AnalyticsSubscription_Subscribe Request to the NWDAF. The NF can request for statistics or for predictions or for both. The type of analytics is set to user data congestion analytics for transfer over user plane, control plane, or both.
Step 11.
The NWDAF determines the UE location, either via internal information or by applying the same steps as steps 2 to 5. The NWDAF then determines an area of interest.
Step 12-13.
The NWDAF subscribes to OAM services (as captured in 6.2.3.2) to get the measurement information for the UE location, possibly providing measurement thresholds. The NWDAF may obtain measurements by invoking management services that are defined in TS 28.532 and TS 28.550.
Step 14.
The NWDAF derives requested analytics.
Step 15.
The NWDAF provides the analytics for user data congestion status information to the NF.
Step 16-17.
The NWDAF subscribes to UE mobility event notification in order to be informed when the UE moves out of the area of interest (in order to define a new area of interest and request new information to OAM if the UE moves to a different area).
Step 18.
A change of user data congestion status corresponding to crossing a threshold set by the NWDAF is detected by OAM and notified to NWDAF.
Step 19.
The NWDAF derives new analytics.
Step 20.
The NWDAF provides a notification for analytics for the user data congestion status information to the NF.
Up

Up   Top   ToC