Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.288  Word version:  19.0.0

Top   Top   Up   Prev   Next
1…   4…   5…   5A…   6…   6.1.3   6.1.4…   6.1.4.4…   6.1.5…   6.1A…   6.1B…   6.1B.2.3…   6.1C   6.2…   6.2.3…   6.2.6…   6.2.6.2   6.2.6.3…   6.2.6.3.3   6.2.6.3.4   6.2.6.3.5   6.2.6.3.6…   6.2.7…   6.2.8…   6.2.9…   6.2.13…   6.2A…   6.2B…   6.2B.3   6.2B.4…   6.2C…   6.2D…   6.2E…   6.2F…   6.3…   6.4…   6.5…   6.6…   6.7…   6.7.3…   6.7.4…   6.7.5…   6.8…   6.9…   6.10…   6.11…   6.12…   6.13…   6.14…   6.16…   6.17…   6.18…   6.19…   6.20…   6.21…   7…   7.4…   7.7…   7.9…   8…   9…   10… 
6.7.3 UE Communication Analytics  6.7.3.1 General  6.7.3.2 Input Data  6.7.3.3 Output Analytics  6.7.3.4 Procedures 
...

 

6.7.3  UE Communication Analytics  p. 198

6.7.3.1  General  p. 198

In order to support some optimized operations, e.g. customized mobility management, traffic routing handling, RFSP Index Management, QoS improvement or Inactivity Timer optimization, in 5GS, an NWDAF may perform data analytics on UE communication pattern and user plane traffic and provide the analytics results (i.e. UE communication statistics or prediction) to NFs in the 5GC or an AF.
An NWDAF supporting UE Communication Analytics collects per-application communication description from AFs. If consumer NF provides an Application ID, the NWDAF only considers the data from AF, SMF and UPF that corresponds to this application ID. NWDAF may also collect data from AMF.
The consumer of these analytics may indicate in the request:
  • Analytics ID = "UE Communication".
  • Target of Analytics Reporting: a single UE (SUPI) or group of UEs (a list of Internal-Group-Ids).
  • Analytics Filter Information optionally including:
    • S-NSSAI;
    • DNN;
    • Application ID;
    • Area of Interest.
    • an optional list of analytics subsets that are requested (see clause 6.7.3.3);
  • An Analytics target period indicates the time period over which the statistics or predictions are requested.
  • Preferred level of accuracy of the analytics.
  • Optional Preferred level of accuracy per analytics subset (see clause 6.7.3.3);
  • Optional preferred order of results for the list of UE Communications:
    • ordering criterion: "start time" or "duration",
    • order: ascending or descending;
  • Optionally, maximum number of objects;
  • Optionally, Spatial granularity size (if an Area of Interest is provided); and
  • In a subscription, the Notification Correlation Id and the Notification Target Address are included.
Up

6.7.3.2  Input Data  p. 199

The NWDAF supporting data analytics on UE communication shall be able to collect communication information for the UE from 5GC. The detailed information collected by the NWDAF includes service data related to UE communication as defined in the Table 6.7.3.2-1.
Information Source Description
UE IDSMF, AFSUPI in the case of SMF, external UE ID (i.e. GPSI) in the case of AF
Group IDSMF, AFTo identify UE group if available
Internal Group ID in the case of SMF, External Group ID in the case of AF
S-NSSAISMFInformation to identify a Network Slice
DNNSMFData Network Name where PDU connectivity service is provided
Application IDSMF, AFIdentifying the application providing this information
Expected UE Behaviour parametersAFSame as Expected UE Behaviour parameters specified in TS 23.502
UE communication (1..max)UPF, AFCommunication description per application
 >Communication startThe time stamp that this communication starts
 >Communication stop The time stamp that this communication stops
 >UL data rate UL data rate of this communication
 >DL data rate DL data rate of this communication
 >Traffic volumeTraffic volume of this communication
Type Allocation code (TAC)AMFTo indicate the terminal model and vendor information of the UE. The UEs with the same TAC may have similar communication behaviour. The UE whose communication behaviour is unlike other UEs with the same TAC may be an abnormal one.
UE locations (1..max)AMFUE positions
 >UE locationTA or cells that the UE enters
 >Timestamp A time stamp when the AMF detects the UE enters this location
