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:  18.4.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.21 Movement Behaviour Analytics  6.21.1 General  6.21.2 Input data  6.21.3 Output analytics  6.21.4 Procedures 
...

 

6.21  Movement Behaviour Analytics |R18|  p. 272

6.21.1  General  p. 272

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;
  • 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;
    • 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.
Up

6.21.2  Input data  p. 273

The NWDAF collects the UE location and velocity information within the area of interest from the sources listed in Table 6.21.2-1.
Information Source Description
UE IDAMFSUPI
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
Fine granularity locations (1 …max)LCS (NOTE 1)UE locations
…>TimestampTime information associated with the collected information
…>LCS QoSThe achieved LCS QoS accuracy (see TS 23.273)
…>Location estimateGeographical location or location in local coordinates (as defined in TS 23.032)
…>Velocity estimateSpeed and direction information
…>Indoors/outdoor indicationIndicate the location estimate is indoor or outdoor
…>Age of locationValid period of the location estimate
NOTE 1:
The procedure to collect location data using LCS is described in clause 6.2.12.
Up

6.21.3  Output analytics  p. 273

The output for analytics of movement behaviour provided by NWDAF is defined in Table 6.21.3-1 and Table 6.21.3-2.
Information Description
Applicable AreaA geographical area as defined in TS 23.273 that the analytics applies to.
Time slot entry (1..max)List of time slots during the Analytics target period
 > Time slot startTime slot start within the Analytics target period
 > DurationDuration of the time slot
 > Total number of UEs (NOTE)Total number of UEs in the area of interest
 > Ratio of moving UEs (NOTE)Ratio of moving UEs in the area of interest
 > Average speed (NOTE)Average speed of all UEs in the area of interest
 > Speed threshold (1...max) (NOTE)Threshold utilized to filter the UEs
  >> Number of UEsThe number of UEs whose speed is faster than the speed threshold
  >> RatioPercentage of UEs whose speed is faster than the speed threshold
 > Direction (1…max) (NOTE)Heading directions of the UE flow in the target area, such as north, south, east, west etc.
  >> Number of UEsThe number of UEs in the specific direction
  >> Average speedAverage speed of v in the specific direction
  >> RatioPercentage of UEs in the specific direction
NOTE:
Analytics subset that can be used in "list of analytics subsets that are requested" and "Preferred level of accuracy per analytics subset".
Information Description
Applicable AreaA geographical area as defined in TS 23.273 that the analytics applies to
Time slot entry (1..max)List of time slots during the Analytics target period
 > Time slot startTime slot start within the Analytics target period
 > DurationDuration of the time slot
 > Total number of UEs (NOTE)Total number of UEs in the area of interest
 > Ratio of moving UEs (NOTE)Ratio of moving UEs in the area of interest
 > Average speed (NOTE)Average speed of all UEs in the area of interest
 > Speed threshold (1...max) (NOTE)Threshold utilized to filter the UEs
  >> Number of UEsThe number of UEs whose speed is faster than the speed threshold
  >> RatioPercentage of UEs whose speed is faster than the speed threshold
 > Direction (1..max) (NOTE)Heading directions of the UE flow in the target area, such as north, south, east, west etc.
  >> Number of UEsThe number of UEs in the specific direction
  >> Average speedAverage speed of UEs in the specific direction
  >> RatioPercentage of UEs in the specific direction
ConfidenceConfidence of the prediction
NOTE:
Analytics subset that can be used in "list of analytics subsets that are requested" and "Preferred level of accuracy per analytics subset".
Up

6.21.4  Procedures  p. 274

Figure 6.21.4-1 depicts the procedure for movement behaviour analytics provided by NWDAF.
Reproduction of 3GPP TS 23.288, Fig. 6.21.4-1: "Movement Behaviour" analytics provided by NWDAF
Figure 6.21.4-1: "Movement Behaviour" analytics provided by NWDAF
Up
Step 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.
The Analytics ID is set to "Movement Behaviour". The target for analytics reporting is set to be any UE. 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.
Step 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.
Step 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 to obtain UE's location information.
Step 4.
The NWDAF derives requested analytics.
Step 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.
Up

Up   Top   ToC