[{"name":"S2-2002607","title":"LS from ETSI TC LI: LS to SA WG5 and SA WG2 on 5G Cell ID(s) in the SA WG5 billing system, related to Retained Data regulations","source":"GSMA NG\/GERI","contact":"Gerald McQuaid","contact-id":25351,"tdoctype":"LS in","for":"Action","abstract":"ETSI TC LI thanks SA WG2, and SA WG5 for the reply LS on 5G Cell ID(s) in the SA WG5 billing specifications, and the confirmation on the current SA WG5 charging specifications for 5G access related to the user location information as information which will be available in the CHF CDRs generated for PDU sessions, with the granularity of the Cell Id when reported. In the context of dual connectivity, only the Cell Id of the Master Node is currently specified. ETSI TC LI confirms the need to have the capabilities of reporting the PSCell Id to the AMF, including the PSCell Id in addition to the PCELL in CHF CDRs for AMF. Therefore, ETSI TC LI kindly asks SA WG5 to include such functionality in its investigation on their ongoing Rel-16 work 'Charging AMF in 5G System Architecture Phase 1'. However, based on the recent work developed between SA WG2 and RAN WG3 on PSCell ID and PCELL information, as highlighted by the reply LS from SA WG2 to ETSI TC LI on Reporting all Cell IDs in 5G (S5-195060\/ S2-1908634), SA WG5 indicated that their specifications do not allow the PSCell Id to be available in the Billing system for EPC, since no MME CDR is specified for this context, and the PSCell Id is not propagated beyond the MME. As a result, ETSI TC LI kindly asks that: - Either the MME is a source of information for SA WG5 billing system to provide the available PSCell Ids in this node; - Or PSCell IDs to be made available at the SGW level, as primary source of information to SA WG5 billing for EPC usage. Such availability could be achieved by further development by SA WG2 either from MME or from RAN. In either case, such information source should be reliable and present at the beginning, at change of TAI\/TAU and at the end of session\/call, as such information could be used as possible evidence for Justice. Secondary RAT data usage report with PSCELL IDs could be a solution but only if it is reliable information available at the beginning\/end of call\/session, or at TAI\/TAU change during call\/session. Action: ETSI TC LI kindly asks SA WG2 to take the above request into account on EPC issue. TC LI kindly asks SA WG2 to ensure that the Secondary RAT data Usage Reports at the SGW are always available at the beginning\/end of call\/session and at TA change, in order to populate the 5GC billing system with PSCell IDs.","secretary_remarks":"Postponed S2-2001776 from S2#137E. Postponed","agenda_item_sort_order":12,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10610,"status":"postponed","reservation_date":"2020-03-26 10:57:36","uploaded":"2020-03-27 13:44:13","revisionof":"S2-2001776","revisedto":"S2-2003513","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5, SA WG2","Cc":"TSG SA, SA WG3-LI, RAN WG3","lsoriginalls":"LI(19)P52055","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002607.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002658","title":"LS from RAN WG3: LS on NAS Non delivery for RRC Inactive state","source":"RAN WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 has discussed the scenario of the NG-RAN node receiving a PDU Session Release Command which includes a NAS PDU for a UE which is in RRC_INACTIVE state and therefore not reachable. There are two interpretations of NG-RAN node expected behaviour: Option 1\/ NG-RAN node sends back to AMF a NG UE Context Release Request including the cause 'UE not reachable' which should be interpreted by AMF that the NAS PDU was not delivered, enabling the AMF to tell the SMF as per C4-195487. The NG-RAN node does not trigger the NAS Non Delivery procedure and therefore does not feed back the NAS PDU. Option 2\/ NG-RAN node shall trigger the NAS Non delivery procedure which includes back the undelivered NAS PDU before\/after sending the UE Context Release Request. A majority of companies assume that option 1\/ is the right expected behaviour, especially because the benefit of sending back the NAS PDU is not clear to them in the discussed scenario. However, some other companies think that 1\/ contradicts the following statement in TS 23.501: If the RAN paging procedure, as defined in TS 38.300 [27], is not successful in establishing contact with the UE the procedure shall be handled by the network as follows: - If NG-RAN has at least one pending NAS PDU for transmission, the RAN node shall initiate the AN Release procedure (see TS 23.502 [3], clause 4.2.6,) to move the UE CM state in the AMF to CM-IDLE state and indicate to the AMF the NAS non-delivery. Action: Q1\/ RAN WG3 would like to ask SA WG2 to clarify the meaning of the above statement in TS 23.501 for the considered scenario and clarify whether option 1\/ or option 2\/ is the expected behaviour? Q2\/ In general, does SA WG2 see any other scenario for which the 5GC expects the NAS-non-delivery report in addition to those failed NAS-PDUs in the DL NAS Transport message?","secretary_remarks":"Responses drafted in S2-2002774, S2-2002867 and S2-2002938. Postponed","agenda_item_sort_order":12,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10570,"status":"postponed","reservation_date":"2020-03-26 10:57:38","uploaded":"2020-03-27 15:57:56","revisionof":"","revisedto":"S2-2003531","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"R3-201362","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002658.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002661","title":"LS from RAN WG3: Reply LS on Rel-16 NB-IoT enhancements","source":"RAN WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 thanks SA WG2 for the LS 'Reply LS on Rel-16 NB-IoT enhancements'. RAN WG3 has discussed how to support UE specific DRX for NB-IoT in both EPS and 5GS in RAN WG3 specifications. RAN WG3 would like to provide the following feedback: From RAN WG3 point of view, both options are feasible and have same potential RAN WG3 specification impact. Action: RAN WG3 kindly asks SA WG2, RAN WG2, RAN WG3, CT WG1 (or TSG RAN and TSG CT) to take above feedback into account.","secretary_remarks":"Noted","agenda_item_sort_order":12,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10620,"status":"noted","reservation_date":"2020-03-26 10:57:38","uploaded":"2020-03-27 15:57:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, TSG RAN, TSG CT, RAN WG2, CT WG1","Cc":"TSG SA","lsoriginalls":"R3-201417","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002661.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002770","title":"UE radio capability retrieval","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding the discription in clause 5.4.4.1 on the triggering of UE Radio Capability information retrival.","secretary_remarks":"Approved","agenda_item_sort_order":12,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10630,"status":"agreed","reservation_date":"2020-04-08 21:13:32","uploaded":"2020-04-10 19:30:54","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.9.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI15"}],"crnumber":2241.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200420","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002770.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002771","title":"UE radio capability retrieval","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Adding the discription in clause 5.4.4.1 on the triggering of UE Radio Capability information retrieval.","secretary_remarks":"Approved","agenda_item_sort_order":12,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10640,"status":"agreed","reservation_date":"2020-04-08 21:13:33","uploaded":"2020-04-10 19:30:54","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI15"}],"crnumber":2242.0,"crrevision":"","crcategory":"A","tsg_crp":"SP-200420","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002771.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002774","title":"[DRAFT] Reply LS on NAS Non delivery for RRC Inactive state","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Response LS to RAN WG3 LS on NAS Non delivery for RRC Inactive state","secretary_remarks":"Response to S2-2002658. Noted","agenda_item_sort_order":12,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10580,"status":"noted","reservation_date":"2020-04-08 21:13:36","uploaded":"2020-04-10 19:30:55","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI15"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002774.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002775","title":"Clarification on NAS non delivery","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update 5.3.3.2.5 to describe the functionality.","secretary_remarks":"Noted","agenda_item_sort_order":12,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10650,"status":"noted","reservation_date":"2020-04-08 21:13:36","uploaded":"2020-04-10 19:30:55","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.9.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI15"}],"crnumber":2244.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002775.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002776","title":"Clarification on NAS non delivery","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Update 5.3.3.2.5 to describe the functionality.","secretary_remarks":"Noted","agenda_item_sort_order":12,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10660,"status":"noted","reservation_date":"2020-04-08 21:13:38","uploaded":"2020-04-10 19:30:55","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI15"}],"crnumber":2245.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002776.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002777","title":"Clarification on NAS non delivery","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update 4.13.3.7 to clarify NAS non delievery notification.","secretary_remarks":"Noted","agenda_item_sort_order":12,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10670,"status":"noted","reservation_date":"2020-04-08 21:13:39","uploaded":"2020-04-10 19:30:55","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.9.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI15"}],"crnumber":2191.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002777.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002778","title":"Clarification on NAS non delivery","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Update 4.13.3.7 to clarify NAS non delievery notification.","secretary_remarks":"Noted","agenda_item_sort_order":12,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10680,"status":"noted","reservation_date":"2020-04-08 21:13:40","uploaded":"2020-04-10 19:30:55","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI15"}],"crnumber":2192.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002778.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002779","title":"Transfer Failure Notification Address handling","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update 5.2.2.2.7 to clarify the handling of 'N1N2TransferFailure Notification Target Address' parameter","secretary_remarks":"Noted","agenda_item_sort_order":12,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10690,"status":"noted","reservation_date":"2020-04-08 21:13:41","uploaded":"2020-04-10 19:30:55","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":2193.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002779.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002824","title":"Clarification on PDU session establishment without S-NSSAI indication","source":"Nokia, Nokia Shanghai Bell","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that the S-NSSAI chosen belongs to one of the allowed NSSAI values of the UE (the UE can have >1 default s-NSSAI but these are not necessarily in the allowed NSSAI)","secretary_remarks":"e-meeting r09 agreed. Revised, merging S2-2002849, to S2-2003286.","agenda_item_sort_order":12,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10700,"status":"revised","reservation_date":"2020-04-09 10:43:42","uploaded":"2020-04-09 14:58:01","revisionof":"","revisedto":"S2-2003286","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":2203.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002824.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002849","title":"PDU Session establishment request without S-NSSAI","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that S-NSSAI(s) used for PDU Sessions needs to be part of the Allowed NSSAI.","secretary_remarks":"Merged into S2-2003286","agenda_item_sort_order":12,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10720,"status":"merged","reservation_date":"2020-04-09 13:43:51","uploaded":"2020-04-10 19:32:32","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":2207.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002849.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002865","title":"Keeping bearers in MME during UE temporary release","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Since re-establishment is expected to be very rapid procedure, the short delay after S1 release and before bearer deactivation that is mentioned in Note 4 is made normative MME requirement to highlight its importance and to avoid the impression that the desired MME behaviour expressed in the note would conflict with the normative requirement right above it.","secretary_remarks":"Revision of (noted) S2-2002258 from S2#137E. Noted","agenda_item_sort_order":12,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10730,"status":"noted","reservation_date":"2020-04-09 16:20:23","uploaded":"2020-04-10 12:42:19","revisionof":"S2-2002258","revisedto":"","release":"Rel-16","crspec":23.401,"crspecversion":"16.6.0","workitem":[{"winame":"SAES"},{"winame":"TEI16"}],"crnumber":3594.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002865.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002867","title":"[DRAFT] Reply LS on NAS non-delivery in RRC Inactive state","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3","secretary_remarks":"Response to S2-2002658. Withdrawn","agenda_item_sort_order":12,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10590,"status":"withdrawn","reservation_date":"2020-04-09 16:20:26","uploaded":"2020-04-10 12:42:19","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002867.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002868","title":"NAS PDU delivery failure in RRC Inactive state","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If NAS PDU delivery fails to UE in RRC Inactive state, then the NG-RAN is only expected to initiate AN Release as specified in TS 23.502 clause 4.2.6. It is not exepcted to trigger any NGAP 'NAS non-delivery' procedure to echo back the PDU that could not be delivered. AMF can then send further signaling to SMF as per C4-195487.","secretary_remarks":"Merged into S2-2002935","agenda_item_sort_order":12,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10740,"status":"merged","reservation_date":"2020-04-09 16:20:26","uploaded":"2020-04-10 12:42:19","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.9.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"NR_newRAT-Core"}],"crnumber":2272.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002868.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002869","title":"NAS PDU delivery failure in RRC Inactive state","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: If NAS PDU delivery fails to UE in RRC Inactive state, then the NG-RAN is only expected to initiate AN Release as specified in TS 23.502 clause 4.2.6. It is not exepcted to trigger any NGAP 'NAS non-delivery' procedure to echo back the PDU that could not be delivered. AMF can then send further signaling to SMF as per C4-195487.","secretary_remarks":"Noted","agenda_item_sort_order":12,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10750,"status":"noted","reservation_date":"2020-04-09 16:20:27","uploaded":"2020-04-10 12:42:19","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"NR_newRAT-Core"}],"crnumber":2273.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002869.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002908","title":"Remove SUPI in the form of NSI from stage 2(in R15)","source":"China Telecom","contact":"Jiayifan Liu","contact-id":74811,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove SUPI in the form of an NSI (Network Specific Identifier) related descriptions to align between different specifications.","secretary_remarks":"Noted","agenda_item_sort_order":12,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10760,"status":"noted","reservation_date":"2020-04-10 02:49:07","uploaded":"2020-04-10 03:05:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.9.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2282.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002908.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002914","title":"Clarification for inter-RAT handover from NR to EN-DC","source":"OPPO, China Telecom, Huawei, China Unicom, vivo","contact":"Yang Xu","contact-id":74478,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the sentence below in step-6 in 5GS->EPS Handover procedure. If the UE has indicated support for Dual Connectivity with NR and MME has an Access Restriction for a UE signalled from EPS MM Context or generated by VPLMN policy in the MME, then the MME shall signal Access Restriction for the UE to E-UTRAN as part of Handover Restriction List.","secretary_remarks":"Noted","agenda_item_sort_order":12,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10770,"status":"noted","reservation_date":"2020-04-10 04:12:03","uploaded":"2020-04-10 12:39:15","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2223.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002914.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002935","title":"NAS Non Delivery during AN Release procedure","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - clarify that only when the pending PDU session was sent via DL NAS Transport message, RAN will send the NAS non delivery to AMF, for other cases, RAN does not need to send NAS non delivery. This is clarified in clause 5.3.3.2.5.","secretary_remarks":"Noted","agenda_item_sort_order":12,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10810,"status":"noted","reservation_date":"2020-04-10 06:02:52","uploaded":"2020-04-10 07:05:51","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.9.0","workitem":[{"winame":"NR_newRAT-Core"},{"winame":"5GS_Ph1"}],"crnumber":2290.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002935.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002936","title":"NAS Non Delivery during AN Release procedure","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: - clarify that only when the pending PDU session was sent via DL NAS Transport message, RAN will send the NAS non delivery to AMF, for other cases, RAN does not need to send NAS non delivery. This is clarified in clause 5.3.3.2.5.","secretary_remarks":"Noted","agenda_item_sort_order":12,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10820,"status":"noted","reservation_date":"2020-04-10 06:07:28","uploaded":"2020-04-10 07:05:51","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.4.0","workitem":[{"winame":"NR_newRAT-Core"},{"winame":"5GS_Ph1"}],"crnumber":2291.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002936.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002938","title":"[DRAFT] Reply LS on NAS Non delivery for RRC Inactive state","source":"QUALCOMM Europe Inc. - Italy","contact":"Juan Zhang","contact-id":73274,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3","secretary_remarks":"Response to S2-2002658. Noted","agenda_item_sort_order":12,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10600,"status":"noted","reservation_date":"2020-04-10 06:30:49","uploaded":"2020-04-10 07:05:51","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002938.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003011","title":"[DRAFT] LS Response on NAS Non delivery for RRC Inactive state","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"LS response on NAS non delivery","secretary_remarks":"Response to S2-2002658. Noted","agenda_item_sort_order":12,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10830,"status":"noted","reservation_date":"2020-04-10 09:33:55","uploaded":"2020-04-10 16:00:53","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003011.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003012","title":"NAS non delivery in case of RRC inactivated state","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If the AN can not deliver the NAS message to the UE, the failure information is indicated to AMF via NAS non-delivery report or the corresponding response message.","secretary_remarks":"Noted","agenda_item_sort_order":12,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10840,"status":"noted","reservation_date":"2020-04-10 09:33:55","uploaded":"2020-04-10 16:00:53","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.4.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":2312.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003012.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003057","title":"Use of DNN replacement when updating URSP rules","source":"Samsung, SK Telecom","contact":"Hoyeon Lee","contact-id":62489,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The use of DNN replacement when URSP rules are updated.","secretary_remarks":"Noted","agenda_item_sort_order":12,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10780,"status":"noted","reservation_date":"2020-04-10 10:41:30","uploaded":"2020-04-10 11:08:19","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2266.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003057.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003058","title":"Use of DNN replacement when updating URSP rules","source":"Samsung, SK Telecom","contact":"Hoyeon Lee","contact-id":62489,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The use of DNN replacement when URSP rules are updated.","secretary_remarks":"e-meeting r03 agreed. Revised to S2-2003289.","agenda_item_sort_order":12,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10790,"status":"revised","reservation_date":"2020-04-10 10:44:24","uploaded":"2020-04-10 11:08:19","revisionof":"","revisedto":"S2-2003289","release":"Rel-16","crspec":23.503,"crspecversion":"16.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":456.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003058.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003286","title":"Clarification on PDU session establishment without S-NSSAI indication","source":"Nokia, Nokia Shanghai Bell, Ericsson","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that the S-NSSAI chosen belongs to one of the allowed NSSAI values of the UE (the UE can have >1 default s-NSSAI but these are not necessarily in the allowed NSSAI)","secretary_remarks":"Revision of S2-2002824, merging S2-2002849. Approved","agenda_item_sort_order":12,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10710,"status":"agreed","reservation_date":"2020-04-27 09:08:19","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2002824","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":2203.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200551","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003286.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003289","title":"Use of DNN replacement when updating URSP rules","source":"Samsung, SK Telecom","contact":"Hoyeon Lee","contact-id":62489,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The use of DNN replacement when URSP rules are updated.","secretary_remarks":"Revision of S2-2003058. Approved","agenda_item_sort_order":12,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10800,"status":"agreed","reservation_date":"2020-04-27 09:08:22","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2003058","revisedto":"","release":"Rel-16","crspec":23.503,"crspecversion":"16.4.1","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":456.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200551","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003289.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]