UE location trendsAMFMetrics on UE locations.
PDU Session ID (1..max)SMFIdentification of PDU Session.
> Inactivity detection timeSMF, UPFValue of session inactivity timer.
> PDU Session statusSMFStatus of the PDU Session (activated, deactivated).
UE CM state AMFUE connection management state (e.g. CM-IDLE).
UE session behaviour trendsSMF Metrics on UE state transitions (e.g. "PDU Session Establishment", "PDU Session Release").
UE communication trendsSMFMetrics on UE communications.
UE access behaviour trendsAMFMetrics on UE state transitions (e.g. access, RM and CM states, handover).
Depending on the requested level of accuracy, data collection may be provided on samples (e.g. spatial subsets of UEs or UE group, temporal subsets of UE communication information).
The application Id is optional. If the application Id is omitted, the collected UE communication information can be applicable to all the applications for the UE.
Up

6.7.3.3  Output Analytics  p. 200

The NWDAF supporting UE Communication Analytics provides the analytics results to consumer NFs. The analytics results provided by the NWDAF include the UE communication statistics as defined in Table 6.7.3.3-1 or predictions as defined in Table 6.7.3.3-2.
Information Description
UE group ID or UE IDIdentifies 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 defined in clause 5.9.7 of TS 23.501.
UE communications (1..max) (NOTE 1)List of communication time slots.
 > Periodic communication indicator (NOTE 1)Identifies whether the UE communicates periodically or not.
 > Periodic time (NOTE 1)Interval Time of periodic communication (average and variance) if periodic.
Example: every hour
 > Start time (NOTE 1)Start time observed (average and variance)
 > Duration (NOTE 1)Duration of communication (average and variance).
 > Traffic characterizationS-NSSAI, DNN, ports, other useful information.
 > Traffic volume (NOTE 1)Volume UL/DL (average and variance).
 > RatioPercentage of UEs in the group (in the case of a UE group).
Applications (0..max) (NOTE 1)List of applications in use.
 > Application IdIdentification of the application.
 > Start timeStart time of the application.
 > Duration timeDuration interval time of the application.
 > Occurrence ratioProportion for the application used by the UE during requested period.
 > Spatial validityArea where the service behaviour applies. If Area of Interest information was provided in the request or subscription, spatial validity may be a subset of the requested Area of Interest. If a Spatial granularity size was provided in the request or subscription, the number of elements of TAs or cells in the area is smaller than or equal to the Spatial granularity size.
N4 Session ID (1..max) (NOTE 1) (NOTE 2)Identification of N4 Session.
> Inactivity detection timeValue of session inactivity timer (average and variance).
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:
This analytics subset shall only be included if the consumer is SMF.
Information Description
UE group ID or UE IDIdentifies 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 defined in clause 5.9.7 of TS 23.501.
UE communications (1..max) (NOTE 1)List of communication time slots.
 > Periodic communication indicator (NOTE 1)Identifies whether the UE communicates periodically or not.
 > Periodic time (NOTE 1)Interval Time of periodic communication (average and variance) if periodic.
Example: every hour.
 > Start time (NOTE 1)Start time predicted (average and variance).
 > Duration time (NOTE 1)Duration interval time of communication.
 > Traffic characterizationS-NSSAI, DNN, ports, other useful information.
 > Traffic volume (NOTE 1)Volume UL/DL (average and variance).
 > ConfidenceConfidence of the prediction.
 > RatioPercentage of UEs in the group (in the case of a UE group).
Applications (0..max) (NOTE 1)List of applications in use.
 > Application IdIdentification of the application.
 > Start timeStart time of the application.
 > Duration timeDuration interval time of the application.
 > Occurrence probabilityProbability the application will be used by the UE.
 > Spatial validityArea where the service behaviour applies. If Area of Interest information was provided in the request or subscription, spatial validity may be a subset of the requested Area of Interest.
