[{"name":"S2-2100015","title":"LS from RAN WG3: Reply LS on NAS Non delivery for RRC_INACTIVE state","source":"RAN WG3","contact":"Jiancheng SUN","contact-id":62128,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 thanks SA WG2 for the LS on NAS Non delivery for RRC Inactive state. For the second answer, RAN WG3 further discussed how to inform AMF the non-delivery of the non-PDU session related NAS PDU received in the 'PDU Session Resource Setup' and 'Initial Context Setup'. For 'PDU Session Resource Setup', some companies in RAN WG3 still doubt if the scenario is valid, especially considering the following statement in TS 23.502 section 4.2.3.2: 'If the Service Request procedure is triggered by the Network (as described in clause 4.2.3.3) while the UE is in CM-CONNECTED state, only N2 SM information received from SMF is included in the N2 Request.' Question 1: For a UE in RRC_INACTIVE state, is there any use case for AMF to piggyback a non-PDU session related NAS PDU in PDU SESSION RESOURE SETUP REQUEST? For 'Initial Context Setup', the scenario is confirmed in RAN WG3, but we have not reached the consensus on how to inform AMF the non-delivery of the non-PDU session related NAS-PDU in the 'Initial Context Setup Request'. Here are two candidate solutions: - Solution 1: Use NAS NON DELIVERY INDICATION message to indicate the failure of the NAS delivery. - Solution 2: Use the 'Initial Context Setup failure' to implicitly indicate the failure of the NAS delivery. Question 2: Which solution is preferred to inform AMF the non-delivery of the non-PDU session related NAS-PDU in the 'Initial Context Setup Request'?. Action: RAN WG3 would like to further ask SA WG2 the following questions: Q1\/ For a UE in RRC_INACTIVE state, is there any use case for AMF to piggyback a non-PDU session related NAS PDU in PDU SESSION RESOURE SETUP REQUEST? Q2\/ Which solution is preferred to inform AMF the non-delivery of the non-PDU session related NAS-PDU in the 'Initial Context Setup Request'?","secretary_remarks":"Revision of postponed S2-2009100 from S2#142E. Responses drafted in S2-2100251, S2-2100297, S2-2100676 and S2-2100698. Moved to 4.3. Postponed","agenda_item_sort_order":7,"ainumber":"4.3","ainame":"Items for further discussion after 4.X deadline","tdoc_agenda_sort_order":10880,"status":"postponed","reservation_date":"2021-01-13 10:03:18","uploaded":"2021-01-13 14:55:02","revisionof":"S2-2009100","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"R3-207170","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100015.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100063","title":"On alignment of RACS capability detection with RAN WG3","source":"Nokia, Nokia Shanghai bell, Qualcomm Inc., Ericsson","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The text not aligned with RAN WG3 is removed.","secretary_remarks":"For CC#2. Outgoing LS was created in S2-2101059. Moved to AI 4.3. Postponed","agenda_item_sort_order":7,"ainumber":"4.3","ainame":"Items for further discussion after 4.X deadline","tdoc_agenda_sort_order":10930,"status":"postponed","reservation_date":"2021-01-15 09:50:24","uploaded":"2021-02-18 11:38:27","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.7.0","workitem":[{"winame":"RACS"}],"crnumber":2524.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100063.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100064","title":"On alignment of RACS capability detection with RAN WG3","source":"Nokia, Nokia Shanghai Bell,Qualcomm Inc, Ericsson","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The text not aligned with RAN WG3 is removed.","secretary_remarks":"For CC#2. Outgoing LS was created in S2-2101059. Moved to AI 4.3. Postponed","agenda_item_sort_order":7,"ainumber":"4.3","ainame":"Items for further discussion after 4.X deadline","tdoc_agenda_sort_order":10940,"status":"postponed","reservation_date":"2021-01-15 10:00:27","uploaded":"2021-02-18 11:38:27","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.401","crspecversion":"16.9.0","workitem":[{"winame":"RACS"}],"crnumber":3617.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100064.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100311","title":"Correcting preventing of home routing due to 'any PLMN' requirement","source":"BlackBerry UK Ltd., Rogers Wireless","contact":"John-Luc Bakker","contact-id":37326,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Allow inclusion of the 'any PLMN' entry in the non-3GPP access node selection information to be optional.","secretary_remarks":"Revision of (noted) S2-2004947 from S2#140E. For CC#2. Moved to 4.3. CC#3: An exception granted at CC#2 for this Rel-17 CR, pending acceptance of the CR. Revised to S2-2101061.","agenda_item_sort_order":7,"ainumber":"4.3","ainame":"Items for further discussion after 4.X deadline","tdoc_agenda_sort_order":10860,"status":"revised","reservation_date":"2021-02-16 17:20:18","uploaded":"2021-02-17 21:12:41","revisionof":"S2-2004947","revisedto":"S2-2101061","release":"Rel-16","crspec":"23.501","crspecversion":"16.7.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":2402.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100311.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100698","title":"[DRAFT] Draft NAS Non delivery for RRC inactivated state","source":"Huawei,HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Draft response LS related to the NAS-non-delivery from RAN WG3.","secretary_remarks":"Response to S2-2100015. For CC#2. Moved to AI 4.3. Noted","agenda_item_sort_order":7,"ainumber":"4.3","ainame":"Items for further discussion after 4.X deadline","tdoc_agenda_sort_order":10890,"status":"noted","reservation_date":"2021-02-18 10:16:57","uploaded":"2021-02-18 16:57:04","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100698.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100849","title":"[DRAFT] LS on Correction on QoS monitoring for URLLC","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Notify RAN WG3 that the CR to 23.502 has been returned to SA WG2 and SA WG2 after further discussion concludes that QoS Monitoring reporting frequency is used by RAN to determine the packet delay measurement frequency of the RAN part, and this frequency n","secretary_remarks":"For CC#2. Moved to AI 4.3. NOTED? CC#3b: This remained noted.","agenda_item_sort_order":7,"ainumber":"4.3","ainame":"Items for further discussion after 4.X deadline","tdoc_agenda_sort_order":10920,"status":"noted","reservation_date":"2021-02-18 12:56:48","uploaded":"2021-02-18 16:14:29","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100849.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101021","title":"Incorrect linkage of 'unreachable' to 'lack of paging response'","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Text corrected to indicate that 'unreachable' is not the same as 'lack of paging response'.","secretary_remarks":"Confirm Spec version used - CR states 16.9.0! For CC#2. Moved to AI 4.3. CC#3b: r011 was confirmed as agreed. Revised to S2-2101062.","agenda_item_sort_order":7,"ainumber":"4.3","ainame":"Items for further discussion after 4.X deadline","tdoc_agenda_sort_order":10900,"status":"revised","reservation_date":"2021-02-18 20:55:11","uploaded":"2021-02-18 20:58:45","revisionof":"","revisedto":"S2-2101062","release":"Rel-16","crspec":"23.502","crspecversion":"16.7.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2598.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101021.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101059","title":"[DRAFT] LS on RACS capability detection","source":"SA WG2","contact":"Alessio Casati","contact-id":82456,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3","secretary_remarks":"Created at CC#2. Revised to S2-2101063.","agenda_item_sort_order":7,"ainumber":"4.3","ainame":"Items for further discussion after 4.X deadline","tdoc_agenda_sort_order":10950,"status":"revised","reservation_date":"2021-03-05 08:04:45","uploaded":"2021-03-05 08:31:18","revisionof":"","revisedto":"S2-2101063","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101059.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101061","title":"Correcting preventing of home routing due to 'any PLMN' requirement","source":"BlackBerry UK Ltd., Rogers Communications Canada","contact":"John-Luc Bakker","contact-id":37326,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Allow inclusion of the 'any PLMN' entry in the non-3GPP access node selection information to be optional.","secretary_remarks":"Revision of S2-2100311r02. Approved","agenda_item_sort_order":7,"ainumber":"4.3","ainame":"Items for further discussion after 4.X deadline","tdoc_agenda_sort_order":10870,"status":"agreed","reservation_date":"2021-03-11 07:54:38","uploaded":"2021-03-11 08:21:19","revisionof":"S2-2100311","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"16.7.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":2402.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-210170","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101061.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101062","title":"Incorrect linkage of 'unreachable' to 'lack of paging response'","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Text corrected to indicate that 'unreachable' is not the same as 'lack of paging response'. Stage 2 specifications model UE reachability and Loss of Connectivity as two different Event types that can inform UE unreachability.","secretary_remarks":"Revision of S2-2101021r11. Approved","agenda_item_sort_order":7,"ainumber":"4.3","ainame":"Items for further discussion after 4.X deadline","tdoc_agenda_sort_order":10910,"status":"agreed","reservation_date":"2021-03-11 07:54:42","uploaded":"2021-03-11 08:21:19","revisionof":"S2-2101021","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.7.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2598.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-210243","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101062.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101063","title":"LS on RACS capability detection with S1 and NG handover","source":"SA WG2","contact":"Chris Pudney","contact-id":1122,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3","secretary_remarks":"Revision of S2-2101059r03. Approved","agenda_item_sort_order":7,"ainumber":"4.3","ainame":"Items for further discussion after 4.X deadline","tdoc_agenda_sort_order":10960,"status":"approved","reservation_date":"2021-03-11 07:54:43","uploaded":"2021-03-11 08:21:19","revisionof":"S2-2101059","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101063.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101800","title":"LS from CT WG3: LS on Session Management Policy Data per PLMN","source":"CT WG3","contact":"Apostolos Papageorgiou","contact-id":81926,"tdoctype":"LS in","for":"Action","abstract":"In the procedure for SM Policy Association Establishment (TS 23.502 clause 4.16.4), SA WG2 has specified that in LBO, the V-PCF interacts with the UDR of the VPLMN but the retrieval of data using Nudr_DM_Query\/Subscribe from the UDR (or V-UDR) is specified per subscriber, as per the text highlighted below {. . .} In the LBO case, the Session Management Policy Data at the VPLMN cannot be stored per subscriber, since the subscribers of the HPLMN are not managed by the VPLMN, but the VPLMN can store Session Management Policy Data that are applicable to all the subscribers of a certain HPLMN. Although the above highlighted text could imply that the V-PCF can retrieve subscriber related data (which includes Session Management Policy Data) from the V-UDR, the key of Session Management Policy Data in the UDR is the SUPI. Based on the above, CT WG3 would like to ask the following clarification question to SA WG2: Q1. Can the UDR of the VPLMN store PDU Session policy control data per HPLMN? Q2. Is all the PDU Session policy control subscription information (specified in TS 23.503 Table 6.2-2) supported in the LBO scenario?. Action: CT WG3 kindly asks SA WG2 to provide feedback for questions Q1 and Q2 and update accordingly the specifications as necessary.","secretary_remarks":"CC#2: Response drafted in S2-2101801. Postponed","agenda_item_sort_order":7,"ainumber":"4.3","ainame":"Items for further discussion after 4.X deadline","tdoc_agenda_sort_order":10970,"status":"postponed","reservation_date":"2021-03-03 06:23:14","uploaded":"2021-03-03 06:23:50","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C3-211469","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101800.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101801","title":"[DRAFT] Reply LS on Session Management Policy Data per PLMN","source":"SA WG2","contact":"Chris Pudney","contact-id":1122,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3","secretary_remarks":"Created at CC#2. Response to S2-2101800. WITHDRAWN","agenda_item_sort_order":7,"ainumber":"4.3","ainame":"Items for further discussion after 4.X deadline","tdoc_agenda_sort_order":10980,"status":"withdrawn","reservation_date":"2021-03-05 08:05:57","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"SBIProtoc17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]