[{"name":"S2-2208138","title":"LS from CT WG4: LS on Packet Delay Failure Threshold","source":"CT WG4","contact":"yong yang","contact-id":59744,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 discussed a contribution (C4-224543) which proposes to add Packet Delay Failure Threshold parameter over N4 in PFCP protocol, so that the UPF can use it to determine if to send a QoS Monitoring Failure report. The contribution is based on the following requirement in 3GPP TS 23.503. ' 6.1.3.21 QoS Monitoring to assist URLLC Service ... - if the reporting frequency is periodic, the reporting period; - threshold for reporting packet delay measurement failure; ...' However, during the discussion, it was pointed there is another contradictory requirement in 3GPP TS 23.503 as below: ' - If the Reporting frequency indicates 'event triggered', the Reporting threshold(s) and the minimum waiting time shall also be included in the PCC rule. The Reporting threshold(s) indicates the measurement threshold for each of the included QoS parameter(s) to be measured, i.e. the UL packet delay, DL packet delay or round trip packet delay. When Reporting threshold(s) is exceeded, the UPF shall report to the SMF and the SMF shall report to the PCF or to the AF. If more than one value is received at one given point of time for UL packet delay, DL packet delay or round trip packet delay respectively, the SMF reports the minimum and maximum packet delays to the PCF or the AF. The SMF sends the first report when the Reporting threshold is exceeded and the minimum waiting time is applied for the subsequent report (if the threshold is exceeded after the waiting time). The Reporting threshold(s) may also be used as the threshold for reporting packet delay measurement failure: if no measurement result is received for a delay exceeding this threshold, the UPF shall report to the SMF and the SMF shall report to the PCF or to the AF indicating a packet delay measurement failure. ' CT WG4 assumes that the UPF shall use the threshold for reporting packet delay measurement failure to determine if to send a measurement failure report, since using reporting threshold would lead the AF\/NEF receive only measurement failure reports. CT WG4 also assumes that the threshold for reporting packet delay measurement failure is only corresponding to the round trip measurement. Action: CT WG4 kindly requests SA WG2 to confirm CT WG4's assumptions and update their specification if necessary.","secretary_remarks":"Postponed","agenda_item_sort_order":35,"ainumber":"7.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":10860,"status":"postponed","reservation_date":"2022-09-21 05:20:41","uploaded":"2022-09-22 05:01:53","revisionof":"","revisedto":"S2-2210173","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG3","lsoriginalls":"C4-224636","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208138.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208572","title":"Clarifications for QoS monitoring control","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The following corrections, additions and clarifications are done: A description for the setting of the parameters of the QoS monitoring policy and the actions that are triggered is added to clauses 6.1.3.5, 6.1.3.18, 6.1.3.21. The options when no packet delay measurement result is received for a delay exceeding a threshold and when the PDU Session is released are removed from the Reporting frequency as they don t work. The PCF is removed and the NEF is added to the Target of reporting parameter. An inappropriate reference to 23.502 for Notification Target Address + Notification Correlation ID is removed. The QoS monitoring policy parameter description is simplified and aligned. The UPF related statements are removed.","secretary_remarks":"Postponed. Revised at S2#154 in S2-2210420","agenda_item_sort_order":35,"ainumber":"7.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":10870,"status":"revised","reservation_date":"2022-09-30 07:46:03","uploaded":"2022-09-30 16:00:41","revisionof":"","revisedto":"S2-2210420","release":"Rel-16","crspec":"23.503","crspecversion":"16.12.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":750.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208572.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208573","title":"Clarifications for QoS monitoring control","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Rel-17 mirror CR: Summary of change: The following corrections, additions and clarifications are done: A description for the setting of the parameters of the QoS monitoring policy and the actions that are triggered is added to clauses 6.1.3.5, 6.1.3.18, 6.1.3.21. The options when no packet delay measurement result is received for a delay exceeding a threshold and when the PDU Session is released are removed from the Reporting frequency as they don t work. The PCF is removed and the NEF is added to the Target of reporting parameter. An inappropriate reference to 23.502 for Notification Target Address + Notification Correlation ID is removed. The QoS monitoring policy parameter description is simplified and aligned. The UPF related statements are removed. The Local NEF is appropriate. The duplicated reporting to Local NEF and PCF is described by changing the parameter indication of direct event notification is changed to Direct event notification method","secretary_remarks":"Postponed. Revised at S2#154 in S2-2210421","agenda_item_sort_order":35,"ainumber":"7.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":10880,"status":"revised","reservation_date":"2022-09-30 07:46:04","uploaded":"2022-09-30 16:00:41","revisionof":"","revisedto":"S2-2210421","release":"Rel-17","crspec":"23.503","crspecversion":"17.6.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":751.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208573.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208574","title":"Clarifications for QoS monitoring control","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The following corrections, additions and clarifications are done: UPF related statements are moved from 23.503 to 23.501 and some details are added. The packet delay measurement failure detection and reporting is described. The description of the UPF reporting behavior in sub-clauses 5.33.3.2 and 5.33.3.3 is replaced by a reference to sub-clause 5.33.3.1. The details of the GTP-U Path Monitoring are moved to a different place in the list of bullets.","secretary_remarks":"Noted. Revised at S2#154 in S2-2210422","agenda_item_sort_order":35,"ainumber":"7.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":10890,"status":"revised","reservation_date":"2022-09-30 07:46:05","uploaded":"2022-09-30 16:00:41","revisionof":"","revisedto":"S2-2210422","release":"Rel-16","crspec":"23.501","crspecversion":"16.14.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":3721.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208574.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208575","title":"Clarifications for QoS monitoring control","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Rel-17 mirror CR: Summary of change: The following corrections, additions and clarifications are done: UPF related statements are moved from 23.503 to 23.501 and some details are added. The packet delay measurement failure detection and reporting is described. The description of the UPF reporting behavior in sub-clauses 5.33.3.2 and 5.33.3.3 is replaced by a reference to sub-clause 5.33.3.1. The details of the GTP-U Path Monitoring are moved to a different place in the list of bullets. The duplicated reporting to Local NEF and PCF is described by changing the parameter indication of direct event notification is changed to Direct event notification method","secretary_remarks":"Noted. Revised at S2#154 in S2-2210423","agenda_item_sort_order":35,"ainumber":"7.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":10900,"status":"revised","reservation_date":"2022-09-30 07:46:07","uploaded":"2022-09-30 16:00:41","revisionof":"","revisedto":"S2-2210423","release":"Rel-17","crspec":"23.501","crspecversion":"17.6.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":3722.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208575.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]