N4 Session ID (1..max) (NOTE 1) (NOTE 2)Identification of N4 Session.
> Inactivity detection timeValue of session inactivity timer (average and variance).
 > ConfidenceConfidence 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:
This analytics subset shall only be included if the consumer is SMF.
The results for UE groups address the group globally. The ratio is the proportion of UEs in the group for a given communication at a given time and duration.
The number of UE communication entries (1..max) is limited by the maximum number of objects provided as part of Analytics Reporting Information. The communications shall be provided by order of time, possibly overlapping.
Depending on the list size limitation, the least probable communications on a given Analytics target period may not be provided.
Up

6.7.3.4  Procedures  p. 201

The NWDAF can provide UE communication related analytics, in the form of statistics or predictions or both, to a 5GC NF.
Reproduction of 3GPP TS 23.288, Fig. 6.7.3.4-1: Procedure for UE communication analytics
Figure 6.7.3.4-1: Procedure for UE communication analytics
Up
Step 1.
5GC NF to NWDAF: Nnwdaf_AnalyticsSubscription_Subscribe (Analytics ID = UE communication, Target of Analytics Reporting=SUPI, Analytics Filter Information = (Application ID, Area of Interest, etc.)).
5GC NF sends a request to the NWDAF for analytics on a specific UE(s), using either Nnwdaf_AnalyticsInfo or Nnwdaf_AnalyticsSubscription_Subscribe service. The analytics type indicated by "Analytics ID" is set to "UE communication". The Target of Analytics Reporting is set to SUPI or an Internal Group Identifier and Analytics Filter may include Application ID and Area of Interest.
Step 2a-b.
NWDAF to AF (Optional): Naf_EventExposure_Subscribe (Event ID, external UE ID, Application ID, Area of Interest).
In order to provide the requested analytics, the NWDAF may subscribe per application communication information, which is identified by Application ID, from AFs for the UE. The Event ID "UE Communication information" as defined in TS 23.502 is used, which indicates communication report for the UE which is requested by the 5GC NF in the step 1. The external UE ID is obtained by the NWDAF based on UE internal ID, i.e. SUPI. In the case of external AF, the NEF translates the requested Area of Interest into a list of geographic zone identifier(s) as described in clause 5.6.7.1 of TS 23.501.
This step is skipped if the NWDAF already has the requested analytics available or has subscribed to the AF.
Step 2c.
NWDAF to SMF: Nsmf_EventExposure_Subscribe (Event ID, SUPI, Application ID).
In order to provide the requested analytics, the NWDAF subscribes via SMF to UPF information on SUPI, providing e.g. Indication of UPF Event Exposure Service and Target subscription UPF Event Id, Filter Information such as Application ID and/or Area of Interest. This is specified in clause 5.8.2.17 of TS 23.501 and clause 4.15.4 of TS 23.502.
Step 2d.
How SMF subscribes to on UPF is defined in clause 5.8.2.17 of TS 23.501 and in clause 4.15.4 of TS 23.502.
Step 2f.
The UPF provides the requested input data to NWDAF. This is specified in clause 4.15.4 of TS 23.502.
Step 2g-h.
NWDAF to AMF: Namf_EventExposure_Subscribe (Event ID, SUPI, Area of Interest).
In order to provide the requested analytics, the NWDAF retrieves one or more of Type Allocation code, UE connection management state, UE access behaviour trends and UE location trends from AMF.
Step 3.
The NWDAF derives requested analytics, in the form of UE communication statistics or predictions or both.
Step 4.
NWDAF to 5GC NF: Nnwdaf_AnalyticsInfo_Request response or Nnwdaf_AnalyticsSubscription_Notify.
The NWDAF provides requested UE communication analytics to the NF, using either Nnwdaf_AnalyticsInfo_Request response or Nnwdaf_AnalyticsSubscription_Notify, depending on the service used in step 1.
Step 5.
If the NF subscribed UE communication analytics at step 1, when, based e.g. on new UPF notifications the NWDAF generates new analytics, the NWDAF notifies the new generated analytics to the 5GC NF.
Up

Up   Top   ToC