hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.7.5.4 Procedure
|
Figure 6.7.5.4-1: Procedure for NWDAF assisted misused or hijacked UEs identification
1a. A consumer NF subscribes to/requests NWDAF using Nnwdaf_AnalyticsSubscription_Subscribe/ Nnwdaf_AnalyticsInfo_Request (Analytics ID = Abnormal behaviour, Target of Analytics Reporting as defined in clause 6.1.3, Analytics Filter Information).
A consumer NF may subscribe to/request abnormal behaviour notification/response from NWDAF for a group of UEs, any UE or a specific UE. The Analytics ID indicates the NWDAF to identify misused or hijacked UEs through abnormal behaviour analytic.
1b. AF to NWDAF: Nnwdaf_AnalyticsSubscription_Subscribe or Nnwdaf_AnalyticsInfo_Request (Analytics ID, Target of Analytics Reporting as defined in clause 6.1.3, Analytics Filter Information).
For untrusted AFs, the AF sends the subscription via a NEF, where the AF invokes NEF service Nnef_AnalyticsExposure_Subscribe or Nnef_AnalyticsExposure_Fetch (Analytics ID, Target of Analytics Reporting = External-group-identifier, any UE or External UE ID, Analytics Filter Information).
An AF may also subscribe to/request abnormal behaviour notification/response from NWDAF for a group of UEs, a specific UE or any UE, where the subscription/request message may contain expected UE behaviour parameters identified on the application layer. If an External-Group-Identifier is provided by the AF, the NEF interrogates UDM to map the External-Group-Identifier to the Internal-Group-Identifier and obtain SUPI list corresponding to the Internal-Group-Identifier.
2. [Conditional] NWDAF to AMF: Namf_EventExposure_Subscribe (Event ID(s), Event Filter(s), Internal-Group-Identifier, any UE or SUPI).
The NWDAF sends subscription requests to the related AMF to collect UE behavioural information if it has not subscribed such data.
NOTE 1: The NWDAF determines the related AMF(s) as described in clause 6.2.2.1.
The AMF sends event reports to the NWDAF based on the report requirements contained in the subscription request received from the NWDAF.
If requested by NWDAF via Event Filter(s), the AMF checks whether the UE's behaviour matches its expected UE behavioural information. In this case, the AMF sends event reports to the NWDAF only when it detects that the UE's behaviour deviated from its expected UE behaviour.
Depending on the Exception ID, the NWDAF may in addition perform data collection from OAM as specified in clause 6.2.3.2.
3. [Conditional] NWDAF to SMF: Nsmf_EventExposure_Subscribe (Event ID(s), Event Filter(s), Internal-Group-Identifier, any UE or SUPI).
The NWDAF sends subscription requests to the related SMF(s) if it has not subscribed to such data.
NOTE 2: Besides Analytics Filter Information, other mechanisms such as setting maximum number of SUPIs and/ or using sampling ratio as part of Analytics Reporting Parameters as per Event Reporting Information (clause 4.15.1 of TS 23.502 [3]) can be used by the analytics consumer to limit signalling load, e.g. when the Target of Analytics Reporting is "any UE". The NWDAF can also use sampling ratio, possibly with partition criteria, when subscribing towards AMF and SMF.
NOTE 3: The NWDAF determines the related SMF(s) as described in clause 6.2.2.1.
The SMF sends event reports to the NWDAF based on the report requirements contained in the subscription request received from the NWDAF.
If requested by NWDAF via Event Filter(s), the SMF checks whether the UE's behaviour matches its expected UE behavioural information. In this case, the SMF sends event reports to the NWDAF only when it detects that the UE's behaviour deviated from its expected UE behaviour.
4. The NWDAF performs data analytics for misused or hijacked UEs identification. Based on the analytics and operator's policies the NWDAF determines whether to send a notification to the consumer NF or AF.
5a. [Conditional] NWDAF to consumer NF (AMF or PCF or SMF depending on the subscription): Nnwdaf_AnalyticsSubscription_Notify or Nnwdaf_AnalyticsInfo_Request response (Analytics ID, Exception ID, Internal-Group-Identifier or SUPI, Exception level) (which is used depending on the service used in step 1a).
If the NWDAF determines to send a notification/response to the consumer 5GC NFs, the NWDAF invokes Nnwdaf_AnalyticsSubscription_Notify or Nnwdaf_AnalyticsInfo_Request response service operations. Based on the notification/response, the 5G NFs adopt configured actions to resolve/mitigate/avoid the risks as described in the Table 6.7.5.3-1.
5b. [Conditional] NWDAF to AF: Nnwdaf_AnalyticsSubscription_Notify or Nnwdaf_AnalyticsInfo_Request response (Analytics ID, Exception ID, External UE ID, Exception level) (which is used depending on the service used in step 1b).
If the NWDAF determines to send a notification/response to the consumer AF, the NWDAF needs to include external UE ID of the identified UE into the notification/response message.
NOTE 3: Based on the notification, the AF can adopt corresponding actions, e.g. adjusting recommended TCP Window Size, adjusting recommended Service Start and End.
NOTE 4: The call flow only shows a subscribe-notify model for the interaction of NWDAF and consumer NF for simplicity instead of both request-response model and subscription-notification model.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.8 User Data Congestion Analytics
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
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 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 = "User Data Congestion";
- Target of Analytics Reporting: either a single UE (SUPI), or "any UE";
NOTE: The Target of Analytics Reporting set to "any UE" applies when user data congestion analytics relates to a specific Area of Interest.
- Analytics Filter Information:
- Area of Interest (i.e. list of TAIs or Cell IDs) 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;
- 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;
- Optionally, Temporal granularity size; and
- 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.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.8.2 Input data
|
The detailed information collected by the NWDAF is defined in Table 6.8.2-1.
NOTE 1: Performance Measurements defined in TS 28.552 [8] 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.
Table 6.8.2-1: Data Collected from the NF and OAM related to User Data Congestion Analytics
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 [8]). The NWDAF may obtain measurements by invoking management services that are defined in TS 28.532 [6] and TS 28.550 [7].
Table 6.8.2-2: Data Collected from the UPF or from the AF related to User Data Congestion Analytics
Information
Source
Description
Application ID
UPF or AF
Application identifier as defined in clause 5.8.2 of TS 23.501 [2] (see NOTE 1).
IP Packet Filter Set
UPF or AF
IP Packet Filter set as defined in clause 5.8.2 of TS 23.501 [2] (see NOTE 1).
Measurement period
UPF or AF
Measurement period.
Throughput UL/DL
UPF or AF
Average Throughput UL/DL over the measurement period.
Throughput UL/DL (peak)
UPF or AF
Peak Throughput UL/DL over the measurement period.
Timestamp
UPF or AF
Time when measurements are taken.
Achieved sampling ratio
UPF
Sampling ratio achieved by UPF (see NOTE 2).
NOTE 1: Application Id and IP Packet Filter Set are mutually exclusive.
NOTE 2: UPF may apply data sampling to reduce the load on the UPF. This parameter is provided when no sampling ratio is configured at the UPF or the UPF could not fulfil the configured sampling ratio.
NOTE 3: Multiple outputs are provided by the UPF when multiple Service Data Flows are running at the UPF for the same UE and measurement period.
NOTE 2: Care needs to be taken with regards to load and major signalling caused when requesting "any UE". This can be achieved via utilization of event filters (e.g. Area of Interest), Analytics Reporting Information (e.g. maximum number of objects), or preferred sampling ratio provided by NWDAF to the UPF and/or local UPF configuration of data collection for specific application IDs, Packet Filter Sets and/or PFDs.
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.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
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.
Table 6.8.3-1: User Data Congestion statistics
Information
Description
Area of Interest
A list of TAIs or Cell IDs
List of user data congestion Analytics (1..max)
List of user data congestion Analytics. See NOTE 5.
> Type
User Plane or Control Plane
> Applicable Time Window
The time period that the analytics applies to. If a Temporal granularity size was provided in the request or subscription, the duration of the Applicable Time Window is greater than or equal to the Temporal granularity size.
> Network Status Indication
Congestion Level
> List of top applications in UL (0..NU) (NOTE 1, NOTE 4)
The list of applications that contribute the most to the traffic in the UL direction.
>> Application ID
Application identifier as defined in clause 5.8.2 of TS 23.501 [2] (see NOTE 2).
>> IP Packet Filter Set
IP Packet Filter set as defined in clause 5.8.2 of TS 23.501 [2] (see NOTE 2).
>> Percentage
The application's throughput as a percentage of the total throughput in the Area of Interest.
> List of top applications in DL (0..ND) (NOTE 1, NOTE 4)
The list of applications that contribute the most to the traffic in the DL direction.
>> Application ID
Application identifier as defined in clause 5.8.2 of TS 23.501 [2] (see NOTE 2)
>> IP Packet Filter Set
IP Packet Filter set as defined in clause 5.8.2 of TS 23.501 [2] (see NOTE 2).
>> Percentage
The application's throughput as a percentage of the total throughput in the Area of Interest.
NOTE 1: This information element is an Analytics subset that can be used in "list of analytics subsets that are requested".
NOTE 2: Application Id and IP Packet Filter Set are mutually exclusive.
NOTE 3: The listed applications are not necessarily ranked by any order of traffic contribution.
NOTE 4: This information element relates to congestion experienced while transferring user data over the user plane.
NOTE 5: The number of user data congestion analytics entries is limited by the maximum number of objects provided as part of Analytics Reporting Information.
Table 6.8.3-2: User Data Congestion predictions
Information
Description
Area of Interest
A list of TAIs or Cell IDs.
List of user data congestion Analytics (1..max)
List of user data congestion Analytics. See NOTE 5.
> Type
User Plane or Control Plane.
> Applicable Time Window
The time period that the analytics applies to. If a Temporal granularity size was provided in the request or subscription, the duration of the Applicable Time Window is greater than or equal to the Temporal granularity size.
> Network Status Indication
Congestion Level.
> Confidence
Confidence of this prediction.
> List of top applications in UL (0..NU) (NOTE 1, NOTE 4)
The list of applications predicted to contribute most of the traffic in the UL direction.
>> Application ID
Application identifier as defined in clause 5.8.2 of TS 23.501 [2] (see NOTE 2).
>> IP Packet Filter Set
IP Packet Filter set as defined in clause 5.8.2 of TS 23.501 [2] (see NOTE 2).
>> Percentage
The application's throughput as a percentage of the total throughput in the Area of Interest.
>> Confidence
Confidence of this prediction.
> List of top applications in DL (0..ND) (NOTE 1, NOTE 4)
The list of applications predicted to contribute most of the traffic in the DL direction.
>> Application ID
Application identifier as defined in clause 5.8.2 of TS 23.501 [2] (see NOTE 2).
>> IP Packet Filter Set
IP Packet Filter set as defined in clause 5.8.2 of TS 23.501 [2] (see NOTE 2).
>> Percentage
The application's throughput as a percentage of the total throughput in the Area of Interest.
>> Confidence
Confidence of this prediction.
NOTE 1: This information element is an Analytics subset that can be used in "list of analytics subsets that are requested".
NOTE 2: Application Id and IP Packet Filter Set are mutually exclusive.
NOTE 3: The listed applications are not necessarily ranked by any order.
NOTE 4: This information element relates to congestion experienced while transferring user data over the user plane.
NOTE 5: The number of user data congestion analytics entries is limited by the maximum number of objects provided as part of Analytics Reporting Information.
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.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.8.4 Procedures
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
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.
Figure 6.8.4.1-1: Procedure for one-time or continuous reporting of analytics for congestion in a geographic area
For one-time reporting:
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 Analytics ID is set to "User Data Congestion" for transfer over user plane, control plane, or both, the Target of Analytics Reporting is set to "any UE" and Analytics Filter Information set to include a location (e.g. ECGI, TA) and an indication to provide the list of applications that contribute the most to the traffic.
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 [6] and TS 28.550 [7].
If the request is to provide the list of applications that contribute the most to the traffic, then the NWDAF collects input data from the AF for the applications being served by AF(s) by invoking Naf_EventExposure_Subscribe service or Nnef_EventExposure_Subscribe (if via NEF) or collected from the UPF or collected from both, AF and UPF.
4. The NWDAF derives requested analytics.
5. The NWDAF provides the analytics for congestion to the NF.
For continuous reporting:
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 and including an indication to provide the list of applications that contribute the most to the traffic. 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.
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 for example, data congestion crossing values. The NWDAF may obtain measurements by invoking management services that are defined in TS 28.532 [6] and TS 28.550 [7]. If a request is to provide the list of applications that contribute the most to the traffic, the NWDAF subscribes to the service data from AF by invoking Naf_EventExposure_Subscribe service or Nnef_EventExposure_Subscribe (if via NEF) or from the UPF or from both.
9. The NWDAF derives requested analytics.
10. The NWDAF provides the analytics for congestion to the NF.
11a. A change of user data congestion status corresponding to crossing a threshold set by the NWDAF at steps 7-8 is detected by OAM and notified to NWDAF.
11b. The AF notifies the NWDAF with the input data as defined in table 6.8.2-2.
11c. The UPF provides the NWDAF with the input data as defined in table 6.8.2-2.
NOTE: How the data from UPF is retrieved (subscribed to on UPF and notified then by UPF) is defined in clause 5.8.2.17 of 23.501 [2] and in clause 4.15.4 of TS 23.502 [3].
12. The NWDAF derives new analytics.
13. The NWDAF provides a notification for analytics for the user data congestion to the NF.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.8.4.2 Procedure for one-time or continuous reporting of analytics for user data congestion for a specific UE
|
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.
Figure 6.8.4.2-1: Procedure for one-time or continuous reporting of analytics for congestion for a specific UE
For one-time reporting:
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.
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.
NOTE 1: The NF sends a request for a UE that is registered, so that NWDAF can retrieve the UE location.
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 [6] and TS 28.550 [7].
If the request is to provide the list of applications that contribute the most to the traffic, then the NWDAF collects the input data from the UPF serving the UE location, or from the AF(s) by invoking Naf_EventExposure_Subscribe service or Nnef_EventExposure_Subscribe (if via NEF) or collects input data from both, AF and UPF. The input data is defined in Table 6.8.2-2.
8. The NWDAF derives requested analytics.
9. The NWDAF provides the analytics for congestion to the NF.
For continuous reporting:
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.
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.
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 [6] and TS 28.550 [7].
If the request is to provide the list of applications that contribute the most to the traffic, then the NWDAF collects input data from the UPF serving the UE location or from the AF(s) by invoking Naf_EventExposure_Subscribe service or Nnef_EventExposure_Subscribe (if via NEF) or collects from both, AF and UPF. The input data is defined in Table 6.8.2-2.
14. The NWDAF derives requested analytics.
15. The NWDAF provides the analytics for user data congestion status information to the NF.
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).
18a. A change of user data congestion status corresponding to crossing a threshold set by the NWDAF is detected by OAM and notified to NWDAF.
18b. The AF notifies the NWDAF with the input data as defined in table 6.8.2-2.
18c. The UPF provides the NWDAF with the input data as defined in table 6.8.2-2.
NOTE 2: How the data from UPF is retrieved (subscribed to on UPF and notified then by UPF) is defined in clause 5.8.2.17 of TS 23.501 [2] and in clause 4.15.4 of TS 23.502 [3].
19. The NWDAF derives new analytics.
20. The NWDAF provides a notification for analytics for the user data congestion status information to the NF.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.9 QoS Sustainability Analytics
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.9.1 General
|
The consumer of QoS Sustainability analytics may request the NWDAF analytics information regarding the QoS change statistics for an Analytics target period in the past in a certain area or the likelihood of a QoS change for an Analytics target period in the future in a certain area. The consumer can request either to subscribe to notifications (i.e. a Subscribe-Notify model) or to a single notification (i.e. a Request-Response model).
The service consumer may be a NF (e.g. AF).
The request includes the following parameters:
- Analytics ID = "QoS Sustainability";
- Target of Analytics Reporting: any UE, a list of UEs;
- Analytics Filter Information:
- QoS requirements (mandatory):
- 5QI (standardized or pre-configured) and applicable additional QoS parameters and the corresponding values (conditional, i.e. it is needed for GBR 5QIs to know the GFBR); or
- the QoS Characteristics attributes including Resource Type, PDB, PER and their values;
- Location information (mandatory): an Area Of Interest or a path of interest. The location information could reflect a list of waypoints:
- if the location information is an Area Of Interest, the area can be either described in a coarse granularity as list of TAIs or Cell IDs, or in a fine granularity as geographical area (that can be smaller than a cell), or both (coarse and fine granularity); if both granularities are provided, the NWDAF understands that the area of interest is the intersection between the fine granularity location and the list of TAIs or Cell IDs.
- if the location information is a path of interest, the area can be either described in a coarse granularity as list of TAIs or Cell IDs, or in a fine granularity as a list of waypoints (expressed as longitude and latitude and optional height in geographical coordinates) and combined with a radius value, or both (coarse and fine granularity); if both granularities are provided, the NWDAF understands that the path of interest is the intersection between the fine granularity location and the list of TAIs or Cell IDs.
- Threshold linear distance: The distance travelled by the UE before reporting subsequent location as described in TS 23.273 [39].
NOTE 1: Threshold linear distance is used by the NWDAF when requesting location of the UE from the GMLC using LCS.
NOTE 2: In this Release, the consumer of the "QoS Sustainability" Analytics ID will provide location information in the area of interest format (TAIs or Cell IDs or geographical area) which is understandable by NWDAF.
NOTE 3: When location information is described as an area of interest in a fine granularity (i.e. as geographical area that can be smaller than a cell) the Cell ID(s) can already be determined by the NEF based on its local configuration and provided to the NWDAF in addition. This addresses the scenario when Cell ID(s) cannot be determined by the NWDAF based on its local configuration. Alternatively, the NWDAF can also be configured with the Cell ID(s) corresponding to an area of interest in a fine granularity.
- S-NSSAI (optional);
- Optional maximum number of objects;
- Optional UE Device and Context Information: which may contain one or more of the following:
- Speed range, which is a range of UE speeds for which analytics is requested, where the speed range is indicated as a range of Velocity Estimate, as in clause 6.1.6.2.17 of TS 29.572 [37];
- Device information, which may contain one of the following:
- List of equipment types, according to clause 8.0 of GSMA TS.06 [38].
- Analytics target period: relative time interval, either in the past or in the future, that indicates the time period for which the QoS Sustainability analytics is requested;
- Optionally, Spatial granularity size and Temporal granularity size;
- Reporting Threshold(s), which apply only for subscriptions and indicate conditions on the level to be reached for the reporting of the analytics, i.e. to discretize the output analytics and to trigger the notification when the threshold(s) provided in the analytics subscription are crossed by the expected QoS KPIs.
- A matching direction may be provided such as crossed (default value), below, or above.
- An acceptable deviation from the threshold level in the non-critical direction (i.e. in which the QoS is improving) may be set to limit the amount of signalling.
The level(s) relate to value(s) of the QoS KPIs defined in TS 28.554 [10], for the relevant 5QI:
- for a 5QI of GBR resource type, the Reporting Threshold(s) refer to the QoS flow Retainability KPI;
- for a 5QI of non-GBR resource type, the Reporting Threshold(s) refer to the RAN UE Throughput KPI and/or end-to-end delay (i.e. sum of delay in RAN KPI and GTP delay KPI) as defined in TS 28.554 [10] and TS 28.552 [8].
- In a subscription, the Notification Correlation Id and the Notification Target Address.
To derive the QoS Sustainability analytics when the location information is an area of interest with coarse granularity (i.e. TAIs or Cell IDs):
- The NWDAF collects the corresponding statistics information on the QoS KPI for the relevant 5QI of interests from the OAM, i.e. the QoS flow Retainability or the RAN UE Throughput or delay in RAN as defined in TS 28.554 [10] and average GTP metrics as defined in TS 28.552 [8].
To derive the QoS Sustainability analytics when the location information is an area of interest with fine granularity (i.e. geographical area that can be smaller than a cell):
- The NWDAF derives the UE list for the area of interest with fine granularity by two steps, firstly based on an initial selection of the UE list in the corresponding coarse area from AMF, secondly based on finer granularity location data using LCS as described in clause 6.2.12, e.g. NWDAF can collect finer granularity location data of a UE using LCS and identify whether this UE is inside of the area of interest with fine granularity area, input data as defined in Table 6.9.2-2. Alternatively, the NWDAF may use a list of UEs provided by the consumer requesting/subscribing to the QoS Sustainability analytics.
- The NWDAF can then collect the corresponding UE level information on the QoS KPI for the relevant 5QI of interests from the 5GC NF/OAM, i.e. input data as defined in Table 6.9.2-2.
- NWDAF derives QoS sustainability statistics or predictions for the area of interest with fine granularity by averaging these input data for all the UEs that are in the list of UEs.
To improve QoS Sustainability analytics, the NWDAF may additionally collect GTP metrics defined in Table 6.9.2-3.
If the Analytics target period refers to the past:
- The NWDAF verifies whether the triggering conditions for the notification of QoS change statistics are met and if so, generates for the consumer one or more notifications.
- The analytics feedback contains the information on the location and the time for the QoS change statistics and the Reporting Threshold(s) that were crossed.
If the Analytics target period is in the future:
- The NWDAF detects the need for notification about a potential QoS change based on comparing the expected values for the KPI of the target 5QI against the Reporting Threshold(s) provided by the consumer in any cell in the requested area for the requested Analytics target period. The expected KPI values are derived from the statistics for the 5QI obtained from OAM. OAM information may also include planned or unplanned outages detection and other information that is not in scope for 3GPP to discuss in detail.
- The analytics feedback contains the information on the location and the time when a potential QoS change may occur and what Reporting Threshold(s) may be crossed.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.9.2 Input data
|
To derive the QoS Sustainability analytics for a path of interest or for an area of interest with coarse granularity (i.e. TAIs or Cell IDs), the input data is listed in Table 6.9.2-1.
Table 6.9.2-1: Data collection for "QoS Sustainability" analytics
Information
Source
Description
RAN UE Throughput
OAM TS 28.554 [10]
Average UE bitrate in the cell (Payload data volume on RLC level per elapsed time unit on the air interface, for transfers restricted by the air interface), per timeslot, per cell, per 5QI and per S-NSSAI.
QoS flow Retainability
OAM TS 28.554 [10]
Number of abnormally released QoS flows during the time the QoS Flows were used per timeslot, per cell, per 5QI and per S-NSSAI.
Delay in RAN
OAM TS 28.554 [10]
Average Uplink and downlink packet transmission delay through RAN part to the UE, per timeslot, per cell, per 5QI and per S-NSSAI.
NOTE 1: The timeslot is the time interval split according to the time unit of the OAM statistics defined by operator.
To derive the QoS Sustainability analytics for an area of interest with fine granularity (i.e. geographical area that can be smaller than a cell), additional input data is listed in Table 6.9.2-2.
Table 6.9.2-2: UE level data collection for "QoS Sustainability" analytics with fine granularity
Information
Source
Description
Timestamp
LCS (NOTE 1)
A time stamp associated with the collected information.
UE ID
LCS, AMF (NOTE 1)
(list of) SUPI(s).
Finer granularity location data
LCS (NOTE 1)
UE position in the area of interest.
Speed
LCS (NOTE 1)
Current UE speed.
SMF info
AMF
SMF address for the SMF serving the UE
UPF info
SMF
Address for the UPF serving the UE.
5QI
SMF
5G QoS Identifier.
PEI
UDM
Permanent Equipment Identifier, as described in clause 5.9.3 of 1 23.501 [2].
Equipment type
GSMA IMEI database or OAM
Equipment Type such as smartphone, tablet, dongle, etc. as described in GSMA TS.06 [38].
NOTE 1: The procedure to collect location data using LCS is described in clause 6.2.12.
NOTE 2: How to use the input data from GSMA for QoS Sustainability analytics is up to NWDAF implementation.
Additionally, the NWDAF collects the following input (Table 6.9.2-3) according to measurements defined in clause 5.33.3 QoS Monitoring to Assist URLLC Service of TS 23.501 [2] and IP-layer section capacity definition from ITU-T Y.1540 [40] between UE, NG-RAN and UPF at GTP level. The UL/DL available GTP capacity between UPF and UE will also be used as inputs for the QoS Sustainability analytics. The NWDAF calculates this value by implementation, e.g. by subtracting the UL/DL traffic volume from the maximum value of the GTP capacity.
Table 6.9.2-3: Data collection for QoS Sustainability analytics at GTP level
Information
Source
Description
UL/DL packet delay GTP
OAM TS 28.552 [8] (NOTE)
UL/DL packet delay measurement round trip on GTP path on N3 for non-GBR traffic.
UL/DL capacity GTP between UPF and NG-RAN
OAM
TS 28.552 [8]
TS 28.554 [10]
Maximum achievable UL/DL capacity measurement from UPF to NG-RAN based on GTP path. The capacity measurement corresponds to the IP-layer section capacity definition from ITU‑T Y.1540 [40]. It also corresponds to the descriptions in clause 5.1 (DL GTP Capacity) and clause 5.4 (UL GTP Capacity) of TS 28.552 [8] and clause 6.3 of TS 28.554 [10].
UL/DL capacity GTP between UPF and UE
OAM
TS 28.552 [8]
TS 28.554 [10]
Maximum achievable UL/DL capacity measurement from UE to UPF based on GTP path. The capacity measurement corresponds to the IP-layer section capacity definition from ITU‑T Y.1540 [40]. It also corresponds to the descriptions in clause 5.4 of TS 28.552 [8] and clause 6.3 of TS 28.554 [10].
NOTE: Refer to clause 5.1 of TS 28.552 [8] for the performance measurement in NG-RAN and clause 5.4 of TS 28.552 [8] for the performance measurement in UPF. In addition, Annex A of TS 28.552 [8] describes various performance measurements, especially, clause A.61 "Monitoring of one way delay between PSA UPF and NG-RAN" indicates that the measurements on the one way DL and UL delay between PSA UPF and NG-RAN can be used to evaluate and optimize the DL and UL user plane delay performance between 5GC and NG-RAN.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.9.3 Output analytics
|
The NWDAF outputs the QoS Sustainability analytics. Depending on the Analytics target period, the output consists of statistics or predictions. The detailed information provided by the NWDAF is defined in Table 6.9.3-1 for statistics and Table 6.9.3-2 for predictions.
Table 6.9.3-1: "QoS Sustainability" statistics
Information
Description
List of QoS sustainability Analytics (1..max)
>Applicable Area (NOTE 1)
A list of TAIs or Cell IDs or a geographical area in a fine granularity (e.g. smaller than a cell) within the Location information that the analytics applies to. 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.
>Applicable Time Period
The time period within the Analytics target period that the analytics applies to. If a Temporal granularity size was provided in the request or subscription, the duration of the Applicable Time Period is greater than or equal to the Temporal granularity size.
>Crossed Reporting Threshold(s)
The Reporting Threshold(s) that are met or exceeded or crossed by the statistics value or the expected value of the QoS KPI.
NOTE 1: The Applicable Area may be described as geographical area in a fine granularity (e.g. smaller than a cell) within the Location information when the location information is an area of interest with finer granularity or a path of interest expressed with a list of waypoints and a radius value. How to determine the geographical area is up to NWDAF implementation.
Table 6.9.3-2: "QoS Sustainability" predictions
Information
Description
List of QoS sustainability Analytics (1..max)
>Applicable Area (NOTE 1)
A list of TAIs or Cell IDs or a geographical area in a fine granularity (e.g. smaller than a cell) within the Location information that the analytics applies to. 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.
>Applicable Time Period
The time period within the Analytics target period that the analytics applies to. If a Temporal granularity size was provided in the request or subscription, the duration of the Applicable Time Period is greater than or equal to the Temporal granularity size.
>Crossed Reporting Threshold(s)
The Reporting Threshold(s) that are met or exceeded or crossed by the statistics value or the expected value of the QoS KPI.
>Confidence
Confidence of the prediction.
NOTE 1: The Applicable Area may be described as geographical area in a fine granularity (e.g. smaller than a cell) within the Location information when the location information is an area of interest with finer granularity or a path of interest expressed with a list of waypoints and a radius value. How to determine the geographical area is up to NWDAF implementation.
NOTE 1: The meaning of Confidence is based on the SLA, i.e. the consumer has to understand the meaning of the different values of Confidence.
NOTE 2: The Analytics can contain multiple sets of the above information if the location information reflected a list of waypoints.
The number of QoS sustainability analytics entries is limited by the maximum number of objects provided as part of Analytics Reporting Information.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.9.4 Procedures
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.9.4.1 Procedure for QoS Sustainability in a coarse granularity area
|
Figure 6.9.4.1-1 depicts a procedure for "QoS Sustainability" analytics in a coarse granularity area provided by NWDAF.
The NWDAF shall not activate the measurements for QoS Monitoring. If QoS Monitoring is already activated, the measurements will be triggered according to QoS Monitoring procedures (see clause 5.33.3 of TS 23.501 [2]).
Figure 6.9.4.1-1: "QoS Sustainability" analytics provided by NWDAF in a coarse granularity area
1. The consumer requests or subscribes to analytics information on "QoS Sustainability" provided by NWDAF. The parameters included in the request are described in clause 6.9.1.
The consumer may include multiple sets of parameters in order to provide different combinations of "Location information" and "Analytics target period" when requesting QoS Sustainability analytics.
2. The NWDAF collects the data specified in clause 6.9.2 from the OAM, following the procedure captured in clause 6.2.3.2.
3. The NWDAF verifies whether the triggering conditions are met and derives the requested analytics. The NWDAF can detect the need for notification based on comparing the requested analytics of the target 5QI against the Reporting Threshold(s) provided by consumer in any cell over the requested Analytics target period.
4. The NWDAF provides response or notification on "QoS Sustainability" to the consumer.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.9.4.2 Procedure for QoS Sustainability in a fine granularity area
|
Figure 6.9.4.2-1: Procedure for "QoS Sustainability" analytics in a fine granularity area
1. The NF consumer requests or subscribes to analytics information on "QoS Sustainability" provided by the NWDAF. The parameters included in the request are defined in clause 6.9.1 of TS 23.288 [5]. The NF can request statistics or predictions or both.
The consumer provides the "Location information" as defined in clause 6.9.1 when requesting QoS Sustainability analytics. If the AF doesn't provide TAIs or Cell IDs, the NWDAF as an 5GC internal NF needs to determine which cells are related to the fine granularity area.
The consumer may optionally provide UE Context or Subscription information such as one or more of the following: device speed or speed range, IMEI or IMEISV or TAC range, equipment type.
The consumer may optionally provide a list of SUPIs for the applicable UAV UEs to be used as a Target of Analytics Reporting.
NOTE 1: A UAS NF/NEF, for instance, can obtain a list of UEs using the procedures described in clause 5.3.4 and/or clause 5.12 of TS 23.256 [53] before requesting analytics from the NWDAF and setting a Target of Analytics Reporting to a list of UEs.
2a. If the request is authorized and in order to provide the requested analytics, the NWDAF decides the AMF(s) based on the TAIs/Cell IDs and obtains the UE list in the TAs/Cells either from AMF by invoking Namf_EventExposure_Subscribe service operation using event ID "Number of UEs present in a geographical area" as described in TS 23.502 [3] or uses the list of UEs provided by the consumer in the request.
2b. The NWDAF invokes Namf_EventExposure_Subscribe service operation to get the update of the UE list using event ID "UE moving in or out of Area of Interest" as described in TS 23.502 [3].
3. The NWDAF obtains location information using LCS by initiating the LCS Service Request to the GMLC to get the location and optionally the speed of UEs from UE list provided by the AMF or by the consumer in step 2 or in step 1, respectively.
4. The GMLC initiates the UE location service procedure and gets the location of the UEs as described in TS 23.273 [39].
5. The GMLC provides location information for each UE in the UE list to the NWDAF.
6. From the list of UE locations returned by the GMLC, the NWDAF identifies the UEs located in fine granularity area by comparing the UEs' locations to the fine granularity area, provided in step 1.
7. The NWDAF invokes Namf_EventExposure_Subscribe service operation to get the serving SMF for the UE.
8. Based on the serving SMF in step 7, the NWDAF invokes Nsmf_EventExposure_Subscribe service operation to get the UPF information and 5QI for the UE.
9. The NWDAF may collect QoS information either from the UPF directly, or subscribe to the UPF via the SMF. The QoS information may include the bandwidth, packet delay for the UE and the information on the serving UPF node id.
NOTE 1: How the data from UPF is retrieved (subscribed to on UPF and notified then by UPF) is defined in clause 5.8.2.17 of 23.501 [2] and in clause 4.15.4 of TS 23.502 [3].
10. Optionally, the NWDAF may collect additional information for the UE Context or UE Subscription from the UDM such as PEI (if available). PEI may be used to retrieve, from GSMA database, additional information such as IMEI or IMEISV or TAC range, equipment type. Such additional information may be used by NWDAF to add more information to the collected measurements and filter those measurements that are applicable to the UE Device and Context Information for which analytics are requested by the service consumer.
11. The NWDAF verifies whether the triggering conditions are met and derives the requested analytics. The NWDAF can detect the need for notification based on comparing the requested analytics of the target 5QI against the Reporting Threshold(s) provided by the consumer in any cell over the requested Analytics target period.
12. The NWDAF provides the response or notification on "QoS Sustainability" to the NF consumer.
NOTE 2: NWDAF may decide to ignore some of the filters if collected measurements are not sufficient to derive meaningful analytics.
NOTE 3: In order to reduce the amount of information collected per measurement point, the additional information from UDM may only be collected for the events of GBR unfulfillment. In this way the additional analytics filter information may only be supported for 5QI of resource type GBR and for events of GBR unfulfillment.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.10 Dispersion Analytics
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.10.1 General
|
Dispersion analytics identifies the location (i.e. areas of interest, TAs, cells) or network slice(s) where a UE, or a group of UEs, or any UE disperse most (if not all) of their data volume and sessions transactions (i.e. MM and SM messages).
The NWDAF shall be able to provide dispersion statistics or predictions and shall be able to collect UE dispersion related information from NFs.
Dispersion is the percentage of activity that a UE, or group of UEs, or any UE, generates at a location or a slice during a period of interest. This enables the operator to rank hot locations or slices by the various activities and to identify the top contributors (i.e. UEs) for that activity. When heavy UEs at a particular location or slice are detected/predicted and reported to a policy entity, their QoS attributes, or access to an area of interest or a slice can then be limited.
- Data volume dispersion - The percentage of data traffic volume that a UE, or a group of UEs, or any UE, generated at a location or in a slice during the period of interest.
- Transactions dispersion - The percentage of MM and SM messages that a UE, or a group of UEs, or any UE, generated at a location or in a slice during the period of interest.
The operator may classify and assign one of the three mobility classes per dispersion characteristics for a UE or a group of UEs, or any UE as fixed, camper or traveller. In addition, the operator may classify a UE as a Top-Heavy UE in case its dispersion percentile rating, at a location or a slice, is higher than a threshold value defined by the operator (e.g. 0.9 percentile), see percentile ranking in the output tables, clause 6.10.3. The classification is based on either Data volume dispersion or Transactions dispersion.
- Data-Classification - fixed, camper, traveller data-classification per thresholds assigned by the operator.
EXAMPLE: When a UE disperses, during the period of observation, most (threshold=95%) of its data at a location or a slice, the dispersion data-classification of the UE at that location or slice is "fixed".
- Transaction-Classification - fixed, camper, traveller transactions-classifications per thresholds assigned by the operator.
EXAMPLE: When a UE disperses, during the period of observation, (threshold=40%) of its session transactions at a location or a slice, the dispersion transaction-classification of the UE is camper at that location or slice.
Based on the dispersion analytics, the analytics consumer can determine that a data volume or transactions hot spot is formed when the volume of data or amount of transactions dispersed by most of the UEs at the area of interest or slice exceeds a certain data or transaction threshold established through trend analysis or operator policy.
The consumer of dispersion analytics may indicate in its request:
- Analytics ID = "Dispersion Analytics";
- Target of Analytics Reporting as defined in clause 6.1.3. "Any UE" is only supported in combination with Analytics Filter Information (S-NSSAI, Area(s) of Interest, Top-Heavy UEs indication, Fixed indication, Camper indication or Traveller indication) and Dispersion Analytics type "Data Volume Dispersion Analytics" and/or "Transaction Dispersion Analytics";
- Analytics Filter Information:
- optional list of TAs, Areas of Interest, Cells, or S-NSSAIs, Application IDs, Top-Heavy UEs, Fixed UEs, Camper UEs, Dispersion Analytics types (Data Volume Dispersion Analytics (DVDA) or Transactions Dispersion Analytics (TDA) or both); and
- optional list of analytics subsets that are requested (see clause 6.10.3);
- Preferred level of accuracy of the analytics;
- Preferred level of accuracy per analytics subset (see clause 6.10.3);
- Preferred order of results for the list of UE Dispersion Analytics information:
- ordering criterion:
- For DDA, one of the following: "time slot start", "data dispersion", "data classification", "data ranking", or "data percentile ranking";
- For TDA, one of the following: "time slot start", "transaction dispersion", "transaction classification", "transaction ranking", or "transaction percentile ranking"; and
- order: ascending or descending;
- Analytics target period indicating the time period over which the statistics or predictions are requested;
- Optionally, maximum number of objects and maximum number of SUPIs;
- Optionally, preferred granularity of location information: TA level or cell level;
- Optionally, Spatial granularity size and Temporal granularity size; and
- In a subscription, the Notification Correlation Id and the Notification Target Address are included.
NOTE 1: If one or multiple ID(s) are included in the filter information, the output analytics will be reported per Application ID, otherwise the output analytics is aggregated information per AOI or slice independent of the applications.
NOTE 2: Care needs to be taken with regards to load when requesting analytics for "Any UE". This could be achieved by utilizing event filters (e.g. Area of Interest for AMF) and possible analytics filters including Top-Heavy UEs and/or Fixed and/or Camper UEs and/or Analytics Reporting Information (e.g. SUPImax), or sampling ratio as part of Event Reporting Information. The load of analytics for "Any UE" can be alleviated by limiting the number of S-NSSAI in the analytics filter.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.10.2 Input Data
|
The NWDAF shall be able to collect UE dispersion information from NF(s) and AFs. The information collected by the NWDAF is network data from 5GC NFs and service data from AFs:
- Data related to UE transactions dispersion and bound by location collected from AMF and SMF are defined in the tables 6.10.2-1 and 6.10.2-2. This may include individual transactions or SMF/AMF state transition information stored as UE behaviour trends, which provides aggregated transaction information.
Table 6.10.2-1: Location based UE transactions dispersion information collected from serving AMF
Information
Source
Description
UE ID
AMF
SUPI.
Type Allocation Code
AMF
Terminal model and vendor information of the UE.
UE locations (1..max)
AMF
UE locations.
> UE location
AMF
Area of Interest (TA or cells that the UE had entered).
> Timestamp
AMF
Time stamp when the AMF detected that the UE had entered this location.
> Transactions
AMF
Either all transactions for this UE in this location or, optionally, if subscription with periodic notification is requested, the amount of UE transactions exchanged at the location in the notified time period.
UE access behaviour trends
AMF
Metrics on UE state transitions (e.g. access, RM and CM states, handover).
UE location trends
AMF
Metrics on UE locations.
NOTE: UE location provides one location per instance while UE location trend provides multiple locations at once. One or both of them may be used.
Table 6.10.2-2: UE transactions dispersion information collected from serving SMF
Information
Source
Description
UE IP address
SMF
UE IP address.
UE ID
SMF
SUPI.
> Timestamp
SMF
Time stamp of the collected information.
> Transactions
SMF
Either all transaction for this UE or, optionally, if subscription with periodic notification is requested, the amount of UE transactions exchanged in the notified time period.
> UE session behaviour trends
SMF
Metrics on UE state transitions (e.g. PDU Session Establishment, PDU Session Release).
Data volume can be collected from the AF per UE across all the UE applications provided by a particular AF or per UE per application when application IDs are requested.
Data related to UE data volume dispersion, bound by a location or slice, collected from the AF and UPF are defined in tables 6.10.2-3 through 6.10.2-6.
If the Target of Analytics Reporting is set to an Internal Group ID and the AF is located in the untrusted domain, NEF translates it into an External Group ID.
NOTE 1: It is assumed that the AF is provisioned with the list of UE IDs (GPSIs or SUPIs) belonging to an External or Internal Group ID.
- In table 6.10.2-3, the data volume is collected per UE from the AF. The collected UE information is applicable across all the applications used by the UE during the period.
Table 6.10.2-3: UE Data volume dispersion information collected from the AF
Information
Source
Description
UE ID
AF
Internal or External UE ID (i.e. SUPI or GPSI, respectively).
Timestamp
AF
Time stamp of the collected information.
Data Volume UL/DL
AF
Sum of UE data volume exchanged at the AF during the period of observation.
- In table 6.10.2-4, the AF reports data volume per UE per application in relation to the start and stop of the application as indicated by the application duration.
Table 6.10.2-4: UE data volume dispersion collected from the AF
Information
Source
Description
UE IP address
AF
UE IP address.
IP 5-tuple
AF
IP address 5-tuple.
Timestamp
AF
Timestamp of the collected information.
Application ID
AF
Identifier of the application at the AF.
Location of Application
AF/NEF
Location of application represented by a list of DNAIs. The NEF may map the AF-Service identifier information to a list of DNAIs when the DNAIs being used by the application are statically defined.
Data Volume UL/DL
AF
Sum of UE data volume exchanged per application during the period.
Application duration
AF
Duration for the application (e.g. Voice talk time).
NOTE 1: Application ID and IP 5-tuple are mutually exclusive.
NOTE 2: Multiple outputs are provided by the AF when multiple applications are running at the AF for the same UE and time period.
Data volume can also be collected from the UPF per UE IP address across all applications or per UE for specific application(s).
- In table 6.10.2-5, the data volume is collected per UE from the UPF. The collected UE information is applicable across all applications used by the UE between start and stop of the PDU session. The UPF reports volume per UE IP address across all applications.
Table 6.10.2-5: UE data volume dispersion collected from serving UPF
Information
Source
Description
UE IP address
UPF
UE IP address.
Timestamp
UPF
Time stamp of the collected information.
Data Volume UL/DL
UPF
Sum of UE data volume exchanged per UE across all applications.
NOTE: The Data volume can be reported either as total volume of the PDU session or periodically. It refers to the Data volume exchanged between the start and stop of the PDU session. When reported periodically, the period can be specified in the requested analytic target period or configured as a default value in the UPF.
- In table 6.10.2-6, the UPF reports data volume per UE for specific application(s) in relation to the start and stop of the application as indicated by the application duration.
There are two modes of data collection:
- Non periodical: A mode where the data volume is requested and consequently provided for the total volume of a PDU session.
- Periodical: A mode where data volume is provided periodically between the start and stop of a PDU session. The period can be specified in the requested analytic target period or configured as a default value in the UPF.
For both modes of data collection, if there are multiple application sessions for the UE PDU session, the NWDAF aggregates (i.e. sums up) the data volume across all applications to obtain per UE information.
Table 6.10.2-6: UE data volume dispersion collected from serving UPF
Information
Source
Description
UE IP address
UPF
UE IP address.
Timestamp
UPF
A timestamp of the collected information.
Application ID
UPF
Identify the application at the UPF
IP 5-tuple
UPF
IP 5-tuple.
Location of Application
UPF
List of Internet applications represented by DNAI(s).
Data Volume UL/DL
UPF
Sum of UE data volume exchanged per application during the period.
Application duration
UPF
Duration for the application (e.g. Voice talk time).
NOTE 1: Application ID and IP 5-tuple are mutually exclusive.
NOTE 2: Multiple outputs are provided by the UPF when multiple applications are running at the UPF for the same UE and time period.
NOTE 3: The Data volume can be reported either as total volume of the PDU session or periodically. It refers to the Data volume exchanged between the start and stop of the PDU session. When reported periodically, the period can be specified in the requested analytic target period or configured as a default value in the UPF.
The task of the NWDAF is to calculate the volume of data and amount of transactions dispersed by the UE at each visited location during a period of interest. The entry time and exit time to a location is provided by the AMF.
Collecting volume per UE and per specific application is optional and such information can be provided by the UPF or AF.
The Correlation Information as defined in table 6.2.4-1 is used to correlate the input data from AMF and SMF, the input data from SMF and UPF and the input data from UPF and AF.
- Slice information related to UE transactions dispersion from NF(s) are defined in tables 6.10.2-7 and 6.10.2-8. This may include individual transactions or SMF/AMF state transition information stored as UE behaviour trends, which provides aggregated transaction information.
- The Slice data volume collection is the same as listed in tables 6.10.2-3 to 6.10.2-6.
Table 6.10.2-7: Slice based UE transactions dispersion information collected from serving AMF
Information
Source
Description
UE ID
AMF
SUPI.
Type Allocation Code
AMF
Terminal model and vendor information of the UE.
Slice (1..max)
AMF
UE assigned slice.
>S-NSSAI
AMF
Identifier of the slice.
>Timestamp
AMF
Time stamp when the slice was assigned.
>Transactions (NOTE)
AMF
Either all transactions for this UE or, optionally, if subscription with periodic notification is requested, an amount of UE transactions exchanged at the slice in the notified time period.
UE access behaviour trends
AMF
Metrics on UE state transitions (e.g. access, RM and CM states, handover).
NOTE: When a UE moves to a new AMF during Analytics target period, timestamps for assigned slices of the UE are set to the date and time of the new AMF. The NWDAF shall aggregate (sum up) the amount of slice transactions, for the requested Analytics target period, across the AMFs traversed by the UE.
Table 6.10.2-8: Slice based UE transactions dispersion information collected from serving SMF
Information
Source
Description
UE IP
SMF
UE IP address.
UE ID
SMF
SUPI.
Slice (1..max)
SMF
UE assigned slice.
>S-NSSAI
SMF
Identifier of the slice.
>Timestamp
SMF
Time stamp associated with the collected information.
>Application ID
SMF
Identifier of the application for the UE in the slice.
>Transactions
SMF
Either all transactions for this UE or, optionally, if subscription with periodic notification is requested, an amount of UE transactions exchanged at the slice in the notified time period.
UE session behaviour trends
SMF
Metrics on UE state transitions (e.g. PDU Session Establishment, PDU Session Release).
The task of the NWDAF is to calculate the volume of data and amount of transactions dispersed by the UE at each slice during a period of interest. A time stamp of a slice assignment is provided by the AMF.
The Correlation Information as defined in table 6.2.4-1 is used to correlate the input data from AMF and SMF, the input data from SMF and UPF and the input data from UPF and AF.
Data collection may be provided on samples (e.g. spatial subsets of UEs or UE group, temporal subsets of UE location information).
NOTE 2: How the data from UPF is retrieved (subscribed to on UPF and notified then by UPF) is defined in clause 5.8.2.17 of TS 23.501 [2] and in clause 4.15.4 of TS 23.502 [3].
NOTE 3: The list of monitored transactions (MM and SM messages) is a subset of the messages listed in clauses 8.2 and 8.3 of TS 24.501 [23].
NOTE 4: The Namf_EventExposure and Nsmf_EventExposure services in clauses 5.2.2.3 and 5.2.8.3 of TS 23.502 [3] provide the required transactions information.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.10.3 Output Analytics
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.10.3.0 General
|
The NWDAF provides UE dispersion analytics, which can be statistics and/or prediction for data volume and/or transactions dispersions, to consumer NFs or AFs.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.10.3.1 Data Volume Dispersion Analytics
|
The data volume dispersion analytics results provided by the NWDAF can be for a UE or group of UEs or "any UE" data volume dispersion statistics as defined in table 6.10.3.1-1 and/or UE data volume dispersion predictions as defined in table 6.10.3.1-2. If the analytics covers multiple UEs, the Data dispersed, Data ranking and Data percentile ranking parameters are calculated as the aggregated (i.e. summed up) data volume. When the Target of Analytics Reporting is set as "any UE" the data volume dispersion analytics results provided by the NWDAF can be for all UEs data volume dispersion statistics at a location and/or the slice and/or data volume dispersion predictions at a location and/or the slice.
Table 6.10.3.1-1: Data volume dispersion statistics bound by location
Information
Description
UE group ID or UE ID or list of UE IDs (1..SUPImax)
Identifies the UE(s) for which the statistic applies by a list of SUPIs, or a group of UEs by a list of Internal-Group-Ids (see NOTE 1).
Time slot entry (1..max)
List of time slots during the Analytics target period.
> Time slot start
Time slot start within the Analytics target period.
> Duration
Duration of the time slot. If a Temporal granularity size was provided in the request or subscription, the Duration is greater than or equal to the Temporal granularity size.
> UE location (1..max)
Observed location statistics.
>> UE location
TA or cells where the UE or UE group or list of UEs dispersed its data (see NOTE 3).
>> Application ID (0..max) (NOTE 7)
To identify the application (NOTE 6).
>>> Data volume dispersed (NOTE 4)
Data volume dispersed at this location.
>> Data mobility classification (NOTE 4)
Data mobility classification of the UE for this location: fixed, camper, traveller (see NOTE 5).
>> Data usage ranking (NOTE 4) (NOTE 7)
Ranking of UE data usage at this location (See NOTE 2).
>> Data usage percentile ranking (NOTE 4) (NOTE 7)
Percentile ranking of the UE or UE group in the Cumulative Distribution Function of data usage for the population of all UEs served at the location.
>> Ratio
Percentage of UEs in the group at the location and observation time (in the case of UE group).
NOTE 1: When Target of Analytics Reporting is an individual UE, a single UE ID (i.e. SUPI) will be included. When Target of Analytics Reporting is a UE group ID, an internal group ID will be included. When Target of Analytics Reporting is a UE group ID or "Any UE" and a filter for Top-Heavy UEs, fixed, camper or traveller is included, the NWDAF will include the list of UEs matching the filter. This information element is not present when Target of Analytic Reporting is "Any UE" and no filter for Top-Heavy UEs, fixed, camper or traveller is included. The NWDAF will provide the dispersion analytics result of one or a list of time slots to the service consumer(s) for the UE, group of UEs or list of UEs.
NOTE 2: UE is ranked high (i.e. 1), medium (2) and low (3) when its data dispersed, during the period of observation at the location, is higher than N1% or at the range of N1% to N2% or less than N2%, respectively. The percentage values of N1 and N2 are subject to operator's configuration.
NOTE 3: When possible and applicable to the access type, UE location is provided according to the preferred granularity of location information and Spatial granularity size.
NOTE 4: This information element is an analytics subset that can be used in "list of analytics subsets that are requested" and "preferred level of accuracy per analytics subset".
NOTE 5: This parameter is only provided for Target of Analytics Reporting set to single UE.
NOTE 6: When Application ID is not included in the input, cardinality is zero and data volume dispersed is provided per UE location and applies across all the applications in that location.
NOTE 7: This parameter is not provided for Target of Analytics Reporting set to "Any UE".
Table 6.10.3.1-2: Data volume dispersion prediction bound by location
Information
Description
UE group ID or UE ID or list of UE IDs (1..SUPImax)
Identifies the UE(s) for which the prediction applies by a list of SUPIs, or a group of UEs by a list of Internal-Group-Ids (see NOTE 1).
Time slot entry (1..max)
List of time slots during the Analytics target period.
> Time slot start
Time slot start within the Analytics target period.
> Duration
Duration of the time slot. If a Temporal granularity size was provided in the request or subscription, the Duration is greater than or equal to the Temporal granularity size.
> UE location (1..max)
Predicted location during the analytics target period.
>> UE location
TA or cells where the UE or UE group or list of UEs is predicted to disperse its data (see NOTE 3).
>> Application ID (0..max) (NOTE 7)
To identify the application (NOTE 6).
>>> Data volume dispersion (NOTE 4)
Data volume dispersion prediction at this location.
>>>> Confidence
Confidence of this prediction (i.e. data volume to be dispersed at this location).
>> Data mobility classification (NOTE 4)
Data mobility classification of the UE for this location: fixed, camper, traveller (see NOTE 5).
>>> Confidence
Confidence of this prediction (i.e. mobility classification at this location).
>> Data usage ranking (NOTE 4) (NOTE 7)
Ranking of UE data usage at this location (See NOTE 2).
>> Data percentile usage ranking (NOTE 4) (NOTE 7)
Percentile ranking of the UE or UE group in the Cumulative Distribution Function of data usage for the population of all UEs served at the location.
>>> Confidence
Confidence of this prediction (i.e. percentile ranking at this location).
>> Ratio
Percentage of UEs in the group (in the case of UE group).
NOTE 1: When Target of Analytics Reporting is an individual UE, a single UE ID (i.e. SUPI) will be included. When Target of Analytics Reporting is a UE group ID, an internal group ID will be included. When Target of Analytics Reporting is a UE group ID or "Any UE" and a filter for Top-Heavy UEs, fixed, camper or traveller is included, the NWDAF will include the list of UEs matching the filter. This information element is not present when Target of Analytic Reporting is "Any UE" and no filter for Top-Heavy UEs, fixed, camper or traveller is included. The NWDAF will provide the dispersion analytics result of one or a list of time slots to the service consumer(s) for the UE, group of UEs or list of UEs.
NOTE 2: UE is ranked high (i.e. 1), medium (2) and low (3) when its data dispersed, during the period of observation at the location, is higher than N1% or at the range of N1% to N2% or less than N2%, respectively. The percentage values of N1 and N2 are subject to operator's configuration.
NOTE 3: When possible and applicable to the access type, UE location is provided according to the preferred granularity of location information and Spatial granularity size.
NOTE 4: This information element is an analytics subset that can be used in "list of analytics subsets that are requested" and "preferred level of accuracy per analytics subset".
NOTE 5: This parameter is only provided for Target of Analytics Reporting set to single UE.
NOTE 6: When Application ID is not included in the input, cardinality is zero and data volume dispersion prediction is provided per UE location and applies across all the applications in that location.
NOTE 7: This parameter is not provided for Target of Analytics Reporting set to "Any UE".
The data volume dispersion analytics results provided by the NWDAF can also be for a UE or group of UEs or "any UE" data volume dispersion statistics at a given slice as defined in Table 6.10.3.1-3 and/or data volume dispersion predictions as defined in Table 6.10.3.1-4. If the analytics covers multiple UEs, the Data dispersed, Data ranking and Data percentile ranking parameters are calculated as the aggregated (i.e. summed up) data volume. When the Target of Analytics Reporting is set as "any UE" the data volume dispersion analytics results provided by the NWDAF can be for all UEs data volume dispersion statistics at a given slice and/or data volume dispersion predictions at a given slice.
Table 6.10.3.1-3: Data volume dispersion statistics bound by slice
Information
Description
UE group ID or UE ID or a list of UE IDs (1..SUPImax)
Identifies the UE(s) for which the statistics applies by a list of SUPIs, or a group of UEs by a list of Internal-Group-Ids (see NOTE 1).
Time slot entry (1..max)
List of time slots during the Analytics target period.
> Time slot start
Time slot start within the Analytics target period.
> Duration
Duration of the time slot. If a Temporal granularity size was provided in the request or subscription, the Duration is greater than or equal to the Temporal granularity size.
> Slice (1..max)
Observed slice statistics.
>> S-NSSAI
Slice where the UE or group of UEs or list of UEs dispersed data.
>> Application ID (0..max) (NOTE 6)
To identify the application at the slice (NOTE 5).
>>> Data volume dispersed (NOTE 3)
Data volume dispersed at this slice.
>> Data mobility classification (NOTE 3)
Data mobility classification of the UE at the slice: fixed, camper, traveller (see NOTE 4).
>> Data usage ranking (NOTE 3) (NOTE 6)
Ranking of UE data usage at this slice. (See NOTE 2).
>> Data usage percentile ranking (NOTE 3) (NOTE 6)
Percentile ranking of the UE or UE group in the Cumulative Distribution Function of data usage for the population of all UEs served by the slice.
>> Ratio
Percentage of UEs in the group (in the case of UE group).
NOTE 1: When Target of Analytics Reporting is an individual UE, a single UE ID (i.e. SUPI) will be included. When Target of Analytics Reporting is a UE group ID, an internal group ID will be included. When Target of Analytics Reporting is a UE group ID or "Any UE" and a filter for Top-Heavy UEs, fixed, camper or traveller is included, the NWDAF will include the list of UEs matching the filter. This information element is not present when Target of Analytic Reporting is "Any UE" and no filter for Top-Heavy UEs, fixed, camper or traveller is included. The NWDAF will provide the dispersion analytics result of one or a list of time slots to the service consumer(s) for the UE, the group of UEs or the list of UEs.
NOTE 2: UE is ranked high (i.e. 1), medium (2) and low (3) when its data dispersed, during the period of observation at the location, is higher than N1% or at the range of N1% to N2% or less than N2%, respectively. The percentage values of N1 and N2 are subject to operator's configuration.
NOTE 3: This information element is an analytics subset that can be used in "list of analytics subsets that are requested" and "preferred level of accuracy per analytics subset".
NOTE 4: This parameter is only provided for Target of Analytics Reporting set to single UE.
NOTE 5: When Application ID is not included in the input, cardinality is zero and data volume dispersed is provided per slice and applies across all the applications in the slice.
NOTE 6: This parameter is not provided for Target of Analytics Reporting set to "Any UE".
Table 6.10.3.1-4: Data volume dispersion prediction bound by slice
Information
Description
UE group ID or UE ID or list of UE IDs (1..SUPImax)
Identifies the UE(s), for which the prediction applies by a list of SUPIs, or a group of UEs by a list of Internal-Group-Ids (see NOTE 1).
Time slot entry (1..max)
List of time slots during the Analytics target period.
> Time slot start
Time slot start within the Analytics target period.
> Duration
Duration of the time slot. If a Temporal granularity size was provided in the request or subscription, the Duration is greater than or equal to the Temporal granularity size.
> Slice (1..max)
Predicted slice during the Analytics target period.
>> S-NSSAI
Slice where the UE or UE group or list of UEs is predicted to disperse its data.
>> Application ID (0..max) (NOTE 6)
To identify the application at the slice (NOTE 5).
>>> Data volume dispersion (NOTE 3)
Data volume dispersion prediction at this slice.
>>>> Confidence
Confidence of this prediction (i.e. data volume to be dispersed at this slice).
>> Data mobility classification (NOTE 3)
Data mobility classification of the UE at this slice: fixed, camper, traveller (see NOTE 4).
>>> Confidence
Confidence of this prediction (i.e. mobility classification at this slice).
>> Data usage ranking (NOTE 3) (NOTE 6)
Ranking of UE data usage at this slice. See NOTE 2.
>> Data usage percentile ranking (NOTE 3) (NOTE 6)
Percentile ranking of the UE or UE group in the Cumulative Distribution Function of data usage for the population of all UEs served by the slice.
>>> Confidence
Confidence of this prediction (i.e. percentile ranking at this slice).
>> Ratio
Percentage of UEs in the group (in the case of UE group).
NOTE 1: When Target of Analytics Reporting is an individual UE, a single UE ID (i.e. SUPI) will be included. When Target of Analytics Reporting is a UE group ID, an internal group ID will be included. When Target of Analytics Reporting is a UE group ID or "Any UE" and a filter for Top-Heavy UEs, fixed, camper or traveller is included, the NWDAF will include the list of UEs matching the filter. This information element is not present when Target of Analytic Reporting is "Any UE" and no filter for Top-Heavy UEs, fixed, camper or traveller is included. The NWDAF will provide the dispersion analytics result of one or a list of time slots to the service consumer(s) for the UE, group of UEs or list of UEs.
NOTE 2: UE is ranked high (i.e. 1), medium (2) and low (3) when its data dispersed, during the period of observation at the location, is higher than N1% or at the range of N1% to N2% or less than N2%, respectively. The percentage values of N1 and N2 are subject to operator's configuration.
NOTE 3: This information element is an analytics subset that can be used in "list of analytics subsets that are requested" and "preferred level of accuracy per analytics subset".
NOTE 4: This parameter is only provided for Target of Analytics Reporting set to single UE.
NOTE 5: When Application ID is not included in the input, cardinality is zero and data volume dispersion prediction is provided per slice and applies across all the applications in the slice.
NOTE 6: This parameter is not provided for Target of Analytics Reporting set to "Any UE".
When the Target of Analytics Reporting is set as "any UE", no filter for Top-Heavy UEs, fixed, camper or traveller is included and the Analytics Filter Information is set to one or several S-NSSAIs and DDVA, the data volume dispersion analytics results provided by the NWDAF can be for all UEs data volume dispersion statistics at a given slice as defined in Table 6.10.3.1-5 and/or data volume dispersion predictions as defined in Table 6.10.3.1-6:
Table 6.10.3.1-5: Data volume dispersion statistics bound by slice (for any UE)
Information
Description
Time slot entry (1..max)
List of time slots during the Analytics target period.
> Time slot start
Time slot start within the Analytics target period.
> Duration
Duration of the time slot. If a Temporal granularity size was provided in the request or subscription, the Duration is greater than or equal to the Temporal granularity size.
> Slice (1..max)
Observed slice statistics.
>> S-NSSAI
Slice where all UEs dispersed data.
>> Data volume dispersed
Data volume dispersed at this slice. (see NOTE 1).
NOTE 1: Utilized bandwidth (i.e. average throughput) at the slice can be calculated by using the Data volume dispersed in the Duration.
Table 6.10.3.1-6: Data volume dispersion prediction bound by slice (for any UE)
Information
Description
Time slot entry (1..max)
List of time slots during the Analytics target period.
> Time slot start
Time slot start within the Analytics target period.
> Duration
Duration of the time slot. If a Temporal granularity size was provided in the request or subscription, the Duration is greater than or equal to the Temporal granularity size.
> Slice (1..max)
Predicted slice during the Analytics target period.
>> S-NSSAI
Slice where the UE is predicted to disperse its data.
>> Data volume dispersion
Data volume dispersion prediction at this slice. (see NOTE 1).
>>>> Confidence
Confidence of this prediction (i.e. data to be dispersed at this slice).
NOTE 1: Utilized bandwidth (i.e. average throughput) predication at the slice can be calculated by using the Data volume dispersion in the Duration.
NOTE: The Application ID in the Data Volume Dispersion Analytics is optional. When the Application ID is missing, the Data Volume Dispersion Analytics is applied across all the applications in an AOI or a slice.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.10.3.2 Transactions Dispersion Analytics
|
The transactions (MM and MS messages) dispersion analytics results provided by the NWDAF can be for a UE or group of UEs or "any UE" transactions dispersion statistics as defined in Table 6.10.3.2-1 and/or UE transactions dispersion predications as defined in Table 6.10.3.2-2. If the analytics covers multiple UEs, the Transactions dispersed, Transactions ranking and Transactions percentile ranking parameters are calculated as the aggregated (i.e. summed up) number of transactions. When the Target of Analytics Reporting is set as "any UE" the transaction dispersion analytics results provided by the NWDAF can be for all UEs transaction dispersion statistics at a location and/or the slice and/or transaction dispersion predictions at a location and/or the slice.
Table 6.10.3.2-1: Transactions dispersion statistics bound by location
Information
Description
UE group ID or UE ID or list of UE IDs (1..SUPImax)
Identifies the UE(s) for which the statistics applies by a list of SUPIs, or a group of UEs by a list of Internal-Group-Ids (see NOTE 1).
Time slot entry (1..max)
List of time slots during the Analytics target period.
> Time slot start
Time slot start within the Analytics target period.
> Duration
Duration of the time slot. If a Temporal granularity size was provided in the request or subscription, the Duration is greater than or equal to the Temporal granularity size.
> UE location (1..max)
Observed location statistics.
>> UE location
TA or cells where the UE or group of UEs or list of UEs dispersed its transactions (see NOTE 3).
>> Transactions dispersed (NOTE 4)
Transactions amount dispersed at this location.
>> Transactions mobility classification (NOTE 4)
Transactions mobility classification of the UE for this location: fixed, camper, traveller (see NOTE 5).
>> Transactions ranking (NOTE 4) (NOTE 6)
Ranking of transactions amount at this location. See NOTE 2.
>> Transactions percentile ranking (NOTE 4) (NOTE 6)
Percentile ranking of the UE or UE group in the Cumulative Distribution Function of transactions for the population of all UEs served at the location.
>> Ratio
Percentage of UEs in the group (in the case of UE group).
NOTE 1: When Target of Analytics Reporting is an individual UE, a single UE ID (i.e. SUPI) will be included. When Target of Analytics Reporting is a UE group ID, an internal group ID will be included. When Target of Analytics Reporting is a UE group ID or "Any UE" and a filter for Top-Heavy UEs, fixed, camper or traveller is included, the NWDAF will include the list of UEs matching the filter. This information element is not present when Target of Analytic Reporting is "Any UE" and no filter for Top-Heavy UEs, fixed, camper or traveller is included. The NWDAF will provide the dispersion analytics result of one or a list of time slots to the service consumer(s) for the UE, group of UEs or list of UEs.
NOTE 2: UE is ranked high (i.e. 1), medium (2) and low (3) when its transactions are dispersed, during the period of observation at the location, is higher than N1% or at the range of N1% to N2% or less than N2%, respectively. The percentage values of N1 and N2 are subject to operator's configuration.
NOTE 3: When possible and applicable to the access type, UE location is provided according to the preferred granularity of location information and Spatial granularity size.
NOTE 4: This information element is an analytics subset that can be used in "list of analytics subsets that are requested" and "preferred level of accuracy per analytics subset".
NOTE 5: This parameter is only provided for Target of Analytics Reporting set to single UE.
NOTE 6: This parameter is not provided for Target of Analytics Reporting set to "Any UE".
Table 6.10.3.2-2: Transactions dispersion prediction bound by location
Information
Description
UE group ID or UE ID or list of UE IDs (1..SUPImax)
Identifies the UE(s), for which the prediction applies by a list of SUPIs, or a group of UEs by a list of Internal-Group-Ids (see NOTE 1).
Time slot entry (1..max)
List of predicted time slots.
> Time slot start
Time slot start within the Analytics target period.
> Duration
Duration of the time slot. If a Temporal granularity size was provided in the request or subscription, the Duration is greater than or equal to the Temporal granularity size.
> UE location (1..max)
Predicted location during the analytic target period.
>> UE location
TA or cells where the UE or group of UEs or list of UEs is predicted to disperse its transactions (see NOTE 3).
>> Transactions dispersion (NOTE 4)
Transaction amount predicted to be dispersed at this location.
>>> Confidence
Confidence of this prediction (i.e. data to be dispersed at this location).
>> Transactions mobility classification (NOTE 4)
Transaction mobility classification of the UE for this location: fixed, camper, traveller (see NOTE 5).
>>> Confidence
Confidence of this prediction (i.e. mobility classification at this location).
>> Transactions ranking (NOTE 4) (NOTE 6)
Ranking of transactions amount at this location. See NOTE 2.
>> Transactions percentile ranking (NOTE 4) (NOTE 6)
Percentile ranking of the UE or UE group in the Cumulative Distribution Function of transactions for the population of all UEs served at the location.
>>> Confidence
Confidence of this prediction (i.e. percentile ranking at this location).
>> Ratio
Percentage of UEs in the group (in the case of UE group).
NOTE 1: When Target of Analytics Reporting is an individual UE, a single UE ID (i.e. SUPI) will be included. When Target of Analytics Reporting is a UE group ID, an internal group ID will be included. When Target of Analytics Reporting is a UE group ID or "Any UE" and a filter for Top-Heavy UEs, fixed, camper or traveller is included, the NWDAF will include the list of UEs matching the filter. This information element is not present when Target of Analytic Reporting is "Any UE" and no filter for Top-Heavy UEs, fixed, camper or traveller is included. The NWDAF will provide the dispersion analytics result of one or a list of time slots to the service consumer(s) for the UE, group of UEs or list of UEs.
NOTE 2: UE is ranked high (i.e. 1), medium (2) and low (3) when its transactions are dispersed, during the period of observation at the location, is higher than N1% or at the range of N1% to N2% or less than N2%, respectively. The percentage values of N1 and N2 are subject to operator's configuration.
NOTE 3: When possible and applicable to the access type, UE location is provided according to the preferred granularity of location information and Spatial granularity size.
NOTE 4: This information element is an analytics subset that can be used in "list of analytics subsets that are requested" and "preferred level of accuracy per analytics subset".
NOTE 5: This parameter is only provided for Target of Analytics Reporting set to single UE.
NOTE 6: This parameter is not provided for Target of Analytics Reporting set to "Any UE".
The transactions dispersion analytics results provided by the NWDAF can be UE or group of UEs or "any UE" transactions dispersion statistics at a given slice as defined in table 6.10.3.2-3 and/or transactions dispersion predictions as defined in table 6.10.1.4.2-4. If the analytics covers multiple UEs, the Transactions dispersed, Transactions ranking and Transactions percentile ranking parameters are calculated as the aggregated (i.e. summed up) number of transactions. When the Target of Analytics Reporting is set as "any UE" the transaction dispersion analytics results provided by the NWDAF can be for all UEs transaction dispersion statistics at a given slice and/or transaction dispersion predictions at a given slice.
Table 6.10.3.2-3: Transactions dispersion statistics bound by slice
Information
Description
UE group ID or UE ID or a list of UE IDs (1..SUPImax)
Identifies the UE(s), for which the statistic applies by a list of SUPIs, or a group of UEs by a list of Internal-Group-Ids (see NOTE 1).
Time slot entry (1..max)
List of time slots during the Analytics target period.
> Time slot start
Time slot start within the Analytics target period.
> Duration
Duration of the time slot. If a Temporal granularity size was provided in the request or subscription, the Duration is greater than or equal to the Temporal granularity size.
> Slice (1..max)
Observed slice statistics.
>> S-NSSAI
Slice where the UE or group of UEs or list of UEs dispersed its transactions.
>> Transactions dispersed (NOTE 3)
Transactions amount dispersed at this location.
>> Transactions mobility classification (NOTE 3)
Transaction mobility classification of the UE at the slice: fixed, camper, traveller (see NOTE 4).
>> Transactions ranking (NOTE 3) (NOTE 5)
Ranking of transactions amount at this slice. See NOTE 2.
>> Transactions percentile ranking (NOTE 3) (NOTE 5)
Percentile ranking of the UE or UE group in the Cumulative Distribution Function of transactions for the population of all UEs served by the slice.
>> Ratio
Percentage of UEs in the group (in the case of UE group).
NOTE 1: When Target of Analytics Reporting is an individual UE, a single UE ID (i.e. SUPI) will be included. When Target of Analytics Reporting is a UE group ID, an internal group ID will be included. When Target of Analytics Reporting is a UE group ID or "Any UE" and a filter for Top-Heavy UEs, fixed, camper or traveller is included, the NWDAF will include the list of UEs matching the filter. This information element is not present when Target of Analytic Reporting is "Any UE" and no filter for Top-Heavy UEs, fixed, camper or traveller is included. The NWDAF will provide the dispersion analytics result of one or a list of time slots to the service consumer(s) for the UE, the group of UEs or the list of UEs.
NOTE 2: UE is ranked high (i.e. 1), medium (2) and low (3) when its transactions are dispersed, during the period of observation at the location, is higher than N1% or at the range of N1% to N2% or less than N2%, respectively. The percentage values of N1 and N2 are subject to operator's configuration.
NOTE 3: This information element is an analytics subset that can be used in "list of analytics subsets that are requested" and "preferred level of accuracy per analytics subset".
NOTE 4: This parameter is only provided for Target of Analytics Reporting set to single UE.
NOTE 5: This parameter is not provided for Target of Analytics Reporting set to "Any UE".
Table 6.10.3.2-4: Transactions dispersion prediction bound by slice
Information
Description
UE group ID or UE ID or list of UE IDs (1..SUPImax)
Identifies the UEs, , or a list of UEs for which the prediction applies by a list of SUPIs, or a group of UEs by a list of Internal-Group-Ids (see NOTE 1).
Time slot entry (1..max)
List of predicted time slots.
> Time slot start
Time slot start within the Analytics target period.
> Duration
Duration of the time slot. If a Temporal granularity size was provided in the request or subscription, the Duration is greater than or equal to the Temporal granularity size.
> Slice (1..max)
Predicted slice during the Analytics target period.
>> S-NSSAI
Slice where the UE or group of UEs or list of UEs is predicted to disperse its transactions.
>> Transactions dispersion (NOTE 3)
Transaction volume to be dispersed at this slice.
>>> Confidence
Confidence of this prediction (i.e. transactions to be dispersed at this slice).
>> Transactions mobility classification (NOTE 3)
Transaction mobility classification of the UE at this slice: fixed, camper, traveller (see NOTE 4).
>>> Confidence
Confidence of this prediction (i.e. mobility classification at this slice).
>> Transactions ranking (NOTE 3) (NOTE 5)
Ranking of transactions amount at this slice. See NOTE 2.
>> Transactions percentile ranking (NOTE 3) (NOTE 5)
Percentile ranking of the UE or UE group in the Cumulative Distribution Function of transactions for the population of all UEs served by the slice.
>>> Confidence
Confidence of this prediction (i.e. percentile ranking at this slice).
>> Ratio
Percentage of UEs in the group (in the case of UE group).
NOTE 1: When Target of Analytics Reporting is an individual UE, a single UE ID (i.e. SUPI) will be included. When Target of Analytics Reporting is a UE group ID an internal group ID will be included. When Target of Analytics Reporting is a UE group ID or "Any UE" and a filter for Top-Heavy UEs, fixed, camper or traveller is included, the NWDAF will include the list of UEs matching the filter. This information element is not present when Target of Analytic Reporting is "Any UE" and no filter for Top-Heavy UEs, fixed, camper or traveller is included. The NWDAF will provide the dispersion analytics result of one or a list of time slots to the service consumer(s) for the UE, group of UEs or list of UEs.
NOTE 2: UE is ranked high (i.e. 1), medium (2) and low (3) when its transactions are dispersed, during the period of observation at the location, is higher than N1% or at the range of N1% to N2% or less than N2%, respectively. The percentage values of N1 and N2 are subject to operator's configuration.
NOTE 3: This information element is an analytics subset that can be used in "list of analytics subsets that are requested" and "preferred level of accuracy per analytics subset".
NOTE 4: This parameter is only provided for Target of Analytics Reporting set to single UE.
NOTE 5: This parameter is not provided for Target of Analytics Reporting set to "Any UE".
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.10.4 Dispersion Analytic Procedure
|
The NWDAF can provide Dispersion analytics, in the form of statistics or predictions, to an NF or AF.
Figure 6.10.4-1: UE Dispersion Analytics provided to an NF or AF
1. The NF sends a request or subscription to the NWDAF for dispersion analytics on a specific UE, any UE, or a group of UEs, using either the Nnwdaf_AnalyticsInfo or Nnwdaf_AnalyticsSubscription service. The NF can request statistics or predictions or both. The Analytics ID is set to "UE Dispersion Analytics", the Dispersion Analytic (DA) type is set to "Data Volume Dispersion Analytics" (DVDA) or "Transactions Dispersion Analytics" (TDA) and Analytic Filter Information = (Area of Interest, slice, target period, optional UE class: Top-Heavy, Fixed, or Camper UEs). The NF or AF provides the Target of Analytics Reporting as defined in clause 6.10.2.
2. If the request is authorized and in order to provide the requested analytics, the NWDAF may subscribe to events with all the serving AMFs, SMFs of the requested UE(s) for notification of location changes or a slice change (a slice change can be an additional slice or a deletion), or to obtain UE location trends, UE access behaviour trends and UE session behaviour trends. This step may be skipped when, e.g. the NWDAF already has the requested analytics available.
The NWDAF subscribes to application service data from AF(s) by invoking Naf_EventExposure_Subscribe service or Nnef_EventExposure_Subscribe (via NEF).
The NWDAF can collect data volume information from the UPF, as listed in tables 6.10.2-5 and 6.10.2-6 and clause 6.2.2.1. How the data from UPF is retrieved (subscribed to on UPF and notified then by UPF) is defined in clause 5.8.2.17 of TS 23.501 [2] and in clause 4.15.4 of TS 23.502 [3].
NOTE: The NWDAF determines the AMF serving the UE, any UE, or the group of UEs, identified by an Internal-Group-Id, as described in clause 6.2.2.1.
3. The NWDAF derives requested analytics.
4. The NWDAF provides requested or subscribed UE dispersion analytics to the NF, using either the Nnwdaf_AnalyticsInfo_Request Response or Nnwdaf_AnalyticsSubscription_Notify, depending on the service used in step 1. The details for UE dispersion analytics provided by NWDAF are described in clause 6.10.3. The provided analytics enables the consumer to predict changing network conditions such as data volume change at a location or a slice, excessive signalling conditions at a location or a slice, etc.
5-6. If at step 1, the NF has subscribed to receive notifications for UE dispersion analytics, after receiving event notification from the AMFs (e.g. location change) or SMFs (e.g. slice change add/delete) subscribed by NWDAF in step 2, the NWDAF may generate new dispersion analytics.
7. The NWDAF provides the newly generated dispersion analytics to the NF. The details for UE dispersion analytics provided by NWDAF are described in clause 6.10.3.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.11 WLAN performance analytics
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.11.1 General
|
The NWDAF provides WLAN performance analytics to a service consumer NF. The analytics results are generated based on the data from other 5GC NFs and OAM. The analytics results, provided in the form of statistics or predictions, contain quality and performance of WLAN connection of UE according to UE location and SSID. The consumer can request either one-time or continuous reporting.
The service consumer may be an NF (e.g. PCF, NEF or AF).
If a service consumer is PCF, the WLAN performance analytics can be used to update WLANSP as defined in TS 23.503 [4].
If the service consumer is NEF or AF, the WLAN performance analytics per UE granularity can be used to select candidate members for an application layer operation.
The consumer of these analytics may indicate in the request or subscription:
- Analytics ID = "WLAN performance";
- Target of Analytics Reporting as defined in clause 6.1.3;
- Analytics Filter Information:
- Area of Interest (list of TA or Cells);
- SSID(s);
- BSSID(s); and
- optional list of analytics subsets that are requested (see clause 6.11.3);
- An Analytics target period indicates the time period over which the statistics or prediction are requested, either in the past or in the future;
- Optionally, Temporal granularity size;
- Optional maximum number of objects;
- Preferred level of accuracy of the analytics;
- Preferred level of accuracy per analytics subset (see clause 6.11.3);
- Preferred order of results for the list of WLAN performance information:
- ordering criterion: "time slot start", "number of UEs", "RSSI", "RTT" or "Traffic information"; and
- order: ascending or descending; and
- In a subscription, the Notification Correlation Id and the Notification Target Address are included.
If the Target of Analytics Reporting is any UE, then the Analytics Filter should at least include Area of Interest or SSID(s) or BSSID(s).
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.11.2 Input Data
|
For the purpose of generating WLAN performance analytics results, the NWDAF collects the data as listed in Table 6.11.2-1.
Table 6.11.2-1: Data collected by NWDAF for WLAN performance analytics
Information
Source
Description
WLAN measurement results
OAM
The WLAN measurement results per wireless network served by the WLAN AP.
> SSID / BSSID / HESSID
SSID / BSSID / HESSID of the selected WLAN during the period of analysis.
> RSSI
Measured RSSI of the selected WLAN during the period of analysis.
> RTT
Measured RTT of the selected WLAN during the period of interest.
> UE Location
Location information tagged by UE when it reports WLAN MDT measurement (e.g. Cell ID and/or longitude/latitude if available).
Information on PDU Session for WLAN (1..max)
SMF
Information on PDU session for which Access Type is Non-3GPP and RAT Type is TRUSTED_WLAN.
> UE ID
SUPI
> SSID / BSSID
SSID / BSSID that the PDU session is related to.
> Start time of the PDU Session for WLAN
The time stamp that indicates when the existing PDU Session's access type changes to WLAN or when the new PDU Session for WLAN is established.
> End time of the PDU Session for WLAN
The time stamp that indicates when the existing WLAN based PDU Session's access type is not WLAN any more or when the PDU Session for WLAN is released.
UE communications (1..max)
UPF
List of communication time slots
> Communication start
The time stamp that PDU session(s) for WLAN starts.
> Communication stop
The time stamp that PDU session(s) for WLAN ends.
> UL data rate
UL data rate of PDU session(s) for WLAN.
> DL data rate
DL data rate of PDU session(s) for WLAN.
> Traffic volume
Traffic volume of PDU session(s) for WLAN.
NOTE 1: WLAN Data from OAM is collected via MDT and aligned with the WLAN measurement reporting list described in clause 5.1.1.3.3 of TS 37.320 [20]. It is assumed that not all UEs support MDT WLAN measurements.
NOTE 2: UE Location from OAM can be used to deduce WLAN location.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.11.3 Output Analytics
|
The NWDAF generates WLAN performance analytics. Depending on the Analytics Target Period, the output consists of statistics or predictions. The detailed information provided by the NWDAF is defined in Table 6.11.3-1 for statistics and Table 6.11.3-2 for predictions.
Table 6.11.3-1: WLAN performance statistics
Information
Description
Area of Interest
A list of TAIs or Cell Ids
List of Analytics per SSID
SSIDs of WLAN access points deployed in the Area of Interest
> Time slot entry (1..max)
List of time slots during the Analytics target period
>> Time slot start
Time slot start time within the Analytics target period
>> Duration
Duration of the time slot. If a Temporal granularity size was provided in the request or subscription, the Duration is greater than or equal to the Temporal granularity size.
>> RSSI (NOTE 1)
Measured RSSI
>> RTT (NOTE 1)
Measured RTT
>> Traffic Information (NOTE 1)
UL/DL data rate, Traffic volume
>> Number of UEs (NOTE 1)
Number of UEs observed for the SSID
List of Analytics per UE
UE ID(s) of WLAN performance analytics
> Time slot entry (1..max)
List of time slots during the Analytics target period
>> Time slot start
Time slot start time within the Analytics target period
>> Duration
Duration of the time slot
>> RSSI (NOTE 1)
Measured RSSI
>> RTT (NOTE 1)
Measured RTT
>> Traffic Information (NOTE 1)
UL/DL data rate, Traffic volume
NOTE 1: This information element is an analytics subset that can be used in "list of analytics subsets that are requested" and "preferred level of accuracy per analytics subset".
Table 6.11.3-2: WLAN performance predictions
Information
Description
Area of Interest
A list of TAIs or Cell Ids
List of Analytics per SSID
SSIDs of WLAN access points deployed in the Area of Interest
> Time slot entry (1..max)
List of time slots during the Analytics target period
>> Time slot start
Time slot start time within the Analytics target period
>> Duration
Duration of the time slot. If a Temporal granularity size was provided in the request or subscription, the Duration is greater than or equal to the Temporal granularity size.
>> RSSI (NOTE 1)
Predicted RSSI
>> RTT (NOTE 1)
Predicted RTT
>> Traffic Information (NOTE 1)
Predicted UL/DL data rate, Traffic volume
>> Number of UEs (NOTE 1)
Number of UEs predicted for the SSID
List of Analytics per UE
UE ID(s) of WLAN performance analytics
> Time slot entry (1..max)
List of time slots during the Analytics target period
>> Time slot start
Time slot start time within the Analytics target period
>> Duration
Duration of the time slot
>> RSSI (NOTE 1)
Measured RSSI
>> RTT (NOTE 1)
Measured RTT
>> Traffic Information (NOTE 1)
UL/DL data rate, Traffic volume
>> Confidence
Confidence of the prediction
NOTE 1: This information element is an analytics subset that can be used in "list of analytics subsets that are requested" and "preferred level of accuracy per analytics subset".
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.11.4 Procedures
|
Figure 6.11.4-1: Procedure for WLAN performance analytics
1. The consumer NF sends a request to the NWDAF for WLAN performance analytics using either the Nnwdaf_AnalyticsInfo or Nnwdaf_AnalyticsSubscription service. The Analytics ID is set to "WLAN performance", the Target of Analytics Reporting and the Analytics Filter Information are set according to clause 6.11.1. The consumer NF can request statistics or predictions.
The analytics can be requested with the filter information (e.g. Area of Interest or specific SSID(s)). When Area of Interest is provided, the analytics results include WLAN performance information of all SSID(s) located in the Area of Interest. When specific SSID(s) is provided, the analytics results include WLAN performance information of a specific UE or all UE(s) connected to the corresponding SSID(s).
2-3. The NWDAF subscribes to information related to PDU Session for WLAN (i.e. Access Type is Non-3GPP and RAT Type is TRUSTED_WLAN) from SMF.
4. The NWDAF collects WLAN measurement data for the period of analysis from the OAM, following the procedure captured in clause 6.2.3.2.
NOTE: The NWDAF collects the data from the UPF as listed in Table 6.11.2.1. How the NWDAF collects the data is defined in clause 5.8.2.17 of TS 23.501 [2] and in clause 4.15.4 of TS 23.502 [3].
5. The NWDAF derives requested analytics with the collected data. Analytics output parameters are listed in clause 6.11.3.
6. The NWDAF provides the requested analytics to the NF, using either the Nnwdaf_AnalyticsInfo or Nnwdaf_AnalyticsSubscription service, depending on the service used at step 1.
7. If the NF subscribed the analytics at step 1, the NWDAF provides a new analytics when it generated the new output.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.12 Session Management Congestion Control Experience Analytics
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.12.1 General
|
According to the Session Management Congestion Control (SMCC) mechanisms, i.e. DNN based congestion control defined in clause 5.19.7.3 of TS 23.501 [2] and S-NSSAI based congestion control defined in clause 5.19.7.4 of TS 23.501 [2], the SMF that is applying or has applied the SMCC mechanism does not store any historical information related to which UEs is/was subject to backoff timer settings. Therefore, fairness to apply the SMCC cannot be considered nor guaranteed. For example, among UEs that use a PDU Session associated with S-NSSAI#1, some of them may have experienced the S-NSSAI based high level of congestion control (e.g. receiving NAS SM reject messages with a long backoff timer) while some of the UEs may have experienced the S-NSSAI based low level congestion control (e.g. receiving NAS SM reject messages with a short backoff timer), within a specific period. The backoff timer provided to each UE can vary, e.g. up to 70 hours.
The SMF service consumer may request the NWDAF to provide Session Management Congestion Control Experience (SMCCE) statistical analytics for a specific DNN and/or S-NSSAI. The SMF uses potential congestion condition as a trigger to request the SMCCE analytics from the NWDAF.
The request by the SMF includes mainly the following parameters:
- Analytics ID = "Session Management Congestion Control Experience".
- Target of Analytics Reporting: one or more SUPI(s).
NOTE 1: The UE(s) contained in the Target of Analytics Reporting. These are UE(s) that have the PDU Session for the DNN and/or S-NSSAI indicated by Analytics Filter Information.
- Analytics Filter Information:
- DNN and/or S-NSSAI; and
- optional list of analytics subsets that are requested (see clause 6.12.3);
- Analytics target period: the time window for which the statistics are requested.
NOTE 2: Predictions are not provided as output for the Session Management Congestion Control Experience analytics.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.12.2 Input Data
|
For the purpose of SMCCE analytics, the NWDAF collects the data as listed in Table 6.12.2-1.
Table 6.12.2-1: Data collected by NWDAF for SMCCE analytics
Information
Source
Description
UE ID
SMF
SUPI.
SMCC experience for PDU Session
SMF
Data related to SMCC experience per PDU Session.
> DNN
SMF
DNN for the PDU Session that SMF collects Data related to SMCCE.
> S-NSSAI
SMF
S-NSSAI for the PDU Session that SMF collects Data related to SMCCE.
> Start time of data collection
SMF
Start time of data collection.
> End time of data collection
SMF
End time of data collection.
> SM NAS request from UE (1..max)
SMF
Information on the SM NAS messages that SMF receives from UE for PDU Session during the collection period.
>> Type of SM NAS request
SMF
The type of SM NAS message transmitted by UE (e.g. PDU Session Establishment Request, PDU Session Modification Request, etc.).
>> Timestamp
SMF
A time stamp when SMF receives SM NAS message from UE.
> SM NAS message from network with backoff timer (1..max)
SMF
Information on SMCC applied to UE for PDU Session.
>> Type of SM NAS message from network
SMF
The type of SM NAS message with backoff timer provided to UE (e.g. PDU Session Establishment Reject, PDU Session Modification Reject, PDU Session Release Command, etc.).
>> Timestamp
SMF
A time stamp when SMF sends SM NAS message to UE.
>> Provided backoff timer
SMF
A value of backoff timer provided to UE.
>> Type of applied SMCC
SMF
The type of applied SMCC, i.e. DNN based congestion control or S-NSSAI based congestion control.
As described in Table 6.12.2-1, the NWDAF subscribes to the network data from SMF(s) by invoking Nsmf_EventExposure_Subscribe service (Event ID = Session Management Congestion Control Experience for PDU Session, Target of Event Reporting = one or more SUPI(s), Event Filter information = DNN and/or S-NSSAI and target period).
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.12.3 Output Analytics
|
The NWDAF outputs the SMCCE statistical analytics. The detailed statistical information provided by the NWDAF is defined in Table 6.12.3-1.
Table 6.12.3-1: SMCCE statistics
Information
Description
List of SMCCE Analytics (1..max)
> DNN
DNN that SMCC is applied.
> S-NSSAI
S-NSSAI that SMCC is applied.
> List of UEs classified based on experience level of SMCC
One, or more than one, of the following lists (SUPI is used to identify a UE).
>> List of high-experienced UEs (NOTE 2)
A list of UEs whose experience level of SMCC for specific DNN and/or S-NSSAI is high.
>> List of medium-experienced UEs (NOTE 2)
A list of UEs whose experience level of SMCC for specific DNN and/or S-NSSAI is medium.
>> List of low-experienced UEs (NOTE 2)
A list of UEs whose experience level of SMCC for specific DNN and/or S-NSSAI is low.
NOTE 1: The high/medium/low-experience thresholds values are operator defined.
NOTE 2: This information element is an analytics subset that can be used in "list of analytics subsets that are requested".
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.12.4 Procedures
|
Figure 6.12.4-1 shows the procedure for Session Management Congestion Control Experience Analytics.
Figure 6.12.4-1: Procedure for Session Management Congestion Control Experience Analytics
1. Consumer SMF requests or subscribes to analytics information for "Session Management Congestion Control Experience" from the NWDAF using either Nnwdaf_AnalyticsInfo or Nnwdaf_AnalyticsSubscription service when the SMF wants to take the analytics information into account for the Session Management Congestion Control to be applied.
The parameters included in the request are described in clause 6.12.1.
NOTE: To account for SMCCE analytics information, the SMF needs to request the analytics information from the NWDAF before applying Session Management Congestion Control due to potential congestion conditions formation.
2. If has not already subscribed, the NWDAF sends subscription requests to all the SMFs serving the DNN and/or S-NSSAI as indicated by Analytics Filter Information to collect data related to SMCCE. The SMF that made the request in step 1 can be also one of the data providers.
3. The SMF(s) provide the collected data to the NWDAF.
4. The NWDAF derives the requested analytics.
5. The NWDAF provides the analytics for Session Management Congestion Control Experience to the consumer SMF, using either Nnwdaf_AnalyticsInfo_Request Response or Nnwdaf_AnalyticsSubscription_Notify.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.13 Redundant Transmission Experience related analytics
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.13.1 General
|
This clause describes the Redundant Transmission Experience related analytics. These analytics may be used as follows:
- by the SMF to determine whether redundant transmission on N3/N9 interfaces (see clause 5.33.2.2 of TS 23.501 [2]) shall be performed, or (if it had been activated) shall be stopped;
- by the PCF for the calculation of the Route Selection Components in a URSP Rule for redundant PDU Sessions as described in clause 5.33.2.1 of TS 23.501 [2].
The service consumer may be a NF (e.g. SMF, PCF).
The consumer of these analytics may indicate in the request:
- Analytics ID = "Redundant Transmission Experience".
- Target of Analytics Reporting as defined in clause 6.1.3.
- Analytics Filter Information optionally containing:
- Area of Interest;
- S-NSSAI;
- DNN;
- optional list of analytics subsets that are requested (i.e. UL/DL packet drop rate GTP-U, UL/DL packet delay GTP-U, see clause 6.13.3).
- An Analytics target period indicates the time period over which the statistics or predictions are requested.
- Optionally, Temporal granularity size;
- Preferred level of accuracy of the analytics;
- Preferred order of results for the list of Redundant Transmission Experience:
- ordering criterion: "time slot start"; and
- order: ascending or descending;
- In a subscription, the Notification Correlation Id and the Notification Target Address are included.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.13.2 Input Data
|
The NWDAF supporting data analytics on Redundant Transmission Experience shall be able to collect UE mobility information from OAM, MDAS/MDAF, 5GC and AFs and service data from AF, as described in clause 6.7.2.2. In addition, NWDAF shall be able to collect the information for PDU session which is established with redundant transmission from the SMF. UE mobility information is specified in Table 6.7.2.2-1 and service data from AF related to UE mobility in Table 6.7.2.2-2. In addition, the NWDAF shall be able to collect performance measurements on user data congestion as specified in Table 6.8.2-1 for user data congestion analytics.
Additionally, the NWDAF collects the following input (see Table 6.13.2-1 and Table 6.13.2-2) according to existing measurements defined in clause 5.33.3 QoS Monitoring to Assist URLLC Service of TS 23.501 [2]. The NWDAF also collects the input from MDAS/MDAF of the end to end latency analysis in Table 6.13.2-3, as defined in clause 8.4.2.4.3 of TS 28.104 [45].
Table 6.13.2-1: Packet drop and/or packet delay measurement per QFI or GTP level
Information
Source
Description
UL/DL packet drop rate GTP-U
OAM (see NOTE 2)
UL/DL packet drop rate measurement on GTP path on N3.
UL/DL packet delay GTP
OAM (see NOTE 2)
UL/DL packet delay measurement round trip on GTP path on N3.
E2E UL/DL packet delay
UPF (see NOTE 3)
End-to-End (between UE and UPF) packet delay measurement between the UE and the UPF.
UL/DL packet drop/loss rate of RAN part
OAM (see NOTE 2)
UL/DL packet drop/loss rate measurement of RAN part.
NOTE 1: The information in this table is provided both as the base to compare with the redundant transmission performance as well as when redundant transmission is enabled.
NOTE 2: Refer to clause 5.1 of TS 28.552 [8] for the performance measurement in NG-RAN and clause 5.4 of TS 28.552 [8] for the performance measurement in UPF. In addition, Annex A of TS 28.552 [8] describes various performance measurements.
NOTE 3: Refer to clause 5.33.3 of TS 23.501 [2] for the packet delay measurement in the UPF.
Table 6.13.2-2: The information related to PDU Session established
Information
Source
Description
DNN
SMF
Data Network Name associated for URLLC service.
UP with redundant transmission
SMF
Redundant transmission is setup or terminated.
Table 6.13.2-3: Data collection from MDAS/MDAF of end-to-end latency analysis
Information
Source
Description
E2ELatencyIssueType
MDAF
Indication the type of the E2E latency issue.
The allowed value is one of the enumerated values: RAN latency issue, CN latency issue.
AffectedObjects
MDAF
The managed object instances of subnetwork, managed elements or network slices where the latency issue happens.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.13.3 Output Analytics
|
The NWDAF supporting data analytics on Redundant Transmission Experience shall be able to provide Redundant Transmission Experience analytics as defined in Table 6.13.3-1 and Table 6.13.3-2.
Table 6.13.3-1: Redundant Transmission Experience statistics
Information
Description
UE group ID or UE ID, any UE
Identifies the UE(s) for which the statistic applies by a list of SUPIs, or a group of UEs by a list of Internal-Group-Ids.
DNN
Data Network Name associated for URLLC service.
Spatial validity
Area where the Redundant Transmission Experience statistics applies.
If Area of Interest information was provided in the request or subscription, spatial validity should be the requested Area of Interest.
Time slot entry (1..max)
List of time slots during the Analytics target period.
> Time slot start
Time slot start within the Analytics target period.
> Duration
Duration of the time slot. If a Temporal granularity size was provided in the request or subscription, the Duration is greater than or equal to the Temporal granularity size.
> Observed Redundant Transmission Experience
Observed Redundant Transmission Experience related information during the Analytics target period.
>> UL/DL packet drop rate GTP-U (NOTE 2)
Observed UL/DL packet drop rate on GTP-U path on N3 (average, variance).
>> UL/DL packet delay GTP-U (NOTE 2)
Observed UL/DL packet delay round trip on GTP-U path on N3 (average, variance).
>> E2E UL/DL packet delay (NOTE 2)
Observed End-to-End (between UE and UPF) UL/DL packet delay (average, variance).
>> E2E UL/DL packet loss rate (NOTE 2) (NOTE 3)
Observed End-to-End (between UE and UPF) UL/DL packet loss (average, variance).
> Redundant Transmission Status
Redundant Transmission Status, i.e. redundant transmission was activated or not activated for the time slot entry.
> Ratio
Percentage on which UE, any UE, or UE group experience the packet drop rate and packet delay.
NOTE 1: The Observed Redundant Transmission Experience can be further derived by SMF from the observed UL/DL packet drop rate GTP-U and UL/DL packet delay GTP-U.
NOTE 2: This information element is an analytics subset that can be used in "list of analytics subsets that are requested" and only applicable when Target of Analytics Reporting is for a single UE.
NOTE 3: The NWDAF outputs the analytics on E2E UL/DL packet loss rate based on the input UL/DL packet drop rate on N3 and UL/DL packet drop/loss rate of RAN part.
Table 6.13.3-2: Redundant Transmission Experience predictions
Information
Description
UE group ID or UE ID, any UE
Identifies the UE(s) for which the prediction applies by a list of SUPIs, or a group of UEs by a list of Internal-Group-Ids.
DNN
Data Network Name associated for URLLC service.
Spatial validity
Area where the estimated Redundant Transmission Experience predictions applies.
If Area of Interest information was provided in the request or subscription, spatial validity should be the requested Area of Interest.
Time slot entry (1..max)
List of predicted time slots.
>Time slot start
Time slot start time within the Analytics target period.
> Duration
Duration of the time slot.
> Predicted Redundant Transmission Experience
Predicted Redundant Transmission Experience related information during the Analytics target period.
>> UL/DL packet drop rate GTP-U (NOTE 2)
Predicted UL/DL packet drop rate on GTP-U path on N3 (average, variance).
>> UL/DL packet delay GTP-U (NOTE 2)
Predicted UL/DL packet delay round trip on GTP-U path on N3 (average, variance).
>> E2E UL/DL packet delay
Predicted End-to-End (between UE and UPF) UL/DL packet delay (average, variance).
>> E2E UL/DL packet loss rate (NOTE 4)
Predicted End-to-End (between UE and UPF) UL/DL packet loss rate (average, variance).
> Redundant Transmission Status (NOTE 3)
Redundant Transmission Status, i.e., redundant transmission is activated or not activated for the time slot entry.
> Ratio
Percentage on which the UE, any UE, or UE group may efficiently use the PDU session with redundant transmission.
> Confidence
Confidence of this prediction.
NOTE 1: The Predicted Redundant Transmission Experience can be further derived by the SMF from the predicted UL/DL packet drop rate GTP-U and UL/DL packet delay GTP-U and based on which the SMF can decide to start redundant transmission or not.
NOTE 2: This information element is an analytics subset that can be used in "list of analytics subsets that are requested" and only applicable when Target of Analytics Reporting is for a single UE.
NOTE 3: The list of predicted time slots and predicted redundant transmission experience is provided to the consumer when both the redundant transmission status is activated and not activated.
NOTE 4: The NWDAF outputs the prediction on E2E UL/DL packet loss rate based on the input UL/DL packet drop rate on N3 and UL/DL packet drop/loss rate of RAN part.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.13.4 Procedures
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.13.4.1 Analytics Procedure
|
Figure 6.13.4.1-1 shows the analytics procedure. The NWDAF can provide analytics, in the form of statistics or predictions or both.
Figure 6.13.4.1-1: Redundant Transmission Experience analytics provided to an NF
1. The analytics consumer sends a request to the NWDAF for analytics on a Target for Analytics Reporting as defined in clause 6.13.2, using either the Nnwdaf_AnalyticsInfo or Nnwdaf_AnalyticsSubscription service. The NF can request statistics or predictions or both. The type of analytics is set to Redundant Transmission Experience. Analytics Filter Information optionally contains DNN, S-NSSAI, Area of Interest, etc.
2. If the request is authorized and in order to provide the requested analytics, the NWDAF may subscribe to events with all the serving AMFs for notification of location changes and may subscribe to events with SMFs serving PDU Session on URLLC service for notification of redundant transmission related information.
The NWDAF may subscribe the service data from AF(s) by invoking Naf_EventExposure_Subscribe service or Nnef_EventExposure_Subscribe (if via NEF).
The NWDAF collects UE mobility information and/or packet measurement information from OAM, following the procedure captured in clause 6.2.3.2. The NWDAF collects redundant transmission status from SMF.
NOTE: The NWDAF determines the AMF serving the UE, any UE, or the group of UEs, identified by an Internal-Group-id, as described in clause 6.2.2.1.
This step may be skipped when e.g. the NWDAF already has the requested analytics available.
3. The NWDAF derives requested analytics.
4. The NWDAF provide requested Redundant Transmission Experience analytics to the NF, using either the Nnwdaf_AnalyticsInfo_Request response or Nnwdaf_AnalyticsSubscription_Notify, depending on the service used in step 1.
5-7. If at step 1, the NF has subscribed to receive notifications for Redundant Transmission Experience analytics, after receiving event notification from the AMFs, SMF, AFs and OAM subscribed by NWDAF in step 2, the NWDAF may generate new analytics and provide them to the NF.
If a service consumer is SMF, the Redundant Transmission Experience analytics can be used to make decision if that redundant transmission shall be performed or (if activated) shall be stopped regarding the PDU session for URLLC service.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.14 DN Performance Analytics
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
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/maximum traffic rate, average/maximum packet delay, average packet loss rate) 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, PCF) or an AF.
The consumer of these analytics shall indicate in the request or subscription:
- Analytics ID = "DN Performance";
- Target of Analytics Reporting as defined in clause 6.1.3;
- Analytics Filter Information as defined in table 6.14.1-1 and optionally a list of analytics subsets that are requested (see clause 6.14.3); and
- optionally, a preferred level of accuracy of the analytics;
- optionally, preferred level of accuracy 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;
- An Analytics target period indicates the time period over which the statistics or predictions are requested; and
- Optionally, Spatial granularity size and Temporal granularity size.
Table 6.14.1-1: Analytics Filter Information related to DN Performance Analytics
Information
Description
Application ID (0..max)
The identification of the application(s) for which the analytics information is subscribed or requested.
S-NSSAI
Identifies 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 Interest
Identifies the Area (i.e. set of TAIs), as defined in TS 23.501 [2] for which the analytics information is subscribed or requested.
Anchor UPF info
Identifies the UPF where a UE has an associated PDU session.
DNN
DNN to access the application.
DNAI
The UPF ID/address/FQDN information identifier of a user plane access to one or more DN(s) where applications are deployed as defined in TS 23.501 [2].
Application Server Addresses
List of IP addresses/FQDNs of the Application Servers 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 subsets
List of analytics subsets that are requested among those specified in clause 6.14.3.
NOTE: All parameters are optional.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.14.2 Input Data
|
The data collected from the AF are defined in table 6.14.2-1
Table 6.14.2-1: Performance Data from AF
Information
Source
Description
UE identifier
AF
IP address of the UE at the time the measurements was made.
UE location
AF
The location of the UE when the performance measurement was made.
Application ID
AF
To identify the service and support analytics per type of service (the desired level of service).
IP filter information
AF
Identify a service flow of the UE for the application.
Locations of Application
AF/NEF
Locations 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 address
AF/NEF
The IP address/FQDN of the Application Server that the UE had a communication session when the measurement was made.
UL/DL Performance Data
AF
The performance associated with the communication session of the UE with an Application Server that includes: UL/DL Average/Maximum Packet Delay, UL/DL Average/Maximum Loss Rate and UL/DL Average/Minimum/Maximum Throughput.
Timestamp
AF
A 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.
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 [3].
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.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.14.3 Output Analytics
|
The DN performance analytics is shown in table 6.14.3-1 and table 6.14.3-2.
Table 6.14.3-1: DN service performance statistics
Information
Description
Application ID
Identifies the application for which analytics information is provided.
S-NSSAI
Identifies 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 Address
Identifies the Application Server Instance (IP address/FQDN of the Application Server).
> Serving anchor UPF info
The UPF ID/address/FQDN information for the involved anchor UPF. See NOTE 1.
> DNAI
Identifier of a user plane access to one or more DN(s) where applications are deployed as defined in TS 23.501 [2].
> Performance (NOTE 4)
Performance indicators.
>> Aggregated Traffic rate (NOTE 2, NOTE 5)
Aggregated traffic rate observed for the UE group or all UEs (i.e. any UE) communicating with the application.
>> Average Traffic rate (NOTE 2)
UE granularity level Average traffic rate observed for the UE group or all UEs communicating with the application, or Average traffic rate observed for the specific UE in the statistics period.
>> Maximum Traffic rate (NOTE 2)
UE granularity level Maximum traffic rate observed for the UE group or all UEs communicating with the application, or Maximum Traffic rate observed for the specific UE in the statistics period.
>> Minimum Traffic rate (NOTE 3)
UE granularity level Minimum traffic rate observed for the UE group or all UEs communicating with the application, or Minimum Traffic rate observed for the specific UE in the statistics period.
>> Variance Traffic rate (NOTE 2, NOTE 5)
UE granularity level Variance of the traffic rate observed for the UE group or all the UEs communicating with the application, or Variance Traffic rate observed for the specific UE in the statistics period.
>> UE ID or list of UE IDs for traffic rate performance (1..SUPImax) (NOTE 2, NOTE 5)
Identifies a UE or a list of UEs whose observed traffic rate is higher or lower than the Reporting Threshold.
>> Average Packet Delay (NOTE 2)
Average packet delay observed for the specific UE, the UE group or all UEs communicating with the application.
>> Maximum Packet Delay (NOTE 2)
Maximum packet delay observed for the specific UE, the UE group or all UEs communicating with the application.
>> Variance Packet Delay (NOTE 2, NOTE 5)
Variance of packet delay observed for the specific UE, the UE group or all UEs communicating with the application.
>> UE ID or list of UE IDs for packet delay performance (1..SUPImax) (NOTE 2, NOTE 5)
Identifies a UE or a list of UEs whose observed packet delay is higher or lower than the Reporting Threshold.
>> Average Packet Loss Rate (NOTE 2)
Average packet loss observed for the specific UE, the UE group or all UEs communicating with the application.
>> Maximum Packet Loss Rate (NOTE 2)
Maximum packet loss observed for the specific UE, the UE group or all UEs communicating with the application.
>> Variance Packet Loss Rate (NOTE 2, NOTE 5)
Variance of packet loss rate observed for the specific UE, the UE group or all UEs communicating with the application.
>> UE ID or list of UE IDs for packet loss performance (1..SUPImax) (NOTE 2, NOTE 5)
Identifies a UE or a list of UEs whose observed packet loss rate is higher than the Reporting Threshold.
>> Number of UEs (NOTE 2)
The observed number of UEs for the UE group or all UEs (i.e. any UE) communicating with the application in the DNAI.
> Spatial Validity Condition
Area (i.e. list of TAIs) where the DN performance analytics applies. 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.
> Temporal Validity Condition
Validity period for the DN performance analytics. If a Temporal granularity size was provided in the request or subscription, the duration of this period is greater than or equal to the Temporal granularity size.
NOTE 1: The item "Serving anchor UPF info" shall not be included if the consumer NF is an AF.
NOTE 2: Analytics subset that can be used in "list of analytics subsets that are requested", "Preferred level of accuracy per analytics subset" and "Reporting Thresholds".
NOTE 3: Minimum traffic rate measurements are only derived from active traffic.
NOTE 4: Performance statistics may not be applicable to short group operation cycle for the given application.
NOTE 5: Analytics subset that can be used to support aggregated UE performance monitoring and exposure for a group of UEs.
Table 6.14.3-2: DN service performance predictions
Information
Description
Application ID
Identifies the application for which analytics information is provided.
S-NSSAI
Identifies 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 performance for the application.
> Application Server Instance Address
Identifies the Application Server Instance (IP address/FQDN of the Application Server).
> Serving anchor UPF info
The UPF ID/address/FQDN information for the involved anchor UPF. See NOTE 1.
> DNAI
Identifier of a user plane access to one or more DN(s) where applications are deployed as defined in TS 23.501 [2].
> Performance
Performance indicators.
>> Aggregated Traffic rate (NOTE 2)
Aggregated traffic rate predicted for the UE group or all UEs (i.e. any UE) communicating with the application.
>> Average Traffic rate (NOTE 2)
UE granularity level Average traffic rate predicted for the UE group or all UEs communicating with the application, or Average traffic rate predicted for the specific UE in the prediction period.
>> Maximum Traffic rate (NOTE 2)
UE granularity level Maximum traffic rate predicted for the UE group or all UEs communicating with the application, or Maximum Traffic rate predicted for the specific UE in the prediction period.
>> Minimum Traffic rate (NOTE 3)
UE granularity level Minimum traffic rate predicted for the UE group or all UEs communicating with the application, or Minimum Traffic rate predicted for the specific UE in the prediction period.
>> Variance Traffic rate (NOTE 2)
UE granularity level Variance of the traffic rate predicted for the UE group or all the UEs communicating with the application, or Variance Traffic rate predicted for the specific UE in the prediction period.
>> Average Packet Delay (NOTE 2)
Average packet delay predicted for the specific UE, the UE group or all UEs communicating with the application.
>> Maximum Packet Delay (NOTE 2)
Maximum packet delay for predicted for the specific UE, the UE group or all UEs communicating with the application.
>> Variance Packet Delay (NOTE 2)
Variance of packet delay predicted for the specific UE, the UE group or all UEs communicating with the application.
>> Average Packet Loss Rate (NOTE 2)
Average packet loss predicted for the specific UE, the UE group or all UEs communicating with the application.
>> Maximum Packet Loss Rate (NOTE 2)
Maximum packet loss predicted for the specific UE, the UE group or all UEs communicating with the application.
>> Variance Packet Loss Rate (NOTE 2)
Variance of packet loss rate predicted for the specific UE, the UE group or all UEs communicating with the application.
>> Number of UEs (NOTE 2)
The predicted number of UEs for the UE group or all UEs (i.e. any UE) communicating with the application in the DNAI.
> Spatial Validity Condition
Area (i.e. list of TAIs) where the DN performance analytics applies. 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.
> Temporal Validity Condition
Validity period for the DN performance analytics. If a Temporal granularity size was provided in the request or subscription, the duration of this period is greater than or equal to the Temporal granularity size.
> Confidence
Confidence of this prediction.
NOTE 1: The item "Serving anchor UPF info" shall not be included if the consumer is an AF.
NOTE 2: Analytics subset that can be used in "list of analytics subsets that are requested", "Preferred level of accuracy per analytics subset" and "Reporting Thresholds".
NOTE 3: Minimum traffic rate measurements are only derived from active traffic.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.14.4 Procedures to request DN Performance Analytics for an Application
|
Figure 6.14.4-1: Procedure for NWDAF providing DN Performance analytics for an Application
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.
1. Analytics consumer sends an Analytics request/subscribe (Analytics ID = DN Performance Target of Analytics Reporting, Analytics Filter Information = (Application ID, S-NSSAI, DNN, Area of Interest, UPF anchor ID, DNAI, Application Server Address(es)), Analytics Reporting Information = Analytics target period) to NWDAF by invoking a Nnwdaf_AnalyticsInfo_Request or a Nnwdaf_AnalyticsSubscription_Subscribe service.
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 [3].
NOTE 1: In the case of trusted AF, NWDAF provides the Area of Interest as a list of TAIs to AF. In the case of untrusted AF, NEF translates the requested Area of Interest provided as event filter by NWDAF into geographic zone identifier(s) that act as event filter for AF.
2b. NWDAF subscribes to the network data from 5GC NF(s) defined in table 6.4.2-2 by invoking Nnf_EventExposure_Subscribe service.
2c. With the collected data, the NWDAF estimates the DN Performance for the application.
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.
NOTE 2: For simplicity, the call flow only shows a request-response model for the interaction of NWDAF and analytics consumer instead of both request-response model and subscription-notification model.
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.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.15 Void
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.16 PFD Determination Analytics
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.16.1 General
|
This clause specifies the procedure on how NWDAF can provide NWDAF-assisted PFD Determination analytics, in the form of statistics.
To assist determination of PFDs for known application identifiers, if the related Service Level Agreement does not preclude this, an NWDAF may perform data analytics on existing PFD information and user plane traffic and provide analytics results in the form of new or updated PFD determination statistics, e.g. new or updated IP 3-tuple list, to an analytics consumer in the 5GC. The NEF(PFDF) as the consumer uses the suggested PFD information of the PFD determination statistics provided by the NWDAF as defined in clause 4.18.2.2 of TS 23.502 [3] and in TS 23.503 [4].
The service consumer is a NEF(PFDF).
The consumer of these analytics shall indicate in the subscription:
- Analytics ID = " PFD Determination";
- Target of Analytics Reporting: "any UE";
- Application identifier;
- Analytics Filter Information optionally containing:
- S-NSSAI(s);
- DNN(s);
- An Analytics target period indicates the time period over which the statistics are requested;
- Analytics Reporting Parameters indicating either periodic reporting (together with the parameter periodicity) or reporting when threshold is reached (together with the parameter Reporting type (as defined in clause 4.15.1 of TS 23.502 [3]) to indicate that the report shall only occur when the information differs from the previous report);
- Optionally, the preferred level of accuracy on the PFD determination statistics;
- Optionally, maximum number of objects. This refers to the analytic output (i.e. maximum number of new or updated suggested PFD information in the PFD determination statistics);
- In a subscription, the Notification Correlation Id and the Notification Target Address are included.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.16.2 Input Data
|
The NWDAF collects information on user data traffic from the UPF for a known Application ID optionally together with a combination of certain S-NSSAI(s) and/or DNN(s) and retrieves the existing PFDs from the NEF(PFDF). The detailed input data are described in Table 6.16.2-1.
Table 6.16.2-1: Input data to detect known application from NFs
Information
Source
Description
Application ID for detection of suggested PFD information
(NOTE 1)
UPF
Identifies the application detection algorithm used for the detection of suggested PFD information.
Application Traffic Flow Information (1..max)
UPF
Per Application Traffic flow related information for the application and optionally, for a DNN, S-NSSAI combination.
> IP 5-tuple
UPF
Identifies a service flow of the UE that uses the application.
> Start time
UPF
Start time of traffic detection for the flow.
> End time
UPF
End time of traffic detection for the flow.
> UL Data volume
UPF
Measured UL data traffic volume for the flow.
> DL Data volume
UPF
Measured DL data traffic volume for the flow.
> UL Data Rate
UPF
Measured UL data rate for the flow.
> DL Data Rate
UPF
Measured DL data rate for the flow.
> URL list
UPF
List of URLs extracted from the inspected user plane packets in the flow.
> Domain Name list
UPF
List of domain names extracted from the inspected user plane packets in the flow.
PFD Information
NEF(PFDF)
PFD Information stored in the UDR (as Application Data) and retrieved by NEF (PFDF), as defined in clause 6.1.2.3.2 of TS 23.503 [4].
> Application ID
NEF(PFDF)
Identification of the application that refers to one or more application detection filters.
> PFD(s) (1..max)
NEF(PFDF)
>> PFD ID
NEF(PFDF)
>> IP 3-tuple list
NEF(PFDF)
Including protocol, server side IP address and port number.
>> URL list
NEF(PFDF)
The significant parts of the URL to be matched, e.g. host name.
>> Domain Name list
NEF(PFDF)
A Domain Name matching criteria and information about applicable protocol(s).
>> Source NF type
(NOTE 2)
NEF(PFDF)
Indicates the source NF type which generated the PFD (i.e. AF or NWDAF).
NOTE 1: In the UPF, the "Application ID for detection of suggested PFD information" can refer to a detection algorithm that has a wider scope than the detection algorithm the Application ID provided by the consumer refers to.
NOTE 2: The absence of the Source NF type indicates that this PFD was generated by the AF.
NOTE 1: Extensive reporting of all traffic flows may conflict with the requirement to avoid extra UPF load. An NWDAF may subscribe only for reporting for some UEs to limit the load.
NOTE 2: In order to enable retrieval of input data from the UPF as listed in Table 6.16.2-1, if UPF supports exposure, then SMF is expected to provide DNN and S-NSSAI to UPF at PDU Session establishment.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.16.3 Output Analytics
|
The output analytics of PFD Determination is defined in Table 6.16.3-1. The output analysis may be used to provision new or updated PFDs information for known applications. The NWDAF may assign a confidence to the PFD Determination statistics based on the analytics of input data provided by UPF and NEF(PFDF).
Table 6.16.3-1: PFD Determination statistics
Information
Description
Application ID
Identifies the application for which the PFD information applies.
List of suggested PFD information (1..max)
Suggested PFD information derived by the analytics for the application.
> PFD ID
Identifier of the PFD (i.e. new PFD ID assigned by NWDAF or existing PFD ID retrieved from UDR).
> IP 3-tuple list
Including protocol, server side IP address and port number.
> URL list
The significant parts of the URL to be matched, e.g. host name.
> Domain Name list
A Domain Name matching criteria and information about applicable protocol(s).
> Confidence
Confidence on the provided suggested PFD information for the Application ID.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.16.4 Procedures
|
Figure 6.16.4-1 shows the procedure that a consumer can use to request PFD Determination analytics.
Figure 6.16.4-1: A procedure for NWDAF-assisted PFD Determination
1. The Consumer NF (NEF(PFDF)) subscribes to the NWDAF to request PFD Determination analytics for a known application identifier. The Target of Analytics Reporting is set to Any UE.
The Analytics Filter Information may optionally include the S-NSSAI and/or DNN.
2. The NWDAF subscribes to PFD notifications for the Application ID provided in step 1 by sending Nnef_PFDManagement_Subscribe message to the NEF (PFDF) in order to be informed about the stored PFD information in use from UDR via NEF(PFDF). The NEF(PFDF) sends the PFD(s) that are currently stored for the Application ID in the Nnef_PFD_Management_Notify message. The NEF(PFDF) will send further Nnef_PFD_Management_Notify messages whenever the PFD(s) for this Application ID change.
3. The NWDAF collects information from the UPF (event "User Data Usage Measures") as listed in Table 6.16.2-1 via SMF as defined in clause 5.8.2.17 of TS 23.501 [2]. NWDAF discovers the SMF through NRF as defined in clause 4.15.4.5.3 of TS 23.502 [3]. The event "User Data Usage Measures" is defined in clause 5.2.26.2 of TS 23.502 [3], the subscription to the event includes an "Application ID for detection of suggested PFD information" which allows the NWDAF to retrieve input information to derive PFD Determination Analytics for the Application ID that is provided by the consumer.
NOTE 1: The Application ID provided by the consumer and the "Application ID for detection of suggested PFD information" provided to the UPF to retrieve input data for PFD Determination Analytics can be different ones.
4. UPF reports the data directly to NWDAF.
5. The NWDAF derives PFD Determination analytics, e.g. new or updated suggested PFD information for the existing Application ID. For providing new suggested PFD information, the NWDAF shall assign a new PFD ID that is not yet used for this Application ID. For updating PFD information, the NWDAF shall use the existing PFD ID when indicating the updated suggested PFD information. For deleting PFD information, the NWDAF shall only indicate the existing PFD ID. The NWDAF can only update or delete suggested PFD information previously generated by the NWDAF, i.e. that contains "NWDAF" as source NF type. When the consumer provides the preferred level of accuracy, the NWDAF provides PFD Determination Analytics that reaches or exceeds this level to the consumer.
6. The NWDAF notifies PFD Determination analytics (shown in table 6.16.3-1) to the consumer NF (i.e. NEF(PFDF)) with suggested PFD Information according to the reporting mode indicated by the Consumer NF (i.e. NEF(PFDF)) during the subscription in step 1.
NOTE 2: Steps 2b, 4, 5 and 6 can occur multiple times during the lifetime of the subscription of the consumer NF (i.e. NEF(PFDF)).
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.17 Location Accuracy Analytics
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.17.1 General
|
This clause specifies how an NWDAF can provide Location Accuracy Analytics which provides analytics for LCS QoS accuracy to an analytics consumer such as LMF.
With different input data to NWDAF, the Location Accuracy Analytics provides one or a combination of the following information:
- when the input data is location:
- location accuracy (i.e. Horizontal Accuracy (see clause 4.3.1 of TS 22.071 [35]) and optionally Vertical Accuracy (see clause 4.3.2 of TS 22.071 [35]) of applicable positioning method at indicated location;
- Indication on whether a UE is indoor or outdoor when a location measurement is made (optional);
- Indication on whether a UE location is measured with NLOS or LOS (optional);
- when the input data is area:
- average location accuracy (i.e. Horizontal Accuracy (see clause 4.3.1 of TS 22.071 [35]) and optionally Vertical Accuracy (see clause 4.3.2 of TS 22.071 [35]) of applicable positioning method at indicated area;
- percentage of indoor/outdoor measurement for an applicable area (optional);
- percentage of NLOS/LOS measurement for an applicable area (optional);
- requested Confidence of location accuracy prediction (optional).
The consumer of these analytics shall indicate in the request or subscription:
- Analytics ID = "Location Accuracy";
- Target of Analytics Reporting: "any UE";
- Analytics Filter Information:
- Optionally, the Positioning methods used as defined in clause 4.2b of TS 23.273 [39];
- Location information (horizontal and optional vertical); or
- Area of Interest: restricts the scope of the LCS accuracy analytics to the provided area. The AOI is TA and/or cell list as defined in TS 23.502 [3]. Depends on the NWDAF consumer, there can be more than one AOIs in one request;
- Optionally, the list of analytics subsets that are requested among those specified in clause 6.17.3;
- optionally, a preferred level of accuracy of the analytics;
- optionally, preferred level of accuracy per analytics subset (see clause 6.17.3);
- optionally, Reporting Thresholds, which apply only for subscriptions and indicate conditions on the level to be reached for respective analytics subsets (see clause 6.17.3) in order to be notified by the NWDAF;
- optionally, maximum number of objects; and
- an Analytics target period indicates the time period over which the statistics or predictions are requested.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.17.2 Input Data
|
In Input data for the analytics ID is listed in Table 6.17.2-1. A training should be done by performing a specific LCS positioning method and comparing the position result with the ground truth UE location obtained by another method.
NOTE: There are at least two conceivable options for the ground truth data used for the ML Model training of this analytics ID. One option is to use the known location of Positioning Reference Units (PRUs), another option is to use the positioning result of one positioning method (preferably Global Navigation Satellite System (GNSS) information such as GPS information). Collecting PRU related information by NWDAF is not supported in this release. There could be other options for ground truth data which can be determined in the future releases.
Table 6.17.2-1: Data Collected by NWDAF for Location Accuracy Analytics
Information
Source
Description
UE IDs
AMF
(List of) SUPI(s)
Finer granularity UE location
LCS
NOTE 1
UE location information.
>UE location
Geographical location or location in local coordinate (as defined in TS 23.032 [34])
>positioning methods
The positioning methods used by the LMF when the location measurement was made
>LCS QoS
LCS QoS accuracy as defined in clause 4.1b in TS 23.273 [39]
>Indoor/outdoor indication
Indication of indoor/outdoor when LMF can distinguish indoor/outdoor environment
>NLOS/LOS indication
Indication whether the UE measurements were based on LOS/NLOS measurements
UE location (ground truth)
AF
Timestamped UE positions
>UE location
NOTE 2,
GNSS location information
>Timestamp
NOTE 3
Time stamp for the UE location
>Accuracy
The accuracy of the GNSS location information
NOTE 1: The procedure to collect location data using LCS is described in clause 6.2.12.
NOTE 2: How the AF obtains timestamped GNSS location information of a UE ID is out of 3GPP scope. Whether to trust the UE location from AF is up to the implementation.
NOTE 3: When AF is deployed in the untrusted domain, NEF is employed to mediate the interactions between NWDAF and AF via the Naf_EventExposure_Subscribe service specified in clause 5.2.19.2 of TS 23.502 [3], as described in clause 6.2.8.2.3.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.17.3 Output Analytics
|
The Location Accuracy analytics are shown in table 6.17.3-1.
Table 6.17.3-1: Location Accuracy statistics
Information
Description
List of Accuracy sustainability Analytics (1..max)
>Applicable Area
A list of TAIs or Cell IDs or longitude and latitude level location information that the analytics applies to
>Applicable Time Period
The time period within the Analytics target period that the statistics applies to.
> Positioning Methods (1…max) (NOTE)
The positioning methods used to measure location as defined in clause 4.2b of TS 23.273 [39]
>> average accuracy of positioning method in applicable area (NOTE)
Statistics about the horizontal and optionally vertical location average accuracy of applicable positioning method at the applicable area
>> Percentage of NLOS/LOS measurements of positioning method in applicable area
Provides ratio of LOS to NLOS measurements of positioning method in the applicable area
> Percentage of UE in indoor/outdoor in applicable area (optional) (NOTE)
Provides ratio of UEs that are indoor/outdoor in the applicable area
> Applicable Location
A location (i.e. Geographical location or location in local coordinate (as defined in TS 23.032 [34])) that the analytics applies to
>Applicable Time Period
The time period within the Analytics target period that the prediction applies to.
> Positioning Methods (1…max) (NOTE)
The positioning methods used to measure location as defined in clause 4.2b of TS 23.273 [39]
>>accuracy of positioning method in applicable location (NOTE)
statistics about the horizontal and optionally vertical location accuracy of applicable positioning method at the applicable location
>>Indication whether the location is measured NLOS/LOS with the positioning method
Indicates whether this applicable location is measured with NLOS or LOS with the positioning method
> Indication whether location is indoor/outdoor (optional) (NOTE)
Indicates whether this applicable location is measured to be indoor or outdoor
NOTE: Analytics subset that can be used in "list of analytics subsets that are requested", "Preferred level of accuracy per analytics subset" and "Reporting Thresholds".
Table 6.17.3-2: Location Accuracy predictions
Information
Description
List of Accuracy sustainability Analytics (1..max)
>Applicable Area
A list of TAIs or Cell IDs or longitude and latitude level location information that the analytics applies to
>Applicable Time Period
The time period within the Analytics target period that the prediction applies to
> Positioning Methods (1…max) (NOTE)
The positioning methods used to measure location as defined in clause 4.2b of TS 23.273 [39]
>> average accuracy of positioning method in applicable area (NOTE)
Prediction about the horizontal and optionally vertical location average accuracy of applicable positioning method at the applicable area
>> Percentage of NLOS/LOS measurements of positioning method in applicable area
Provides predicted ratio of LOS to NLOS measurements of positioning method in the applicable area
> Percentage of UE in indoor/outdoor in applicable area (optional) (NOTE)
Provides predicted ratio of UEs that are indoor/outdoor in the applicable area
> Applicable Location
A location (i.e. Geographical location or location in local coordinate (as defined in TS 23.032 [34])) that the analytics applies to
>Applicable Time Period
The time period within the Analytics target period that the prediction applies to.
> Positioning Methods (1…max) (NOTE)
The positioning methods used to measure location as defined in clause 4.2b of TS 23.273 [39]
>>accuracy of positioning method in applicable location (NOTE)
Prediction about the horizontal and optionally vertical location accuracy of applicable positioning method at the applicable location
>>Indication whether the location is measured NLOS/LOS with the positioning method
Predicts whether this applicable location is measured with NLOS or LOS with the positioning method
> Indication whether location is indoor/outdoor (optional) (NOTE)
Predicts whether this applicable location is measured to be indoor or outdoor
> Confidence
Confidence of the prediction
NOTE: Analytics subset that can be used in "list of analytics subsets that are requested", "Preferred level of accuracy per analytics subset" and "Reporting Thresholds".
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.17.4 Procedures to request Location Accuracy Analytics
|
Figure 6.17.4-1: Location accuracy analytics retrieval
Pre-condition: NWDAF has a trained supervised ML Model for predicting location accuracy. In the training phase, the NWDAF consumes input data as listed in clause 6.17.2. To pre-train the ML Model, NWDAF may collect input data based on area of interest (AoI). The AoI is determined by NWDAF.
0-1. NWDAF collects UE IDs from AMF as defined in Table 6.17.2 via the AMF event exposure service with AoI as filtering criteria.
0-2. NWDAF collects the UE location information using LCS (location estimate, Position Methods Used, Indoor/Outdoor indication, NLOS/LOS indication) as described in clause 6.2.12 and Table 6.17.2 with UE ID as filtering criteria.
0-3. NWDAF collects ground truth UE location information (i.e. timestamped GNSS location information) from AF.
0-4. NWDAF prepares the analytics for statistics and/or pre-trains the ML Model for prediction.
1. The Analytics consumer, e.g. LMF, requests from NWDAF location accuracy statistics or predictions, giving as inputs the corresponding Analytics ID and UE location estimate (in the form of horizontal and/or vertical location) or corresponding area (cell ID/TAI). The analytics request to the NWDAF may be a one time or a subscription request. Other inputs such as UE positioning method, applicable period can be assistance data.
NOTE 1: It is assumed that the analytics consumer determines a location. For instance, the LMF can be triggered by LCS client request to determine a location and then use location accuracy analytics to inquire the accuracy of the determined location.
NOTE 2: Both Nnwdaf_AnalyticsSubscription or Nnwdaf_AnalyticsInfo services can be used for step 1. The Nnwdaf_AnalyticsSubscription service can be used by a service consumer to receive notifications about location accuracy, e.g. when a change is detected.
2. The NWDAF uses the trained ML Model and provides the location accuracy as output to the analytics consumer.
NOTE 3: The NWDAF can derive the accuracy based on the model without further input data.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.18 End-to-end data volume transfer time analytics
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.18.1 General
|
Clause 6.18 describes how NWDAF can provide E2E data volume transfer time analytics, in the form of statistics or predictions or both, to a service consumer. NWDAF collects E2E data volume transfer time related input data from 5GC NFs, OAM and AF. The consumer can either subscribe to analytics notifications (i.e. a Subscribe-Notify model) or request a single notification (i.e. a Request-Response model).
The E2E data volume transfer time refers to a time delay for completing the transmission of a specific data volume from UE to AF, or from AF to UE. The data volume may be the expected or observed data volume from UE to AF or from AF to UE. The NWDAF may use the data volume indicated by the consumer as a reference to collect the input data for deriving the statistics and predictions of the end-to-end data volume transfer time. If a target repetition number of data transmissions or a target time interval between data transmissions is given, the E2E data volume transfer time can be provided as an average value of the data volume transfer times within the Analytics target period. The E2E data volume transfer time analytics may be used to assist an AF or NEF with AI/ML-based services, e.g. for member UE selection of federated learning.
The E2E data volume transfer time analytics may be provided as defined in clause 6.18.3 for a single UE or a list of UEs.
More than one E2E data volume transfer time classes might be assigned by operator or AF to a list of UEs. The UEs might be classified into high-, medium- and low-transfer time classes with respect to the threshold(s) of the corresponding class.
The service consumer may be an NF (e.g. AF, or NEF).
The consumer of these analytics indicates in the request or subscription:
- Analytics ID = "E2E data volume transfer time ".
- Target of Analytics Reporting as defined in clause 6.1.3.
- Analytics Filter Information, including:
- Optionally, DNN;
- Optionally, S-NSSAI;
- Optionally, Application ID;
- Optionally, Area of Interest (AOI(s)): restricts the scope of the E2E data volume transfer time analytics to the provided area;
- Optionally, a list of analytics subsets that are requested (see clause 6.18.3);
- QoS requirements (e.g. 5QI, QoS Characteristics);
- Optionally, either a target number of repeating data transmissions or a target time interval between data transmissions within the Analytics target period;
- Data Volume UL/DL: indicates a specific data volume per transmission either from UE to AF or from AF to UE;
- A request for geographical distribution (i.e. the AoIs) of the UEs.
An Analytics target period indicates the time period over which the statistics or predictions are requested.
- In a subscription, the Notification Correlation Id and the Notification Target Address are included.
- Optionally, preferred level of accuracy of the analytics.
- Optionally, preferred level of accuracy per analytics subset (see clause 6.18.3).
- Optionally, preferred order of results for the list of E2E data volume transfer times:
- ordering criterion: "E2E data volume transfer time",
- order: ascending or descending.
- Optionally, Reporting Thresholds, which apply only for subscriptions and indicate conditions on the levels to be reached for the respective analytics subsets (see clause 6.18.3)
- Optionally, maximum number of UEs.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.18.2 Input Data
|
The NWDAF supporting analytics on E2E data volume transfer time shall be able to collect information from AF, OAM and 5GC NFs.
The information collected by the NWDAF from the OAM is defined in the Table 6.18.2-1, from relevant 5GC NFs (i.e. UPF, SMF, AMF) is defined in Table 6.18.2-2 and from AF is defined in Table 6.18.2-3.
Table 6.18.2-1: Input data from OAM related to E2E data volume transfer time
Information
Source
Description
RAN part delay for DL and UL
OAM
(See NOTE 2)
Average packet transmission delay through the RAN part to the UE per 5QI and per S-NSSAI as specified in clauses 6.3.1.2.1 and 6.3.1.7.1 of TS 28.554 [10] and per UE level per supported S-NSSAI and per QoS level in clauses 6.3.1.1.1 and 6.3.1.1.6 of TS 28.558 [50].
Timestamp
OAM
A time stamp associated with the collected information.
RAN Throughput for DL and UL
OAM
(see NOTE 1)
The per UE measurement of the throughput for DL and UL as specified in clauses 5.2.1.1 and 5.4.1.1 of TS 37.320 [20].
RAN Packet delay for DL and UL
OAM
(see NOTE 1)
The per UE measurement of the packet delay for DL and UL, including per DRB per UE packet delay as specified in clause 5.4.1.1 of TS 37.320 [20].
RAN Packet loss rate for DL and UL
OAM
(see NOTE 1, NOTE 2)
The per UE measurement of the packet loss rate for DL and UL, including per DRB per UE packet loss rate as specified in clause 5.4.1.1 of TS 37.320 [20] and packet loss rate per UE per QoS level and per supported S-NSSAI in clauses 6.3.1.2.1 and 6.3.1.3.1 of TS 28.558 [50].
Average UL/DL packet delay between PSA UPF and UE
OAM
(See NOTE 2)
The average of UL/DL packet delay between PSA UPF and UE per S-NSSAI as specified in clauses 5.4.9.1.1 and 5.4.9.2.1 of TS 28.552 [8] and per UE level per supported S-NSSAI and per QoS level in clauses 6.2.2.1.1 and 6.2.2.1.3 of TS 28.558 [50].
Average UL/DL Packet delay between PSA UPF and RAN
OAM
(See NOTE 2)
The per UE level per supported S-NSSAI and per QoS level of the average UL/DL packet delay between PSA UPF and RAN as specified in clauses 6.2.2.1.4 and 6.2.2.1.5 of TS 28.558 [50].
Average DL/UL UE throughput in gNB
OAM
(See NOTE 2)
Average DL/UL UE throughput in the gNB per QoS level (mapped 5QI) and per S-NSSAI as specified in clauses 5.1.1.3.1 and 5.1.1.3.3 of TS 28.552 [8] and per UE per supported S-NSSAI and per QoS level clauses 6.3.1.4.1 and 6.3.1.4.2 of TS 28.558 [50].
NOTE 1: Per UE measurement for a specific UE from OAM (via MDT), is as specified in clause 6.2.3.1 in TS 37.230 [20].
NOTE 2: In addition to the average KPIs, per UE level measurements if available, can be taken into account by the NWDAF.
NWDAF subscribes to the input data from OAM as defined in the Table 6.18.2-1 by using the services provided by OAM as described in clause 6.2.3.
NOTE 1: Whether the UE(s) is supporting a Slice or not can be checked by retrieving the registered AMF details from UDM or by asking AMF about what Slice is used by the UE(s) at the current registration (Alternatively, if NSACF is deployed, NSACF can provide a report on what slices are used by the UE(s)).
NOTE 23: User consent checking from UDM can apply to these analytics.
Table 6.18.2-2: Service Data from 5GC NFs for E2E data volume transfer time analytics
Information
Source
Description
Timestamp
5GC NF
A time stamp associated with the collected information.
UE location
AMF, LCS (NOTE 1)
Location of the UE(s) needs to be collected from AMF if the application needs to be started at the same time. If the AoI indicated by the AF is a finer granularity area than the Cell level, the current location of the UE(s) needs to be collected from GMLC instead.
UE ID
AMF
(list of) SUPI(s).
5QI
SMF
A reference to 5G QoS characteristics.
QoS flow Packet Delay
SMF, UPF
The observed Packet delay for UL/DL/round trip directions between UE and PSA_UPF.
RAT Type
SMF
The RAT types the UE camps on.
Access Type
SMF
The list of Access Type(s) used for the PDU Session.
NOTE 1: The procedure to collect location data using LCS is described in clause 6.2.12.
Table 6.18.2-3: Service Data from AF for E2E data volume transfer time analytics
Information
Source
Description
Timestamp
AF
Timestamp of the collected information.
Application ID
AF
Identifier of the application at the AF.
UE ID(s)
AF
Internal or External UE IDs (i.e. SUPI or GPSI, respectively).
Transmitted UL/DL data volume
AF
The volume of the transmitted UL/DL data.
UL/DL transmission time duration
AF
The time duration (start and end time) needed for sending the volume of UL/DL data.
Application Server Instance information
AF
The IP address/FQDN of the Application Server.
NOTE 3: How to derive the time delay for sending a specific data volume between UPF and AF on N6 interface is out of scope of the present specification.
For calculation of the E2E data volume transfer time, the NWDAF uses mainly the Data Volume DL/UL provided by the analytics consumer (see clause 6.18.1) and the Average DL/UL UE throughput in gNB of the NG-RAN serving the UE or in the AoI (if an AoI is provided by the analytics consumer). Per UE input parameters if available may also be taken into account by the NWDAF.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.18.3 Output Analytics
|
The NWDAF supporting E2E data volume transfer time analytics provides the analytics results to consumer NFs, e.g. AF, or NEF. The analytics results provided by the NWDAF could be E2E data volume transfer time statistics as defined in Table 6.18.3-1 or predictions as defined in table 6.18.3-2.
Table 6.18.3-1: E2E data volume transfer time statistics
Information
Description
UE ID or list of UE IDs (1..SUPImax)
Identifies the UE(s)for which the statistic applies by a list of SUPIs.
Time slot entry (1..max)
List of time slots during the Analytics target period.
> Time slot start
Time slot start within the Analytics target period.
> Duration
Duration of the time slot.
> E2E data volume transfer time information (1…max)
List of E2E data volume transfer time statistics per UE.
Max. is the number of UEs, if applicable.
>> Application ID
Identifies the application in use during the time slot
>> UE location
Indicate the UE location information when the service is delivered.
>> DNN
DNN for the PDU Session which contains the QoS flow.
>> S-NSSAI
Identifies the Network Slice used to access the application.
>> RAT Type
Indicate the list of RAT types for which the E2E data volume transfer time applies.
>> Access Type
Access Type when the UE establishes a PDU Session for the AF.
>> Validity period
The validity period within the time slot for the E2E data volume transfer time statistics as defined in clause 6.1.3.
>> Spatial validity
Area where the E2E data volume transfer time statistics applies.
>> E2E data volume transfer time UL
E2E data volume transfer time UL indicators.
Statistics of E2E data volume transfer time for uplink over the time slot (e.g. average, variance).
>>> Data volume UL
Indicates uplink data volume used to derive E2E data volume transfer time UL.
>> E2E data volume transfer time DL
E2E data volume transfer time DL indicators.
Statistics of E2E data volume transfer time for downlink over the time slot (e.g. average, variance).
>>> Data volume DL
Indicates downlink data volume used to derive E2E data volume transfer time DL.
> Classified E2E data volume transfer time information for a list of UEs (NOTE 1)
Classified E2E data volume transfer time statistics for multiple UEs with respect to one or more reporting thresholds (e.g. NWDAF may provide the ratio of UEs that have reached certain Reporting Threshold(s)).
The list of UEs is indicated in the request of service consumer.
>> E2E data volume transfer time classes (1…max) (NOTE 2)
List with group of UEs classified by ranges of E2E data volume transfer time.
>>> UE ID(s)
Identifies the UE(s) in the transfer time class with respect to the threshold of the corresponding transfer time class.
>>> Ratio of UEs per E2E data volume transfer time class
Ratio of UEs.
>> Validity period
The validity period within the time slot for the Classified E2E data volume transfer times for a list of UEs statistics as defined in clause 6.1.3.
>> Spatial Validity
Area where the Classified E2E data volume transfer times statistics for a list of UEs analytics applies.
> Geographical distribution of the UE(s)
If requested, a list of UEs per location information.
NOTE 1: Analytics subset that can be used in "list of analytics subsets that are requested", "Preferred level of accuracy per analytics subset" and "Reporting Thresholds".
NOTE 2: The number of transfer time classes may be pre-configured by the operator or provided by the service consumer via reporting thresholds.
Table 6.18.3-2: E2E data volume transfer time predictions
Information
Description
UE ID or list of UE IDs (1..SUPImax)
Identifies the UE(s) for which the predictions applies by a list of SUPIs.
Time slot entry (1..max)
List of time slots during the Analytics target period.
> Time slot start
Time slot start within the Analytics target period.
> Duration
Duration of the time slot.
> E2E data volume transfer time information (1…max)
List of E2E data volume transfer time predictions per UE.
Max. is the number of UEs, if applicable.
>> Application ID
Identifies the application in use during the time slot.
>> UE location
Indicate the UE location information when the service is delivered.
>> DNN
DNN for the PDU Session which contains the QoS flow.
>> S-NSSAI
Identifies the Network Slice used to access the application.
>> RAT Type
Indicate the list of RAT types for which the E2E data volume transfer time applies.
>> Access Type
Access Type when the UE establishes a PDU Session for the AF.
>> Validity period
The validity period within the time slot for the E2E data volume transfer time prediction as defined in clause 6.1.3.
>> Spatial validity
Area where the E2E data volume transfer time prediction applies.
>> E2E data volume transfer time UL
E2E data volume transfer time indicators.
Predictions of E2E data volume transfer time for uplink over the time slot (e.g. average, variance).
>>> Data volume UL
Indicates uplink data volume used to derive E2E data volume transfer time UL.
>> E2E data volume transfer time DL
E2E data volume transfer time DL indicators.
Predictions of E2E data volume transfer time for downlink over the time slot (e.g. average, variance).
>>> Data volume DL
Indicates downlink data volume used to derive E2E data volume transfer time DL.
> Classified E2E data volume transfer time information for a list of UEs (NOTE 1)
Classified E2E data volume transfer time prediction for multiple UEs with respect to one or more reporting thresholds (e.g. NWDAF may provide the ratio of UEs that have reached certain Reporting Threshold(s)).
The list of UEs is indicated in the request of service consumer.
>> E2E data volume transfer time classes (1…max) (NOTE 2)
List with group of UEs classified by ranges of E2E data volume transfer time.
>>> UE ID(s)
Identifies the UE(s) in the transfer time class with respect to the threshold of the corresponding transfer time class.
>>> Ratio of UEs per E2E data volume transfer time class
Ratio of UEs.
>> Validity period
The validity period within the time slot for the Classified E2E data volume transfer times for a list of UEs prediction as defined in clause 6.1.3.
>> Spatial Validity
Area where the Classified E2E data volume transfer times prediction for a list of UEs applies.
> Geographical distribution of the UE(s)
If requested, a list of UEs per location information.
Confidence
Confidence of this prediction.
NOTE 1: Analytics subset that can be used in "list of analytics subsets that are requested", "Preferred level of accuracy per analytics subset" and "Reporting Thresholds".
NOTE 2: The number of transfer time classes may be pre-configured by the operator or provided by the service consumer via reporting thresholds.
NOTE: When Target of Analytics Reporting is an individual UE, one UE ID (i.e. SUPI) will be included, the NWDAF will provide the analytics transfer time result (i.e. list of (predicted) time slots) to NF service consumer(s) for the UE.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.18.4 Procedures
|
The NWDAF may provide E2E data volume transfer time analytics to a 5GC NF (e.g. AF, or NEF).
Figure 6.18.4-1: Procedure for E2E data volume transfer time analytics
1. The Consumer NF, e.g. AF or NEF, requests or subscribes to analytics for E2E data volume transfer time analytics from NWDAF (possibly via NEF in case the consumer NF is an untrusted AF) and provides the input information as specified in clause 6.18.1 to 5GC.
2a-b. The NWDAF may subscribe to the service data from AMF as defined in Table 6.18.2-2 using Namf_EventExposure_Subscribe service operation for collecting UE location(s) for a UE or a group of UEs using an Internal-Group-Id.
NOTE: If NWDAF requires UE location information with finer granularity than TA/cell level, then NWDAF collects the location data from GMLC instead of AMF.
2c. The NWDAF may subscribe to service data from SMF as defined in Table 6.18.2-2 by invoking Nsmf_EventExposure_Subscribe service operation (Event ID, SUPI(s) or Application ID).
2c. The NWDAF may subscribe to service data from SMF as defined in Table 6.18.2-2 by invoking Nsmf_EventExposure_Subscribe service operation (Event ID, SUPI(s) or Application ID).
2d. In order to provide the QoS flow Packet delay to NWDAF the SMF subscribe to QoS Monitoring information from UPF, as defined in Table 6.18.2-2, using the N4 Session level Reporting procedure defined in TS 23.502 [3].
2e. The subscribed event is triggered in the UPF.
2f. The UPF notifies the subscribed event report directly to the NWDAF.
2g. The NWDAF may subscribe to the input data from the OAM as defined in the Table 6.18.2-1 according to the data collection principles described in clause 6.2.3.
2h. The NWDAF may subscribe to the service data from as defined AF in the Table 6.18-3 by invoking Nnef_EventExposure_Subscribe or Naf_EventExposure_Subscribe (Event ID = E2E data volume transfer time information, Application ID, Event Filter information, Target of Event Reporting = UE ID(s)) service as defined in TS 23.502 [3].
3. The NWDAF derives the requested analytics, in the form of E2E data volume transfer time statistics and/or predictions.
4. The NWDAF provides the requested E2E data volume transfer time analytics to the consumer NF, using either Nnwdaf_AnalyticsInfo_Request response or Nnwdaf_AnalyticsSubscription_Notify, depending on the service used in step 1.
5-7. If the consumer NF subscribed to E2E data volume transfer time analytics in step 1, once the NWDAF generates new analytics for E2E data volume transfer time, it provides a notification using Nnwdaf_AnalyticsSubscription_Notify to the Consumer NF.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.19 Relative Proximity Analytics
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.19.1 General
|
Relative Proximity Analytics among UEs provided by NWDAF can be used to assist a consumer NF to more accurately localize a cluster (or a set) of UEs via provisioning statistics or prediction information related to their relative proximity. This analytics type may help the consumer improve the location estimation accuracy of a UE by using proximity information from nearby UEs, or it may help the consumer identify UEs in the vicinity of another UE. Relative proximity information can also be leveraged by NWDAF to provide location information with finer granularity than TA/cell.
The NWDAF provides relativity proximity analytics to a NF (e.g. NEF or AF).
The consumer of these analytics shall indicate in the request or subscription:
- Analytics ID = "Relative Proximity";
- Target of Analytics Reporting as defined in clause 6.1.3;
- Analytics Filter Information:
- optionally, S-NSSAI and/or DNN
- an optional Area of Interest;
- an optional individual or set of direction(s) of interest;
- an optional number of UEs to be accounted for relative proximity (i.e. the number of UEs for which one UE may report proximity information);
- optionally, one or several attributes to be accounted for relative proximity (i.e. additional information that can be provided in addition to distance between two UEs): velocity, average speed, orientation, mobility trajectory;
- Optionally, the list of analytics subsets that are requested among those specified in clause 6.19.3;
- Optionally, preferred level of accuracy of the analytics;
- Optionally, preferred level of accuracy per analytics subset (see clause 6.19.3);
- Optionally, "maximum number of objects" indicating the maximum number of UEs
- An Analytics target period indicating the time period over which the statistics or predictions are requested.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.19.2 Input data
|
The detailed input data collected by the NWDAF for relative proximity analytics is listed in Table 6.19.2-1, Table 6.19.2-2 and Table 6.19.2-3.
Table 6.19.2-1: OAM input data for relative proximity analytics
Information
Source
Description
Per UE information
OAM
> Speed
UE Speed
> Orientation
UE Orientation
NOTE 1: To collect the input data in Table 6.19.2-1, NWDAF can invoke TraceJob with the UE ID (e.g. SUPI) of the UE as described in clause 4.3.30 of TS 28.622 [41] using Generic Provisioning Management Service as described in clause 11.1 of TS 28.532 [6] to get Sensor Information as part of MDT data collection mechanism. The UE sensor information includes Barometric pressure, UE speed and UE orientation as described in clause 5.10.29 of TS 32.422 [42].
Table 6.19.2-2: Proximity related input data collected via DCAF/NEF
Information
Source
Description
Proximity Attribute
DCAF / NEF
Characterise a set of UEs in relative proximity.
> Number of UEs
Total number of UEs in proximity of target UE.
> Timestamp
A time stamp of time that the proximity attribute derived.
> Application ID(s)
Identifying the applications(s) providing this information.
> List of UE IDs
UE IDs in proximity of target UE if available.
> Other attribute(s)
Other attributes for the set of UEs i.e. destination, route, average speed, time of arrival.
> Confidence
Confidence on relative proximity data.
NOTE 2: The list of UE IDs that fulfil a proximity criterion can be determined by NWDAF based on the input information collected from the UE application via DCAF. The UE does not need to determine proximity information related to other UEs.
NOTE 3: When DCAF is deployed in untrusted domain, NEF is employed to mediate the interactions between NWDAF and DCAF via the Naf_EventExposure_Subscribe service specified in clause 5.2.19.2 of TS 23.502 [3], as described in clause 6.2.8.2.3.
Table 6.19.2-3: Proximity related input data from 5GC/AF
Information
Source
Description
UE ID(s)
AMF
SUPI(s) of individual UE(s).
UE location
AMF, GMLC
Absolute location of an UE.
UE location accuracy
GMLC
Accuracy of the location estimation.
Velocity estimate
LCS
UE velocity.
Collision risk distance
AF
Derived from the UE connected physical object dimensions e.g. length, width, height.
UE heading
AF
UE moving direction.
> Absolute heading
Heading of the UE movement with respect to the true north.
> Relative heading
Heading of the UE movement with respect to another UE.
UE trajectory
AF
Timestamped UE positions.
>UE location
Geographical area where the UE is located.
>Timestamp
Time stamp for the UE location.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.19.3 Output analytics
|
The NWDAF services as defined in the clauses 7.2 and 7.3 are used to expose the analytics.
- Relative proximity statistics information is defined in Table 6.19.3-1.
- Relative proximity predictions information is defined in Table 6.19.3-2.
Table 6.19.3-1: Relative proximity statistics
Information
Description
UE group ID or set of UE IDs
Identifies the UE(s) for which the statistics apply by a list of SUPIs or GPSIs, or a group of UEs by a list of Internal-Group-Ids.
Time slot entry (1..max)
List of time slots during the Analytics target period.
> Time slot start
Time slot start within the Analytics target period.
> Duration
Duration of the time slot.
> UE proximity attributes
Observed proximity data. This includes distance between UEs in the group/list and other proximity data as mentioned in clause 6.19.1
>> relative proximity information
Observed proximity information.
>> Sampling Ratio
Percentage of UEs accounted based on proximity criteria.
NOTE 1: Analytics subset that can be used in "list of analytics subsets that are requested" and "Preferred level of accuracy per analytics subset".
Table 6.19.3-2: Relative proximity predictions
Information
Description
UE group ID or set of UE IDs
Identifies the UE(s) for which the statistics apply by a list of SUPIs or GPSIs, or a group of UEs by a list of Internal-Group-Ids.
Time slot entry (1..max)
List of predicted time slots.
>Time slot start
Time slot start time within the Analytics target period.
> Duration
Duration of the time slot.
> UE proximity attributes
Predicted proximity data. This includes distance between UEs in the group/list and other proximity data as mentioned in clause 6.19.1.
>> relative proximity information
Predicted proximity information.
>> Confidence
Confidence of this prediction.
>> Sampling Ratio
Percentage of UEs accounted based on proximity criteria.
Time To Collision (TTC) information (NOTE 1)
> Time To Collision
Time until a collision with another UE happens.
>> Collision space
Predicted space of the collision at the collision time, e.g. Ellipsoid point with altitude and uncertainty ellipsoid in TS 23.032 [34].
>> Confidence
Confidence of the prediction for Collision space
>> Collision direction
Predicted collision direction of the target UE at the collision time.
>> Confidence
Confidence of the prediction for collision direction.
>> Accuracy
Accuracy of collision direction.
> Confidence
Confidence of the prediction.
> Accuracy
Accuracy of TTC (dependent on both the UE location accuracy and confidence of the 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".
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.19.4 Procedures
|
Figure 6.19.4-1: Procedure for NWDAF providing relative proximity analytics
Figure 6.19.4-1 shows the procedure for NWDAF to derive relative proximity analytics. The steps are described as follows:
1. The Consumer NF/AF sends a request to the NWDAF for analytics related to relative proximity, using either the Nnwdaf_AnalyticsInfo or Nnwdaf_AnalyticsSubscription service.
The Analytics ID is set to "Relative Proximity". The target for analytics reporting as defined in clause 6.19.1. Analytic filters may be provided as shown in clause 6.19.1.
The Consumer NF/AF can request statistics or predictions or both for a given Analytics target period.
2-5. If the request is authorized and in order to provide the requested analytics, the NWDAF may subscribe to OAM services to retrieve relevant information to proximity analytics. The NWDAF may collect MDT input data per individual UE from OAM as defined in Table 6.19.2-1.
6-7. For relative proximity information, if the request is authorized and in order to provide the requested analytics, NWDAF may follow the UE Input Data Collection Procedure via the DCAF. DCAF may collect proximity related input data directly from the UE Application, for NWDAF to determine a list of UEs fulfilling certain proximity criterion.
NOTE 1: The UE data collection procedure should be based on clause 6.2.8.
NOTE 2: Different Application IDs of the same DCAF or different DCAFs may be selected for different UEs, since each DCAF can only collect the proximity information for the UEs that have PDU session between UE and DCAF.
The NWDAF subscribes to the AF services as above invoking either Nnef_EventExposure_Subscribe for untrusted DCAF or Naf_EventExposure_Subscribe service for trusted DCAF with (Event ID = Relative Proximity, Event Filter information, Target of Event Reporting). The target of event reporting and / or Event Filter information is set according to the target of analytics reporting and / or analytics filters set during the step 1 of the procedure.
Event filters can be defined for relative proximity to indicate to NWDAF on how to process the data from individual UEs to determine the set of UEs to be accounted for relative proximity.
In the case of a trusted DCAF, the NWDAF may provide the Area of Interest, proximity range, predefined geographical area, or other criteria to the DCAF on the resolution of TAIs or any other finer resolution recognizable by the 5GC. In the case of an untrusted DCAF, NEF translates the requested criteria provided as event filter by the NWDAF into geographic zone identifier(s) or other geographic range identifier(s) or geographic direction identifier(s) that act as event filter(s) for the DCAF.
The DCAF may collect the data from individual UEs based on Event Filters indicated by the NWDAF to determine the set of UEs to be accounted for relative proximity before notifying that directly (for trusted DCAF) or via NEF (for untrusted DCAF) to the NWDAF. Input data that may be collected from DCAF can be found in Table 6.19.2-2.
NOTE 3: Details of DCAF and its data processing can be found in TS 26.531 [32] and TS 26.532 [43].
8. The NWDAF collects input data from AMF as defined in Table 6.19.2-3 via the AMF event exposure service as defined in TS 23.502 [3].
NOTE 4: Step 8 could be performed before step 6 when DCAF cannot determine the set of UEs fulfilling a proximity criterion.
9. The NWDAF collects input data from GMLC as defined in Table 6.19.2-3 using the Ngmlc_Location service as defined in TS 23.273 [39] and TS 29.515 [48].
10. The NWDAF collects input data from AF as defined in Table 6.19.2-3 via the AF event exposure service as defined in TS 23.502 [3].
11. The NWDAF derives requested analytics.
12. The NWDAF provides requested relative proximity and TTC information as defined in Table 6.19.3-1 and Table 6.19.3-2 to the consumer NF or AF along with the corresponding Validity Period or any Validity Area, Validity Direction of interest or ranging distance, using either the Nnwdaf_AnalyticsInfo_Request response or Nnwdaf_AnalyticsSubscription_Notify, depending on the service used in step 1.
13-15. If at step 1 the consumer NF or AF has subscribed to receive continuous reporting of relative proximity information, the NWDAF may generate new analytics and, when relevant according to the Analytics target period and Reporting Threshold, provide them along with the corresponding Validity Period (or any Validity Area, Validity Direction of interest or ranging distance) to the consumer NF or AF.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.20 PDU Session traffic analytics
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.20.1 General
|
This clause specifies the procedure for an NWDAF to provide statistics on whether traffic of UEs via one or multiple PDU sessions is according to the information provides by the service consumer.
The NWDAF collects traffic flow information of UE traffic via PDU session(s) established for a specific S-NSSAI and/or DNN and provides statistics of UEs that route traffic according to the information provided by the service consumer (e.g., Traffic Descriptor, S-NSSAI, DNN) and UEs that route traffic which is not expected according to the information provided by the service consumer (e.g., Traffic Descriptor, S-NSSAI, DNN).
The assumption is that Traffic Descriptors are known (e.g. known flow description), so that there are associated Packet Detection Rule(s) for the known traffic configured in the UPF.
NOTE 1: How traffic from different applications over the same S-NSSAI/DNN and/or PDU session is discerned is implementation-specific.
The service consumer may be a PCF.
The consumer of these analytics includes in the request:
- Analytics ID = "PDU Session traffic".
- Target of Analytics Reporting as defined in clause 6.1.3.
- Traffic Descriptor: Application Identifier, IP Descriptions or Domain Descriptors are applicable.
NOTE 2: The Application Id provided by the consumer is known by the network, i.e. corresponds to an Application Id known at the UPF.
- Analytics Filter Information containing:
- Area of Interest (i.e. the location of UEs where PDU Session traffic is monitored);
- S-NSSAI;
- DNN;
- an optional list of analytics subsets that are requested (see clause 6.20.3);
- Optionally, preferred level of accuracy of the analytics.
- Optionally, preferred level of accuracy per analytics subset (see clause 6.20.3);
- An Analytics target period indicates the time period over which the analytics are requested.
- Optionally, maximum number of objects.
- In a subscription, the Notification Correlation Id and the Notification Target Address are included.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.20.2 Input Data
|
NWDAF collects input data from the SMF and/or UPF. The detailed data are described in Table 6.20.2-1.
Table 6.20.2-1: Collected PDU Session User Plane Traffic Information
Information
Source
Description
SUPI
SMF, UPF
UE ID for the UE that established PDU sessions to an S-NSSAI/DNN.
S-NSSAI
SMF, UPF
The S-NSSAI for which the PDU session is established.
DNN
SMF, UPF
The DNN for which the PDU session is established.
PDU Session Information
The detected Service Data Flow, volume measured and Application related information in a PDU Session.
> Packet Filter Set
SMF, UPF
Packet Filter Set for the detected Service Data Flow as defined in clause 5.8.2.4.2 of TS 23.502 [3].
> URL list
SMF, UPF
If available, list of URLs extracted from the inspected user plane packets in the Service Data Flow.
> Domain Name list
SMF, UPF
If available, list of domain names extracted from the inspected user plane packets in the Service Data Flow.
> UL Data volume
SMF, UPF
Measured UL data traffic volume for the Service Data Flow for the duration of the PDU Session.
> DL Data volume
SMF, UPF
Measured DL data traffic volume for the Service Data Flow for the duration of the PDU Session.
NOTE: Care needs to be taken with regards to load and major signalling caused when requesting Any UE. This could be achieved via utilization of some event filters (e.g. Area of Interest), a specific DNN, S-NSSAI or sampling ratio as part of Event Reporting Information.
The NWDAF collects input data from the UPF either indirectly via the SMF, or directly from the UPF using the "UserDataUsageMeasures" event exposure event as described in clause 4.15.4.5 of TS 23.502 [3]. Further details about input parameters are described in Table 4.15.4.5.1 of TS 23.502 [3].
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.20.3 Output Analytics
|
The NWDAF collects input data from the UPF, via SMF when the request is for a UE or a group of UEs identified by an Internal-Group-ID or directly from the UPF when possible (see clause 5.8.2.17 of TS 23.501 [2]) if the request applies for any UE and NWDAF provides analytics of UEs about the traffic they route over a PDU session of specific S-NSSAI/DNN according to the Traffic Descriptor provided by the consumer and traffic they route over a PDU Session that is not according to the Traffic Descriptor provided by the consumer and information about that traffic.
The output analytics is shown in Table 6.20.3-1.
Table 6.20.3-1: PDU Session traffic statistics
Information
Description
List of SUPIs or SUPI
Identifies a SUPI, or a list of SUPIs for which analytics are provided.
S-NSSAI
Identifies the Network Slice for which analytic information is provided.
DNN
Identifies the data network name (e.g. internet) for which analytics information is provided.
Traffic matching the Traffic Descriptor (NOTE 1)
Identifies traffic that matches Traffic Descriptor provided by the consumer in those PDU Sessions identified by the S-NSSAI and DNN above and the volume.
> Traffic Descriptor
IP Flow descriptor containing 3-tuple, server side (destination address, port and protocol) or Application ID or Domain descriptor.
> Volume
measures of data volume exchanged (UL, DL and/or overall) and/or number of packets exchanged (UL, DL and/or overall) for the Traffic Descriptor within the PDU Session.
Traffic which does not match Traffic Descriptor (NOTE 1)
Identifies traffic that does not match Traffic Descriptor provided by the consumer in those PDU Sessions identified by the S-NSSAI and DNN above and the volume.
> Traffic Descriptor
IP Flow descriptor containing 3-tuple, server side (destination address, port and protocol) or Application ID or Domain descriptor.
> Volume
measures of data volume exchanged (UL, DL and/or overall) and/or number of packets exchanged (UL, DL and/or overall).
NOTE 1: Analytics subset that can be used in "list of analytics subsets that are requested" and "Preferred level of accuracy per analytics subset". The list is ordered by descending volume.
NOTE: Predictions are not provided.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.20.4 Procedures
|
The procedure for deriving PDU Session traffic is shown below.
Figure 6.20.4-1: NWDAF providing PDU Session traffic analytics
1. The Consumer NF (e.g. the PCF) requests or subscribes to the NWDAF to request PDU Session Traffic analytics. The consumer includes within analytics filter the expected traffic via a PDU session according to the Traffic Descriptors and the SUPI or list of SUPIs, the S-NSSAI and DNN of the PDU session. It is assumed that there are associated Packet Detection Rule(s) for the expected traffic listed in the analytics request, i.e. the expected traffic is known.
2. The NWDAF determines to collect data, either directly from the UPF or indirectly via the SMF and identifies the SMF(s) and/or UPF(s) to retrieve input data according to the S-NSSAI/DNN and SUPI or list of SUPIs in the analytics request.
3. The NWDAF collects input information using the procedure for subscription to UPF event exposure for certain UEs via SMF as described in clause 4.15.4.5.2 of TS 23.502 [3]; the Target of Event Reporting is set to each of the tuples (SUPI, DNN and S-NSSAI) that have a PDU Session in the same SMF, the Target Subscription Information is set to "UserDataUsageMeasures", the Target service data flows is absent to indicate that the UPF reports any detected service data flow in the PDU Session.
The UPF reports volume measurements for the PDU Session with per application granularity, the report includes volume measurements and provide the application related information, i.e. URLs and Domain names.
4. The NWDAF derives analytics indicating a list of UEs and the traffic they route according to the provided information provided by the consumer (i.e. Traffic Descriptor, S-NSSAI and DNN), including its volume and the traffic they route and a list of UEs which route traffic that it is not expected according to the information provided by the consumer (i.e. Traffic Descriptor, S-NSSAI and DNN) including its volume.
5. The NWDAF provides the analytics as defined in Table 6.20.3-1 using either the Nnwdaf_AnalyticsInfo_Request response or Nnwdaf_AnalyticsSubscription_Subscribe_Notify, depending on the service used in step 1
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.21 Movement Behaviour Analytics
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.21.1 General
|
The movement behaviour analytics provides analytics information (statistics or predictions) regarding e.g. the number, direction and velocity of UEs during an analytics target period in a target area. The analytics of movement behaviour requires to collect UE movements in a certain region in a certain period of time. In addition, the consumers can further derive the congestion situation in the target area through analytics.
The NWDAF provides movement behaviour analytics to a NF (e.g. NEF, AF).
The consumer of these analytics shall indicate in the request or subscription:
- Analytics ID = "movement behaviour";
- Target of Analytics Reporting: any UE, a list of UEs;
- Analytics Filter Information:
- Area of Interest (AOI): restricts the scope of the movement behaviour analytics to the provided area. The AOI may be described as shown in clause 5.5 of TS 23.273 [39];
- Optionally, the list of analytics subsets that are requested among those specified in clause 6.21.3;
- An Analytics target period indicates the time period over which the statistics or predictions are requested;
- Optionally, preferred level of accuracy of the analytics;
- Optionally, preferred level of accuracy per analytics subset (see clause 6.21.3);
- Optionally, preferred granularity of location information: "longitude and latitude level";
- Optionally, preferred orientation of location information: ("horizontal", "vertical", "both")"; and
- Optionally, maximum number of objects.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.21.2 Input data
|
The NWDAF collects the UE location and velocity information within the area of interest from the sources listed in Table 6.21.2-1.
Table 6.21.2-1: Data collection by NWDAF for "movement behaviour" analytics
Information
Source
Description
UE ID
AMF
SUPI; a list of SUPIs
UE locations (1..max)
AMF
UE positions
>UE location
TA or cells that the UE enters
>Timestamp
A time stamp when the AMF detects the UE enters this location
Fine granularity locations (1 …max)
LCS (NOTE 1)
UE locations
…>Timestamp
Time information associated with the collected information
…>LCS QoS
The achieved LCS QoS accuracy (see TS 23.273 [39])
…>Location estimate
Geographical location or location in local coordinates (as defined in TS 23.032 [34])
…>Velocity estimate
Speed and direction information
…>Indoors/outdoor indication
Indicate the location estimate is indoor or outdoor
…>Age of location
Valid period of the location estimate
NOTE 1: The procedure to collect location data using LCS is described in clause 6.2.12.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.21.3 Output analytics
|
The output for analytics of movement behaviour provided by NWDAF is defined in Table 6.21.3-1 and Table 6.21.3-2.
Table 6.21.3-1: movement behaviour statistics
Information
Description
Applicable Area
A geographical area as defined in TS 23.273 [39] that the analytics applies to.
Applicable UEs
A list of SUPIs for the applicable UEs (NOTE 2)
Time slot entry (1..max)
List of time slots during the Analytics target period
> Time slot start
Time slot start within the Analytics target period
> Duration
Duration of the time slot
> Total number of UEs (NOTE 1)
Total number of UEs in the area of interest
> Ratio of moving UEs (NOTE 1)
Ratio of moving UEs in the area of interest
> Average speed (NOTE 1)
Average speed of all UEs in the area of interest
> Speed threshold (1...max) (NOTE 1)
Threshold utilized to filter the UEs
>> Number of UEs
The number of UEs whose speed is faster than the speed threshold
>> Ratio
Percentage of UEs whose speed is faster than the speed threshold
> Direction (1…max) (NOTE 1)
Heading directions of the UEs in the target area, such as north, south, east, west etc.
>> Number of UEs
The number of UEs in the specific direction
>> Average speed
Average speed of UEs in the specific direction
>> Ratio
Percentage of UEs in the specific direction
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: If Target of Analytics Reporting is set to a "List of UEs", the statistics are estimated considering only UEs in the area of interest that are also in the provided List of UEs.
Table 6.21.3-2: movement behaviour predictions
Information
Description
Applicable Area
A geographical area as defined in TS 23.273 [39] that the analytics applies to
Applicable UEs
A list of SUPIs for the applicable UAV UEs (NOTE 2)
Time slot entry (1..max)
List of time slots during the Analytics target period
> Time slot start
Time slot start within the Analytics target period
> Duration
Duration of the time slot
> Total number of UEs (NOTE 1)
Total number of UEs in the area of interest
> Ratio of moving UEs (NOTE 1)
Ratio of moving UEs in the area of interest
> Average speed (NOTE 1)
Average speed of all UEs in the area of interest
> Speed threshold (1...max) (NOTE 1)
Threshold utilized to filter the UEs
>> Number of UEs
The number of UEs whose speed is faster than the speed threshold
>> Ratio
Percentage of UEs whose speed is faster than the speed threshold
> Direction (1..max) (NOTE 1)
Heading directions of the UEs in the target area, such as north, south, east, west etc.
>> Number of UEs
The number of UEs in the specific direction
>> Average speed
Average speed of UEs in the specific direction
>> Ratio
Percentage of UEs in the specific direction
Confidence
Confidence of the 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: If Target of Analytics Reporting is set to a "List of UEs", the statistics are predicted considering only UEs in the area of interest that are also in the provided List of UEs.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.21.4 Procedures
|
Figure 6.21.4-1 depicts the procedure for movement behaviour analytics provided by NWDAF.
Figure 6.21.4-1: "Movement Behaviour" analytics provided by NWDAF
1. The NWDAF receives an analytics request from the NWDAF service consumer (as defined in clause 6.1.1.1) or from an AF via NEF (as defined in clause 6.1.1.2) to request movement behaviour analytics within a target area for any UE or a list of UEs; the list of UEs may be provided by the NWDAF service consumer.
NOTE: A UAS NF/NEF, for instance, can obtain a list of UEs using the procedures described in clause 5.3.4 and/or clause 5.12 of TS 23.256 [53] before requesting analytics from the NWDAF and setting a Target of Analytics Reporting to a list of UEs.
The Analytics ID is set to "Movement Behaviour". The target for analytics reporting is set to be any UE or a list of UEs. Analytic filters may be provided as shown in clause 6.21.1. The Area of Interest is the target area that may be defined as a geographical area or as a geopolitical name of an area, in such case, the NEF will translate it as the identities of one or more radio cells or tracking areas.
The NWDAF service consumer NF can request statistics or predictions or both for a given Analytics target period.
2. The NWDAF collects input data from AMF as defined in Table 6.21.2-1 via the AMF event exposure service.
The collected UE location information from AMF is optional and may assist in the statistics/prediction of UE moving direction and speed in step 4.
3. The NWDAF collects the UE location information using LCS as defined in Table 6.21.2-1 and clause 6.2.12.
Based on the analytics target period, the NWDAF may trigger the immediate 5GC-MT-LR procedure as defined in clause 6.1.2 or the deferred 5GC-MT-LR procedure in clause 6.3.1 of TS 23.273 [39] to obtain UE's location information.
4. The NWDAF derives requested analytics.
If the NWDAF service consumer provides a list of UEs in step 1, the NWDAF derives the analytics specified in Table 6.21.3-1 and Table 6.21.3-2 only for UEs from the provided list of UEs if they are in the applicable area.
5. The NWDAF provides the analytics as defined in Table 6.21.3-1 and Table 6.21.3-2 using either the Nnwdaf_AnalyticsInfo_Request response or Nnwdaf_AnalyticsSubscription_Notify, depending on the service used in step 1.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.22 Signalling Storm Analytics
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.22.1 General
|
This clause specifies how NWDAF supports analytics for network abnormal behaviours (i.e. signalling storm) mitigation and prevention.
The signalling storm analytics provides analytics information (statistics or predictions) regarding the abnormal signalling rate condition. An abnormal signalling rate condition is when signalling rate is experiencing an abnormal growth. The abnormal signalling growth may indicate a potential signalling storm due to a significant deviations from the signalling level in the normal conditions. The analytics of signalling storm provides the identification of whether the signalling storm is due to massive signalling from NF(s) or from UEs based on the analytics consumer request.
The NWDAF provides statistics and/or prediction analytics to consumer entity (e.g. SCP) or consumer NFs, e.g. AMF, SMF, UDM, PCF, NRF, OAM and AF.
NOTE 1: When the consumer is SCP, the target NF(s) (i.e. The NF that signalling storm analytics should be provided for) might be deployed either in front of the SCP (egress) or behind the SCP (ingress).
The consumer of these analytics may indicate in the request or subscription:
- Analytics ID = "Signalling Storm";
- Target of Analytics Reporting:, a list of NF instance ID(s) or NF Set ID(s) which may suffer signalling storm or any NF if the target is the whole network;
- Target Cause ID(s): Indicates specific Cause ID(s) as Analytics Output (e.g. signalling storm caused by UEs, signalling storm caused by NF, or all);
- Analytics Filter Information:
- NF ID List: instance IDs or NF Set IDs may cause signalling storm to the target NF;
- a group of UEs or several groups of UEs identified by internal Group ID(s) or a SUPI list which may cause signalling storm to the Target of the Analytics Reporting;
- Area of Interest (AoI) and/or S-NSSAI which restricts the scope of signalling storm analytics to the specific area and/or slice.
- Analytics Reporting Information:
- Expected Report Time: indicates the time limit by which the analytics results need to be received, e.g. 10 seconds, 5 minutes, etc.;
- An Analytics target period indicates the time period over which the statistics or predictions are requested;
- Optionally, preferred level of accuracy of the analytics;
- Signalling frequency threshold: indicates the frequency of the received signalling within the time period;
- UE number threshold: indicates a threshold of the amount of UEs of which the number of one type of request messages meets the frequency of UE requests threshold. For example, if the number of UEs that initiate registration requests exceeds the pre-set rate threshold (10 times per hour) and the number of such UEs exceeding the pre-set rate threshold exceeds 100 (the UE number threshold is set to 100), the NWDAF will provide the analytics.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.22.2 Input data
|
The NWDAF collects the signalling feature data, NF context, AF data and MDAF data as listed in Tables 6.22.2-1, 6.22.2-2, 6.22.2-3, 6.22.2-4, 6.22.2-5 and 6.22.2-6.
The NWDAF can collect UE behavioural information per UE or group of UEs as specified in clause 6.7.5.2.
The NWDAF may use output of abnormal UE behaviour analytics and UE dispersion analytics as specified in clause 6.7.5 and clause 6.10.3 as input data for analytics on signalling storm. This information may be collected from a different NWDAF (e.g. distributed architecture).
The NWDAF may collect a subset of input data based on implementation.
Table 6.22.2-1: UE related Context Data collection
Information
Source
Description
UE ID
Identifies a single UE.
Signalling feature data
NF procedures containing signalling exchange information related to a particular UE or session from the Connection, Registration, Mobility and Session Managements procedures (NOTE 1).
> Request type and number from UE/RAN (0..max)
AMF
Request type of N1 or N2 interface (such as received Initial Registration Request, Mobility and Periodic Registration Request, Service Request, etc.) and the number of requests corresponding to the request type.
>> Time duration from receiving request from UE/RAN to response to UE/RAN
AMF
Time duration between the request from UE/RAN and response to UE/RAN.
>> Number of successful responses of UE/RAN
AMF
Number of successful responses associated to their initial requests, such as Registration Response, etc.
>> Number of failed responses of UE/RAN
AMF
Number of failed responses associated to their initial requests, such as Registration Reject, Service Reject, etc.
>> Reason of failed responses of UE/RAN
AMF
Reasons of failed responses associated to their initial requests, e.g. reject, no-response, etc.
>> A posterior Request type of UE/RAN (0..max)
AMF
A posterior Request types triggered from UE/RAN, for NF Service request, or request to UE/RAN (NOTE 6).
> Request type and number from NF (0..max)
NF
Request type received from NF, e.g. Namf_N1N2Trans, Namf_comm, etc., as well as the number of requests received from NF, e.g. Namf_N1N2Trans, Namf_comm, etc. (NOTE 2) (NOTE 3).
>> Time duration from receiving request from NF to response to NF
NF
Time duration between the request from NF and response to NF.
>> Time duration of transactions related to SCP ingress interface
SCP
Time duration between the received request from consumer NF and response forwarded by SCP to consumer NF (NOTE 4).
>> Time duration of transactions related to SCP egress interface
SCP
Time duration between the routed/forwarded request to producer NF and response received from producer NF (NOTE 4).
>> Number of successful responses of NF
NF
Number of successful responses associated to their initial requests (NOTE 2).
>> Number of failed responses of NF
NF
Number of failed responses associated to their initial requests (NOTE 2).
>> Number of successful responses related to SCP egress interface
SCP
Number of successful responses received over the egress interface associated to their initial requests.
>> Number of failed responses related to SCP egress interface
SCP
Number of failed responses received over the egress interface associated to their initial requests.
>> Reason of failed responses of NF
NF
Reasons of failed responses associated to their initial requests, e.g. reject, no-response, etc.
>> Reason of failed responses related to SCP egress interface
SCP
Reasons of failed responses over the egress interface associated to their initial requests, e.g. reject, no-response, etc. (NOTE 5).
>> Number of redundant signalling of NF
NF
Number of received redundant signalling. The redundant signalling means the signalling which is transmitted multiple times (NOTE 2) (NOTE 3).
>> A posterior Request type of NF (0..max)
NF
A posterior Request types triggered from NF, for NF Service request (NOTE 3) (NOTE 6).
> Public Warning information
AMF
Public Warning information as defined in the TS 23.041 [52], such as WRITE-REPLACE WARNING REQUEST, etc.
> Frequent Mobility Registration Update
AMF
The number of Mobility Registration Updates N within a period M may be an indication for abnormal ping-pong behaviour, where N and M are operator's configurable parameters.
> Number of receiving Session Report from UPFs
SMF
Number of receive Session Report from UPF triggered by DL packet in case of PDU Session is in 5GCM-idle state.
UE Context in NF
> State transition information
AMF, SMF
UE related state transition information such as transition type, frequency of CM state changes, etc.
State transition identifier:
- "Access Type change to 3GPP access";
- "Access Type change to non-3GPP access";
- "RM state change to RM-DEREGISTERED";
- "RM state change to RM-REGISTERED ";
- "CM state change to CM-IDLE";
- "CM state change to CM-CONNECTED";
- "Handover";
- "Mobility Registration Update"; or
- "Frequent Mobility Registration Update"(table 6.7.2.2-1).
Or, PDU Session related state transition information such as transition type, frequency SM state changes, etc.
State transition identifier:
- "PDU Session Establishment";
- "PDU Session Release";
- "Communication failure"; or
- "PLMN change".
It can be reported for a group of UEs (e.g. the number of total transitions or percentage of the group UEs who have transitions).
> timer information
AMF, SMF
Timer information which has been set for the UE, such as timer type, duration.
NOTE 1: NWDAF can optionally provide transaction dispersion analytic information for MM and SM transactions.
NOTE 2: This data is provided per time interval that is indicated by the NWDAF.
NOTE 3: The word "NF" refers here to SCP as well. As a centric routing/proxy entity, SCP might be involved with some signalling that may not be visible to the NF sending the SCP's ingress traffic, such a signalling could be associated with actions such as selection & discovery, retransmissions, re-directions, re-selection, throttling, etc.
NOTE 4: e.g. average time duration of a transaction (averaged over all of the transactions handled by the SCP within the requested time interval).
NOTE 5: Distribution of the failed responses, e.g. how many time-outs vs how many server errors vs how many consumer errors.
NOTE 6: A posterior request is a request sent from NF1 to NF2 (or from NF2 to NF1) that was triggered by a previous request received by NF1. For example, in clause 4.3.2.2 of TS 23.502, the request sent by AMF in step 3 and the request sent by SMF in step 11 are both posterior requests of the request received by the AMF in step 1. These posterior requests can be collected by NF1 (the AMF in this example).
An SCP can collect a posterior request between NF1 and NF2 only if it routes incoming requests to NF1 as well as route requests between NF1 and NF2.
Table 6.22.2-2: NF Context Data collection
Information
Source
Description
NF ID
NF instance ID
> NF profile
NRF
NF Profile information such as allowed NF information for the NF and NF Service(s).
> NF load status information
NRF, SCP
Load information indicates the current load of the NF and NF Service(s), e.g. CPU, memory, and/or percentage of load information (NOTE 1).
> Capacity and priority information of NFs and NF Services
NRF, SCP
Capacity and priority information of the registered NF and NF Service(s) (NOTE 1).
NF heart-beat related information
NF
NF heart-beat related information such as responding time, Number of retransmissions, heart-beat intervals.
heart-beat related information
SCP
heart-beat related information such as responding time, Number of retransmissions, heart-beat intervals between the NF and NRF and/or between SCP and NRF.
> Unexpected operational status indicator
NF, OAM
The parameter indicates unexpected operational status occurs. It is an indication of deviation from the normal operations, based on thresholds or rules configured by operator at the NF or OAM (e.g. for energy consumptions, loads, etc.).
NOTE 1: If this information is not available in the NRF, it can be obtained from the OAM.
Table 6.22.2-3: NF Specific Data collection
Information
Source
Description
NF ID
NF instance ID
> Usage information of UE IP address resources
SMF
Usage information of UE IP address resources (dynamic and static, V4, V6, etc.) for CP or UP allocation, such as number, usage, number of UE IPs, which prohibit allocation during certain time interval, etc. This parameter is valid for SMF only.
> Load information of connected UPFs
SMF
Load information of connected UPFs such as using PFCP Load Control Information. This parameter is valid for SMF only.
SCP Signalling statistics
SCP
The number of different types of signalling received and sent by SCP during a target time period, etc. This parameter is valid for SCP only.
Table 6.22.2-4: Application activation time information
Information
Source
Description
Application ID
AF
Identifies the application providing this information.
User activation time information (1…max)
AF
Information of activation time for the users (e.g. IoT users) per application.
> Number of UEs
AF
The total number of UEs
> Active Time
AF
The time stamp of the users per application switch to active, or the start and end time of the users activity per application.
> Inactive Time
AF
The time stamp of the users per application switch to inactive, or the start and end time of the users inactivity per application, if applicable.
> UE type ID
AF
Identifies a group of UEs, e.g. external group ID, or a list of UE IDs.
Table 6.22.2-5: Data collection from NRF/OAM
Information
Source
Description
NRF ID
NRF instance ID.
Number of NF service registration requests
OAM
Number of registration request received at the NRF.
> Number of successful NF service registrations
OAM
Number of successful registrations.
> Number of failed NF service registrations due to encoding error of NF profile
OAM
Number of failed registrations.
> Number of failed NF service registrations due to NRF internal error
OAM
Number of failed registrations.
Number of NF service update requests
OAM
Number of update request received at the NRF.
> Number of successful NF service updates
OAM
Number of successful updates
> Number of failed NF service updates due to encoding error of NF profile
OAM
Number of failed updates.
> Number of failed NF service updates due to NRF internal error
OAM
Number of failed updates.
Number of NF discovery requests
OAM
Number of discovery request received at the NRF.
> Number of successful NF discoveries
OAM
Number of successful discovery attempts.
> Number of failed NF service discoveries due to unauthorized NF Service consumer
OAM
Number of failed discovery attempts.
> Number of failed NF discoveries due to input errors
OAM
Number of failed discovery attempts.
> Number of failed NF discoveries due to NRF internal error
OAM
Number of failed discovery attempts.
NOTE 1: If this information is not available in the OAM, it can be obtained from the NRF if available.
Table 6.22.2-6: Data collection from MDAF/MDAS of control plane congestion analysis as defined in clause 8.4.7.1.3 of TS 28.104 [45]
Information
Source
Description
affectedObject
MDAF
Indication of 5GC NFs where congestion issues occurred or potentially may occur.
cPCongestionIssueID
MDAF
This field holds the ID of the control plane congestion issue which is reported.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.22.3 Output analytics
|
The output analytics of signalling storm provided by NWDAF is defined in Table 6.22.3-1, and Table 6.22.3-2. The Table 6.22.3-3 gives examples of NF/SCP actions for solving each risk. The final mitigation or prevention operations are based on operator's policy/configuration and NF/SCP implementation.
The statistics and predictions are provided with a Validity Period, as defined in clause 6.1.3.
Table 6.22.3-1: Signalling storm statistics
Information
Description
Report (1..max)
List of observed signalling storm statistics.
> Target NF ID/SCP ID
A list of impacted NFs/SCPs of signalling storm detected by NWDAF.
> Cause ID of the signalling storm
The potential cause of abnormal level of signalling (i.e. massive signalling from UE or NF abnormal signalling).
> Source UE/NF
a UE or a group of UEs or several groups of UEs identified by internal Group ID or SUPI or SUPI range, or a list of NFs which cause the signalling storm.
> OPTIONAL Time slot entry (1..max)
List of time slots during the Analytics target period.
>> Time slot start
Time slot start within the Analytics target period.
>> Duration
Duration of the time slot. If a Temporal granularity size was provided in the request or subscription, the Duration is greater than or equal to the Temporal granularity size.
>> Received Signalling Analytics
Information of signalling received by the target NF(s).
>>> Total number of received signalling
Indicates the statistics on the number of signalling messages received by the target NF(s) in the time slot.
>>> Growth rate of received signalling
Difference between the number of signalling messages received by the NF in the time slot and the number of signalling messages received by the target NF(s) in the previous time slot.
>>> Signalling analytics of UE
Indicates the statistics on the number of signalling messages received from UEs within the time slot (NOTE 1).
> OPTIONAL Timer List
The list of timer information per source UE(s) (NOTE 1).
>> Type of timer
The type of timer which has been set.
>> Timer duration
The timer duration that has be selected for the source UE(s).
NOTE 1: Only available when Cause ID of signalling storm is massive signalling from UEs, and there exists Source UE(s).
Table 6.22.3-2: Signalling storm predictions
Information
Description
Report (1..max)
List of predicted signalling storm analytics.
> Target NF ID/SCP ID
A list of impacted NFs/SCPs signalling storm predicted by NWDAF.
> Cause ID of the signalling storm
The potential cause of abnormal level of signalling (i.e. massive signalling from UE or NF abnormal signalling).
> Source UE/NF
a UE or a group of UEs or several groups of UEs identified by internal Group ID or SUPI or SUPI range, or a list of NFs which cause the signalling storm.
> OPTIONAL Time slot entry (1..max)
List of time slots during the Analytics target period.
>> Time slot start
Time slot start within the Analytics target period.
>> Duration
Duration of the time slot. If a Temporal granularity size was provided in the request or subscription, the Duration is greater than or equal to the Temporal granularity size.
>> Reference point
The information of the reference point impacted. (e.g. N1, N2)
>> Service operation(s)
The information of the service operation(s) impacted. (e.g. Namf_Communication(UEContextTransfer), Nsmf_PDUSession(UpdateSMContext)).
>> Received Signalling Analytics
Information of signalling received by the target NF(s).
>>> Received number of signalling
Received number of signalling of the specific signalling type.
>>> Growth rate of received signalling
Difference between the number of signalling messages received by the NF in the time slot and the number of signalling messages received by the target NF(s) in the previous time slot.
>>> Signalling analytics of UE
Indicates the statistics on the number of signalling messages received from UEs within the time slot (NOTE 1).
> OPTIONAL Timer List
The list of timer information per Source UE(s) (NOTE 1).
>> Type of timer
The type of timer.
>> Timer duration
The timer duration that commonly is selected for the Source UE(s).
> Priority
Priority (relative to other NFs of the same type) of candidate NFs as defined in the TS 29.510 [18].
> Capacity
Candidate NF capacity information, expressed as a weight relative to other NF instances of the same type as defined in the TS 29.510 [18].
> Confidence
Confidence of this prediction.
NOTE 1: Only available when Cause ID of signalling storm is massive signalling from UEs, and there exists Source UE(s).
Table 6.22.3-3: Example mechanisms to mitigate and prevent the signalling storm
Cause of the signalling storm
Example actions of NFs
massive signalling from UE
AMF sets MM NAS related timer (e.g. back-off, T3512) for a selected set of UEs.
massive signalling from UE
SMF sets SM NAS related timer (e.g. back-off) for a selected set of Sessions.
massive signalling from UE
AMF/SMF sets suggested N1/N2 interface related ingress/egress threshold, or AMF triggers RAN to initiate overload control for a selected set of UEs in specific slice or priority as defined in clause 8.7.7 of TS 38.413 [8] to start overload control. The AMF may assign a slice under signalling storm conditions to the UEs and initiate overload control for the specific slice.
NF abnormal signalling
NRF configures the local policy (e.g. to prevent the source NF with abnormal signalling from being discovered or discovering others, to update the NF profile(s)(e.g. Priority, Capacity) of NF(s) based on the signalling storm statistics and/or predictions and send the updated NF profiles(s) to NF service consumer(s) of the NF(s)(e.g. subscriber of the NF profile as defined in clause 4.17.7 of TS 23.502 [3])).
NF abnormal signalling
Source NF configures to (re)select other NFs instead of NF with abnormal signalling and may unsubscribes the NF with abnormal signalling.
NF abnormal signalling
Source NF configures to deprioritize the NFs/Services with abnormal signalling from being selected.
NF abnormal signalling
Source NF triggers UE Reregistration and/or Session Reestablishments to avoid NF with abnormal signalling.
NF abnormal signalling
SCP blocks or throttles messages originating from an NF/service with abnormal signalling.
NF abnormal signalling
SCP redirects requests towards an NF service producer with abnormal signalling towards another service producer.
NF abnormal signalling
SCP notifies communication peers of an NF that the NF may suffer signalling storm.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.22.4 Procedures
|
The NWDAF can provide information on network signalling storm as follows (Figure 6.22.4-1).
Figure 6.22.4-1: Procedure for NWDAF-assisted Network Signalling Storm Mitigation and Prevention
1. The consumer NF (SCP included) or other entities subscribes to or sends a request to NWDAF for the signalling storm analytics using either Nnwdaf_AnalyticsSubscription_Subscribe or Nnwdaf_AnalyticsInfo_Request service operation. The request additionally includes thresholds such as confidence level and accuracy of detection:
- The Analytics ID is set to "Signalling Storm analytics". The target for analytics reporting is set to be any NF/SCP or any UE. Analytic filters may be provided as shown in clause 6.22.1.
- The consumer NF can request statistics or/and predictions for a given Analytics target period.
- The consumer NF may also subscribe to "NF load analytics" as depicted in clause 6.5 and trigger the signalling storm analytics based on output of the NF load analytics, e.g. CPU usage is over 80%.
- The consumer NF may also subscribe to "Abnormal behaviour" analytics as depicted in clause 6.7.5 and trigger the signalling storm analytics based on the suspicion of DDoS attack.
- The consumer NF may also subscribe to "Dispersion Analytics" analytics as depicted in clause 6.10 and trigger the signalling storm analytics when the transaction dispersion is above the expected transaction dispersion configurable threshold.
2. The NWDAF retrieves Input data from NFs, AFs and SCPs, using Nnf_EventExposure_Subscribe, or from NRF using Nnrf_NFManagement_NFStatusSubscribe service operation, such as UE and/or NF as depicted in Table 6.22.2-1 and Table 6.22.2-2, NF specific data as depicted in Table 6.22.2-1, application data as depicted in Table 6.22.2-4, and collects input data from OAM and MDAF as depicted in Table 6.22.2-5 and Table 6.22.2-6 to derive the required analytics as depicted in clause 6.22.2. The NWDAF may optionally request additional data aligned with the analysis target identified in step 1.
The NWDAF may optionally subscribe the abnormal UE behaviour analytics and UE dispersion analytics as specified in clause 6.7.5 and 6.10.3 as input data from other NWDAFs, using Nnwdaf_AnalyticsSubscription_Subscribe or Nnwdaf_AnalyticsInfo_Request service operation.
3. The NWDAF derives the required analytics with the collected data described in clause 6.22.2.
4. The NWDAF invokes Nnwdaf_AnalyticsSubscription_Notify or Nnwdaf_AnalyticsInfo_Request response or response to the consumer NF/SCP for the Output data analytics as depicted in clause 6.22.3.
5. The consumer upon receiving the detection and/or prediction and/or mitigation may execute based on the example mechanisms as depicted in clause 6.22.3.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.23 QoS and Policy Assistance Analytics
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.23.1 General
|
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 analytics 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 Nnwdaf_AnalyticsInfo_Request or Nnwdaf_AnalyticsSubscription_Subscribe request to the NWDAF with one or multiple sets of QoS parameters and optionally a requested QoE. The NWDAF provides the candidate set(s) of QoS parameters and the corresponding predicted QoE that can be achieved by applying the candidate QoS parameters set(s).
The candidate QoS parameters set(s) provided by the NWDAF are within the sets of QoS parameters provided by the consumer (i.e. PCF). The NWDAF shall only include the parameter(s) and the corresponding value(s) that are provided by the consumer request (i.e. PCF) in the QoS parameter set(s). The candidate QoS parameters set(s) provided by the NWDAF are within the sets of QoS provided by the consumer (i.e. PCF). The NWDAF shall only include the parameter(s) and the corresponding value(s) that are provided by the consumer request (i.e. PCF) in the QoS parameter set(s).
The QoS and policy assistance analytic may be provided for an individual UE or a 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(s) 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 associated QoS parameter set ID(s). Based on the consumer decision (i.e. PCF), each QoS parameter set(s) may include the following individual parameters and non-empty value list(s) for each individual parameter(s):
- 5QI (standardized or pre-configured); or
- QoS characteristics attributes (as defined in clause 5.7.3 of TS 23.501 [2]): Resource Type, Priority Level, PDB, PER, Averaging Window, Maximum Data Burst Volume.
And optionally for GBR 5QI(s):
- GBR and MBR.
NOTE 1: In the case of standardised and pre-configured 5QI(s), the specified/configured QoS parameters and QoS characteristics (e.g. as defined in Table 5.7.4-1 of TS 23.501 [2]) may be pre-configured into NWDAF by operators, subject to operator policy. Therefore, the NWDAF is able to associate the QoS parameters and QoS characteristics to the given 5QI in consumer request to derive the predicted QoE.
NOTE 2: QoS characteristics may be included in the QoS parameter set(s) only in the case of dynamically assigned non-standardized 5QI(s).
- Application ID or SDF template(s).
- Optionally, a requested QoE that indicates the NWDAF to only provide the QoS parameter set(s) and their corresponding value(s) for which the predicted QoE is equal to, or higher than, the requested QoE.
- Analytics Filter Information optionally includes:
- DNN;
- Area of Interest (AOI(s));
NOTE 3: A service consumer can use the AOI(s) in order to reduce the amount of signalling that the analytics subscription or request generates.
- 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).
- RAT Type.
- Frequency.
- DNAI (for analytics with an edge application server).
- 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.
- Optionally, preferred order of results for the list of candidate QoS parameter sets and the predicted QoE associated to each 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.
- Optionally, reporting Thresholds, which apply only for subscriptions and indicate conditions on the levels to be reached for the reporting of respective analytics subsets (see clause 6.23.3).
- Optionally, maximum number of objects and maximum number of SUPIs.
- Optionally, preferred granularity of location information: TA level or cell level or "longitude and latitude level".
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.23.2 Input Data
|
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 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) is defined in Table 6.23.2-1 and from OAM in Table 6.23.2-2.
NOTE: The NWDAF may also collect the Observed Service Experience Analytics from other NWDAFs, based on NWDAF implementation.
Table 6.23.2-1: Input data from 5GC NF related to QoS and Policy Assistance information
Information
Source
Description
QFI allocation or QFI deallocation events (1…max)
SMF
SMF provides such event when specific QoS parameters are applied to or released from certain QoS flow(s).
> Used QoS parameter set(s)
SMF
The QoS parameter set(s) that have been already applied by SMF.
As detailed in clause 6.23.1, the QoS parameter set includes 5QI or QoS characteristics attributes and optionally GFBR and MFBR for GBR flows.
> Used QoS profile
SMF
The QoS profile associated to the used QoS parameter set(s).
> Traffic descriptor
SMF
One of Application Identifier, IP Packet Filter Set or Ethernet Packet Filter Set
> S-NSSAI
SMF
Slice used to transport the QoS flow(s).
> DNN
SMF
DNN associated with the QoS flow(s).
> DNAI
SMF
Identifies the access to the DN that the PDU Session is connected to.
UE identifier
SMF, AMF
The identifier of UE, e.g. SUPI, UE IP address, etc.
UE Location
AMF
The UE location information, e.g. cell ID or TAI.
RAT Type
SMF
RAT Type used for the UE.
Time stamp
SMF, AMF
The time stamp associated to the collected data.
N6 Delay (NOTE 1)
UPF
The observed N6 delay between the UPF and measurement endpoint in the DN, as defined in clause 5.8.2.23 of TS 23.501 [2].
Packet Loss Rate (NOTE 2)
UPF
The Packet Loss Rate for uplink and/or downlink.
NOTE 1: Whether and how N6 delay (independent of QoS profile) is considered to derive the analytics in comparison to delay between UE and UPF (dependent on the QoS profile) is left to implementation based on the operator's policy.
NOTE 2: The Packet Loss Rate is applicable to the TCP traffic for which the UPF is able to provide the information.
For the analysis of a QoE that must meet the provided Packet Delay Budget, the following input is collected to enable the latency analysis between UE and PSA UPF.
Table 6.23.2-2: Input data from OAM related to Packet Delay between UE and Anchor UPF
Information
Source
Description
UL/DL GTP packet delay
OAM
Average UL/DL packet delay measurement on N3 between NG-RAN and PSA UPF, as defined in clause 5.4.7 of TS 28.552 [8].
Delay in RAN
OAM
Average Uplink and Downlink packet transmission delay over the air interface, as defined in clause 5.1.1.1 of TS 28.552 [8].
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.23.3 Output Analytics
|
The NWDAF shall be able to provide predictions on QoS and Policy Assistance to consumer NFs, i.e. PCF, as defined in Table 6.23.3-1.
Table 6.23.3-1: QoS and Policy Assistance predictions
Information
Description
Time slot entry (1..max)
List of time slots during the Analytics target period.
> Time slot start
Time slot start within the Analytics target period.
> Duration
Duration of the time slot.
> QoS and Policy Assistance information (1…max)
List of QoS and Policy Assistance information.
Max. is the number of the candidate QoS parameter set(s), if applicable.
>> QoS parameter set identifier (NOTE 6)
Identifies the QoS parameter set for which the entry applies to.
>> DNN
DNN for the PDU Session which contains the QoS flow of the application for which the predicted QoE and the candidate QoS parameter set are provided.
>> Application ID or SDF template(s)
Identifies the application or SDF template(s) for which the predicted QoE and the candidate QoS parameter set are provided.
>> Duration for the Application
Duration for the corresponding application ID.
>> Predicted QoE (NOTE 6)
The predicted QoE of the application when the corresponding QoS parameter set is applied, e.g. average, variance, maximum, minimum of QoE.
>> QoS parameter values (NOTE 4)
The parameters in the QoS parameter set and their corresponding values associated to the predicted QoE.
>>> 5QI
The reference to 5G QoS characteristics and QoS parameters.
>>> Priority level
The Priority Level associated with 5G QoS characteristics, as defined in clause 5.7.3.3 of TS 23.501 [2].
>>> Resource type
The resource type of the corresponding QoS flow, e.g. GBR QoS flow, non-GBR QoS flow, delay-critical GBR QoS flow.
>>> Packet Delay Budget
Packet 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 [2].
>>> Packet Error Rate
Packet Error Rate (PER) defines an upper bound for a rate of non-congestion related packet losses, as defined in TS 23.501 [2].
>>> Bit Rates (NOTE 2)
The bit rates are only applied to GBR for a SDF template or Application IDs.
>>>> GBR
Guaranteed Bit Rate (GBR) for UL and/or DL.
>>>> MBR
Maximum Bit Rate (MBR) for UL and/or DL.
>>> Maximum 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 [2].
>>> 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 [2].
>> Applicable duration of the QoS and Policy Assistance information
The applicable duration/ time window of the QoS and Policy Assistance information.
>> RAT Type
Indicating the list of RAT type(s) for which the QoS and Policy Assistance Information applies.
>> Frequency
Indicating the list of carrier frequency value(s) for which the QoS and Policy Assistance Information applies.
>> Validity period
The validity period within the time slot for the QoS and Policy Assistance information analytics as defined in clause 6.1.3.
>> Spatial validity
Area where the QoS and Policy Assistance information analytics applies.
>> (Optional) Usage Duration information (NOTE 5)
Maximum/Minimum/Average usage duration of the QoS Flows associated to candidate QoS parameter set.
>> (Optional) Number of usage (NOTE 5)
The number of times that the QoS Flows associated to candidate QoS parameter set to be used.
> Confidence
Confidence 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 for a SDF template or Application ID QoS Flow.
NOTE 3: The output analytics only applies to GBR for a SDF template or Application ID 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: This parameter is included in analytics output if the Target of Analytics Reporting is a specific UE or Analytics Filter contains specific Application ID. It is determined by NWDAF using the SMF QFI allocation and deallocation events. For example, the duration equals to the timestamps difference between the QoS Flow change(s) (e.g. QFI allocation, change, and deallocation); the usage number counts the number of times the application traffic is allocated to the QoS Flow.
NOTE 6: The predicted QoE is reported for the entire QoS parameter set (together with QoS parameter set identifier) if only one parameter value has been provided for each parameter in the set. Otherwise separate predicted QoE for each combination of different parameter values are provided.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.23.4 Procedures
|
Figure 6.23.4 shows the procedure for deriving and providing the QoS and Policy Assistance analytics to a consumer 5GC NF (i.e. PCF).
Figure 6.23.4-1: Procedure for QoS and Policy Assistance Analytics
1. The Consumer NF, i.e. PCF, requests or subscribes to QoS and Policy Assistance analytics from NWDAF (via NEF in the case that the consumer NF is an untrusted AF) and provides the request input information as specified in clause 6.23.1 to NWDAF.
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 operations, 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) for collecting the data related to QoS parameter set, 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 [39] and TS 29.515 [48].
2b. For average UL/DL packet delay analysis between UE and PSA_UPF, the SMF subscribes to QoS Monitoring information from UPF using the N4 Session level Reporting procedure defined in TS 23.502 [3]. The UPF notifies the subscribed event report directly to the NWDAF.
2c. The NWDAF may collect data from the OAM following the procedure captured in clause 6.2.3.2.
2d. The NWDAF may subscribe to the service data from AF as defined in Table 6.4.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 [3].
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 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.
NOTE: When requested by the NF consumer (i.e. PCF), the NWDAF may also collect data from OAM as described in clause 6.6.4 and clause 6.9.4 for the purpose of deriving NW performance and QoS sustainability information associated to the QoS parameters set(s).
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.
5-7. If the consumer NF subscribes to QoS and Policy Assistance Analytics in step 1, once the NWDAF generates new analytics on QoS and Policy Assistance, it provides the new analytics via Nnwdaf_AnalyticsSubscription_Notify to the Consumer NF.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
7 Nnwdaf Services Description
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
7.1 General
|
Table 7.1-1 illustrates the NWDAF Services.
Table 7.1-1: NF services provided by NWDAF
Service Name
Service Operations
Operation
Semantics
Example Consumer(s)
Nnwdaf_AnalyticsSubscription
Subscribe
Subscribe / Notify
PCF, NSSF, AMF, SMF, NEF, AF, OAM, CEF, NWDAF, DCCF, LMF, NRF, SCP, ADRF
Unsubscribe
PCF, NSSF, AMF, SMF, NEF, AF, OAM, CEF, NWDAF, DCCF, LMF, NRF, SCP, ADRF
Notify
PCF, NSSF, AMF, SMF, NEF, AF, OAM, CEF, NWDAF, DCCF, MFAF, LMF, NRF, SCP, ADRF
Transfer
Request / Response
NWDAF
Nnwdaf_AnalyticsInfo
Request
Request / Response
PCF, NSSF, AMF, SMF, NEF, AF, OAM, CEF, NWDAF, DCCF, LMF, NRF, SCP, ADRF
ContextTransfer
Request / Response
NWDAF
Nnwdaf_DataManagement
Subscribe
Subscribe / Notify
NWDAF, DCCF
Notify
NWDAF, DCCF, MFAF, ADRF
Fetch
Request / Response
NWDAF, DCCF, MFAF, ADRF
Nnwdaf_MLModelProvision
Subscribe
Subscribe / Notify
NWDAF, LMF
Unsubscribe
NWDAF, LMF
Notify
NWDAF, LMF
Nnwdaf_MLModelInfo
Request
Request / Response
NWDAF, LMF
Nnwdaf_MLModelMonitor
Subscribe
Subscribe / Notify
NWDAF
Unsubscribe
NWDAF
Notify
NWDAF
Register
Request / Response
NWDAF
Deregister
NWDAF
Nnwdaf_MLModelTraining
Subscribe
Subscribe / Notify
NWDAF
Unsubscribe
NWDAF
Notify
NWDAF
Nnwdaf_MLModelTrainingInfo
Request
Request / Response
NWDAF
Nnwdaf_RoamingAnalytics
Subscribe
Subscribe / Notify
H-RE-NWDAF, V-RE-NWDAF
Unsubscribe
H-RE-NWDAF, V-RE-NWDAF
Notify
H-RE-NWDAF, V-RE-NWDAF
Request
Request / Response
H-RE-NWDAF, V-RE-NWDAF
Nnwdaf_RoamingData
Subscribe
Subscribe / Notify
H-RE-NWDAF, V-RE-NWDAF
Unsubscribe
H-RE-NWDAF, V-RE-NWDAF
Notify
H-RE-NWDAF, V-RE-NWDAF
Nnwdaf_VFLTraining
Subscribe
Subscribe / Notify
NWDAF, AF, NEF
Unsubscribe
NWDAF, AF, NEF
Notify
NWDAF, AF, NEF
Request
Request / Response
NWDAF, AF, NEF
Nnwdaf_VFLInference
Subscribe
Subscribe / Notify
NWDAF, AF, NEF
Unsubscribe
NWDAF, AF, NEF
Notify
NWDAF, AF, NEF
Request
Request / Response
NWDAF, AF, NEF
NOTE 1: How OAM consumes Nnwdaf services and which Analytics information is relevant is defined in TS 28.550 [7] Annex H and out of the scope of this TS.
NOTE 2: How CEF consumes Nnwdaf services and which Analytics information is relevant is defined in TS 28.201 [21] and out of the scope of this TS.
NOTE 3: The Nnwdaf_MLModelProvision service and the Nnwdaf_MLModelInfo service are provided by an NWDAF containing MTLF and consumed by an NWDAF containing AnLF or provided by an NWDAF containing MTLF supporting FL as a server and consumed by an NWDAF containing MTLF.
Table 7.1-2 shows the analytics information provided by NWDAF service.
Table 7.1-2: Analytics information provided by NWDAF
Analytics Information
Request Description
Response Description
Slice Load level information
Analytics ID: load level information
Load level provided as number of UE registrations and number of PDU sessions for a Network Slice and Network Slice instances as well as resource utilization for Network Slice instances.
Observed Service experience information
Analytics ID: Service Experience
Observed Service experience statistics or predictions may be provided for a Network Slice or an Application. They may be derived from an individual UE, a group of UEs or any UE. For slice service experience, they may be derived from an Application, a set of Applications or all Applications on the Network Slice.
NF Load information
Analytics ID: NF load information
Load statistics or predictions information for specific NF(s).
Network Performance information
Analytics ID: Network Performance
Statistics or predictions on the load in an Area of Interest; in addition, statistics or predictions on the number of UEs that are located in that Area of Interest.
UE mobility information
Analytics ID: UE Mobility
Statistics or predictions on UE mobility. When visited AOI(s) is included in the Analytics Filter information, only statistics on UE mobility can be provided.
UE Communication information
Analytics ID: UE Communication
Statistics or predictions on UE communication.
Expected UE behavioural parameters
Analytics ID: UE Mobility and/or UE Communication
Analytics on UE Mobility and/or UE Communication.
UE Abnormal behaviour information
Analytics ID: Abnormal behaviour
List of observed or expected exceptions, with Exception ID, Exception Level and other information, depending on the observed or expected exceptions.
End-to-end data volume transfer time
Analytics ID: E2E data volume transfer time
Analytics on E2E data volume transfer time.
User Data Congestion information
Analytics ID: User Data Congestion
Statistics or predictions on the user data congestion for transfer over the user plane, for transfer over the control plane, or for both.
QoS Sustainability
Analytics ID: QoS Sustainability
For statistics, the information on the location and the time for the QoS change and the threshold(s) that were crossed; or, for predictions, the information on the location and the time when a potential QoS change may occur and what threshold(s) may be crossed.
Session Management Congestion Control Experience
Analytics ID: Session Management Congestion Control Experience
Statistics on session management congestion control experience for specific DNN and/or S-NSSAI.
Redundant Transmission Experience
Analytics ID: Redundant Transmission Experience
Statistics or predictions aimed at supporting redundant transmission decisions for URLLC services.
WLAN performance
Analytics ID: WLAN performance
Statistics or predictions on WLAN performance of UE.
Dispersion
Analytics ID: UE Dispersion
Statistics or predictions that identify the location (i.e. areas of interest) or network slice(s) where a UE, or a group of UEs disperse their data volume, or disperse mobility or session management transactions or both.
DN Performance
Analytics ID: DN Performance
Statistics or predictions on user plane performance for a specific Edge Computing application.
PFD Determination
Analytics ID: PFD Determination
Statistics on PFD information for a known application identifier(s).
Movement Behaviour
Analytics ID: Movement Behaviour
Statistics or predictions on movement behaviour for an applicable area.
Location Accuracy
Analytics ID: Location Accuracy
Predictions on Location Accuracy.
Relative Proximity
Analytics ID: Relative Proximity
Statistics or predictions on Relative Proximity among UEs.
PDU Session traffic
Analytics ID: PDU Session traffic
Statistics on whether traffic of UEs via one or multiple PDU sessions is according to the information provided by the service consumer.
Signalling Storm
Analytics ID: Signalling storm
Statistics or predictions for signalling storm mitigation or prevention.
QoS and Policy Assistance
Analytics ID: QoS and Policy Assistance
Analytics on predicted QoE for QoS parameter set(s) and candidate QoS parameter sets associated to the corresponding predicted QoE.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
7.2 Nnwdaf_AnalyticsSubscription Service
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
7.2.1 General
|
Service Description: This service enables the consumer to subscribe/unsubscribe for network data analytics and optionally its corresponding Analytics Accuracy Information.
When the subscription for network data analytics and optionally Analytics Accuracy Information is accepted by the NWDAF containing AnLF, the consumer receives from the NWDAF an identifier (Subscription Correlation ID) allowing to further manage (modify, delete) this subscription. The modification of Analytics and optionally Analytics Accuracy Information subscription can be enforced by NWDAF based on operator policy and configuration.
This service also enables the consumer to transfer analytics subscriptions to another NWDAF using the Nnwdaf_AnalyticsSubscription_Transfer service operation. Using this service operation, a consumer can request to the NWDAF to prepare for or take over analytics subscription(s), indicating also if and where analytics context is available.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
7.2.2 Nnwdaf_AnalyticsSubscription_Subscribe service operation
|
Service operation name: Nnwdaf_AnalyticsSubscription_Subscribe
Description: Subscribes to NWDAF analytics and optionally Analytics Accuracy Information with specific parameters.
Inputs, Required:
- (Set of) Analytics ID(s) as defined in Table 7.1-2;
- Target of Analytics Reporting;
- Notification Target Address (+ Notification Correlation ID);
- Analytics Reporting Parameters (including Analytics target period, etc.).
NOTE 1: Target of Analytics Reporting can be provided per individual Analytics ID.
Inputs, Optional:
- Analytics Filter Information;
- Time window for historical analytics;
- Subscription Correlation ID (in the case of modification of the analytics subscription);
- Preferred level of accuracy of the analytics;
- Preferred level of accuracy per analytics subset;
- Reporting Thresholds;
- Maximum number of objects requested (max);
- Preferred order of results;
- Maximum number of SUPIs requested (SUPImax);
- Time when analytics information is needed;
- Analytics Metadata Request;
- (Set of) NWDAF identifiers used by the NWDAF service consumer when aggregating multiple analytic subscriptions;
- Dataset Statistical Properties;
- Output strategy;
- Data time window;
- Consumer NF's serving area or NF ID;
- Information of previous analytics subscription, i.e. NWDAF identifier (i.e. Instance ID or Set ID), Analytics ID(s) (including SUPIs and Analytics Filter Information for UE-related Analytics) and Subscription Correlation ID;
- Use case context.
- Analytics Accuracy Request information.
- Analytics Feedback Information.
- QoS parameter set(s) and corresponding value(s), optionally a requested QoE.
NOTE 2: Analytics Filter Information, Reporting Thresholds, maximum number of objects requested (max), maximum number of SUPIs requested (SUPImax), Analytics Metadata Request, Dataset Statistical Properties, Output strategy, Data time window and time when analytics information is needed can be provided per individual Analytics ID.
NOTE 3: Analytics Feedback Information only can be included in modification request for the existing analytics subscription.
NOTE 4: Other input parameters specific for different analytics ID can be also needed, as specified in the corresponding clause for each analytics ID.
Outputs Required: When the subscription is accepted: Subscription Correlation ID (required for management of this subscription). When the subscription is not accepted, an error response.
Outputs, Optional: First corresponding Analytics report is included, if available and if analytics consumer requested immediate reporting (see clause 4.15.1 of TS 23.502 [3]).
NOTE 5: When the Target of Analytics Reporting is a SUPI or a GPSI then the subscription may not be accepted, e.g. user consent is not granted and an error is sent to the consumer. When the Target of Analytics Reporting is an Internal Group Id, or a list of SUPIs/GPSIs or any UE, no error is sent, but a SUPI or GPSI is skipped if user consent is not granted.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
7.2.3 Nnwdaf_AnalyticsSubscription_Unsubscribe service operation
|
Service operation name: Nnwdaf_AnalyticsSubscription_Unsubscribe
Description: Unsubscribe to NWDAF analytics.
Inputs, Required: Subscription Correlation ID.
Inputs, Optional: None.
Outputs, Required: Operation execution result indication.
Outputs, Optional: None.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
7.2.4 Nnwdaf_AnalyticsSubscription_Notify service operation
|
Service operation name: Nnwdaf_AnalyticsSubscription_Notify
Description: NWDAF notifies the consumer instance of the analytics and optionally Analytics Accuracy Information that has subscribed to the specific NWDAF service. See also clause 6.1.3 for contents of the Analytics Exposure.
Inputs, Required: Notification Correlation Information: this parameter indicates the Notification Correlation ID that has been assigned by the consumer during analytics subscription.
Inputs, Optional:
- Set of the tuple (Analytics ID, Analytics specific parameters): this parameter shall be present if output analytics are reported.
- Timestamp of analytics generation (required when ADRF is deployed).
- Validity period.
- Confidence
- Revised waiting time.
- Analytics Metadata Information.
- Analytics Accuracy Information.
- Stop Analytics Output Consumption indication.
- Stop Analytics Output Consumption time window.
- Resume Analytics Output Consumption indication.
- Termination Request: this parameter indicates that NWDAF requests to terminate the analytics subscription, i.e. NWDAF will not provide further notifications related to this subscription, with cause value (e.g. user consent revoked, NWDAF overload, UE moved out of NWDAF serving area, etc.).
- Accuracy Information Termination.
NOTE 1: Validity period can also be provided as part of Analytics specific parameters for some NWDAF output analytics.
- Subscription Change Notification Correlation ID: this parameter shall be present if the notification is for informing the assignment of a new Subscription Correlation Id by the NWDAF. It is set to the old Subscription Correlation ID.
- Subscription Correlation ID: this parameter shall be present if the notification is for informing the assignment of a new Subscription Correlation Id by the NWDAF. It is set to a new Subscription Correlation ID assigned by the NWDAF.
NOTE 2: Other input parameters specific for different analytics ID can be also needed, as specified in the corresponding clause of each analytics ID.
Outputs, Required: Operation execution result indication.
Outputs, Optional: None.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
7.2.5 Nnwdaf_AnalyticsSubscription_Transfer service operation
|
Service operation name: Nnwdaf_AnalyticsSubscription_Transfer
Description: Requests to NWDAF for transferring analytics subscription(s) from the consumer NWDAF.
Inputs, Required:
- Transfer type: indicates the type of the transfer request. The following values are supported:
- Analytics subscription transfer preparation: requests the NWDAF to prepare for taking over the analytics subscription(s) and/or prepare for collecting Analytics Context(s).
- Analytics subscription transfer: requests the NWDAF to take over the analytics subscription(s).
- Analytics subscription transfer cancel: cancels a prepared analytics subscription request.
Inputs, Optional:
- If this service operation is for "analytics subscription transfer preparation", the following parameter shall be provided:
- (Set of) analytics subscription information with the following parameters:
- All input parameters for the analytics exposure as specified in clause 6.1.3.
- [OPTIONAL] Active data source ID(s): Instance ID or Set ID of the active data source(s) the consumer NWDAF is currently using for the analytics of this analytics subscription.
- [OPTIONAL] ML Model related information, i.e. information related to the ML Model(s) that the NWDAF is currently using for the analytics:
- ID(s) of NWDAF(s) containing MTLF: Instance ID(s) of the NWDAF(s) containing MTLF from which the consumer NWDAF currently subscribes to the ML Model information used for the analytics.
- [OPTIONAL] File address of the ML Model(s).
- ID of the analytics consumer, e.g. NF, AF or OAM, that is subscribed to receive analytics.
- [OPTIONAL] (Set of) analytics context identifier(s): identifies analytics context available at the consumer NWDAF as defined in clause 6.1B.4.
- If this service operation is to request analytics subscriptions transfer and if analytics subscription transfer preparation is not performed, the same parameters as those for transfer type "Analytics subscription transfer preparation" shall be provided.
- If this service operation is to request analytics subscriptions transfer and if analytics subscription transfer preparation is performed, the same parameters as those for transfer type "Analytics subscription transfer preparation" can be provided with updated parameter values.
- If this service operation is to request analytics subscriptions transfer cancel, the following parameter shall be provided:
- Subscription Correlation ID.
Outputs Required: Operation execution result indication.
Outputs, Optional: None.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
7.3 Nnwdaf_AnalyticsInfo service
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
7.3.1 General
|
Service description: this service enables the consumer to request and get from NWDAF network data analytics, Analytics Accuracy Information or enables NWDAF to request transfer of analytics context from another NWDAF.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
7.3.2 Nnwdaf_AnalyticsInfo_Request service operation
|
Service operation name: Nnwdaf_AnalyticsInfo_Request
Description: The consumer requests NWDAF operator specific analytics and optionally Analytics Accuracy Information.
Inputs, Required: (Set of) Analytics ID(s) as defined in Table 7.1-2, Target of Analytics Reporting, Analytics Reporting Parameters (including Analytics target period, etc.).
NOTE 1: Target of Analytics Reporting can be provided per individual Analytics ID.
Inputs, Optional: Analytics Filter Information, preferred level of accuracy of the analytics, preferred level of accuracy per analytics subset, time when analytics information is needed, maximum number of objects requested (max), preferred order of results, maximum number of SUPIs requested (SUPImax), Analytics Metadata Request, Dataset Statistical Properties, Output strategy, Data time window, Use case context, Time window for historical analytics and Analytics Accuracy Request information, QoS parameter set(s) and corresponding value(s), optionally a requested QoE.
NOTE 2: Analytics Filter Information, Maximum number of objects requested (max), Maximum number of SUPIs requested (SUPImax), Analytics Metadata Request, Dataset Statistical Properties, Output strategy, Data time window and time when analytics information is needed can be provided per individual Analytics ID.
Outputs, Required: If the request is accepted, then set of the tuple (Analytics ID, Analytics specific parameters). When the request is not accepted, an error response.
Outputs, Optional: Timestamp of analytics generation (required when ADRF is deployed), validity period, confidence, revised waiting time, Analytics Metadata Information, Analytics Accuracy Information. See clause 6.1.3.
NOTE 3: Validity period can also be provided as part of Analytics specific parameters for some NWDAF output analytics.
NOTE 4: When the Target of Analytics Reporting is a SUPI or a GPSI then the request may not be accepted, e.g. user consent is not granted and an error is sent to the consumer. When the Target of Analytics Reporting is an Internal Group Id, or a list of SUPIs/GPSIs or any UE, no error is sent, but a SUPI or GPSI is skipped if user consent is not granted.
NOTE 5: Other input or output parameters specific for different analytics ID can be also needed, as specified in the corresponding clause of each analytics ID.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
7.3.3 Nnwdaf_AnalyticsInfo_ContextTransfer service operation
|
Service operation name: Nnwdaf_AnalyticsInfo_ContextTransfer
Description: Requests to NWDAF to transfer context information related to analytics subscriptions.
Inputs, Required: (Set of) Analytics context identifier(s).
Inputs, Optional: Requested Analytics Context per analytics context identifier.
Outputs Required: (Set of) Analytics Context as specified in clause 6.1B.4.
Outputs, Optional: ADRF ID with Analytics Context Type stored in the ADRF (i.e. Historical output Analytics and/or Data related to Analytics).
NOTE: For the Requested Analytics Context, the NWDAF can return a combination of Analytics Context and reference to ADRF ID from where Historical output Analytics and/or Data related to Analytics can be retrieved.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
7.4 Nnwdaf_DataManagement Service
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
7.4.1 General
|
Service Description: This service enables the consumer to subscribe/unsubscribe for data exposed by an NWDAF, fetch the subscribed data. Historical data or runtime data may be obtained using this service.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
7.4.2 Nnwdaf_DataManagement_Subscribe service operation
|
Service operation name: Nnwdaf_DataManagement_Subscribe
Description: The consumer subscribes to receive data, or if the data is already requested from the NWDAF, then the subscription is updated. The subscription includes service operation specific parameters that identify the data to be provided and may include formatting and processing instructions that specify how the data is to be delivered to the consumer. The consumer may request bulked data related to Analytics, as an alternative to asking individual events (i.e. subscription to multiple event IDs to obtain the data required for an analytics generation). The consumer may also request that data be stored in an ADRF. When historical data is being obtained, the consumer may specify the ID of the ADRF or NWDAF containing the data.
Inputs, Required: Data Specification, Notification Target Address(es) (+ Notification Correlation ID(s)).
When the required data is data for Event IDs received from NFs, the Data Specification includes set of Event IDs, Event Filter Information, Target of Event Reporting.
When the required data is a bulked data for an Analytics ID, the Data Specification includes Target of Reporting with the Analytics ID to generate bulked data, Target of Analytics reporting and Analytics Filter.
Inputs, Optional: Service Operation, Time Window, NF (or NF-Set) ID, ADRF or NWDAF hosting ADRF information where data are to be stored, ADRF ID where historical data are stored, Formatting Instructions, Processing Instructions, user consent check information (i.e. an indication that the data consumer has checked user consent), purpose for data collection, Storage Handling Information.
NOTE 1: See clause 8.2.2 for further description of the Input Parameters.
Outputs Required: When the subscription is accepted: Subscription Correlation ID (required for management of the requested subscription). When the subscription is not accepted, an error response.
Outputs, Optional: First corresponding event report is included, if available (see clause 4.15.1 of TS 23.502 [3]), Requested data, Storage Approach (see clause 5B.1).
NOTE 2: When the Target of Event Reporting or Target of Reporting is a SUPI or a GPSI then the subscription may not be accepted, e.g. for user consent is not granted and an error is sent to the consumer. When the Target of Event Reporting or Target of Reporting is an Internal Group Id, or a list of SUPIs/GPSI(s) or any UE, no error is sent, but a SUPI or GPSI is skipped if user consent is not granted.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.