Tech-invite  3GPPspecsRELsGlossariesSIP
Info21222324252627282931323334353637384‑5x

full Contents for  TS 23.288  Word version:   16.3.0

Top   Up   Prev   Next
1…   4…   6…   6.2…   6.3…   6.4…   6.5…   6.6…   6.7…   6.7.3…   6.7.4…   6.7.5…   6.8…   6.9…   7…

 

6.7  UE related analyticsWord-p. 34
6.7.1  General
This clause specifies the UE related analytics which can be provided by NWDAF:
  • UE mobility analytics;
  • UE communication analytics;
  • Expected UE behavioural parameters related network data analytics; and
  • Abnormal behaviour related network data analytics.
The NWDAF service consumer may request for these analytics separately, or in a combined way. As an example, an NWDAF service consumer may learn 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, by requesting analytics for both UE mobility (see clause 6.7.2) and for UE communication (see clause 6.7.3).
NOTE:
Possible uses of such analytics is for the AMF to learn about expected UE behaviour to derive appropriate MICO mode configuration, or for an AF to learn about expected UE behaviour to further provision 5GC with appropriate UE parameters.
Up
6.7.2  UE mobility analytics
6.7.2.1  General
NWDAF supporting UE mobility statistics or predictions shall be able to collect UE mobility related information from NF, OAM, and to perform data analytics to provide UE mobility statistics or predictions.
The service consumer may be a NF (e.g. AMF).
The consumer of these analytics may indicate in the request:
  • The Target of Analytics Reporting which is a single UE or a group of UEs.
  • Analytics Filter Information optionally containing:
    • Area of Interest;
    • maximum number of objects.
  • An Analytics target period indicates the time period over which the statistics or predictions are requested.
  • Preferred level of accuracy of the analytics (low/high).
  • In a subscription, the Notification Correlation Id and the Notification Target Address are included.
Up
6.7.2.2  Input Data
The NWDAF supporting data analytics on UE mobility shall be able to collect UE mobility information from OAM, 5GC and AFs. The detailed information collected by the NWDAF could be MDT data from OAM, network data from 5GC and/or service data from AFs:
  • UE mobility information from OAM is UE location carried in MDT data;
  • Network data related to UE mobility from 5GC is UE location information as defined in the Table 6.7.2.2-1;
Information
Source
Description

UE ID
AMF
SUPI
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
Type Allocation code (TAC)
AMF
To indicate the terminal model and vendor information of the UE. The UEs with the same TAC may have similar mobility behavior. The UE whose mobility behavior is unlike other UEs with the same TAC may be an abnormal one.
Frequent Mobility Registration Update
AMF
A UE (e.g. a stationary UE) may re-select between neighbour cells due to radio coverage fluctuations. This may lead to multiple Mobility Registration Updates if the cells belong to different registration areas. 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.

 
  • Service data related to UE mobility provided by AFs is defined in the Table 6.7.2.2-2;
Information
Description

UE ID
Could be external UE ID (i.e. GPSI)
Application ID
Identifying the application providing this information
UE trajectory (1..max)
Timestamped UE positions
>UE location
Geographical area that the UE enters
>Timestamp
A time stamp when UE enters this area

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 location information).
The application Id is optional. If the application Id is omitted, the collected UE mobility information can be applicable to all the applications for the UE.
Up
6.7.2.3  Output AnalyticsWord-p. 35
The NWDAF supporting data analytics on UE mobility shall be able to provide UE mobility analytics to consumer NFs or AFs. The analytics results provided by the NWDAF could be UE mobility statistics as defined in Table 6.7.2.3-1, UE mobility predictions as defined in Table 6.7.2.3-2:
Information
Description

UE group ID or UE ID
Identifies a UE or a group of UEs, e.g. internal group ID defined in TS 23.501, clause 5.9.7, SUPI (see NOTE).
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 (average and variance)
> UE location (1..max)
Observed location statistics
>> UE location
TA or cells which the UE stays
>> Ratio
Percentage of UEs in the group (in the case of an UE group)

 
Information
Description

UE group ID or UE ID
Identifies an UE or a group of UEs, e.g. internal group ID defined in TS 23.501, clause 5.9.7, or SUPI (see NOTE).
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 location (1..max)
Predicted location prediction during the Analytics target period
>> UE location
TA or cells where the UE or UE group may move into
>> Confidence
Confidence of this prediction
>> Ratio
Percentage of UEs in the group (in the case of an UE group)

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 mobility result (i.e. list of (predicted) time slots) to NF service consumer(s) for the UE.
The results for UE groups address the group globally. The ratio is the proportion of UEs in the group at a given location at a given time.
The number of time slots and UE locations is limited by the maximum number of objects provided as input parameter.
The time slots shall be provided by order of time, possibly overlapping. The locations shall be provided by decreasing value of ratio for a given time slot. The sum of all ratios on a given time slot must be equal or less than 100%. Depending on the list size limitation, the least probable locations on a given Analytics target period may not be provided.
Up
6.7.2.4  ProceduresWord-p. 36
The NWDAF can provide UE mobility related analytics, in the form of statistics or predictions or both, to another NF. If the NF is an AF, and when the AF is untrusted, the AF will request analytics via the NEF, and the NEF will then convey the request to NWDAF.
Up
Step 1.
The NF sends a request to the NWDAF for analytics on a specific 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 type of analytics is set to UE mobility information. The NF provides the UE id or Internal Group ID in the Target of Analytics Reporting.
Step 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. This step may be skipped when e.g. the NWDAF already has the requested analytics available.
The NWDAF subscribes the service data from AF(s) in the Table 6.7.2.2-2 by invoking Naf_EventExposure_Subscribe service or Nnef_EventExposure_Subscribe (if via NEF).
The NWDAF collects UE mobility information from OAM, following the procedure captured in clause 6.2.3.2.
NOTE:
The NWDAF determines the AMF serving the UE or the group of UEs as described in clause 6.2.2.1.
Step 3.
The NWDAF derives requested analytics.
Step 4.
The NWDAF provide requested UE mobility 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 mobility analytics provided by NWDAF are defined in clause 6.7.2.3.
Step 5-6.
If at step 1, the NF has subscribed to receive notifications for UE mobility analytics, after receiving event notification from the AMFs, AFs and OAM subscribed by NWDAF in step 2, the NWDAF may generate new analytics and provide them to the NF.
Up

Up   Top   ToC