[{"name":"S2-2500037","title":"LS from CT WG3: LS on Clarification of the scope of QME","source":"CT WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"CT WG3 is now working on stage 3 of TEI19_QME and notice that 3GPP TS 23.501 clause 5.45.1 have defined the feature to support QoS monitoring capability configuration and transfer within 5GC. ' Based on configuration, the AMF knows that the QoS monitoring feature is supported by all NG RAN nodes in an area. The AMF shall, when configured, inform the SMF about the support of the QoS monitoring feature by sending the parameter NG RAN QoS monitoring capability during PDU Session establishment, PDU Session modification, Service request and UE mobility procedures. The SMF determines whether QoS monitoring is possible or not for the PDU Session based on whether the NG RAN QoS monitoring capability is received (or not) from the AMF and the QoS monitoring capability of the UPF. QoS monitoring is possible if the SMF has received the NG RAN QoS monitoring capability in the last message received from AMF (i.e. Nsmf_PDUSession_CreateSMContext or Nsmf_PDUSession_UpdateSMContext service operation) and the UPF also supports the QoS monitoring capability. Otherwise, QoS monitoring is not possible for the PDU Session. ' CT WG3 has defined the QoS Monitoring Capability Report for packet delay. CT WG3 would like to ask: Question1: May all the QoS Monitoring mechanism (e.g. RT delay over two QoS flow, Packet Delay Variation, congestion, data rate) to be supported for the QoS monitoring capability report or not?. Action: CT WG3 kindly asks SA WG2 to answer the above question and update the SA WG2 specifications respectively, if necessary.","secretary_remarks":"Responses drafted in S2-2500265, S2-2500304, S2-2500801, S2-2500862, S2-2500995. FInal response in S2-2501312","agenda_item_sort_order":151,"ainumber":"19.25","ainame":"QoS monitoring (TEI19_QME)","tdoc_agenda_sort_order":21700,"status":"replied to","reservation_date":"2024-12-06 13:48:12","uploaded":"2024-12-29 12:18:51","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"C3-246506","lsreply":"S2-2501312","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500037.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500040","title":"LS from CT WG4: Reply LS on RAN support of QoS monitoring capability","source":"CT WG4","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 thanks SA WG2 for the reply LS on RAN support of QoS monitoring capability. CT WG4 has discussed it and has the following answers to SA WG2 questions: {. .} Action: CT WG4 kindly asks SA WG2 to take the above information into account.","secretary_remarks":"CC#4: Postponed","agenda_item_sort_order":151,"ainumber":"19.25","ainame":"QoS monitoring (TEI19_QME)","tdoc_agenda_sort_order":21760,"status":"postponed","reservation_date":"2024-12-06 13:48:12","uploaded":"2024-12-29 12:18:51","revisionof":"","revisedto":"S2-2501363","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG3","lsoriginalls":"C4-245437","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500040.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500264","title":"Clarifications of QoS monitoring capability configuration and transfer within 5GC","source":"China Telecom","contact":"Mengzhen Jian","contact-id":92934,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Following changes are introduced: - Add description to clarify that after the SMF determines whether QoS monitoring is possible or not, the SMF needs to notify the PCF whether the QoS monitoring requests are accepted or rejected. - Add","secretary_remarks":"Confirm CR Revision - CR states 1! r01 agreed.","agenda_item_sort_order":151,"ainumber":"19.25","ainame":"QoS monitoring (TEI19_QME)","tdoc_agenda_sort_order":21770,"status":"noted","reservation_date":"2025-01-11 02:50:53","uploaded":"2025-01-13 03:04:48","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.501","crspecversion":"19.2.1","workitem":[{"winame":"TEI19_QME"}],"crnumber":5911.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500264.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500265","title":"[DRAFT] LS reply on clarification of the scope of QME","source":"China Telecom Corporation Ltd.","contact":"Mengzhen Jian","contact-id":92934,"tdoctype":"LS out","for":"Approval","abstract":"This contribution proposes to send a reply LS on clarification of the scope of QME.","secretary_remarks":"Response to S2-2500037. Merged into S2-2501312","agenda_item_sort_order":151,"ainumber":"19.25","ainame":"QoS monitoring (TEI19_QME)","tdoc_agenda_sort_order":21710,"status":"merged","reservation_date":"2025-01-11 02:55:36","uploaded":"2025-01-13 03:04:48","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"TEI19_QME"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500265.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500304","title":"[DRAFT] Reply LS on CT WG3 LS to SA WG2 on QME","source":"China Mobile Com. Corporation","contact":"Aihua Li","contact-id":58162,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC: -. Attachments: N\/A.","secretary_remarks":"Response to S2-2500037. Merged into S2-2501312","agenda_item_sort_order":151,"ainumber":"19.25","ainame":"QoS monitoring (TEI19_QME)","tdoc_agenda_sort_order":21720,"status":"merged","reservation_date":"2025-01-13 02:21:38","uploaded":"2025-01-14 08:43:34","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500304.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500305","title":"QME clarification on Reply LS on CT WG3 LS to SA WG2","source":"China Mobile","contact":"Aihua Li","contact-id":58162,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarification is made for some QoS Monitoring mechanisms to be supported for QoS monitoring capability report, including UL packet delay, DL packet delay, RT delay for single service data flow, Congestion, Data Rate and\/or Packet Delay","secretary_remarks":"WI Code seems to be AIML_CN, not TEI19_QME! Merged into S2-2501337","agenda_item_sort_order":151,"ainumber":"19.25","ainame":"QoS monitoring (TEI19_QME)","tdoc_agenda_sort_order":21780,"status":"merged","reservation_date":"2025-01-13 02:23:55","uploaded":"2025-01-14 08:43:34","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.501","crspecversion":"19.2.1","workitem":[{"winame":"TEI19_QME"}],"crnumber":5919.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500305.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500800","title":"Discussion on the QME capability issue from CT WG3.","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"discussion","for":"Discussion","abstract":"This paper discusses the CT WG3 LS (S2-2500037) on Clarification of the scope of QME and give the proposal.","secretary_remarks":"Noted in e-mail session","agenda_item_sort_order":151,"ainumber":"19.25","ainame":"QoS monitoring (TEI19_QME)","tdoc_agenda_sort_order":21790,"status":"noted","reservation_date":"2025-01-14 11:15:40","uploaded":"2025-01-14 11:39:03","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"TEI19_QME"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500800.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500801","title":"[DRAFT] Reply LS on Clarification of the scope of QME","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"LS out","for":"Approval","abstract":"Proposes a reply LS on Clarification of the scope of QME","secretary_remarks":"Response to S2-2500037. Merged into S2-2501312","agenda_item_sort_order":151,"ainumber":"19.25","ainame":"QoS monitoring (TEI19_QME)","tdoc_agenda_sort_order":21730,"status":"merged","reservation_date":"2025-01-14 11:15:40","uploaded":"2025-01-14 11:39:03","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"TEI19_QME"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3, CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500801.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500802","title":"Clarification on the Qos monitoring capability","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifying the capabilities in Qos monitoring feature","secretary_remarks":"CC#4: r01 + changes agreed. Revised in CC#4 to S2-2501337, merging S2-2500305 and S2-2500863","agenda_item_sort_order":151,"ainumber":"19.25","ainame":"QoS monitoring (TEI19_QME)","tdoc_agenda_sort_order":21800,"status":"revised","reservation_date":"2025-01-14 11:15:40","uploaded":"2025-01-14 11:39:03","revisionof":"","revisedto":"S2-2501337","release":"Rel-19","crspec":"23.501","crspecversion":"19.2.1","workitem":[{"winame":"TEI19_QME"}],"crnumber":6004.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500802.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.45.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500862","title":"[DRAFT] LS Reply to C3-246506 on clarification of the scope of QME","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"It is proposed to to reply C3-246506 on clarification of the scope of QME","secretary_remarks":"Response to S2-2500037. CC#4: r04 agreed. Revised in CC#4 to S2-2501312, merging S2-2500265, S2-2500304, S2-2500801 and S2-2500995","agenda_item_sort_order":151,"ainumber":"19.25","ainame":"QoS monitoring (TEI19_QME)","tdoc_agenda_sort_order":21740,"status":"revised","reservation_date":"2025-01-14 13:29:37","uploaded":"2025-01-14 15:36:45","revisionof":"","revisedto":"S2-2501312","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"TEI19_QME"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500862.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500863","title":"Clarification of the scope of QME","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the scope of QME as above.","secretary_remarks":"Merged into S2-2501337","agenda_item_sort_order":151,"ainumber":"19.25","ainame":"QoS monitoring (TEI19_QME)","tdoc_agenda_sort_order":21820,"status":"merged","reservation_date":"2025-01-14 13:29:37","uploaded":"2025-01-14 15:36:46","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.501","crspecversion":"19.2.1","workitem":[{"winame":"TEI19_QME"}],"crnumber":6017.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500863.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.45.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500995","title":"[DRAFT] LS on Clarification of the scope of QME","source":"Nokia","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"[draft] LS on Clarification of the scope of QME","secretary_remarks":"Response to S2-2500037. Merged into S2-2501312","agenda_item_sort_order":151,"ainumber":"19.25","ainame":"QoS monitoring (TEI19_QME)","tdoc_agenda_sort_order":21690,"status":"merged","reservation_date":"2025-01-14 16:24:05","uploaded":"2025-01-14 17:15:13","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"TEI19_QME"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500995.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2501312","title":"LS Reply on Clarification of the scope of QME","source":"SA WG2","contact":"Haiyang Sun","contact-id":79579,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3, CT WG4. Attachments: TS 23.501 CR 6004 (S2-252501337)","secretary_remarks":"Revision of S2-2500862r04, merging S2-2500265, S2-2500304, S2-2500801 and S2-2500995. This LS OUT was approved","agenda_item_sort_order":151,"ainumber":"19.25","ainame":"QoS monitoring (TEI19_QME)","tdoc_agenda_sort_order":21750,"status":"approved","reservation_date":"2025-01-25 09:56:21","uploaded":"2025-01-27 09:03:58","revisionof":"S2-2500862","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"TEI19_QME"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2500037","lsto":"CT WG3, CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2501312.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2501337","title":"Clarification on the Qos monitoring capability","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifying the capabilities in Qos monitoring feature","secretary_remarks":"Revision of S2-2500802r01 + changes, merging S2-2500305 and S2-2500863. This CR was agreed","agenda_item_sort_order":151,"ainumber":"19.25","ainame":"QoS monitoring (TEI19_QME)","tdoc_agenda_sort_order":21810,"status":"agreed","reservation_date":"2025-01-25 09:56:35","uploaded":"2025-01-28 08:51:09","revisionof":"S2-2500802","revisedto":"S2-2501922","release":"Rel-19","crspec":"23.501","crspecversion":"19.2.1","workitem":[{"winame":"TEI19_QME"}],"crnumber":6004.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2501337.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.45.1","crsinpack":null,"crsinpacknumber":0}]