Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.288  Word version:  18.5.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.19  Relative Proximity Analytics |R18|p. 269

6.19.1  Generalp. 269

Relative Proximity Analytics among UEs provided by NWDAF can be used to assist a consumer NF to more accurately localize a cluster (or a set) of UEs via provisioning statistics or prediction information related to their relative proximity. This analytics type may help the consumer improve the location estimation accuracy of a UE by using proximity information from nearby UEs, or it may help the consumer identify UEs in the vicinity of another UE. Relative proximity information can also be leveraged by NWDAF to provide location information with finer granularity than TA/cell.
The NWDAF provides relativity proximity analytics to a NF (e.g. NEF or AF).
The consumer of these analytics shall indicate in the request or subscription:
  • Analytics ID = "Relative Proximity";
  • Target of Analytics Reporting as defined in clause 6.1.3;
  • Analytics Filter Information:
    • optionally, S-NSSAI and/or DNN
    • an optional Area of Interest;
    • an optional individual or set of direction(s) of interest;
    • an optional number of UEs to be accounted for relative proximity (i.e. the number of UEs for which one UE may report proximity information);
    • optionally, one or several attributes to be accounted for relative proximity (i.e. additional information that can be provided in addition to distance between two UEs): velocity, average speed, orientation, mobility trajectory;
  • Optionally, the list of analytics subsets that are requested among those specified in clause 6.19.3;
  • Optionally, preferred level of accuracy of the analytics;
  • Optionally, preferred level of accuracy per analytics subset (see clause 6.19.3);
  • Optionally, "maximum number of objects" indicating the maximum number of UEs
  • An Analytics target period indicating the time period over which the statistics or predictions are requested.
Up

6.19.2  Input datap. 269

The detailed input data collected by the NWDAF for relative proximity analytics is listed in Table 6.19.2-1, Table 6.19.2-2 and Table 6.19.2-3.
Information Source Description
Per UE informationOAM
> SpeedUE Speed
> OrientationUE Orientation
Information Source Description
Proximity AttributeDCAF / NEFCharacterise a set of UEs in relative proximity.
 > Number of UEsTotal number of UEs in proximity of target UE.
 > TimestampA time stamp of time that the proximity attribute derived.
 > Application ID(s)Identifying the applications(s) providing this information.
 > List of UE IDsUE IDs in proximity of target UE if available.
 > Other attribute(s)Other attributes for the set of UEs i.e. destination, route, average speed, time of arrival.
 > ConfidenceConfidence on relative proximity data.
Information Source Description
UE ID(s)AMFSUPI(s) of individual UE(s).
UE locationAMF, GMLCAbsolute location of an UE.
UE location accuracyGMLCAccuracy of the location estimation.
Velocity estimateLCSUE velocity.
Collision risk distanceAFDerived from the UE connected physical object dimensions e.g. length, width, height.
UE headingAFUE moving direction.
 > Absolute headingHeading of the UE movement with respect to the true north.
 > Relative headingHeading of the UE movement with respect to another UE.
UE trajectoryAFTimestamped UE positions.
 >UE locationGeographical area where the UE is located.
 >Timestamp Time stamp for the UE location.
Up

6.19.3  Output analyticsp. 270

The NWDAF services as defined in the clause 7.2 and 7.3 are used to expose the analytics.
  • Relative proximity statistics information is defined in Table 6.19.3-1.
  • Relative proximity predictions information is defined in Table 6.19.3-2.
Information Description
UE group ID or set of UE IDsIdentifies the UE(s) for which the statistics apply by a list of SUPIs or GPSIs, or a group of UEs by a list of Internal-Group-Ids.
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.
 > UE proximity attributes Observed proximity data. This includes distance between UEs in the group/list and other proximity data as mentioned in clause 6.19.1
 >> relative proximity informationObserved proximity information.
 >> Sampling RatioPercentage of UEs accounted based on proximity criteria.
NOTE 1:
Analytics subset that can be used in "list of analytics subsets that are requested" and "Preferred level of accuracy per analytics subset".
Information Description
UE group ID or set of UE IDsIdentifies the UE(s) for which the statistics apply by a list of SUPIs or GPSIs, or a group of UEs by a list of Internal-Group-Ids.
Time slot entry (1..max)List of predicted time slots.
 >Time slot startTime slot start time within the Analytics target period.
 > DurationDuration of the time slot.
 > UE proximity attributesPredicted proximity data. This includes distance between UEs in the group/list and other proximity data as mentioned in clause 6.19.1.
 >> relative proximity informationPredicted proximity information.
 >> ConfidenceConfidence of this prediction.
 >> Sampling RatioPercentage of UEs accounted based on proximity criteria.
