Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.288  Word version:  17.2.0

Top   Top   Up   Prev   Next
1…   4…   5…   5A…   6…   6.1.4…   6.1A…   6.1B…   6.2…   6.2.3…   6.2.6…   6.2.6.3…   6.2.7…   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.15…   7…   8…   9…   10…

 

6.7.4  Expected UE behavioural parameters related network data analyticsWord‑p. 123

6.7.4.1  GeneralWord‑p. 123

The clause 6.7.4 defines how a service consumer learns from the NWDAF the expected UE behaviour parameters as defined in clause 4.15.6.3 of TS 23.502 for a group of UEs or a specific UE.
The service consumer may be an NF (e.g. AMF, UDM, AF), or the OAM.
The consumer of these analytics shall indicate in the request:
  • Analytics ID set to "UE Mobility" or "UE Communication".
  • The Target of Analytics Reporting can be a UE or an Internal Group Identifier.
  • An Analytics target period, which indicates the time period over which the statistics or predictions are requested.
  • Optional maximum number of objects;
  • In a subscription, the Notification Correlation Id and the Notification Target Address are included.
The NWDAF shall notify the result of the analytics to the consumer as indicated in clause 6.7.4.3.
Up

6.7.4.2  Input DataWord‑p. 123

In order to produce "UE Mobility" analytics, the NWDAF collects UE mobility information, UE location trends and/or UE access behaviour trends, as defined in clause 6.7.2.2.
In order to produce "UE Communication" analytics, the NWDAF collects UE communication information, UE communication trends, UE session behaviour trends and/or UE access behaviour trends, as defined in clause 6.7.3.2.
Up

6.7.4.3  Output AnalyticsWord‑p. 124

The analytics results for "UE Mobility" are specified in Table 6.7.2.3-1 and Table 6.7.2.3-2.
The analytics results for "UE Communication" are specified in Table 6.7.3.3-1 and Table 6.7.3.3-2.
Up

6.7.4.4  ProceduresWord‑p. 124

6.7.4.4.1  NWDAF-assisted expected UE behavioural analyticsWord‑p. 124
Reproduction of 3GPP TS 23.288, Figure 6.7.4.4.1-1: NWDAF assisted expected UE behavioural analytics procedure
Up
Step 1.
5GC NF (e.g. AMF, SMF, AF and UDM) to NWDAF: Nnwdaf_AnalyticsInfo_Request (Analytics ID, Target of Analytics Reporting=SUPI) or Nnwdaf_AnalyticsSubscription_Subscribe (Analytics ID, Target of Analytics Reporting =SUPI).
The Analytics ID is set to "UE Mobility" or to "UE Communication" and the consumer request analytics.
Step 2.
If Analytics ID is set to "UE Mobility", the NWDAF collects data from OAM, AMF and/or AF as specified in clause 6.7.2.4 step 2, unless the information is already available.
If Analytics ID is set to "UE Communication", the NWDAF collects data from AMF, SMF and/or AF as specified in clause 6.7.3.4 step 2, unless the information is already available.
Step 3.
The NWDAF derives requested analytics.
Step 4.
NWDAF to 5GC NF: Nnwdaf_AnalyticsInfo_Request response or Nnwdaf_AnalyticsSubscription_Notify.
The NWDAF provides requested Expected UE behaviour to the NF, using either Nnwdaf_AnalyticsInfo_Response or Nnwdaf_AnalyticsSubscription_Notify, depending on the service used in step 1.
Step 5-6.
If the NF subscribed to at step 1, when the NWDAF generates new analytics, it provides the new generated analytics to the NF.
Up

Up   Top   ToC