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:  19.3.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.2H…   6.2H.2.2…   6.2H.2.3…   6.2H.2.4…   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…   6.22…   6.23…   7…   7.4…   7.7…   7.9…   8…   9…   10…   11…   12…   A… 
6.12 Session Management Congestion Control Experience Analytics  6.12.1 General  6.12.2 Input Data  6.12.3 Output Analytics  6.12.4 Procedures 
...

 

6.12  Session Management Congestion Control Experience Analytics |R17|  p. 274

6.12.1  General  p. 274

According to the Session Management Congestion Control (SMCC) mechanisms, i.e. DNN based congestion control defined in clause 5.19.7.3 of TS 23.501 and S-NSSAI based congestion control defined in clause 5.19.7.4 of TS 23.501, the SMF that is applying or has applied the SMCC mechanism does not store any historical information related to which UEs is/was subject to backoff timer settings. Therefore, fairness to apply the SMCC cannot be considered nor guaranteed. For example, among UEs that use a PDU Session associated with S-NSSAI#1, some of them may have experienced the S-NSSAI based high level of congestion control (e.g. receiving NAS SM reject messages with a long backoff timer) while some of the UEs may have experienced the S-NSSAI based low level congestion control (e.g. receiving NAS SM reject messages with a short backoff timer), within a specific period. The backoff timer provided to each UE can vary, e.g. up to 70 hours.
The SMF service consumer may request the NWDAF to provide Session Management Congestion Control Experience (SMCCE) statistical analytics for a specific DNN and/or S-NSSAI. The SMF uses potential congestion condition as a trigger to request the SMCCE analytics from the NWDAF.
The request by the SMF includes mainly the following parameters:
  • Analytics ID = "Session Management Congestion Control Experience".
  • Target of Analytics Reporting: one or more SUPI(s).
  • Analytics Filter Information:
    • DNN and/or S-NSSAI; and
    • optional list of analytics subsets that are requested (see clause 6.12.3);
  • Analytics target period: the time window for which the statistics are requested.
Up

6.12.2  Input Data  p. 274

For the purpose of SMCCE analytics, the NWDAF collects the data as listed in Table 6.12.2-1.
Information Source Description
UE IDSMFSUPI.
SMCC experience for PDU SessionSMFData related to SMCC experience per PDU Session.
 > DNNSMFDNN for the PDU Session that SMF collects Data related to SMCCE.
 > S-NSSAISMFS-NSSAI for the PDU Session that SMF collects Data related to SMCCE.
 > Start time of data collectionSMFStart time of data collection.
 > End time of data collection SMFEnd time of data collection.
> SM NAS request from UE (1..max)SMFInformation on the SM NAS messages that SMF receives from UE for PDU Session during the collection period.
>> Type of SM NAS requestSMFThe type of SM NAS message transmitted by UE (e.g. PDU Session Establishment Request, PDU Session Modification Request, etc.).
>> TimestampSMFA time stamp when SMF receives SM NAS message from UE.
 > SM NAS message from network with backoff timer (1..max)SMFInformation on SMCC applied to UE for PDU Session.
>> Type of SM NAS message from networkSMFThe type of SM NAS message with backoff timer provided to UE (e.g. PDU Session Establishment Reject, PDU Session Modification Reject, PDU Session Release Command, etc.).
>> TimestampSMFA time stamp when SMF sends SM NAS message to UE.
>> Provided backoff timerSMFA value of backoff timer provided to UE.
>> Type of applied SMCCSMFThe type of applied SMCC, i.e. DNN based congestion control or S-NSSAI based congestion control.
As described in Table 6.12.2-1, the NWDAF subscribes to the network data from SMF(s) by invoking Nsmf_EventExposure_Subscribe service (Event ID = Session Management Congestion Control Experience for PDU Session, Target of Event Reporting = one or more SUPI(s), Event Filter information = DNN and/or S-NSSAI and target period).
Up

6.12.3  Output Analytics  p. 275

The NWDAF outputs the SMCCE statistical analytics. The detailed statistical information provided by the NWDAF is defined in Table 6.12.3-1.
Information Description
List of SMCCE Analytics (1..max)
 > DNNDNN that SMCC is applied.
 > S-NSSAIS-NSSAI that SMCC is applied.
 > List of UEs classified based on experience level of SMCCOne, or more than one, of the following lists (SUPI is used to identify a UE).
>> List of high-experienced UEs (NOTE 2)A list of UEs whose experience level of SMCC for specific DNN and/or S-NSSAI is high.
>> List of medium-experienced UEs (NOTE 2)A list of UEs whose experience level of SMCC for specific DNN and/or S-NSSAI is medium.
>> List of low-experienced UEs (NOTE 2)A list of UEs whose experience level of SMCC for specific DNN and/or S-NSSAI is low.
NOTE 1:
The high/medium/low-experience thresholds values are operator defined.
NOTE 2:
This information element is an analytics subset that can be used in "list of analytics subsets that are requested".
Up

6.12.4  Procedures  p. 275

Figure 6.12.4-1 shows the procedure for Session Management Congestion Control Experience Analytics.
Reproduction of 3GPP TS 23.288, Fig. 6.12.4-1: Procedure for Session Management Congestion Control Experience Analytics
Figure 6.12.4-1: Procedure for Session Management Congestion Control Experience Analytics
Up
Step 1.
Consumer SMF requests or subscribes to analytics information for "Session Management Congestion Control Experience" from the NWDAF using either Nnwdaf_AnalyticsInfo or Nnwdaf_AnalyticsSubscription service when the SMF wants to take the analytics information into account for the Session Management Congestion Control to be applied.
The parameters included in the request are described in clause 6.12.1.
Step 2.
If has not already subscribed, the NWDAF sends subscription requests to all the SMFs serving the DNN and/or S-NSSAI as indicated by Analytics Filter Information to collect data related to SMCCE. The SMF that made the request in step 1 can be also one of the data providers.
Step 3.
The SMF(s) provide the collected data to the NWDAF.
Step 4.
The NWDAF derives the requested analytics.
Step 5.
The NWDAF provides the analytics for Session Management Congestion Control Experience to the consumer SMF, using either Nnwdaf_AnalyticsInfo_Request Response or Nnwdaf_AnalyticsSubscription_Notify.
Up

Up   Top   ToC