Content for TS 23.288 Word version: 18.1.0

1… 4… 5… 5A… 6… 6.1.4… 6.1.4.4… 6.1A… 6.1B… 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.2A… 6.2B… 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… 7… 8… 9… 10…

6.7 UE related analytics p. 167

6.7.1 General p. 167

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).

Depending on local regulations, the NWDAF retrieves user consent for the UE with UDM prior to data collection as defined in clause 6.2.2.2 or clause 6.2.2.3. If user consent to collect data is not granted by the UE, the NWDAF rejects/cancels any analytics subscriptions to any of the UE related analytics with target for analytics set to the SUPI or GPSI of that UE. If the target for analytics is either an Internal or External Group Id or a list of SUPIs or "any UE", the NWDAF skips those SUPIs that do not grant user consent for the purpose of analytics or model training.

6.7.2 UE mobility analytics p. 167

6.7.2.1 General p. 167

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, SMF or AF).

The consumer of these analytics may indicate in the request:

Analytics ID = "UE Mobility".
Target of Analytics Reporting: a single UE (SUPI) or a group of UEs (an Internal Group ID);
Analytics Filter Information optionally containing:
- Area of Interest (AOI): restricts the scope of the UE mobility analytics to the provided area;
- Visited Area(s) of Interest (visited AOI(s)): additional filter to only consider UEs that are currently (i.e. now) in the "AOI" and had previously (i.e. in the "Analytics target period") been in at least one of the Visited AOI(s). If this parameter is provided, the Analytics target period shall be in the past (i.e. supported for statistics only);
NOTE 1:
For LADN service, the consumer (e.g. SMF) provides the LADN DNN to refer the LADN service area as the AOI.
An Analytics target period indicates the time period over which the statistics or predictions are requested;

NOTE 2:
For regular analytics scenarios, the Analytics target period is associated with the Analytics Filter Information = AOI, while for the scenario that Analytics ID=UE Mobility and Analytics Filter Information = (AOI and visited AOI(s)), as described in this clause, the Analytics target period is associated with the visited AOI(s) and to obtain the statistics for those UEs that currently reside in the AOI and had previously (i.e. in the "Analytics target period") been in at least one of the Visited AOI(s).
Optionally, maximum number of objects;
Preferred level of accuracy of the analytics;
Preferred order of results for the time slot entries: ascending or descending time slot start;
Optionally, preferred granularity of location information: TA level or cell level; and
In a subscription, the Notification Correlation Id and the Notification Target Address are included.

6.7.2.2 Input Data p. 168

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, UE location trends or UE access behaviour trends, as defined in the Table 6.7.2.2-1;

Table 6.7.2.2-1: UE Mobility information collected from 5GC

Information	Source	Description
UE ID	AMF	SUPI
UE locations (1..max)	AMF	UE positions
>UE location		TA or cells that the UE enters (NOTE)
>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 behaviour. The UE whose mobility behaviour 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.
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 includes either the last known location or the current location, under the conditions defined in Table 4.15.3.1-1 in TS 23.502.

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

Table 6.7.2.2-2: Service Data from AF related to UE mobility

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
NOTE: 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.

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).

6.7.2.3 Output Analytics p. 169

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:

Table 6.7.2.3-1: UE mobility statistics

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

Table 6.7.2.3-2: UE mobility predictions

Information	Description
UE group ID or UE ID	Identifies a UE or a group of UEs, e.g. internal group ID defined in clause 5.9.7 of TS 23.501, 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 (see NOTE 3)
>> Confidence	Confidence of this prediction
>> Ratio	Percentage of UEs in the group (in the case of a UE group)

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 part of Analytics Reporting Information

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.

6.7.2.4 Procedures p. 171

The NWDAF can provide UE mobility related analytics, in the form of statistics or predictions or both, directly 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.

Reproduction of 3GPP TS 23.288, Fig. 6.7.2.4-1: UE mobility analytics provided to an NF

Figure 6.7.2.4-1: UE mobility analytics provided to an NF

Step 1.

The NF sends a request (Analytics ID = UE mobility, Target of Analytics Reporting = UE id or Internal Group ID, Analytics Filter Information = AOI, Analytics Reporting Information= Analytics target period) to the serving NWDAF for analytics information on a specific UE or a group of UEs, using either the Nnwdaf_AnalyticsInfo or Nnwdaf_AnalyticsSubscription service to derive UE mobility information. The NF can request statistics or predictions or both. For LADN service, the NF (i.e. SMF) provides LADN DNN as AOI in the Analytics Filter Information.

If NF wants to obtain the aggregated mobility analytics of those UEs, that currently reside in the AOI and had visited at least one of visited AOI(s) during an Analytics target period, the NF may send a request for UE mobility analytics with Analytics ID = UE mobility, Target of Analytics Reporting = UE group ID or UE ID, Analytics Filter Information = (AOI, visited AOI(s)), Analytics Reporting information = Analytics target period. In this case, the requested mobility analytics is a statistics.

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 the requested UE(s), 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 for the requested UE(s) from AF(s) in the Table 6.7.2.2-2 by invoking Naf_EventExposure_Subscribe service or Nnef_EventExposure_Subscribe (if via NEF) using event ID "UE Mobility information" as defined in TS 23.502.

The NWDAF collects UE mobility information from OAM for the requested UE(s), following the procedure captured in clause 6.2.3.2.

Step 3.

The NWDAF derives requested analytics.

If in step 1 the NWDAF receives analytics subscription/request from NF to obtain the aggregated mobility analytics of those UEs, which currently reside in AOI and had visited at least one of visited AOI(s) during an Analytics target period and if visited AOI(s) and AOI are covered by different NWDAFs, in addition to the data collected in the AOI in step 2, the NWDAF can also obtain UE mobility analytics in one of the visited AOI(s) during the Analytics target period from other NWDAF instance(s) for the requested UE(s). Then the NWDAF supporting analytics aggregation capability derives a UE ID list based on the request from the NF in step 1 and the requested aggregated analytics based on the data collected in the AOI in step 2 and UE mobility analytics in one or more of the visited AOI(s) obtained from the other NWDAF instance(s). UE visited locations in visited AOI(s) and AOI will be included in the aggregated UE mobility analytics.

Step 4.

The NWDAF provides 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.

If in step 1 the NF wants to obtain the aggregated mobility analytics of those UEs, that currently reside in the AOI and had visited at least one of visited AOI(s) during an Analytics target period, the NWDAF will provide the requested aggregated analytics for the UE(s) matching this criteria, i.e. the derived mobility analytics can cover a subset of UEs compared to the Target of Analytics Reporting as provided in step 1.

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.