Time To Collision (TTC) information (NOTE 1)
 > Time To CollisionTime until a collision with another UE happens.
 > ConfidenceConfidence of the prediction.
 > AccuracyAccuracy of TTC (dependent on both the UE location accuracy and confidence 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".
Up

6.19.4  Proceduresp. 272

Reproduction of 3GPP TS 23.288, Fig. 6.19.4-1: Procedure for NWDAF providing relative proximity analytics
Up
Figure 6.19.4-1 shows the procedure for NWDAF to derive relative proximity analytics. The steps are described as follows:
Step 1.
The Consumer NF/AF sends a request to the NWDAF for analytics related to relative proximity, using either the Nnwdaf_AnalyticsInfo or Nnwdaf_AnalyticsSubscription service.
The Analytics ID is set to "Relative Proximity". The target for analytics reporting as defined in clause 6.19.1. Analytic filters may be provided as shown in clause 6.19.1.
The Consumer NF/AF can request statistics or predictions or both for a given Analytics target period.
Step 2-5.
If the request is authorized and in order to provide the requested analytics, the NWDAF may subscribe to OAM services to retrieve relevant information to proximity analytics. The NWDAF may collect MDT input data per individual UE from OAM as defined in Table 6.19.2-1.
Step 6-7.
For relative proximity information, if the request is authorized and in order to provide the requested analytics, NWDAF may follow the UE Input Data Collection Procedure via the DCAF. DCAF may collect proximity related input data directly from the UE Application, for NWDAF to determine a list of UEs fulfilling certain proximity criterion.
The NWDAF subscribes to the AF services as above invoking either Nnef_EventExposure_Subscribe for untrusted DCAF or Naf_EventExposure_Subscribe service for trusted DCAF with (Event ID = Relative Proximity, Event Filter information, Target of Event Reporting). The target of event reporting and / or Event Filter information is set according to the target of analytics reporting and / or analytics filters set during the step 1 of the procedure.
Event filters can be defined for relative proximity to indicate to NWDAF on how to process the data from individual UEs to determine the set of UEs to be accounted for relative proximity.
In the case of a trusted DCAF, the NWDAF may provide the Area of Interest, proximity range, predefined geographical area, or other criteria to the DCAF on the resolution of TAIs or any other finer resolution recognizable by the 5GC. In the case of an untrusted DCAF, NEF translates the requested criteria provided as event filter by the NWDAF into geographic zone identifier(s) or other geographic range identifier(s) or geographic direction identifier(s) that act as event filter(s) for the DCAF.
The DCAF may collect the data from individual UEs based on Event Filters indicated by the NWDAF to determine the set of UEs to be accounted for relative proximity before notifying that directly (for trusted DCAF) or via NEF (for untrusted DCAF) to the NWDAF. Input data that may be collected from DCAF can be found in Table 6.19.2-2.
Step 8.
The NWDAF collects input data from AMF as defined in Table 6.19.2-3 via the AMF event exposure service as defined in TS 23.502.
Step 9.
The NWDAF collects input data from GMLC as defined in Table 6.19.2-3 using the Ngmlc_Location service as defined in TS 23.273 and TS 29.515.
Step 10.
The NWDAF collects input data from AF as defined in Table 6.19.2-3 via the AF event exposure service as defined in TS 23.502.
Step 11.
The NWDAF derives requested analytics.
Step 12.
The NWDAF provides requested relative proximity and TTC information as defined in Table 6.19.3-1 and Table 6.19.3-2 to the consumer NF or AF along with the corresponding Validity Period or any Validity Area, Validity Direction of interest or ranging distance, using either the Nnwdaf_AnalyticsInfo_Request response or Nnwdaf_AnalyticsSubscription_Notify, depending on the service used in step 1.
Step 13-15.
If at step 1 the consumer NF or AF has subscribed to receive continuous reporting of relative proximity information, the NWDAF may generate new analytics and, when relevant according to the Analytics target period and Reporting Threshold, provide them along with the corresponding Validity Period (or any Validity Area, Validity Direction of interest or ranging distance) to the consumer NF or AF.
Up

Up   Top   ToC