Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.288  Word version:  17.1.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.13  Redundant Transmission Experience related analytics |R17|Word‑p. 158

6.13.1  General

This clause describes the Redundant Transmission Experience related analytics. This analytics may be used by the SMF to determine whether redundant transmission shall be performed, or (if it had been activated) shall be stopped.
The service consumer may be a NF (e.g. SMF).
The consumer of these analytics may indicate in the request:
  • Analytics ID = "Redundant Transmission Experience".
  • The Target of Analytics Reporting can be a single UE, any UE, or a group of UEs.
  • Analytics Filter Information optionally containing:
    • Area of Interest;
    • S-NSSAI;
    • DNN.
  • An Analytics target period indicates the time period over which the statistics or predictions are requested.
  • Preferred level of accuracy of the analytics;
  • Preferred order of results for the list of Redundant Transmission Experience:
    • ordering criterion: "time slot start" or "Redundant Transmission Experience"; and
    • order: ascending or descending;
  • In a subscription, the Notification Correlation Id and the Notification Target Address are included.
Up

6.13.2  Input DataWord‑p. 159

The NWDAF supporting data analytics on Redundant Transmission Experience shall be able to collect UE mobility information from OAM, 5GC and AFs, and service data from AF, as described in clause 6.7.2.2. In addition, it shall be able to collect the information for PDU session which is established with redundant transmission from NF and OAM. UE mobility information is specified in Table 6.7.2.2-1 and service data from AF related to UE mobility in Table 6.7.2.2-2. In addition, it shall be able to collect performance measurement on user data congestion as specified in Table 6.8.2-1.
Additionally, the NWDAF collects the following input (see Table 6.13.2-1 and Table 6.13.2-2) according to existing measurements defined in clause 5.33.3 of TS 23.501 "QoS Monitoring to Assist URLLC Service".
Information Source Description
UL/DL packet drop GTPOAM (see NOTE 3)UL/DL packet drop rate measurement on GTP path on N3.
UL/DL packet delay GTPUPF (see NOTE 2)End-to-End measurements from UE to UPF.
UL/DL packet delay GTPOAM (see NOTE 3)UL/DL packet delay measurement round trip on GTP path on N3.
NOTE 1:
The information in this Table is provided both as the base to compare with the redundant transmission performance as well as when redundant transmission is enabled.
NOTE 2:
How NWDAF collects the information from UPF is not defined in this specification.
NOTE 3:
Refer to clause 5.1 of TS 28.552 for the performance measurement in NG-RAN and clause 5.4.1 of TS 28.552 for the performance measurement in UPF. In addition, Annex A of TS 28.552 describes various performance measurements, in particular, clause A.61 of TS 28.552 indicates that the measurements on the one way DL and UL delay between PSA UPF and NG-RAN can be used to evaluate and optimize the DL and UL user plane delay performance between 5GC and NG-RAN.
NOTE 4:
The NWDAF data collection request/subscription will not activate the measurements for QoS Monitoring. When QoS Monitoring is activated the measurements are triggered according to existing procedures. When QoS Monitoring is not activated SMF may per configuration activate measurements for QoS Monitoring at least at the same time as it requests Analytics.
 
Information Source Description
DNNSMFData Network Name associated for URLLC service.
UP with redundant transmissionSMFRedundant transmission setup.
Up

6.13.3  Output Analytics

The NWDAF supporting data analytics on Redundant Transmission Experience shall be able to provide Redundant Transmission Experience analytics as defined in Table 6.13.3-1 and Table 6.13.3-2.
Information Description
UE group ID or UE ID, any UEIdentifies a UE, any UE, or a group of UEs.
DNNData Network Name associated for URLLC service.
Spatial validityArea where the Redundant Transmission Experience applies.
If Area of Interest information was provided in the request or subscription, spatial validity should be the requested Area of Interest.
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 (average and variance).
> Redundant Transmission ExperienceRedundant Transmission Experience value.
> RatioPercentage on which UE, any UE, or UE group efficiently use the PDU session with redundant transmission.
 
Information Description
UE group ID or UE ID, any UEIdentifies an UE or, any UE, a group of UEs.
DNNData Network Name associated for URLLC service.
Spatial validityArea where the estimated Redundant Transmission Experience applies.
If Area of Interest information was provided in the request or subscription, spatial validity should be the requested Area of Interest.
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.
> Redundant Transmission ExperiencePredicted Redundant Transmission Experience value during the Analytics target period.
> RatioPercentage on which the UE, any UE, or UE group may efficiently use the PDU session with redundant transmission.
> ConfidenceConfidence of this prediction.
Up

6.13.4  ProceduresWord‑p. 160

6.13.4.1  Analytics Procedure

Figure 6.13.4.1-1 shows the analytics procedure. The NWDAF can provide analytics, in the form of statistics or predictions or both.
Reproduction of 3GPP TS 23.288, Figure 6.13.4.1-1: Redundant Transmission Experience analytics provided to an NF
Up
Step 1.
The analytics consumer sends a request to the NWDAF for analytics on a specific UE, any 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 Redundant Transmission Experience. The NF provides the UE id or Internal Group ID in the Target of Analytics Reporting. Analytics Filter Information optionally contains DNN, S-NSSAI, Area of Interest, etc.
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, and may subscribe to events with SMFs serving PDU Session on URLLC service for notification of redundant transmission related information.
The NWDAF may subscribe the service data from AF(s) by invoking Naf_EventExposure_Subscribe service or Nnef_EventExposure_Subscribe (if via NEF).
The NWDAF collects UE mobility information, packet measurement information and/or redundant transmission related information from OAM, following the procedure captured in clause 6.2.3.2.
This step may be skipped when e.g. the NWDAF already has the requested analytics available.
Step 3.
The NWDAF derives requested analytics.
Step 4.
The NWDAF provide requested UE Presence Pattern analytics to the NF, using either the Nnwdaf_AnalyticsInfo_Request response or Nnwdaf_AnalyticsSubscription_Notify, depending on the service used in step 1.
Step 5-7.
If at step 1, the NF has subscribed to receive notifications for Redundant Transmission Experience 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.
If a service consumer is SMF, the Redundant Transmission Experience analytics can be used to make decision if that redundant transmission shall be performed or (if activated) shall be stopped regarding the PDU session for URLLC service.
Up

Up   Top   ToC