[{"name":"S2-2003513","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":"ETSI TC LI","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":"Revision of postponed S2-2002607 from S2-138E. Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11530,"status":"noted","reservation_date":"2020-04-29 13:30:23","uploaded":"2020-04-29 13:38:49","revisionof":"S2-2002607","revisedto":"","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":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003513.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003515","title":"LS from SA WG5: LS Reply to LS Reply to LS to SA WG2 Introduction of CHF Address from PCF","source":"SA WG5","contact":"Maryse Gardella","contact-id":68914,"tdoctype":"LS in","for":"Action","abstract":"SA WG5 would like to thank SA WG2 for having considered the description on charging for 5G connection and mobility domain in their TS 23.501 specification. SA WG5 has reviewed the corresponding approved SA WG2 CR and has no specific comment. As requested by SA WG2, SA WG5 would like to provide further clarification on the motivation for the solution of CHF address(es) being provided to AMF by the PCF as part of Access and mobility policy control during registration as follows: At UE initial registration, the step after which the AMF has exchanged with the PCF for Access and mobility policy association has been determined by SA WG5 as the appropriate step for the AMF to interact with a CHF for charging the registration in some scenario. For this reason, the solution would allow the CHF Address(es) to be dynamically allocated by PCF as part of the same procedure and as an alternative of using NRF based selection. Note that CHF(s) to be selected by the AMF at UE registration may be independent from CHF(s) subsequently selected by SMF(s) on a per PDU session basis for UE registered in this AMF. Action: SA WG5 kindly asks SA WG2 to take into account the answer above in order to decide on whether and how to define the feature in their TS 23.503 specification.","secretary_remarks":"Revision of postponed S2-2002609 from S2-138E. Response drafted in S2-2004247. Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11570,"status":"noted","reservation_date":"2020-04-29 13:30:23","uploaded":"2020-04-29 13:38:49","revisionof":"S2-2002609","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG3","lsoriginalls":"S5-197495","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003515.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003521","title":"LS from SA WG3LI: LS on uniqueness of PEI in certain FN-RG configurations","source":"SA WG3LI","contact":"Jeffrey Gray","contact-id":61557,"tdoctype":"LS in","for":"Action","abstract":"SA WG3-LI would like to get some clarification on the following aspects of the uniqueness of PEI in certain FN-RG configurations. SA WG3-LI understands that in many implementations, networks enforce MAC locking such that an FN-RG has to be unique in a network. SA WG3-LI considers an FN-RG to be a UE from a regulatory perspective, per TS 23.316 clause 4.2.6 'UE is replaced by FN-RG', thus all requirements for a 3GPP UE apply to the FN-RG as specified in TS 33.126. SA WG3-LI kindly asks SA WG3 and SA WG2 to consider that when each UE has a globally unique PEI, the ability for the Lawful Interception aspects to operate normally can be standardized by SA WG3-LI. However, if the PEI is not globally unique, this will lead to problems for LI including the potential to deliver interception product for UEs not under warrant. For LI and security procedures in the overall 3GPP system to work as intended, the PEI is required to be trusted and globally unique. SA WG3-LI kindly asks that this be taken into consideration during continuing system design. Action: SA WG3-LI asks SA WG2 and SA WG3 to take the above into account when developing a solution.","secretary_remarks":"Revision of postponed S2-2002623 from S2-138E. Response drafted in S2-2003684. Final response in S2-2004479","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11600,"status":"replied to","reservation_date":"2020-04-29 13:30:23","uploaded":"2020-04-29 13:38:50","revisionof":"S2-2002623","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3","Cc":"","lsoriginalls":"s3i200069","lsreply":"S2-2004479","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003521.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003523","title":"LS from ETSI TC LI: LS on making PSCELL ID available at the SGW of EPC","source":"ETSI TC LI","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"ETSI TC LI thanks SA WG5 for the reply LS and for highlighting the progress on 5G Cell ID(s) in the SA WG5 billing system. The Rel-16 pCR S5-197113 for the draft TS 32.256 '5G connection and mobility domain charging; Stage 2' will help CSPs to comply with regulations that require such information in the CDRs from 5GC. Based on the SA WG5 reply LS (S5-197481), ETSI TC LI kindly asks SA WG2 to make the PSCELL ID available at the SGW in EPC, in addition to the PCELL ID, in order to make it subsequently possible for SA WG5 to specify the SGW CDR accordingly. Action: ETSI TC LI kindly asks SA WG2 to make the PSCELL ID available at the SGW in EPC, in addition to the PCELL ID for Rel-17.","secretary_remarks":"Revision of postponed S2-2002625 from S2-138E. Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11520,"status":"noted","reservation_date":"2020-04-29 13:30:23","uploaded":"2020-04-29 13:38:50","revisionof":"S2-2002625","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG5","Cc":"SA WG3-LI","lsoriginalls":"LI(20)P53048r2","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003523.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003524","title":"LS from CT WG1: LS on service area restriction for CIoT 5GS optimization","source":"CT WG1","contact":"Mahmoud Watfa","contact-id":85785,"tdoctype":"LS in","for":"Action","abstract":"Overall description: CT WG1 would like to seek guidance on the applicability of service area restriction for UEs that use CIoT 5GS optimizations. CT WG1 would like to ask the following question: Is the UE using CP CIoT or UP CIoT optimization allowed to send or receive data in a non-allowed area, including exception data? Action: CT WG1 respectfully requests SA WG2 to provide an answer to the question above.","secretary_remarks":"Revision of postponed S2-2002636 from S2-138E. Responses drafted in S2-2003711 and S2-2004199. Final response in S2-2004440","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10120,"status":"replied to","reservation_date":"2020-04-29 13:30:23","uploaded":"2020-04-29 13:38:50","revisionof":"S2-2002636","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C1-200839","lsreply":"S2-2004440","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003524.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003525","title":"LS from CT WG1: Reply LS on Non-UE N2 Message Services Operations","source":"CT WG1","contact":"Mikael Wass","contact-id":42217,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 thanks SA WG2 for informing CT WG1 of the discussion and decision on documentation of Non-UE N2 Message Service operations - NonUeN2MessageTransfer, NonUeN2InfoSubscribe, NonUeN2InfoUnSubscribe, NonUeN2InfoNotify belonging to Namf_Communication service. CT WG1 agrees that duplicated documentation should be avoided, and therefore CT WG1 intends to address this issue in the Rel-16 version of TS 23.041 as recommended by SA WG2 in a future meeting. Action: CT WG1 asks SA WG2 to take the information provided above into account.","secretary_remarks":"Revision of postponed S2-2002637 from S2-138E. Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11650,"status":"noted","reservation_date":"2020-04-29 13:30:23","uploaded":"2020-04-29 13:38:50","revisionof":"S2-2002637","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"C1-200889","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003525.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003526","title":"LS from CT WG1: LS on the applicability of LADN in an SNPN","source":"CT WG1","contact":"Sang Min Park","contact-id":62105,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 has discussed on the applicability of LADN in an SNPN. Current stage 2 text specifies that LADN is a service provided by the serving PLMN, but nothing is specified for the SNPN case. In clause 5.6.5 of TS 23.501 {...} CT WG1 would like to ask SA WG2 to provide guidance on whether an SNPN can provide LADN service as well. Question. Can LADN service be provided by an SNPN? Action: CT WG1 kindly requests SA WG2 to provide answer to the above question.","secretary_remarks":"Revision of postponed S2-2002639 from S2-138E. Response drafted in S2-2003664. Final response in S2-2004478","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11480,"status":"replied to","reservation_date":"2020-04-29 13:30:23","uploaded":"2020-04-29 13:38:50","revisionof":"S2-2002639","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG1","lsoriginalls":"C1-200994","lsreply":"S2-2004478","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003526.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003527","title":"LS from CT WG1: Reply LS on sending CAG ID","source":"CT WG1","contact":"Ivo Sedlacek","contact-id":78448,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 would like to thank SA WG2 for the LS (S2-2001616\/C1-200252) on Sending CAG ID. SA WG2's LS states: ----------------- Attachments: S2-2001614, S2-2001615 ... 2 Actions ... To CT WG1: Action: Kindly confirm the attached CRs are fine from CT WG1 perspective. ----------------- CT WG1 confirms that the S2-2001614 and S2-2001615 are OK. Action: CT WG1 asks TSG SA and SA WG2 to take the above into consideration.","secretary_remarks":"Revision of postponed S2-2002642 from S2-138E. Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10270,"status":"noted","reservation_date":"2020-04-29 13:30:23","uploaded":"2020-04-29 13:38:50","revisionof":"S2-2002642","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG2","Cc":"RAN WG2, RAN WG3, SA WG3","lsoriginalls":"C1-201027","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003527.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003528","title":"LS from CT WG3: Reply LS on Service on I-NEF Event Exposure","source":"CT WG3","contact":"Yali Yan","contact-id":66362,"tdoctype":"LS in","for":"Action","abstract":"CT WG3 thanks SA WG2 for the reply LS on Service on I-NEF Event Exposure. And would like to provide following feedback including some further questions. In stage 3, the NEF event exposure services are specified in two TSes, i.e. TS 29.122\/29.522 for NEF northbound APIs, and TS 29.591 for NEF southbound APIs. CT WG3 acknowledges SA WG2 that different formats of UE Id are used, i.e. external format (e.g. external group id) in northbound APIs and internal format (e.g. SUPI) in southbound APIs. SA WG2 S2-2001575 states: - NEF Event Exposure is designed for the consumer to subscribe to notifications. But via I-NEF Event Exposure, AMF or SMF is not subscribing to receive I-NEF notifications but configuring a routing address for sending its own notifications by means of subscription on behalf of third party NF (i.e. the NEF). This implies that the I-NEF processing for NEF Event Exposure differs from NEF processing of the same service operation. The above text implies that a subscription service is not used for subscription purpose but for configuration. The I-NEF will receive event notification from its NF service consumer (e.g. AMF, SMF) but not from other NF service provider. CT WG3 have the following questions:. Question 1: Why 'NF ID' is required for the Ninef_EventExposure_Subscribe request? Such NF ID is not included in Nnef_EventExposure_Subscribe operation, also not included in clause 4.15.1 of TS 23.502, is there any specific handling on I-NEF for the NF ID? Question 2: If Q1 is required, is the 'NF ID' an NF service consumer ID or producer ID? Question 3: Why '(Set of) Event ID(s)', 'Target of Event Reporting (SUPI or Internal Group Identifier)' and 'Event Reporting Information' in Ninef_EventExposure_Subscribe request are required for the Ninef_EventExposure_Subscribe operation and what's the I-NEF behaviour upon receipt of these information? Question 4: Is it possible that the target address of I-NEF is locally configured in NFs (e.g. AMF) or retrieved from NRF so that the NFs (e.g. AMF) sends Namf_EventExposure_Notify (or Nsmf_EventExposure_Notify) directly to the I-NEF to skip the Ninef_EventExposure_Subscribe? Question 5: Since the Ninef_EventExposure_Notify is removed in the SA WG2 CR in C3-201029\/S2-2001575, instead the Namf_EventExposure_Notify (or Nsmf_EventExposure_Notify) is sent by I-NEF to the NEF. Is I-NEF pretending to be the NF (e.g. AMF\/SMF)? What is the relationship between I-NEF and NF? Action: CT WG3 kindly asks SA WG2 to answer the above questions and update their specifications if necessary.","secretary_remarks":"Revision of postponed S2-2002645 from S2-138E. Response drafted in S2-2004035. Final response in S22004451","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10210,"status":"replied to","reservation_date":"2020-04-29 13:30:23","uploaded":"2020-04-29 13:38:50","revisionof":"S2-2002645","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"C3-201494","lsreply":"S2-2004451","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003528.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003529","title":"LS from CT WG4: LS on End Marker Indication","source":"CT WG4","contact":"Caixia Qi","contact-id":56676,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 has discussed the support of stage2 requirement on End Marker Indication over N16\/N16a interface, and agreed that there is no need to define the new End Marker Indication, as the (H-)SMF\/UPF can send an End Marker packet every time there is a change of N9 tunnel information. It was also pointed out during the discussion that the new End Marker Indication over N16 would cause backward compatibility problem, as Rel-15 V-SMF changing the V-UPF would never send the End Marker Indication to the Rel-16 H-SMF, while the Rel-16 H-SMF would wait for this indication to send the End Marker packet. It is also desirable to keep the SMF behaviour aligned with H-SMF, i.e. sending an End Marker packet on the old I-UPF\/V-UPF tunnel when switching to a new N3\/N9 tunnel. Action: CT WG4 kindly asks SA WG2 group to take the above information into account and to consider aligning TS 23.502 accordingly.","secretary_remarks":"Revision of postponed S2-2002649 from S2-138E. Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11640,"status":"postponed","reservation_date":"2020-04-29 13:30:23","uploaded":"2020-04-29 13:38:50","revisionof":"S2-2002649","revisedto":"S2-2004768","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C4-201165","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003529.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003530","title":"LS from RAN WG2: LS on Manual CAG ID selection and granularity of UAC parameters for PNI-NPNs","source":"RAN WG2","contact":"Gy\u00f6rgy Wolfner","contact-id":68507,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 understanding is that after manual CAG ID selection by UE NAS the UE AS shall select a cell that supports the manually selected CAG ID in order to perform the registration procedure triggered by UE NAS. RAN WG2 is seeking further guidance on the manual CAG ID selection issue. RAN WG2 has the following questions: Question 1.1; TO: SA WG2; CC: CT WG1: If a UE performs manual CAG selection and a successful registration, then whether the UE shall stay on cells supporting the manually selected CAG ID in RRC_CONNECTED state especially in the case when after registration the Allowed CAG List in the UE does not contain the manually selected CAG ID? Question 1.2; TO: SA WG2; CC: CT WG1 Shall a UE prioritize for cell reselection the cells supporting the manually selected CAG ID over other suitable cells that do not support the manually selected CAG ID after a successful registration? Question 1.3; TO: CT WG1: It is RAN WG2 understanding that the UE NAS provide the manually selected CAG ID to UE AS. Is the manually selected CAG ID provided as part of the allowed CAG list, or as a separate element? Although at least one operator has indicated that UAC Parameters should also specify CAG ID, to date there is no agreement in RAN WG2 on the required granularity of UAC parameters broadcasted in a cell in case of PNI-NPNs with multiple CAG IDs for the same PLMN. More specifically whether it is sufficient to broadcast the Unified Access Control (UAC) parameters per PLMN or there is need to broadcast CAG ID specific configuration of UAC parameters. RAN WG2 observed that SA WG2 has specified in TS23.501 Section 5.30.3.4 that 'In order to prevent access to NPNs for authorized UE(s) in case of network congestion\/overload, existing mechanisms defined for Control Plane load control, congestion and overload control in clause 5.19 can be used, as well as the access control and barring functionality described in clause 5.2.5, or Unified Access Control using the access categories as defined in TS 24.501 [47] can be used'. RAN WG2 was not able to conclude whether this means that using the operator-defined access categories with access category criteria type set to the S-NSSAI used for PNI-NPN is sufficient to provide CAG specific access control. Question 2.1; TO: SA WG1: Is there a requirement to enable PNI-NPN (CAG ID) specific access control in cells that are shared among PNI-NPNs belonging to the same PLMN? Question 2.2; TO: CT WG1, SA WG1: If there is a requirement to enable PNI-NPN (CAG ID) specific access control in cells that are shared among PNI-NPNs belonging to the same PLMN, then is it sufficient to broadcast the Unified Access Control (UAC) parameters per PLMN (assuming that using the operator-defined access categories with access category criteria type set to the S-NSSAI used for PNI-NPN is sufficient to provide CAG specific UAC) or there is need to enable the broadcast of CAG ID specific configuration of UAC parameters?. Action: RAN WG2 respectfully asks CT WG1, SA WG1, and SA WG2 to reply the above questions.","secretary_remarks":"Revision of postponed S2-2002656 from S2-138E. Response drafted in S2-2003723. Final response in S2-2004335","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10310,"status":"replied to","reservation_date":"2020-04-29 13:30:23","uploaded":"2020-04-29 13:38:50","revisionof":"S2-2002656","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, SA WG1, SA WG2","Cc":"RAN WG3","lsoriginalls":"R2-2002417","lsreply":"S2-2004335","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003530.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003531","title":"LS from RAN WG3: LS on NAS Non delivery for RRC Inactive state","source":"RAN WG3","contact":"Philippe Godin","contact-id":68843,"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":"Revision of postponed S2-2002658 from S2-138E. Response drafted in S2-2003805. Final response in S2-2004452","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11540,"status":"replied to","reservation_date":"2020-04-29 13:30:23","uploaded":"2020-04-29 13:38:50","revisionof":"S2-2002658","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"R3-201362","lsreply":"S2-2004452","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003531.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003535","title":"LS from CT WG1: LS on manipulation of CAG Information element by a VPLMN","source":"CT WG1","contact":"Kundan Tiwari","contact-id":81849,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 has discussed a scenario in which a VPLMN can manipulate CAG information list, e.g. to keep the UE registered to the VPLMN although according to the updated CAG information list from the UDM other VPLMN can be selected. An example of this is given below. CT WG1 seeks guidance from SA WG2 how to avoid VPLMN manipulating the CAG information List. 1. A UE first registers to a VPLMN 1 as only VPLMN 1 is available at the location. The country also has VPLMN 2, which is higher priority than VPLMN 1 for the user. 2. The VPLMN 1 manipulates CAG information list received from the HPLMN or send a manipulated CAG information list even when the VPLMN did not receive the CAG information from HPLMN. In the manipulated CAG information list, the VPLMN sets the indication that the UE can access the 5GS of VPLMN 2 via a CAG Cell only. The VPLMN 1 sends this to the UE. 3. The UE once receiving this information shall never camp on the non-CAG cell of the VPLMN 2. In this way, the VPLMN 1 will keep the UE to its PLMN although higher priority PLMN is available in the country. Action: CT WG1 ask SA WG2 to provide a guidance to solve the above scenario.","secretary_remarks":"Response drafted in S2-2003600, S2-2003641 and S2-2004261. Final response in S2-2004453","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10340,"status":"replied to","reservation_date":"2020-04-29 13:30:23","uploaded":"2020-04-29 13:38:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG3","lsoriginalls":"C1-202617","lsreply":"S2-2004453","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003535.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003536","title":"LS from CT WG1: Reply LS on Non-UE N2 Message Services Operations","source":"CT WG1","contact":"Peter Sanders","contact-id":33850,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 has earlier replied to SA WG2's LS from CT WG1-122e in C1-200889 in which CT WG1 stated its intention to address the issue in the Rel-16 version of TS 23.041, as recommended by SA WG2, in a future meeting. CT WG1 would like to draw SA WG2's attention to the Namf_Communication_NonUeN2MessageTransfer service operation as specified in 3GPP TS 23.502 subclause 5.2.2.2.17 in which the following IEs are missing from the optional input elements: Send Write-Replace-Warning-Indication IE or Send Stop-Warning-Indication IE. If the CBCF includes the Send Write-Replace-Warning-Indication IE in a Write-Replace-Warning-Request-NG-RAN or the Send Stop-Warning-Indication IE in a Stop-Warning-Request-NG-RAN, then the AMF is requested to use the Namf_Communication_NonUeN2InfoNotify service operation to notify a particular event towards the CBCF that has subscribed for the specific information, specifically for the current NonUeN2MessageTransfer service operation. Action: CT WG1 asks SA WG2 to take the information provided above into account and add the missing IEs to the optional input elements of the Namf_Communication_NonUeN2MessageTransfer service operation.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11660,"status":"noted","reservation_date":"2020-04-29 13:30:23","uploaded":"2020-04-29 13:38:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"C1-202663","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003536.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003537","title":"LS from CT WG1: LS on security context for 5GC to EPC mobility","source":"CT WG1","contact":"Lin Shu","contact-id":43310,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 has discussed the NAS security context used for EPC interworking. For a UE operating in the single-registration mode which performs idle mode mobility from 5GC to EPC and initiates a TAU procedure, currently as per CT WG1 NAS protocol in TS 24.501, the UE shall always use the current 5G NAS security context to protect the TAU request message, regardless whether the network supports N26 interface or not. However, CT WG1 observed below security requirement in TS 33.501 subclause 8.7 that the UE shall use available EPS NAS security context if it operates in the single-registration mode in a network without N26 interface: 'When the UE supports single-registration mode and network supports interworking procedure without N26 interface: - For mobility from 5GC to EPC, if the UE has a current EPS NAS security context, the UE shall start using the EPS security context as defined in TS 33.401 [10].' Hence, misalignment exists between CT WG1 NAS protocol and SA WG3 security requirement on the use of NAS security context for idle mode mobility from 5GC to EPC for UEs operating in the single-registration mode in a network without N26 interface.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10060,"status":"noted","reservation_date":"2020-04-29 13:30:23","uploaded":"2020-04-29 13:38:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG2","lsoriginalls":"C1-202666","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003537.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003538","title":"LS from CT WG1: Reply LS on Manual CAG ID selection and granularity of UAC parameters for PNI-NPNs","source":"CT WG1","contact":"Vishnu Preman","contact-id":75279,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 would like to thank RAN WG2 for the questions for clarification on the manual CAG selection. As CT WG1 is responsible for the stage 2 work for NAS IDLE mode procedures, including manual CAG selection and the network selection, CT WG1 thinks that it will be appropriate for CT WG1 to reply to Questions1.2. Question 1.2; TO: SA WG2; CC: CT WG1 Shall a UE prioritize for cell reselection the cells supporting the manually selected CAG ID over other suitable cells that do not support the manually selected CAG ID after a successful registration? - Answer 1.2: No. Question 1.3; TO: CT WG1: It is RAN WG2 understanding that the UE NAS provide the manually selected CAG ID to UE AS. Is the manually selected CAG ID provided as part of the allowed CAG list, or as a separate element? - Answer 1.3: Manually selected CAG ID will be provided as a separate element. Please find the attached CR with the solution. Question 2.2; TO: CT WG1, SA WG1: If there is a requirement to enable PNI-NPN (CAG ID) specific access control in cells that are shared among PNI-NPNs belonging to the same PLMN, then is it sufficient to broadcast the Unified Access Control (UAC) parameters per PLMN (assuming that using the operator-defined access categories with access category criteria type set to the S-NSSAI used for PNI-NPN is sufficient to provide CAG specific UAC) or there is need to enable the broadcast of CAG ID specific configuration of UAC parameters? - Answer 2.2; As this question is dependent on service requirements which do not exist yet, this question can be answered only if and when the service requirements are specified by SA WG1.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10280,"status":"noted","reservation_date":"2020-04-29 13:30:23","uploaded":"2020-04-29 13:38:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"RAN WG3, SA WG1, SA WG2","lsoriginalls":"C1-202846","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003538.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003539","title":"LS from CT WG1: LS on manual CAG selection","source":"CT WG1","contact":"Sung Hwan Won","contact-id":70307,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 would like to thank SA WG1 for answering to the questions in the previous LS and providing the following stage 1 requirement. The 5G system shall support a mechanism for a PLMN to control whether a user of a UE can manually select a non-public network hosted by this PLMN that the UE is not authorized to select automatically. Based on the requirement, CT WG1 agreed a CR attached. CT WG1 would like to highlight the following note in the CR. Editor's note [Vertical_LAN; CR# 0499]: RAN WG2 needs to confirm whether there will be modification in the radio interface in order to enable a CAG cell's broadcasting that the PLMN allows a user to manually select a CAG-ID supported by the CAG cell.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10290,"status":"noted","reservation_date":"2020-04-29 13:30:23","uploaded":"2020-04-29 13:38:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"SA WG1, SA WG2","lsoriginalls":"C1-202927","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003539.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003540","title":"LS from CT WG1: PAP\/CHAP and other point-to-point protocols usage in 5GS","source":"CT WG1","contact":"Osama Lotfallah","contact-id":84634,"tdoctype":"LS in","for":"Action","abstract":"During session management procedure, the UE and the network can exchange certain information using protocol configuration options (PCO) or extended protocol configuration options (ePCO). The following point-to-point protocols are defined in TS 24.008 as (e)PCO parameters which can be exchanged between the UE and the network during GPRS and EPS session management procedure: - C021 Link Control Protocol (LCP) - C023 Password Authentication Protocol (PAP) - 8021 IP Control Protocol (IPCP) - C223 Challenge Handshake Authentication Protocol (CHAP) Question: Are above point-to-point protocols supported in 5GS (i.e. Rel-15 and\/or Rel-16) as (e)PCO parameters or to be supported in the near future (i.e. Rel-17)?. Action: CT WG1 kindly ask SA WG2 to provide an answer to the above question.","secretary_remarks":"Response drafted in S2-2004196. Final response in S2-2004481","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11690,"status":"replied to","reservation_date":"2020-04-29 13:30:23","uploaded":"2020-04-29 13:38:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG3, CT WG3, CT WG4","lsoriginalls":"C1-202933","lsreply":"S2-2004481","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003540.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003541","title":"LS from CT WG3: LS on subscription to V2X services","source":"CT WG3","contact":"Xiaoyun Zhou","contact-id":77294,"tdoctype":"LS in","for":"Action","abstract":"As defined in clause 5.5 of TS 23.287, c) the list of the PLMNs where the UE is authorized to perform V2X communication over PC5 reference point. For each PLMN in the list, the RAT(s) over which the UE is authorized to perform V2X communications over PC5 reference point; and d) PC5 QoS parameters as defined in clause 5.4.2 used by NG-RAN, are provided by the UDR to the PCF during the UE Policy Association Establishment procedure and UE Policy Association Modification procedure using Nudr service for Data Set 'Policy Data' and Data Subset 'Policy Set Entry'. If the subscription information provided to the PCF from UDR is changed (e.g., PC5 QoS related parameters, the list of PLMNs where the UE is authorized to perform V2X communication over PC5 reference point), the PCF initiates the UE Configuration Update procedure. As defined in clause 6.1.2.2.2 of TS 23.503, - during Initial Registration, the (H-)PCF retrieves the list of PSIs and its content stored in the (H-)UDR for this SUPI while the V-PCF (in the roaming scenario) retrieves the list of PSIs and its content stored in the V-UDR for the PLMN ID of this UE (alternatively, the V-PCF can have this information configured locally). - the (H-)PCF maintains the latest list of PSIs delivered to each UE as part of the information related to the Policy Association until the UE policy association termination request is received from the AMF. Then the (H-)PCF stores the latest list of PSIs and its contents in the (H-)UDR using the Nudr_DM_Update including DataSet 'Policy Data' and Data Subset 'Policy Set Entry'. CT WG3 would like to ask SA WG2 following questions related to the list of PSIs stored in the Policy Set Entry: Q1: If there is no PSI stored in the Policy Set Entry, how does the PCF create the related V2X policies for the V2X UE? (e.g, first V2X UE registration, where the V2X UE may not report any PSI)? Is there any subscription information outside of the Policy Set Entry for the PCF authorization in the UDR? Q2: As there is no procedure to define that the V2X UE reports the PSI during the initial registration, why does the H-PCF need to store the V2X Policy for the V2X UE in the UDR? Q3: If the PCF updates the V2X Policy for the V2X UE based on the changes of the subscription information which UDR data set stores the above referred subscription information?. Action: CT WG3 asks SA WG2 to answer above questions and update their specification if necessary.","secretary_remarks":"Response drafted in S2-2003908. Final response in S2-2004475","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11360,"status":"replied to","reservation_date":"2020-04-29 13:30:24","uploaded":"2020-04-29 13:38:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"C3-202347","lsreply":"S2-2004475","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003541.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003542","title":"LS from CT WG3: LS on Clarification of Support of Frame Routing Feature","source":"CT WG3","contact":"Xiaoyun Zhou","contact-id":77294,"tdoctype":"LS in","for":"Action","abstract":"As defined in clause 5.6.14 of TS 23.501: Framed Routing information is provided by the SMF to the UPF (acting as PSA) as part of Packet Detection Rule (PDR, see clause 5.8.2.11.3) related with the network side (N6) of the UPF. The actual ranges of IPv4 address \/ IPv6 Prefixes corresponding to a Framed Route may be provided to the SMF by the DN-AAA server as part of PDU Session Establishment authentication\/authorization by a DN-AAA server (as defined in clause 5.6.6). The IPv4 address \/ IPv6 Prefix allocated to the UE as part of the PDU Session establishment (e.g. delivered in NAS PDU Session Establishment Accept) may belong to one of the Framed Routes associated with the PDU Session or may be dynamically allocated outside of such Framed Routes. The actual ranges of IPv4 address \/ IPv6 Prefixes corresponding to a Framed Route may be defined in the subscription data associated with a (DNN, S-NSSAI) received by the SMF from the UDM (Session Management Subscription data defined in Table 5.2.3.3.1-1 of TS 23.502 [3]) If PCC applies to the PDU Session, at PDU Session establishment the SMF reports to the PCF the Framed Routes corresponding to the PDU Session. In this case, in order to support session binding, the PCF may further report to the BSF the Framed Routes corresponding to the PDU Session. CT WG3 would like to ask SA WG2 following questions: Q1: If the SMF receives the Framed Routes both from the DN-AAA and UDM, which value shall be reported by the SMF to the PCF? Q2: Is it possible that the UDM or DN-AAA updates the Framed Routes during the lifetime of the PDU session? Q3: If answer to Q2 is yes, whether the SMF needs to report the updated Framed Routes to the PCF and how? Q4: What's the policy control functionality SA WG2 requires related to Framed Routing support function? E.g. Is it (only) the ability to provide dynamic services for the devices behind the UE's?. Action: CT WG3 asks SA WG2 to answer above questions and update their specification if necessary.","secretary_remarks":"Response drafted in S2-2003657 and S2-2003885. Final response in S2-2004456","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10550,"status":"replied to","reservation_date":"2020-04-29 13:30:24","uploaded":"2020-04-29 13:38:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"C3-202350","lsreply":"S2-2004456","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003542.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003543","title":"LS from CT WG3: LS on Network Area Information in BDT Policy","source":"CT WG3","contact":"Yali Yan","contact-id":66362,"tdoctype":"LS in","for":"Action","abstract":"CT WG3 analysed the recent changes in SA WG2 TSs to finalize work on eNA and xBDT work items and would like to clarify usage of a Network Area Information related to background data transfer policy negotiations. {...} CT WG3 asks SA WG2 to clarify the following questions: Q1: Is the network area information part of background data transfer policy or not? Q2: If the answer of Q1 is yes, is the network area information in the AF request the same as the network area information in each background data transfer policy, as defined in clause 6.1.2.4 of TS 23.503? During the BDT warning notification, do the list of all candidate BDT policies which are sent to the AF apply to the same network area information in the AF request, as defined in clause 6.1.2.4 of TS 23.503?. Action: CT WG3 kindly asks SA WG2 to answer above questions and update their specifications if necessary.","secretary_remarks":"Response drafted in S2-2004250. Final response in S2-2004460","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10670,"status":"replied to","reservation_date":"2020-04-29 13:30:24","uploaded":"2020-04-29 13:38:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C3-202420","lsreply":"S2-2004460","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003543.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003544","title":"LS from CT WG3: LS on Clarification on eNA","source":"CT WG3","contact":"Yali Yan","contact-id":66362,"tdoctype":"LS in","for":"Action","abstract":"As defined in TS 23.288, the network slice instance (NSI ID) associated with the S-NSSAI is introduced as optional parameter in clause 6.3 for slice load level analytics type and observed service experience analytics type in clause 6.4, since the network may deploy multiple network slice instances for one S-NSSAI, depending on the deployment choices of the operator. Clause 6.1.3 of TS 23.288 specifies the maximum number of objects and maximum number of SUPIs as two parameters of Analytics Reporting Information. {...} CT WG3 asks SA WG2 to clarify the following questions: Q1: Is the network slice instance also applicable for other analytics types which may provide the S-NSSAI during the analytics request, e.g. QoS Sustainability Analytics? Q2: Does the maximum number of objects and\/or the maximum number of SUPIs can be provided as both Analytics Reporting Information and Analytics Filter Information in one Nnwdaf_AnalyticsSubscription_Subscribe or Nnwdaf_AnalyticsInfo_Request request sent from the NF consumer to the NWDAF? Action: CT WG3 kindly asks SA WG2 to answer above questions and update their specifications if necessary.","secretary_remarks":"Response drafted in S2-2004327. Final response in S2-2004482","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11720,"status":"replied to","reservation_date":"2020-04-29 13:30:24","uploaded":"2020-04-29 13:38:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C3-202507","lsreply":"S2-2004482","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003544.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003545","title":"LS from CT WG3: LS on Access Type Report for a MA PDU session","source":"CT WG3","contact":"Fuencisla Garcia Azorero","contact-id":43873,"tdoctype":"LS in","for":"Action","abstract":"TS 23.503 v16.4.1 specifies for the Access Type change event that: If an AF requests the PCF to report on the change of Access Type, the PCF shall provide the corresponding Policy Control Request Trigger to the SMF to enable the report of the Change in Access Type to the PCF. The PCF shall, upon reception of information about the Access Type the user is currently using and upon indication of change of Access Type, notify the AF on changes of the Access Type and forward the information received from the SMF to the AF. The change of the RAT Type shall also be reported to the AF, even if the Access Type is unchanged. For MA PDU Session the Access Type information may include two Access Type information that the user is currently using. To ensure CT WG3 is properly capturing the requirement above, CT WG3 would like to ask SA WG2 following questions: Q1: Is it required that additional information about how all or subset of the traffics are steered on the available access(s) is provided together with the access type(s)? Q2: If the reply to Q1 is yes, which kind of information should be reported? (E.g., an indication of whether only one of the accesses is applied for the requested SDF, or information about the steering method.) Q3: What's the foreseen applicability of the received event report by the receiver application?. Action: CT WG3 kindly asks SA WG2 to answer above questions and update their specification if necessary.","secretary_remarks":"Response drafted in S2-2003665 and S2-2003691. Final response in S2-2004483","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11800,"status":"replied to","reservation_date":"2020-04-29 13:30:24","uploaded":"2020-04-29 13:38:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C3-202512","lsreply":"S2-2004483","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003545.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003546","title":"LS from CT WG3: LS on clarification on TSN for Vertical_LAN","source":"CT WG3","contact":"Xiaoyun Zhou","contact-id":77294,"tdoctype":"LS in","for":"Action","abstract":"As defined in clause 5.28.1 of TS 23.501, when the SMF detects a new 5GS Bridge, the SMF reports the 5GS Bridge information to the PCF and then the PCF reports the 5GS Bridge information to the TSN AF. After that, in order to retrieve port management information of the 5GS Bridge and provision the TSCAI, the TSN AF sends the request the PCF. CT WG3 has following questions to ask SA WG2: 1) What's the criteria in the PCF to select the TSN AF that receives the first Npcf_PolicyAuthorization_Notify service operation? Is it bound to the 5GS Bridge Identity handling the PDU session? Is there only one TSN AF shall be selected for all the PDU sessions corresponding to a 5GS bridge? 2) After receiving the first Npcf_PolicyAuthorization_Notify service operation with new 5GS Bridge information, the TSN AF triggers an Npcf_PolicyAuthorization_Create service operation. How does the TSN AF find the PCF? Is the PCF Discovery and Selection function modified?. Action: CT WG3 asks SA WG2 to answer above questions and update their specification if necessary.","secretary_remarks":"Response drafted in S2-2003757, S2-2003889, S2-2003950 and S2-2004187. Final response in S2-2004462","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10760,"status":"replied to","reservation_date":"2020-04-29 13:30:24","uploaded":"2020-04-29 13:38:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C3-202515","lsreply":"S2-2004462","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003546.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003547","title":"LS from CT WG4: LS on Presence of PEI in Nudm_UECM_Registration Requests","source":"CT WG4","contact":"Ulrich Wiehe","contact-id":73600,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 have detected a misalignment between TS 23.502 and TS 29.503 with regard to the presence of PEI in Nudm_UECM_Registration requests sent from AMF to UDM: TS 23.502 indicates in clause 5.2.3.2.1 that PEI is a required input. However, in other clauses, it gives the impression that PEI is optional; for example, clause 4.2.2.2.1 says: If the AMF needs the PEI in the initial registration, it should retrieve the PEI as it establishes the NAS security context with a Security Mode Command. And also, clause 4.2.2.2.2 says: The PEI may be retrieved in initial registration from the UE as described in clause 4.2.2.2.1. Regarding stage-3, TS 29.503 has defined PEI as an optional attribute in Amf3GppAccessRegistration and AmfNon3GppAccessRegistration data types (see clauses 6.2.6.2.2 and 6.2.6.2.3). CT WG4 have discussed the attached CR to TS 29.503 which tries to align with TS 23.502 by making PEI mandatory in Amf3GppAccessRegistration and AmfNon3GppAccessRegistration data types. During discussions concerns were raised, suggesting to relax the requirement from TS 23.502 and to allow absence of PEI from Nudm_UECM_Registrations. It was also noted that absence of PEI from Amf3GppAccessRegistration or AmfNon3GppAccessRegistration data types does not allow the UDM to properly report change of SUPI-PEI associations to NFs (e.g. NEF) that have subscribed to receiving such reports. CT WG4 kindly ask SA WG2 to either confirm that PEI is a required input for Nudm_UECM_Registration (and, if so, to consider updating the clauses mentioned above that might suggest otherwise), or to remove this requirement in TS 23.502 clause 5.2.3.2.1. Action: CT WG4 kindly ask SA WG2 to clarify whether PEI is required or optional input to Nudm_UECM_Registration and if this applies from Rel-15 onwards.","secretary_remarks":"Response drafted in S2-2003613 and S2-2004145. Final response in S2-2004464","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10860,"status":"replied to","reservation_date":"2020-04-29 13:30:24","uploaded":"2020-04-29 13:38:50","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C4-202344","lsreply":"S2-2004464","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003547.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003548","title":"LS from CT WG4: LS on Network Configuration Parameters in Monitoring Events","source":"CT WG4","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"TS 23.502 clause 4.15.6.3a specifies the Network Configuration Parameters (e.g. Maximum Response Time, Maximum Latency, Suggested Number of Downlink Packets) can be provisioned via Nudm_ParameterProvisioning services, where the UDM further update the parameters to AMF\/SMF. These parameters will be applied as UE configuration e.g. using Maximum Response time to configure the Active Time or Extended Connected time for MICO mode. TS 23.502 clause 4.15.3 also specifies that the Network Configuration Parameters may be provided via Monitoring Event subscription (e.g. for UE Reachability Event) via Nudm_EventExposure service, where the UDM shall perform the calculation of the final value to be applied in the network, together with the Network Configuration Parameters previously provisioned. If any UE configuration is updated as after the calculation, the UDM notifies the data change to the AMF. It also specifies that the AMF will receive the aggregated Suggested Number of Downlink Packets and provide it to the SMF. The configuration of Network Configuration Parameters in Monitoring Event seems to be inherited from EPC domain, where both Monitoring Events and Network Parameters are configured via the same interface on HSS (s6t). Since the introduction of Network Configuration, the use of configuration of parameters via monitoring events is no longer recommended, according to latest TS 23.682: NOTE 3: The Network Parameter Configuration via SCEF feature (see clause 4.5.21) feature supersedes the option of setting Reachability Type to 'configuration' during configuration of the UE Reachability Monitoring Event which is no longer recommended. In 5GC, Parameter Provisioning and Event Exposure are provided via different APIs. Allowing same Network Configuration Parameters provisioned via different APIs brings drawbacks: 1. This requires the same logic of handling Network Configuration Parameters being duplicated in service producer entities providing different service APIs. Such a requirement lowers the system efficiency with extra network resources and increases the risks of race condition; 2. Event Exposure service and Parameters Provisioning service may apply different authorization policies and constraints. The mixing of the functionality of the services make it more difficult or even impossible to manage the authorization policies independently; 3. According to 23.682 clause 5.18 'Procedure for Network Parameter Configuration via SCEF', it is specified that the HSS may notify the SCEF (which then notifies the SCS\/AS) of the actual value of Maximum Latency and Maximum Response Time that are being applied in the 3GPP network. If similar feature should be supported in 5GC in future, i.e. the UDM will inform the NEF\/AF when the actual network parameters applied to the 5GC, then UDM will maintain the Parameter Provisioning instances and inform the AFs accordingly. If the network configuration parameters are also allowed in Event Subscriptions, the UDM will need to also inform the subscribers. This introduces close dependencies between these two APIs, which is against the principle of Service Based Architecture. CT WG4 considers managing Network Configuration Parameters ONLY via Nudm_ParameterProvisioining service is a better choice, which follows the direction of SBI design and better fits the service logic as the parameters are applied on UE level, regardless of the events being monitored. The handling of the parameters by different AFs on the same UE can be described properly (similar to the handling of parameters when they are included in monitoring event in TS 23.502 clause 4.15.3.2.3b) if SA WG2 decides to go down this path. Action: CT WG4 kindly asks SA WG2 to take the information into account and provide feedbacks to the above recommendation.","secretary_remarks":"Response drafted in S2-2003616 and S2-2003861. Final response in S2-2004467","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10950,"status":"replied to","reservation_date":"2020-04-29 13:30:24","uploaded":"2020-04-29 13:38:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG3","lsoriginalls":"C4-202355","lsreply":"S2-2004467","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003548.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003549","title":"LS from CT WG4: LS on which features cannot interwork with ETSUN","source":"CT WG4","contact":"Caixia Qi","contact-id":56676,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 has discussed the interworking issue between ETSUN feature and other features. In 3GPP TS 23.501, clause 5.34.1 describes LADN feature cannot interwork with ETSUN as below: The SMF shall release or reject the PDU Session if the DNN of the PDU Session corresponds to a LADN and the I-SMF is inserted to the PDU Session. CT WG4 has also noticed that the working assumption for ATSSS feature is: In this release of the specification, ATSSS assumes SMFs Service Areas covering the whole PLMN or MA-PDU session is released when UE moves out of SMF service area. But for some other features, e.g. 5G_URLLC feature, there is no explicit requirement or restriction in stage2 specifications on whether the PDU session with I-SMF shall support the 5G_URLLC feature or not. It is CT WG4 understanding that all of the other features can interwork with ETSUN, unless it is clearly restricted in stage 2 specifications, like LADN. Action: CT WG4 kindly asks SA WG2 group to clarify which features cannot interwork with ETSUN and add the clarification in relevant specification if needed, and to confirm in particular whether URLLC applies to PDU session with I-SMF.","secretary_remarks":"Response drafted in S2-2003706 and S2-2004124. Final response in S2-2004443","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11010,"status":"replied to","reservation_date":"2020-04-29 13:30:24","uploaded":"2020-04-29 13:38:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C4-202536","lsreply":"S2-2004443","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003549.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003550","title":"LS from SA WG3: Reply LS on AUSF role in slice specific authentication","source":"SA WG3","contact":"Zander Lei","contact-id":46558,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 thanks SA WG2 for the LS Response S2-1910668 on the AUSF role in Network Slice Specific Authentication and Authorization (NSSAA). SA WG3 understands the motivation to include a contact point within the HPLMN for facilitating the execution of the NSSAA procedures using SBA services with the AMF and translating them to AAA protocols towards the AAA-S\/AAA-P. SA WG3 also understands that this contact point can also assist the AAA-S to select the AMF serving the UE for the execution of the AAA-S initiated Re-authentication and Revocation procedures. However, SA WG3 has a security requirement to fully isolate the following two SBA Authentication service types, - primary authentication services towards UDM currently supported by AUSF - NSSAA services involving interactions with a AAA-S SA WG3 have discussed multiple options to meet this security requirement for isolation and agreed on: - The NSSAA SBI services used by the AMF shall be hosted by a new NF (e.g. NSSAAF) to provide the NSSAA related services. From a specification point of view, this will require the definition of a new NF within the SBA architecture. From AMF point of view, this requires that AMF selects the new NF in the HPLMN when an NSSAA service is invoked. SA WG3 will define the security requirements for the new NF. Action: To take the above recommendations into consideration and update the specifications as necessary.","secretary_remarks":"Response drafted in S2-2003745. Final response in S2-2004476","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11400,"status":"replied to","reservation_date":"2020-04-29 13:30:24","uploaded":"2020-04-29 13:38:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1, CT WG3, CT WG4","Cc":"","lsoriginalls":"S3-200821","lsreply":"S2-2004476","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003550.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003551","title":"LS from SA WG3LI: LS on Location information for SMS over IMS","source":"SA WG3LI","contact":"Maurizio Iovieno","contact-id":23687,"tdoctype":"LS in","for":"Action","abstract":"LI requirements include the need for the operator to provide target's location information as part of intercepted signaling, when required by the LI warrant. With reference to SMS over IMS, SA WG3-LI would expect that, whenever an IMS user sends or receives a SMS over IMS, the CSCFs include the Network Provided Location Information (NPLI) in the PANI header (or equivalent functionalities), in addition to any possible user provided location information, for possible use by the LI functions in the operator network in case the user is a LI target. Location information is required to be the location when the SMS is sent\/received by the user. The requirement is applicable to both non-roaming and roaming scenarios. In order to ensure LI undetectability, this needs to be done for all users, no matter whether they are LI target. Looking at IMS Core Network specifications, it was however unclear to SA WG3-LI whether the needed capabilities, i.e. the inclusion of a NPLI in the PANI header when SMS over IMS are handled, are currently supported. Action: SA WG3-LI asks SA WG2 to provide feedback on the availability of location information at CSCFs when any IMS user sends or receives SMS over IMS and, if seen needed, to update their specifications in order to ensure that LI requirements on location information for LI of SMS over IMS are fulfilled.","secretary_remarks":"Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11850,"status":"postponed","reservation_date":"2020-04-29 13:30:24","uploaded":"2020-04-29 13:38:50","revisionof":"","revisedto":"S2-2004771","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1, CT WG3, SA WG3","lsoriginalls":"S3i200161","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003551.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003557","title":"LS from RAN WG3: LS on AS rekeying handling","source":"RAN WG3","contact":"Aijuan Liu","contact-id":43714,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 discussed the behaviour of NG-RAN node if it receives one NGAP UE CONTEXT MODIFICATION REQUEST message that includes both the Security Key IE and the Emergency Fallback Indicator IE. From RAN WG3 point of view, if the NG-RAN node performs the AS rekeying procedure as the highest priority, the emergency fallback will be delayed. Therefore it should be beneficial for the NG-RAN node to ignore the Security Key IE and only perform emergency fallback in this case. From NGAP protocol, the IEs mentioned above are all optional and could be present in one message. However, RAN WG3 is not sure whether such case is possible to happen, considering the AMF is possible to halt the trigger for AS rekeying (i.e. to decide not to include the Security Key IE) when it requests the NG-RAN node to perform emergency fallback. Besides, RAN WG3 understands that AS re-keying procedure could be initiated by AMF via either UE CONTEXT MODIFICATION REQUEST message or PATH SWITCH REQUEST ACKNOWLEDGE message. One issue discussed in RAN WG3 is whether it should be supported for the NG-RAN node to inform the AMF of the re-keying failure in either of the two cases. Action: RAN WG3 respectfully asks SA WG2 to feedback whether the case that both the Security Key IE and the Emergency Fallback Indicator IE are included within one NGAP UE CONTEXT MODIFICATION REQUEST message is abnormal or not","secretary_remarks":"Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11860,"status":"postponed","reservation_date":"2020-05-06 09:05:45","uploaded":"2020-05-08 12:52:59","revisionof":"","revisedto":"S2-2004772","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3","Cc":"","lsoriginalls":"R3-202833","lsreply":"S2-2005233","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003557.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003558","title":"LS from SA WG5: LS to CT4 on SNSSAI support in N4 Session Establishment","source":"SA WG5","contact":"Deepanshu Gautam","contact-id":81664,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to inform CT WG4 that TS 28.554 defines procedures KPIs of Uplink and Downlink throughput per network slice andthese KPI are calculated based on related measurments from UPF. There is a requirement in SA WG5 to define measurements per S-NSSAI and 5QI on UPF, e.g Average DL GTP packets delay in PSA UPF per 5QI and S-NSSAI, as specified in TS 28.552. However, since currently SMF does not transfer S-NSSAI information associated with a PDU Session to UPF, UPF cannot report per slice measurements to OAM, and hence OAM cannot collect the required measurements and calculate the required KPIs correctly. This become critical when a single UPF is shared among multiple slices. In addition, since currently SMF does not transfer 5QI information associated with a PDU Session and a QoS flow to UPF, UPF cannot report per 5QI measurements to OAM, and hence OAM cannot collect the required measurements.","secretary_remarks":"Response drafted in S2-2003653. Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11870,"status":"noted","reservation_date":"2020-05-06 09:05:45","uploaded":"2020-05-08 12:52:59","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"SA WG2","lsoriginalls":"S5-202308","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003558.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003559","title":"LS from SA WG5: LS to SA2 on QoS requirements for OAM traffic on IAB","source":"SA WG5","contact":"Yizhi Yao","contact-id":66963,"tdoctype":"LS in","for":"Action","abstract":"In SA WG5#128, SA WG5 received a LS (S2-1910347) from SA WG2 on whether new 5QIs are needed OAM traffic on IAB. In the initial reply (S5-197814) to SA WG2, SA WG5 confirmed one or more new 5QIs are needed for OAM\/Charging traffic on IAB and informed SA WG2 that SA WG5 would like to provide detailed QoS requirements when they are available. This LS provides more detailed QoS requirements for OAM traffic on IAB, and SA WG5 requires dedicated 5QI values for the types of OAM traffic as shown in the table below. {...} SA WG5 would like to request SA WG2 to take the above-mentioned QoS requirements for OAM traffic on IAB into account. Action: SA WG5 respectfully asks SA WG2 to take the above-mentioned QoS requirements for OAM traffic on IAB into account.","secretary_remarks":"Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11890,"status":"postponed","reservation_date":"2020-05-06 09:06:06","uploaded":"2020-05-08 12:52:59","revisionof":"","revisedto":"S2-2004773","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"S5-202458","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003559.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003560","title":"LS from RAN WG2: Reply LS on category M devices and NR","source":"RAN WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 thanks SA WG2 for their LS on category M devices and NR and RAN WG2 has considered LS and in particular following question: 'SA WG2 kindly asks RAN WG2 whether a category M1\/M2 device accessing WB-E-UTRA does not indicate NR support, and whether a device accessing NR does not indicate category M1\/M2.' Answer: Interworking with NR is not supported by Cat M UE. This means: - a Cat M UE does not report NR capability and network does not configure Cat M UE to operate in NR mode. - a NR UE does not report Cat M capability and network does not configure NR UE to operate in Cat M mode. Action: RAN WG2 respectfully asks SA WG2 to take into consideration the above response.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11900,"status":"noted","reservation_date":"2020-05-06 09:06:06","uploaded":"2020-05-08 12:52:59","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"R2-2003934","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003560.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003561","title":"LS from RAN WG2: LS on SIB indication for UE specific DRX","source":"RAN WG2","contact":"Mungal Singh Dhanda","contact-id":84552,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 like to inform SA WG2 of the following agreement: - The SIB indication to enable\/disable the use of UE specific DRX for 5GS is cell specific indication. Action: RAN WG2 respectfully asks SA WG2 to take into consideration the above agreement.","secretary_remarks":"Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11910,"status":"postponed","reservation_date":"2020-05-08 12:31:32","uploaded":"2020-05-08 12:52:59","revisionof":"","revisedto":"S2-2004774","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"R2-2004057","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003561.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003562","title":"LS from RAN WG2: LS on RLF Agreements","source":"RAN WG2","contact":"Martino Freda","contact-id":44622,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 has discussed TX-based RLM\/RLF and has reached the following agreements: Agreements on RLM\/RLF: 1: UE can trigger RLF based on the absence of HARQ feedback (DTX). 2: Enhancements addressing absence of HARQ feedback (i.e. DTX) resulting from half duplex and UL\/SL prioritization are not considered in this release (similar to NR-U for absence of IS\/OOS). 3: RLF can be triggered following reception of a configurable number of consecutive DTX.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10030,"status":"noted","reservation_date":"2020-05-08 12:31:32","uploaded":"2020-05-08 12:52:59","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG1","Cc":"SA WG2","lsoriginalls":"R2-2004086","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003562.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003566","title":"LS from RAN WG2: Response LS on the support for ECN in 5GS","source":"RAN WG2","contact":"Masato Kitazoe","contact-id":29801,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 would like to thank SA WG2 for their LS on the support for ECN in 5GS. Please see RAN WG2's answers to the SA WG2 request below. SA WG2 request #1: 'SA WG2 would like to ask RAN WG2 whether there is any other any other use of ECN beyond bitrate adaptation for MTSI.' RAN WG2 answer: RAN WG2 has not agreed on the use of ECN for any other purposes. SA WG2 request #2: 'SA WG2 invite RAN WG2 to consider whether or not the text in TS 38.300 needs to be aligned with the text in TS 36.300'. RAN WG2 answer: There is no consensus in RAN WG2 on such alignment. Action: RAN WG2 asks SA WG2 to take the above RAN WG2 response into account.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11960,"status":"noted","reservation_date":"2020-05-08 12:31:32","uploaded":"2020-05-08 12:52:58","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG3, CT WG1, SA WG4","lsoriginalls":"R2-2004284","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003566.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003574","title":"LS from RAN WG2: Reply LS on manual CAG selection","source":"RAN WG2","contact":"Gy\u00f6rgy Wolfner","contact-id":68507,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 would like to thank CT WG1 for the LS on manual CAG selection (R2-2004178\/C1-202927). RAN WG2 will make the necessary changes in their specifications to support CT WG1 agreement to enable a CAG cell to broadcast that the PLMN allows a user to manually select a CAG-ID supported by the CAG cell but outside the UE's allowed CAG list. RAN WG2 is looking for guidance whether the indication that the PLMN allows a user to manually select a CAG-ID supported by the CAG cell but outside the UE's allowed CAG list is per PLMN or per CAG ID.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10300,"status":"noted","reservation_date":"2020-05-14 05:10:58","uploaded":"2020-05-14 05:38:34","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, SA WG1","Cc":"SA WG2, RAN WG3","lsoriginalls":"R2-2003870","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003574.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003575","title":"LS from RAN WG2: LS on early UE capability retrieval for eMTC","source":"RAN WG2","contact":"Veera Prasada Kadiri","contact-id":72325,"tdoctype":"LS in","for":"Action","abstract":"In case of CP CIoT EPS\/5GS optimization for NB-IoT, SA WG2\/RAN WG3 has specified a procedure for (ng-)eNB to retrieve the NB-IoT UE Priority that allows retrieval of additional parameters such as UE radio capabilities from MME\/AMF during RRC Connection Setup procedure i.e. upon receiving RRCConnectionRequest-NB in Msg3 from the UE and before sending RRCConnectionSetup-NB in Msg4 to the UE. RAN WG2 discussed and concluded the same feature would be beneficial for configuring eMTC UEs which support only CP IoT optimization. RAN WG2 concluded it would be beneficial if the (ng-)eNB is aware of UE radio capabilities sufficiently early, i.e. after receiving Msg3 before Msg4 transmission, so that the radio configuration for the features supported by the UE can be included in Msg4. In case of CP CIoT 5GS optimization for eMTC, due to Msg3 size limitation, UE can only send 40 bit LSB of 5G-S-TMSI in RRCConnectionRequest message and with this limitation ng-eNB may not be able to uniquely identify AMF for early retrieval of UE capability information from AMF upon receiving Msg3 from UE. SA WG2\/RAN WG3\/CT WG1 already introduced truncated 5G-S-TMSI solution for NB-IoT CP CIoT 5GC Optimization Re-establishment. RAN WG2 would like to ask SA WG2\/RAN WG3\/CT WG1 on the feasibility of using the same truncated 5G-S-TMSI solution for early UE capability retrieval in case of eMTC connected to 5GC. RAN WG2 would like to further highlight that there is not enough space to indicate which UE identity (5G-S-TMSI or truncated 5G-S-TMSI) is used in Msg3 thus the same UE identity shall be used by all UEs in the cell. Action: RAN WG2 respectfully asks SA WG2, CT WG1 and RAN WG3 - To consider feasibility of introducing enhancements to enable the (ng-)eNB for early UE capability retrieval for eMTC UEs connected to EPC and 5GC in Rel-16, and if confirmed feasible, specify the required changes based on truncated 5G-S-TMSI solution in their specifications.","secretary_remarks":"Response drafted in S2-2004188. Final response in S2-2004446","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11970,"status":"replied to","reservation_date":"2020-05-14 05:10:58","uploaded":"2020-05-14 05:38:34","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG3, CT WG1","Cc":"SA WG3","lsoriginalls":"R2-2003935","lsreply":"S2-2004446","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003575.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003576","title":"LS from RAN WG2: LS on UAC applicability to IABs","source":"RAN WG2","contact":"Ajmal Muhammad","contact-id":81936,"tdoctype":"LS in","for":"Information","abstract":"At the RAN WG2 #109-e meeting, RAN WG2 made the following agreement for IAB WI: - IAB-MTs are not under UAC control. The agreement means that IAB-MT, being part of an IAB node which is a network node, does not perform access barring check for its access attempts to a cell. RAN WG2 thinks that SA WG1\/CT WG1 should be aware of this agreement as it might have some impact on their specifications.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10040,"status":"noted","reservation_date":"2020-05-14 05:10:58","uploaded":"2020-05-14 05:38:34","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, CT WG1","Cc":"RAN WG3, SA WG2","lsoriginalls":"R2-2003941","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003576.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003577","title":"LS from RAN WG2: LS on IAB supporting in NPN deployment","source":"RAN WG2","contact":"YULONG SHI","contact-id":81972,"tdoctype":"LS in","for":"Action","abstract":"At the RAN WG2 #109bis-e meeting, RAN WG2 made the following agreements: ? R2 make an attempt to support IAB functionality in non-public network deployments in R16 in R2#109bis and R2#110 meeting. If the agreeable CRs can be achieved before ASN.1 freeze, then it is supported. Otherwise, it is not supported in R16 RAN WG2 attempts to support the IAB functionality in non-public network deployments in R16, i.e. allowing IAB-MT to access a NPN-only cell or PLMN+NPN cell. The endorsed CRs to TS 38.331 and TS 38.304 have been enclosed for reference. RAN WG2 respectfully asks RAN WG3\/SA WG2 to take into account the above RAN WG2 agreement. Action: RAN WG2 respectfully asks RAN WG3\/SA WG2 to take into account the above RAN WG2 agreement and inform RAN WG2 if the corresponding WG has any issues with the agreement above.","secretary_remarks":"Response drafted in S2-2004161 and S2-2004278. Final response in S2-2004469","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11100,"status":"replied to","reservation_date":"2020-05-14 05:10:58","uploaded":"2020-05-14 05:38:34","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, SA WG2","Cc":"CT WG1","lsoriginalls":"R2-2004282","lsreply":"S2-2004469","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003577.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003578","title":"LS from RAN WG3: LS on Stage 3 for V2X QoS","source":"RAN WG3","contact":"Philippe Godin","contact-id":68843,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 would like to inform SA WG2 that RAN WG3 has made the Working Assumption (WA) to proceed with stage 3 design as shown in the attached TPs. Action: RAN WG3 would like to ask SA WG2 to take into account and feedback if needed.","secretary_remarks":"Response drafted in S2-2003911 and S2-2004242. Final response in S2-2004445","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11160,"status":"replied to","reservation_date":"2020-05-14 05:19:06","uploaded":"2020-05-14 05:38:34","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"R3-202856","lsreply":"S2-2004445","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003578.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003579","title":"LS from RAN WG3: LS on S1\/NG DAPS handover","source":"RAN WG3","contact":"Chunlin Ni","contact-id":66233,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 agreed to support S1\/NG DAPS (Dual Active Protocol Stacks) Handover over S1 and NG. RAN WG3 agreed to introduce the below changes as described in the attached BL CRs for S1AP and NGAP: 1. Add the DAPS related information in transparent containers between source and target in the Handover Preparation and Handover Resource Allocation procedures. 2. Introduce two new class-2 procedures for transferring the COUNT value for the early data forwarding. The content of these messages is transparent to the core network. 3. Introduce a new message (i.e. Handover Success from MME\/AMF to source node) and enhance the Handover Notify message for indicating the successful access of the UE from target node to source node via MME\/AMF. These changes may have impact on SA WG2 and CT WG4 specifications. Action: RAN WG3 kindly asks SA WG2 and CT WG4 to take the above RAN WG3 agreements into account and do corresponding change(s) to the specification(s) if needed.","secretary_remarks":"Response drafted in S2-2003861 and S2-2004010. Final response in S2-2004474","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11280,"status":"replied to","reservation_date":"2020-05-14 05:19:14","uploaded":"2020-05-14 05:38:34","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG4","Cc":"","lsoriginalls":"R3-202932","lsreply":"S2-2004474","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003579.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003599","title":"Updating the UE with new CAG information","source":"Ericsson, Qualcomm Incorporated, China Mobile","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified when the network configures the UE with CAG information. Correcting the usage of 'UE 5GMM Core Network Capability'.","secretary_remarks":"Revision of (agreed) S2-2003249 from S2#138E. Revised, merging S2-2004302, to S2-2004311","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10450,"status":"revised","reservation_date":"2020-05-18 01:43:11","uploaded":"2020-05-22 20:47:19","revisionof":"S2-2003249","revisedto":"S2-2004311","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":2135.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003599.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003600","title":"LS reply on manipulation of CAG Information element by a VPLMN","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"LS reply on manipulation of CAG Information element by a VPLMN","secretary_remarks":"Response to S2-2003535. Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10430,"status":"noted","reservation_date":"2020-05-18 01:43:12","uploaded":"2020-05-22 20:47:19","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003600.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003601","title":"UE handling of CAG information","source":"Ericsson, Qualcomm Incorporated","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that when the UE gets CAG information from a Serving PLMN that includes CAG information for other PLMNs, the UE will only update the stored CAG information for the Serving PLMN. Also, when the UE gets rejected, the UE will not update its stored CAG information based on rejection cause.","secretary_remarks":"Merged into S2-2004313","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10380,"status":"merged","reservation_date":"2020-05-18 01:43:12","uploaded":"2020-05-22 20:48:45","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":2367.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003601.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003602","title":"Handling of MRL with updated CAG information","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that the AMF triggers AN release when CAG information been updated by the UDM..","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10500,"status":"noted","reservation_date":"2020-05-18 01:43:13","uploaded":"2020-05-22 20:48:45","revisionof":"","revisedto":"S2-2005574","release":"Rel-16","crspec":"23.502","crspecversion":"16.4.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":2309.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003602.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003613","title":"Reply LS on 'LS on Presence of PEI in Nudm_UECM_Registration Requests'","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Replies that SA WG2 will align with CT WG4 to make PEI optional","secretary_remarks":"Response to S2-2003547. Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10900,"status":"noted","reservation_date":"2020-05-18 01:55:45","uploaded":"2020-05-22 20:48:45","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003613.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003614","title":"Presence of PEI in Nudm_UECM_Registration Request","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clauses 4.2.2.2.1 &4.2.2.2.2: clarify that the AMF shall retrieve PEI if needed. Clause 5.2.3.2.1: Move PEI from 'Input, Required' to 'Input, Optional'.","secretary_remarks":"R04 agreed. Revised to S2-2004465","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10910,"status":"revised","reservation_date":"2020-05-18 01:55:45","uploaded":"2020-05-22 20:48:45","revisionof":"","revisedto":"S2-2004465","release":"Rel-15","crspec":"23.502","crspecversion":"15.9.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2310.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003614.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003615","title":"Presence of PEI in Nudm_UECM_Registration Request","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Clauses 4.2.2.2.1 &4.2.2.2.2: clarify that the AMF shall retrieve PEI if needed. Clause 5.2.3.2.1: Move PEI from 'Input, Required' to 'Input, Optional'.","secretary_remarks":"Mirror, merging S2-2004144, to S2-2003614_R04. Revised to S2-2004466.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10930,"status":"revised","reservation_date":"2020-05-18 01:55:46","uploaded":"2020-05-22 20:48:45","revisionof":"","revisedto":"S2-2004466","release":"Rel-16","crspec":"23.502","crspecversion":"16.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2311.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003615.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003616","title":"Reply LS on 'LS on Network Configuration Parameters in Monitoring Events'","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Replies that SA WG2 propose to keep the possibility of including event specific parameters in the EE subscription to cater for legacy AF.","secretary_remarks":"Response, merging S2-2004027, to S2-2003548. R05 agreed. Revised to S2-2004467","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10970,"status":"revised","reservation_date":"2020-05-18 01:55:47","uploaded":"2020-05-22 20:48:46","revisionof":"","revisedto":"S2-2004467","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003616.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003617","title":"Network Parameters Configuration by Parameter Provisioning and Event Exposure Subscription","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 4.15.3.2.3b, Correct the description related to Suggested Number of Downlink Packets to be consistent with clause 4.15.6.3a (i.e. Suggested Number of Downlink Packets are SMF-associated parameters). Clarify how UDM derives the subscribed periodic registration timer and subscribed Active Time. Correct the behavior how UDM derives the Suggested Number of Downlink Packets. Add a note clarifying that Event Exposure to configure network parameters is assumed to be used only when the AF does not support Parameter Provision service operation. Clause 4.15.6.3a: Remove the text indicating that parameters Maximum Latency and Maximum Response Time are associated with DNN and S-NSSAI; Clarify that the SMF-associated parameters Suggested Number of Downlink Packets are provided by UDM to SMF; Clarify how the UDM handles multiple requests of Network Configuration parameters for AMF- and SMF-associated parameters. Clauses 5.2.3.6.3, 5.2.3.6.4: Allow Nudm_ParameterProvision_Create and Nudm_ParameterProvision_Delete to handle network configuration parameters.","secretary_remarks":"R06 agreed. Revised to S2-2004468","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10990,"status":"revised","reservation_date":"2020-05-18 01:55:47","uploaded":"2020-05-22 20:48:46","revisionof":"","revisedto":"S2-2004468","release":"Rel-16","crspec":"23.502","crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2312.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003617.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003618","title":"Alignment with RAN stage 3 on Alternative QoS Profile","source":"Ericsson, LG Electronics, Nokia, Nokia Shanghai Bell, Samsung, Interdigital, ZTE, CATT","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: (Editorial) Clause 4.9.1.3.2, step 10, indent the list for alternative QoS (i.e. fix the very last bullet in step 10 to B2) Clause 4.9.1.3.3, remove AQP from Handover Notify.","secretary_remarks":"This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11200,"status":"agreed","reservation_date":"2020-05-18 01:55:48","uploaded":"2020-05-22 20:48:46","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.4.0","workitem":[{"winame":"eV2XARC"}],"crnumber":2313.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200434","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003618.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003627","title":"LS from BBF: Issue with FN-RG IPv6 support","source":"BBF (LIAISE-394)","contact":"Lincoln Lavoie","contact-id":39231,"tdoctype":"LS in","for":"Action","abstract":"Dear colleagues, We have identified issues with IPv6 support for FN-RGs with respect to the currently specified behaviors of the 5G system. 1) Support for FN-RGs using IPv6oE procedures The current specification has the interface identifier used by a UE for construction of the IPv6 Link Local addresses (LLA) assigned by the SMF. FN-RGs that use the IPoE protocol suite for IPv6 support currently conform to IETF RFC 2464 for LLA assignment. A 2464 compliant FN-RG will self-assign an interface identifier expressed as an EUI-64 using the FN-RG's WAN interface MAC address as input. There is no means to explicitly override this with a network assigned value. We believe a potential (and perhaps the only possible) solution exists in the form of adding an optional field to the PDU Session Establishment Request that the W-AGF may or may not send. The field would be the 'suggested interface identifier' and carry an 8 byte EUI-64 as an argument. The W-AGF would encode the FN-RG MAC address as an EUI-64 in the request. If the SMF receives the 'suggested interface identifier' field, it will use that information in the construction of the LLA to use for the FN-RG for that PDU session. The SMF would have the opportunity to verify it was not a duplicate (and if so it was take local measures to circumvent the issue), and will echo that value back in the PDU Session Establishment Accept Message as per existing practice. Therefore, a means would exist to synchronize the LLA expected by the FN-RG and the LLA sent by the SMF. 2) Support for FN-RGs using PPPoE and IPv6CP procedures IETF RFC 5072 NCP negotiation procedures performed between the FN-RG and W-AGF require the AGF to know the SMF's link local address. Again, we believe a potential (and only possible solution) is that an information element be added to the PDU Session Establishment Accept message that provides this information to the W-AGF for use in RFC 5072 negotiation procedures. This would ensure reliable knowledge of the SMF LLA when the AGF performed IPv6CP negotiation procedures with the FN-RG. We assume the SMF LLA is invariant for the duration of the PDU session. Member companies will be submitting CRs more completely documenting this proposal. We would request they be given consideration. The impact of the lack of this solution would require that the W-AGF would have to be specified as a layer 3 node and perform extensive interworking between the SMF and an FN-RG for IPv6 procedures. We also would advise that with respect to DHCP support in the SMF, DHCPv4 and DHCPv6 messages will not be directly received from the FN-RGs or 5G-RGs, but will have transited one or more DHCP relays that will exist in the path taken by the PDU session traffic. We would like to understand what an SMF would accept from the point of view of addressing for a DHCPv4 DISCOVER or DHCPv6 SOLICIT message. For example whether the request is unicast or broadcast, and will it accept requests with relay options. We look forward to continuing our fruitful relationship. Thanks, Lincoln Lavoie, Broadband Forum Technical Committee Chair","secretary_remarks":"Response drafted in S2-2003686. Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":12020,"status":"postponed","reservation_date":"2020-05-18 13:55:30","uploaded":"2020-05-18 14:10:11","revisionof":"","revisedto":"S2-2004775","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1, CT WG3","Cc":"","lsoriginalls":"LIAISE-394","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003627.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003640","title":"[DRAFT] Reply LS on manual CAG ID selection and granularity of UAC parameters for PNI-NPNs","source":"vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"LS out","for":"Approval","abstract":"This contribution gives the reply LS on manual CAG ID selection and granularity of UAC parameters for PNI-NPNs","secretary_remarks":"Response to S2-2003530. Revised to S2-2004335.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10320,"status":"revised","reservation_date":"2020-05-19 18:34:27","uploaded":"2020-05-22 23:25:26","revisionof":"","revisedto":"S2-2004335","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"CT WG1, RAN WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003640.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003641","title":"[DRAFT] Reply LS on manipulation of CAG Information element by a VPLMN","source":"vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"LS out","for":"Approval","abstract":"This contribution gives the reply LS on manipulation of CAG Information element by a VPLMN","secretary_remarks":"Response to S2-2003535. Merged into S2-2004453","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10470,"status":"merged","reservation_date":"2020-05-19 18:34:27","uploaded":"2020-05-22 23:25:26","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003641.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003653","title":"[DRAFT] Reply LS on SNSSAI support in N4 Session Establishment","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on SNSSAI support in N4 Session Establishment","secretary_remarks":"Response to S2-2003558. Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11880,"status":"noted","reservation_date":"2020-05-20 06:54:55","uploaded":"2020-05-22 12:53:02","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4, SA WG5","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003653.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003654","title":"PCO support for DNS over (D)TLS (avoiding attacks against DNS traffic)","source":"Nokia, Nokia Shanghai Bell, Qualcomm Incorporated","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When DNS over (D)TLS as specified in RFC 7858 and RFC 8310 is supported by the network, PCO may also include the corresponding DNS server security information. WI is new SA WG3 WID UPIP_SEC","secretary_remarks":"R03 agreed. Revised to S2-2004486","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2020-05-20 06:54:55","uploaded":"2020-05-22 18:15:05","revisionof":"","revisedto":"S2-2004486","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":2368.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003654.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003655","title":"Clarification of the Support of the Frame Routing Feature","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If the SMF receives Framed Routes information both from DN-AAA and from UDM, the information received from DN-AAA takes precedence and supersedes the information received from UDM If the UDM or DN-AAA updates the Framed Routes information during the lifetime of the PDU session, the SMF releases the PDU Session and may include in the release request an indication for the UE to re-establish the PDU session.","secretary_remarks":"R03 agreed. Revised to S2-2004457","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10580,"status":"revised","reservation_date":"2020-05-20 06:54:56","uploaded":"2020-05-22 12:53:02","revisionof":"","revisedto":"S2-2004457","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"5WWC"}],"crnumber":2369.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003655.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003656","title":"Clarification of Support of Frame Routing Feature","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"WITHDRAWN: Summary of change: Refer to Frame Route information on 4.16.4 SM Policy Association Establishment","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10600,"status":"withdrawn","reservation_date":"2020-05-20 06:54:57","uploaded":"2020-05-22 12:53:02","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.4.0","workitem":[{"winame":"5WWC"}],"crnumber":2314.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003656.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003657","title":"[DRAFT] Reply LS on Clarification of Support of Frame Routing Feature","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on Clarification of Support of Frame Routing Feature","secretary_remarks":"Response to S2-2003542. R02 agreed. Revised to S2-2004456","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10560,"status":"revised","reservation_date":"2020-05-20 06:54:58","uploaded":"2020-05-22 12:53:02","revisionof":"","revisedto":"S2-2004456","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003657.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003664","title":"[DRAFT] Reply LS on the applicability of LADN in an SNPN","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to CT WG1 on the applicability of LADN in an SNPN","secretary_remarks":"Response, merging S2-2003723, to S2-2003526. R02 agreed. Revised to S2-2004478","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11490,"status":"revised","reservation_date":"2020-05-20 07:02:11","uploaded":"2020-05-22 09:47:31","revisionof":"","revisedto":"S2-2004478","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003664.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003665","title":"[DRAFT] Reply LS on Access Type Report for a MA PDU session","source":"Nokia, Nokia Shanghai Bell","contact":"Yannick Lair","contact-id":76350,"tdoctype":"LS out","for":"Approval","abstract":"Draft reply LS to CT WG3 on Access Type Report for a MA PDU session","secretary_remarks":"Response to S2-2003545. Merged into S2-2004483","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11810,"status":"merged","reservation_date":"2020-05-20 07:25:09","uploaded":"2020-05-22 20:54:12","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"ATSSS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003665.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003666","title":"Correction for access type change for MA PDU session","source":"Nokia, Nokia Shanghai Bell","contact":"Yannick Lair","contact-id":76350,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that what the PCF reports for MA PDU session is the access type(s) for which user plane resources have been established.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11820,"status":"noted","reservation_date":"2020-05-20 07:26:46","uploaded":"2020-05-22 20:54:12","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.503","crspecversion":"16.4.1","workitem":[{"winame":"ATSSS"}],"crnumber":469.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003666.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003667","title":"[DRAFT] Reply LS on Clarification on eNA","source":"Nokia, Nokia Shanghai Bell","contact":"Yannick Lair","contact-id":76350,"tdoctype":"LS out","for":"Approval","abstract":"Draft reply LS to CT WG3 on Clarification on eNA","secretary_remarks":"Response to S2-2004327. Revised, merging S2-2003866, to S2-2003544","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11740,"status":"revised","reservation_date":"2020-05-20 07:39:05","uploaded":"2020-05-22 20:54:12","revisionof":"","revisedto":"S2-2004327","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003667.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003668","title":"Corrections for maximum number of objects and Maximum number of SUPIs","source":"Nokia, Nokia Shanghai Bell","contact":"Yannick Lair","contact-id":76350,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1\/ Make sure that maximum number of objects and maximum number of SUPIs are independent request parameters from the Analytics filters. 2\/ Add Maximum number of objects as an optional parameter for the request for expected UE behavioural parameters analytics.","secretary_remarks":"Revised, merging S2-2003867, to S2-2004328","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11780,"status":"revised","reservation_date":"2020-05-20 07:40:40","uploaded":"2020-05-22 20:54:12","revisionof":"","revisedto":"S2-2004328","release":"Rel-16","crspec":"23.288","crspecversion":"16.3.0","workitem":[{"winame":"eNA"}],"crnumber":176.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003668.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003683","title":"Corrections to description of lawful intercept","source":"Ericsson, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update incorrect text from 23.316","secretary_remarks":"This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11610,"status":"agreed","reservation_date":"2020-05-20 13:15:08","uploaded":"2020-05-22 20:50:08","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.316","crspecversion":"16.3.0","workitem":[{"winame":"5WWC"}],"crnumber":2045.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200427","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003683.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003684","title":"[DRAFT] Reply LS on uniqueness of PEI in certain FN-RG configurations","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"This paper proposes a reply to the 5WWC LS received form SA WG3-LI","secretary_remarks":"Response to S2-2003521. Revised to remove 'draft' in S2-2004479.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11620,"status":"revised","reservation_date":"2020-05-20 13:15:10","uploaded":"2020-05-22 20:50:08","revisionof":"","revisedto":"S2-2004479","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3-LI","Cc":"BBF, Cabelabs","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003684.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003685","title":"Handling of IPv6 addresses for FN-RG","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: W-AGF to provide FN-RGs IPv6 LLA at PDU session establishment request message. SMF to provide SMF IPv6 LLA in PDU session establishment accept message.","secretary_remarks":"Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":12040,"status":"postponed","reservation_date":"2020-05-20 13:15:10","uploaded":"2020-05-22 20:50:08","revisionof":"","revisedto":"S2-2004926","release":"Rel-16","crspec":"23.316","crspecversion":"16.3.0","workitem":[{"winame":"5WWC"}],"crnumber":2046.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003685.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003686","title":"[DRAFT] Reply LS on Issue with FN-RG IPv6 support","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"This paper proposes a reply to the BBF LS on FN-RG IPv6 support","secretary_remarks":"Response to S2-2003627. Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":12030,"status":"postponed","reservation_date":"2020-05-20 13:15:13","uploaded":"2020-05-22 20:50:08","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"BBF","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003686.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003691","title":"[DRAFT] Reply LS on Access Type Report for a MA PDU session","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"LS reply to CT WG3 questions on Access Type reporting","secretary_remarks":"Response, merging S2-2003665, to S2-2003545. R01 agreed. Revised to S2-2004483","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11830,"status":"revised","reservation_date":"2020-05-20 14:23:05","uploaded":"2020-05-22 20:50:08","revisionof":"","revisedto":"S2-2004483","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"ATSSS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"-","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003691.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003704","title":"Alignment on Alternative QoS Profile","source":"Ericsson, LG Electronics, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify what QoS parameters are included in the Alternative QoS profile.","secretary_remarks":"Revised to S2-2004444","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11210,"status":"revised","reservation_date":"2020-05-20 14:40:34","uploaded":"2020-05-22 20:51:02","revisionof":"","revisedto":"S2-2004444","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"eV2XARC"}],"crnumber":2370.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003704.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003705","title":"URLLC - TSN interworking with ETSUN","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In this release of the specification, support for Time Sensitive Communications (as defined in clause 5.27 or 5.28) or Ultra Reliable Low Latency Communications (as defined in clause 5.33) assumes SMF Service Areas covering the whole PLMN or that a PDU Session supporting Time Sensitive Communications or Ultra Reliable Low Latency Communications is released by the SMF when the UE moves out of the SMF Service Area.","secretary_remarks":"Revised to S2-2004442.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11080,"status":"revised","reservation_date":"2020-05-20 14:48:30","uploaded":"2020-05-22 12:53:02","revisionof":"","revisedto":"S2-2004442","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"ETSUN"},{"winame":"Vertical_LAN"},{"winame":"5G_URLLC"}],"crnumber":2371.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003705.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003706","title":"[DRAFT] Reply LS on which features cannot interwork with ETSUN","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"WITHDRAWN: Reply LS on which features cannot interwork with ETSUN","secretary_remarks":"Response to S2-2003549. WITHDRAWN","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11020,"status":"withdrawn","reservation_date":"2020-05-20 14:48:31","uploaded":"2020-05-22 12:53:02","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"ETSUN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003706.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003711","title":"[DRAFT] Reply LS on service area restriction for CIoT 5GS optimization","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Response LS to CT WG1 LS on service area restriction","secretary_remarks":"Response to S2-2003524. Merged into S2-2004440","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10150,"status":"merged","reservation_date":"2020-05-20 16:08:07","uploaded":"2020-05-22 20:51:03","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003711.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003712","title":"Service Area Restriction clarification","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1.Update clause 5.3.4.1.1 to clarify what services are not allowed and allowed in a Non-Allowed Area. It also clarifies what services are allowed based on subscription and operator policy in a Non-Allowed Area. 2.(Editorial)Move priority service description to the beginning of the clause for easy understanding.","secretary_remarks":"Revision of S2-2002773. R13 agreed. Revised, merging S2-2004204, to S2-2004439.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10160,"status":"revised","reservation_date":"2020-05-20 16:08:07","uploaded":"2020-05-22 20:51:03","revisionof":"S2-2002773","revisedto":"S2-2004439","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2243.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003712.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003713","title":"Service Area Restriction clarification","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update clause 5.2.2.2.2 and 5.2.3.3.1 to clarify that in the information of the Service Restriction Area, it may also include specific indications which indicate if SMS over NAS service, Location Service and Exception Reporting are allowed in a Non-Allowed Area.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10180,"status":"noted","reservation_date":"2020-05-20 16:08:12","uploaded":"2020-05-22 20:51:03","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2315.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003713.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003723","title":"[DRAFT] Reply LS on applicability of LADN in an SNPN","source":"OPPO","contact":"ChenHo CHIN","contact-id":80545,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: SA WG1","secretary_remarks":"Response to S2-2003526. Merged into S2-2004478","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11510,"status":"merged","reservation_date":"2020-05-20 16:33:50","uploaded":"2020-05-21 09:16:02","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003723.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003743","title":"Replacing AUSF by NSSAAF to support NSSAA","source":"ZTE, Ericsson, Qualcomm, Nokia, Nokia shanghai Bell","contact":"Tricci So","contact-id":44974,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introducing the new NF, NSSAAF, into Rel-17 network architecture to replace AUSF to support NSSAA by adding\/updating the corresponding clauses to support this new NF.","secretary_remarks":"R01 agreed. Revised to S2-2004477","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11430,"status":"revised","reservation_date":"2020-05-20 23:10:15","uploaded":"2020-05-22 06:53:05","revisionof":"","revisedto":"S2-2004477","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"eNS"}],"crnumber":2372.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003743.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003744","title":"Replacing AUSF by NSSAAF to support NSSAA","source":"ZTE, Ericsson, Nokia, Nokia Shanghai Bell.","contact":"Tricci So","contact-id":44974,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introducing the new NF, NSSAAF, into Rel-17 network architecture to replace AUSF to support NSSAA by adding\/updating the corresponding clauses to support this new NF. Note that, Figure 4.2.9.2-1 in this CR is based on the agreed CR, S2-2003477, from SA WG2#138E eMeeting.","secretary_remarks":"This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11450,"status":"agreed","reservation_date":"2020-05-20 23:15:40","uploaded":"2020-05-22 06:53:05","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.4.0","workitem":[{"winame":"eNS"}],"crnumber":2316.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200432","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003744.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003745","title":"[DRAFT] Reply LS on NSSAAF in slice specific authentication","source":"ZTE Wistron Telecom AB","contact":"Tricci So","contact-id":44974,"tdoctype":"LS out","for":"Approval","abstract":"SA WG2 thanks SA WG3 for the LS Response S2-20xxxxx on the decision of new network function, NSSAAF, in Network Slice Specific Authentication and Authorization (NSSAA). SA WG2 agreed CRs are attached.","secretary_remarks":"Response to S2-2003550. Revised to update attachments in S2-2004476.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11410,"status":"revised","reservation_date":"2020-05-20 23:33:46","uploaded":"2020-05-22 06:53:05","revisionof":"","revisedto":"S2-2004476","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"eNS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG2, CT WG1, CT WG3, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003745.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003757","title":"[DRAFT] Reply LS on clarification on TSN for Vertical_LAN","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"LS out","for":"Approval","abstract":"Reply to S2-2003546","secretary_remarks":"Response to S2-2003546. Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10770,"status":"noted","reservation_date":"2020-05-21 08:51:00","uploaded":"2020-05-22 17:48:37","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003757.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003763","title":"Correction of the Registration with AMF re-allocation procedure","source":"Nokia, Nokia Shanghai Bell, Telecom Italia","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The procedure is updated to enable the support of the use cases where there is no IP level reachability between source and target AMF","secretary_remarks":"Revision of S2-2000819. Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":12090,"status":"noted","reservation_date":"2020-05-21 09:58:57","uploaded":"2020-05-22 09:31:09","revisionof":"S2-2000819","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.4.0","workitem":[{"winame":"TEI16"}],"crnumber":2057.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003763.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003805","title":"[DRAFT] Reply LS on NAS Non delivery for RRC Inactive state","source":"Cisco Systems","contact":"Irfan Ali","contact-id":74090,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3, CT WG4","secretary_remarks":"Response to S2-2003531. R06 agreed. R06 agreed. Revised to S2-2004452","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11550,"status":"revised","reservation_date":"2020-05-21 20:03:52","uploaded":"2020-05-22 05:02:06","revisionof":"","revisedto":"S2-2004452","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003805.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003814","title":"Clarification on Registration with AMF re-allocation","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Align the procedure in Rel-16 with Rel-15","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":12100,"status":"noted","reservation_date":"2020-05-22 01:31:15","uploaded":"2020-05-22 10:35:47","revisionof":"","revisedto":"SP-200516","release":"Rel-16","crspec":"23.502","crspecversion":"16.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":2317.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003814.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003848","title":"Alignment CR for DAPS HO","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - adds new clause 5.5.1.2.2a to support DAPS HO. New changes beyond RAN's spec. - S-RAN requests DAPS HO when DAPS HO is supported by both S-RAN and S-MME. - T-RAN sends the DAPS Information IE If the DAPS HO is supported by both the T-RAN and T-MME.","secretary_remarks":"R05 agreed. Revised to S2-2004472","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11300,"status":"revised","reservation_date":"2020-05-22 06:40:58","uploaded":"2020-05-22 11:48:39","revisionof":"","revisedto":"S2-2004472","release":"Rel-16","crspec":"23.401","crspecversion":"16.6.0","workitem":[{"winame":"NR_Mob_enh-Core"},{"winame":"LTE_feMob-Core"},{"winame":"5GS_Ph1"}],"crnumber":3602.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003848.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003860","title":"Alignment CR for DAPS HO","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - adds new clause 4.9.1.3.3a to support DAPS HO. New changes beyond RAN's spec. - S-RAN requests DAPS HO when DAPS HO is supported by both S-RAN and S-AMF. - T-RAN sends the DAPS Information IE If the DAPS HO is supported by both the T-RAN and T-AMF.","secretary_remarks":"R07 agreed. Revised to S2-2004473","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11320,"status":"revised","reservation_date":"2020-05-22 06:47:53","uploaded":"2020-05-22 11:48:39","revisionof":"","revisedto":"S2-2004473","release":"Rel-16","crspec":"23.502","crspecversion":"16.4.0","workitem":[{"winame":"NR_Mob_enh-Core"},{"winame":"LTE_feMob-Core"},{"winame":"5GS_Ph1"}],"crnumber":2318.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003860.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003861","title":"[DRAFT] Reply LS on S1\/NG DAPS handover","source":"QUALCOMM Europe Inc. - Italy","contact":"Juan Zhang","contact-id":73274,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3. CC: CT WG4. Attachments: TS 23.502 S2-2003860, TS 23.401 S2-2003848","secretary_remarks":"Response to S2-2003579. Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11290,"status":"noted","reservation_date":"2020-05-22 06:56:00","uploaded":"2020-05-22 11:48:39","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003861.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003864","title":"Reflective QoS","source":"Huawei, HiSilicon, Ericsson","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified how the SMF starts and stops Reflective QoS.","secretary_remarks":"Revision of S2-2002750. R05 agreed. Revised to S2-2004447.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":12110,"status":"revised","reservation_date":"2020-05-22 07:10:19","uploaded":"2020-05-22 13:24:09","revisionof":"S2-2002750","revisedto":"S2-2004447","release":"Rel-15","crspec":"23.501","crspecversion":"15.9.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2237.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003864.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003865","title":"Reflective QoS","source":"Huawei, HiSilicon, Ericsson","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: It is clarified how the SMF starts and stops Reflective QoS.","secretary_remarks":"Revision of S2-2002751. Revised to S2-2004448.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":12130,"status":"revised","reservation_date":"2020-05-22 07:10:20","uploaded":"2020-05-22 13:24:09","revisionof":"S2-2002751","revisedto":"S2-2004448","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1732.0,"crrevision":4.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003865.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003866","title":"[DRAFT] Reply LS on Clarification on eNA (C3-202507)","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"This LS is to reply the CT WG3 some clarifications about the analytics reporting information.","secretary_remarks":"Merged into S2-2004327","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11730,"status":"merged","reservation_date":"2020-05-22 07:10:22","uploaded":"2020-05-22 12:33:12","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003866.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003867","title":"Corrections to Nnwdaf service operations","source":"Nokia, Nokia Shanghai Bell, Samsung, Huawei","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Reporting Thresholds, Maximum number of objects and Maximum number of SUPIs added as inputs for Nnwdaf_AnalyticsSubscription_Subscribe and a note clarifies that these can be provided per individual Analytics ID. - Maximum number of objects and Maximum number of SUPIs added as inputs for Nnwdaf_AnalyticsInfo_Request and a note clarifies that these can be provided per individual Analytics ID. - Validity period added as input to Nnwdaf_AnalyticsSubscription_Notify and as output for Nnwdaf_AnalyticsInfo_Request, with a note clarifying that Validity period can also be provided as part of Analytics specific parameters for some NWDAF output analytics. - Notes added to Nnwdaf_AnalyticsInfo_Request description to clarify that Target of Analytics Reporting can be provided per individual Analytics ID in a set of Analytics IDs, and Analytics Filter Information can be provided per individual Analytics ID in a set of Analytics IDs. In 7.1, the response description for observed service experience analytics is aligned with general description in clause 6.4.1, i.e. the Observed Service Experience analytics may provide one or both of the following: - Service Experience for a Network Slice - Service Experience for an Application The details regarding network slice instances can be left to the output analytics tables in 6.4.3. Clarify the Maximum number of objects and the Maximum number of SUPIs can be only provided by the Analytics Reporting Information, but not the Analytics Filter Information.","secretary_remarks":"Revision of S2-2003339 Merged into S2-2004328. S2-2003339 from S2#138E remains agreed.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11770,"status":"merged","reservation_date":"2020-05-22 07:10:22","uploaded":"2020-05-22 12:33:12","revisionof":"S2-2003339","revisedto":"","release":"Rel-16","crspec":"23.288","crspecversion":"16.3.0","workitem":[{"winame":"eNA"}],"crnumber":172.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003867.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003868","title":"[DRAFT] Reply LS on Network Area Information in BDT Policy (C3-202420)","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"This LS replies CT WG3 clarifications about the network area in the AF Request and the network area in the BDT policy.","secretary_remarks":". Merged into S2-2004460","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10720,"status":"merged","reservation_date":"2020-05-22 07:10:23","uploaded":"2020-05-22 12:33:12","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003868.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003869","title":"Correction of BDT policy re-negotiation description","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The description is updated so that the background data transfer policy removal in the UDR happens after the AF selection. This ensures that there is only one URSP rule update to the UEs. It is also clarified that the previously negotiated BDT policy shall be kept if the PCF does not find an alternative BDT policy to offer to the AF. In addition, the terminology is corrected in several places by adding the word 'data' to achieve a consistent usage of the term 'background data transfer'. Furthermore, the network performance analytics related description is generalized to allow for other output parameters of the network performance analytics. A statement about the PCF subscribing to the network performance analytics is also added.","secretary_remarks":"Revision of S2-2002754. Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10730,"status":"noted","reservation_date":"2020-05-22 07:10:23","uploaded":"2020-05-22 12:33:12","revisionof":"S2-2002754","revisedto":"","release":"Rel-16","crspec":"23.503","crspecversion":"16.4.0","workitem":[{"winame":"eNA"}],"crnumber":439.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003869.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003870","title":"Correction of BDT policy re-negotiation procedure","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: First, remove the analytics parameters such as load and number of UEs in the Network Performance analytics. Second, update the BDT warning notification procedure so that the background data transfer policy removal in the UDR happens after the AF selection. This ensures that there is only one URSP rule update to the UEs.","secretary_remarks":"Revision of S2-2002971. R04 agreed. Revised to S2-2004461","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10740,"status":"revised","reservation_date":"2020-05-22 07:10:24","uploaded":"2020-05-22 12:33:12","revisionof":"S2-2002971","revisedto":"S2-2004461","release":"Rel-16","crspec":"23.502","crspecversion":"16.4.0","workitem":[{"winame":"eNA"},{"winame":"xBDT"}],"crnumber":2237.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003870.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003885","title":"[DRAFT] LS Reply on clarification of Support of Frame Routing Feature","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"This LS is to reply the CT WG3 for clarifications about the on the support of Frame Routing Feature.","secretary_remarks":"Response to S2-2003542. Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10610,"status":"noted","reservation_date":"2020-05-22 07:10:25","uploaded":"2020-05-22 12:33:12","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5WWC"}],"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_139e_Electronic\/Docs\/S2-2003885.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003886","title":"Correction on Framed Routing information reporting","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add PCR trigger to report Frame Routes information to the PCF. Add the description that PCF may send the Framed Routes information to the BSF.","secretary_remarks":"R04 agreed. Revised to S2-2004458","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10620,"status":"revised","reservation_date":"2020-05-22 07:10:25","uploaded":"2020-05-22 12:33:12","revisionof":"","revisedto":"S2-2004458","release":"Rel-16","crspec":"23.503","crspecversion":"16.4.1","workitem":[{"winame":"5WWC"}],"crnumber":470.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003886.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003887","title":"Correction on Framed Routing information reporting","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the reference to TS 23.503 for the detail description of Frame Route reporting. Clarify and correct the terminology. The information transferred within 5GC is unified as Framed Routing information.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10640,"status":"noted","reservation_date":"2020-05-22 07:10:27","uploaded":"2020-05-22 12:33:12","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"5WWC"}],"crnumber":2373.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003887.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003888","title":"Correction on Framed Routing information reporting","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Align the terminology of Framed Route with TS 23.501 and TS 23.503.","secretary_remarks":"R05 agreed. Revised to S2-2004459","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10650,"status":"revised","reservation_date":"2020-05-22 07:10:29","uploaded":"2020-05-22 12:33:12","revisionof":"","revisedto":"S2-2004459","release":"Rel-16","crspec":"23.502","crspecversion":"16.4.0","workitem":[{"winame":"5WWC"}],"crnumber":2319.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003888.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003889","title":"[DRAFT] LS Reply on clarifications on TSN for Vertical_LAN","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"This LS replies CT WG3 clarifications about the interaction between PCF and TSN AF.","secretary_remarks":"Response, merging S2-2003950 and S2-2004187, to S2-2003546. R03 agreed. Revised to S2-2004462","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10780,"status":"revised","reservation_date":"2020-05-22 07:10:31","uploaded":"2020-05-22 12:33:12","revisionof":"","revisedto":"S2-2004462","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003889.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003890","title":"Correction on the interaction between PCF and TSN AF","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the description that The TSN AF address should be pre-configured in the PCF for a 5GS Bridge. And The TSN AF should not retrieve the PCF ID from BSF but will establish the corresponding AF Session with the PCF providing the 5GS bridge information directly.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10830,"status":"noted","reservation_date":"2020-05-22 07:10:31","uploaded":"2020-05-22 12:33:12","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.503","crspecversion":"16.4.1","workitem":[{"winame":"Vertical_LAN"}],"crnumber":471.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003890.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003891","title":"Missing important assumptions on how Npcf_PolicyAuthorization_Notify is used in TSN context","source":"Huawei, HiSilicon, [Intel]","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 4.16.5.1: Clarified in step 2 that upon reception of Npcf_PolicyAuthorization_Notify on the pre-configured AF session, the AF shall request creation of a new AF session and shall subscribe for notifications on TSN related events. Annex F.1: Clarified that step 2b (Notify) is used over a pre-configured AF session, and added two more steps (Create and Subscribe, in step 2c and 2d, resp.).","secretary_remarks":"Revision of S2-2003244. R08 agreed. Revised to S2-2004463","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10810,"status":"revised","reservation_date":"2020-05-22 07:10:34","uploaded":"2020-05-22 12:33:12","revisionof":"S2-2003244","revisedto":"S2-2004463","release":"Rel-16","crspec":"23.502","crspecversion":"16.4.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":2297.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003891.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003907","title":"On Subscription to V2X services","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add a new policy data within UE context policy control subscription information. Clarify that during registration or UE trigger parameters update procedure PSI will be used","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11390,"status":"noted","reservation_date":"2020-05-22 07:55:25","uploaded":"2020-05-22 12:33:12","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.287","crspecversion":"16.2.0","workitem":[{"winame":"eV2XARC"}],"crnumber":140.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003907.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003908","title":"[DRAFT] Reply LS on subscription to V2X Services","source":"Huawei","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"This LS replies to CT WG3 LS S2-2003541\/C3-202347","secretary_remarks":"Response to S2-2003541. R08 agreed. Revised to S2-2004475","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11370,"status":"revised","reservation_date":"2020-05-22 07:55:25","uploaded":"2020-05-22 12:33:12","revisionof":"","revisedto":"S2-2004475","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003908.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003909","title":"Discussion on way forward for content of Alternative QoS Profiles.","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"discussion","for":"Agreement","abstract":"This discussion paper addresses S2-200xxxx \/ R3-202856 LS on Stage 3 for V2X QoS.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11180,"status":"noted","reservation_date":"2020-05-22 07:55:25","uploaded":"2020-05-22 12:33:12","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5G_URLLC"},{"winame":"eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003909.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003910","title":"Correction of Alternative QoS Profile handling","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In step 2) of clause 5.7.2.4.1b added text describing the details of the notifications sent to the SMF. Removed incorrect limitation to GFBR and MFBR as QoS parameters to be signalled to the UE.","secretary_remarks":"Revision of S2-2002697. Merged into S2-2004471","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11190,"status":"merged","reservation_date":"2020-05-22 07:55:25","uploaded":"2020-05-22 12:33:12","revisionof":"S2-2002697","revisedto":"S2-2005057","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"5G_URLLC"},{"winame":"eV2XARC"}],"crnumber":2228.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003910.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003911","title":"[DRAFT] Reply LS on Stage 3 for V2X QoS","source":"Huawei","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"This LS replies to RAN WG3 LS S2-2003578\/R3-202856","secretary_remarks":"Response to S2-2003578. Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11170,"status":"noted","reservation_date":"2020-05-22 07:55:26","uploaded":"2020-05-22 12:33:12","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"eV2XARC"},{"winame":"5G_V2X_NRSL"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003911.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003949","title":"Discussion on the issue raised by CT WG3 LS (S2-2003546) on the TSN.","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"discussion","for":"Discussion","abstract":"This paper discuss the issue on the CT WG3 LS (S2-2003546), and give the proposed answer.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10800,"status":"noted","reservation_date":"2020-05-22 09:17:35","uploaded":"2020-05-22 17:54:05","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003949.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003950","title":"[DRAFT] Reply LS on clarification on TSN for Vertical_LAN","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"LS out","for":"Approval","abstract":"This paper proposes a reply to Vertical_LAN LS received form CT WG3","secretary_remarks":"Response to S2-2003546. Merged into S2-2004462","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10840,"status":"merged","reservation_date":"2020-05-22 09:17:35","uploaded":"2020-05-22 17:54:05","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2003950.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004010","title":"[DRAFT] Reply LS on S1\/NG DAPS handover","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on S1\/NG DAPS handover","secretary_remarks":"Response to S2-2003579. R04 agreed. Revised to S2-2004474","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11340,"status":"revised","reservation_date":"2020-05-22 09:58:27","uploaded":"2020-05-22 12:53:02","revisionof":"","revisedto":"S2-2004474","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"LTE_feMob-Core"},{"winame":"NR_Mob_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004010.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004027","title":"[DRAFT] ReplyLS on Network Configuration Parameters in Monitoring Events","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"ReplyLS on Network Configuration Parameters in Monitoring Events","secretary_remarks":"Response to S2-2003548. Merged into S2-2004467","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10960,"status":"merged","reservation_date":"2020-05-22 10:21:55","uploaded":"2020-05-22 13:22:35","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004027.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004035","title":"[DRAFT] LS on I-NEF","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"LS out","for":"Approval","abstract":"LS to reply to CT WG3 questions on I-NEF based on SA WG2 CRs","secretary_remarks":"Response to S2-2003528. R01 agreed. Revised to S2-2004451.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10220,"status":"revised","reservation_date":"2020-05-22 10:26:45","uploaded":"2020-05-22 11:01:39","revisionof":"","revisedto":"S2-2004451","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"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_139e_Electronic\/Docs\/S2-2004035.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004036","title":"Removal of I-NEF","source":"Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removal of I-NEF from the network functions, network architectures, interfaces and reference points, its description and services. Merge I-NEF functionalities with AMF and SMF","secretary_remarks":"This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10240,"status":"agreed","reservation_date":"2020-05-22 10:26:45","uploaded":"2020-05-22 11:01:39","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2374.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200422","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004036.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004037","title":"Removal of I-NEF","source":"Nokia, Nokia Shanghai Bell, Ericsson, Huawei, HiSilicon","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: I-NEF is removed from the specification and the Monitoring Event Report normalisation, if necessary, and generation of the related charging information becomes AMF or SMF task.","secretary_remarks":"This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10250,"status":"agreed","reservation_date":"2020-05-22 10:26:46","uploaded":"2020-05-22 11:01:39","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2320.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200422","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004037.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004038","title":"Removal of I-NEF","source":"Nokia, Nokia Shanghai Bell, Ericsson, Huawei, HiSilicon","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: I-NEF is removed from the specification. In addition to this complete removal of I-NEF from this TS, another CR (0118) that modifies the I-NEF text in TS 23.273 must be stopped before plenary approval.","secretary_remarks":"This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10260,"status":"agreed","reservation_date":"2020-05-22 10:26:46","uploaded":"2020-05-22 11:01:39","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.273","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":126.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200422","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004038.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004066","title":"Missing parameters in Namf_Communication_NonUeN2MessageTransfer","source":"NTT DOCOMO, one2many","contact":"Atsushi Minokuchi","contact-id":26474,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add Send Write-Replace-Warning-Indication and Send Stop-Warning-Indication as optional input elements to Namf_Communication_NonUeN2MessageTransfer.","secretary_remarks":"R01 agreed. Revised to S2-2004480","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11670,"status":"revised","reservation_date":"2020-05-22 11:17:36","uploaded":"2020-05-22 11:28:15","revisionof":"","revisedto":"S2-2004480","release":"Rel-16","crspec":"23.502","crspecversion":"16.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":2321.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004066.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004124","title":"[DRAFT] LS response on which features cannot interwork with ETSUN","source":"Huawei,HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"LS response on which features cannot interwork with ETSUN","secretary_remarks":"Response to S2-2003549. R04 agreed. Revised to S2-2004443.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11030,"status":"revised","reservation_date":"2020-05-22 12:06:15","uploaded":"2020-05-22 16:13:30","revisionof":"","revisedto":"S2-2004443","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"ETSUN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004124.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004125","title":"Interworking between ETSUN and URLLC\/TSN","source":"Huawei, HiSilicon, China Mobile","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add description on impacts to URLLC and TSN when I-SMF is involved in the PDU Session.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11050,"status":"noted","reservation_date":"2020-05-22 12:06:15","uploaded":"2020-05-22 16:13:30","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"ETSUN"}],"crnumber":2375.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004125.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004126","title":"Interworking between ETSUN and URLLC\/TSN","source":"Huawei, HiSilicon,China Mobile","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add description on impacts to URLLC and TSN when I-SMF is involved in the PDU Session. Updated the incorrect reference step. Add the QoS monitoring related parameter into the service operation.","secretary_remarks":"Revised to S2-2004441.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11060,"status":"revised","reservation_date":"2020-05-22 12:06:19","uploaded":"2020-05-22 16:13:30","revisionof":"","revisedto":"S2-2004441","release":"Rel-16","crspec":"23.502","crspecversion":"16.4.0","workitem":[{"winame":"ETSUN"}],"crnumber":2322.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004126.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004144","title":"CR to Fix PEI inclusion in Nudm_UECM_Registration","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Ensure that PEI inclusion is mandatory in the Nudm_UECM_Registration.","secretary_remarks":". Merged into S2-2004466","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10890,"status":"merged","reservation_date":"2020-05-22 12:11:27","uploaded":"2020-05-22 18:25:30","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":2323.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004144.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004145","title":"[DRAFT] Reply LS on Presence of PEI in Nudm_UECM_Registration Requests","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"LS out","for":"Approval","abstract":"[DRAFT] Reply LS on Presence of PEI in Nudm_UECM_Registration Requests","secretary_remarks":"Response to S2-2003547. R03 agreed. Revised to S2-2004464","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10870,"status":"revised","reservation_date":"2020-05-22 12:11:28","uploaded":"2020-05-22 18:25:30","revisionof":"","revisedto":"S2-2004464","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004145.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004161","title":"[DRAFT] Reply LS on IAB supporting in NPN deployment","source":"Huawei, Hisilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3. CC: RAN WG3, CT WG1","secretary_remarks":"Response to S2-2003577. Merged into S2-2004469","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11110,"status":"merged","reservation_date":"2020-05-22 13:20:37","uploaded":"2020-05-22 13:27:05","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"RAN WG3, CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004161.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004164","title":"Unsubscribe the notification of Re-authentication and Re-authorization or Revocation","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The AMF unsubscribes the notification of Re-authentication and Re-authorization or Revocation in case UE no longer access to the authorized S-NSSAIs.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11460,"status":"noted","reservation_date":"2020-05-22 13:33:07","uploaded":"2020-05-22 16:13:30","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"eNS"}],"crnumber":2376.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004164.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004165","title":"Unsubscribe the notification of Re-authentication and Re-authorization or Revocation","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The AMF unsubscribes notification of Re-authentication and Re-authorization or Revocation in case UE no longer access to the authorized S-NSSAIs.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11470,"status":"noted","reservation_date":"2020-05-22 13:33:09","uploaded":"2020-05-22 16:13:30","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.4.0","workitem":[{"winame":"eNS"}],"crnumber":2324.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004165.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004187","title":"[DRAFT] Reply LS on clarification on TSN for Vertical_LAN","source":"Ericsson Inc.","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC: CT WG4","secretary_remarks":"Response to S2-2003546. Merged into S2-2004462","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10850,"status":"merged","reservation_date":"2020-05-22 14:35:02","uploaded":"2020-05-22 20:51:03","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"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_139e_Electronic\/Docs\/S2-2004187.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004188","title":"[DRAFT] Reply LS on early UE capability retrieval for eMTC","source":"Qualcomm Technologies Int","contact":"Miguel Griot","contact-id":84607,"tdoctype":"LS out","for":"Approval","abstract":"Response to RAN WG2 that early UE capability retrieval is feasible from system architecture perspective","secretary_remarks":"Response to S2-2003575. R07 agreed. Revised to S2-2004446.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11980,"status":"revised","reservation_date":"2020-05-22 14:36:59","uploaded":"2020-05-22 17:33:13","revisionof":"","revisedto":"S2-2004446","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3, CT WG1","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004188.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004189","title":"Truncated 5G S-TMSI for early UE capability retrieval","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":84607,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Extend the AMF provisioning of truncated 5G S-TMSI information to UEs accesing via LTE-M.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":12000,"status":"noted","reservation_date":"2020-05-22 14:43:52","uploaded":"2020-05-22 17:33:13","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"TEI16"},{"winame":"5G_CIoT"}],"crnumber":2377.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004189.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004193","title":"Early UE capability retrieval support","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":84607,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add reference to 36.300 and TS 36.413 for early UE capability retrieval procedure.","secretary_remarks":"Confirm Spec version used - CR states 16.4.0!. Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":12010,"status":"noted","reservation_date":"2020-05-22 15:10:15","uploaded":"2020-05-22 17:33:13","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.401","crspecversion":"16.6.0","workitem":[{"winame":"TEI16"}],"crnumber":3603.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004193.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004194","title":"Proposed way forward for service area restriction for CIoT 5GS optimization.","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":84607,"tdoctype":"discussion","for":"Agreement","abstract":"Discusses and proposes way forward on service area restriction for CIOT.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10190,"status":"noted","reservation_date":"2020-05-22 15:14:49","uploaded":"2020-05-22 17:33:13","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004194.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004196","title":"[DRAFT] Reply PAP\/CHAP and other point-to-point protocols usage in 5GS","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"Responds to LS from CT WG1 for use of PAP\/CHAP in 5GS","secretary_remarks":"Response to S2-2003540. R06 agreed. Revised to S2-2004481","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11700,"status":"revised","reservation_date":"2020-05-22 15:15:04","uploaded":"2020-05-22 19:03:26","revisionof":"","revisedto":"S2-2004481","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5GProtoc16"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG3, CT WG3, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004196.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004199","title":"[DRAFT] Reply LS on service area restriction for CIoT 5GS optimization","source":"Qualcomm Technologies Int","contact":"Miguel Griot","contact-id":84607,"tdoctype":"LS out","for":"Approval","abstract":"Responds that CP and UP optimization are not allowed in non-allowed area, and exception reporting is not allowed in non-allowed area.","secretary_remarks":"Response, merging S2-2003711, to S2-2003524. R06 agreed. Revised to S2-2004440.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10130,"status":"revised","reservation_date":"2020-05-22 15:19:47","uploaded":"2020-05-22 17:33:13","revisionof":"","revisedto":"S2-2004440","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004199.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004204","title":"Service Area Restriction clarification","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":84607,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1.Update clause 5.3.4.1.1 to clarify that Control Plane and User Plane optimization procedures are not allowed in a Non-Allowed Area. 2.(Editorial)Move priority service description to the beginning of the clause for easy understanding.","secretary_remarks":"Revision of S2-2002773. Merged into S2-2004439","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10200,"status":"merged","reservation_date":"2020-05-22 15:23:37","uploaded":"2020-05-22 17:33:13","revisionof":"S2-2002773","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2243.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004204.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004210","title":"UE specific DRX for NB-IoT RAN support clarification based on LS R2-2004057","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":84607,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the possiblity that each cell may or may not indicate support of UE specific DRX for NB-IoT.","secretary_remarks":"R04 agreed. Revised to S2-2004484","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11920,"status":"revised","reservation_date":"2020-05-22 15:31:11","uploaded":"2020-05-22 18:05:27","revisionof":"","revisedto":"S2-2004484","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2378.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004210.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004216","title":"UE specific DRX for NB-IoT RAN support clarification","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":84607,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the possiblity that each cell may or may not indicate support of UE specific DRX for NB-IoT.","secretary_remarks":"R06 agreed. Revised to S2-2004485","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11940,"status":"revised","reservation_date":"2020-05-22 15:35:18","uploaded":"2020-05-22 17:33:13","revisionof":"","revisedto":"S2-2004485","release":"Rel-16","crspec":"23.401","crspecversion":"16.6.0","workitem":[{"winame":"TEI16"}],"crnumber":3604.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004216.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004228","title":"Capability for HPLMN to understand whether or not the NG-RAN node supports Alternative QoS Profiles","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: More detail added to the existing requirements on AQP.","secretary_remarks":"R04 agreed. Revised, merging S2-2003910, to S2-2004471","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11250,"status":"revised","reservation_date":"2020-05-22 16:19:55","uploaded":"2020-05-22 16:29:44","revisionof":"","revisedto":"S2-2004471","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"eV2XARC"}],"crnumber":2379.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004228.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004241","title":"Update about Alternative QoS Profile","source":"Nokia, Nokia Shanghai Bell, Ericsson, CATT, LGE, ZTE, Samsung, InterDigital","contact":"Yang Shen","contact-id":68465,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies that Alternative QoS Parameters Set includes GFBR, PDB and PER.","secretary_remarks":"This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11270,"status":"agreed","reservation_date":"2020-05-22 16:59:20","uploaded":"2020-05-22 18:35:36","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.503","crspecversion":"16.4.1","workitem":[{"winame":"5G_URLLC"},{"winame":"eV2XARC"}],"crnumber":472.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200425","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004241.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004242","title":"[DRAFT] Reply LS on Stage 3 for V2X QoS","source":"VODAFONE Group Plc","contact":"Chris Pudney","contact-id":1122,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3, CT WG3, CT WG4","secretary_remarks":"Response to S2-2003578. R04 agreed. Revised to S2-2004445.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11230,"status":"revised","reservation_date":"2020-05-22 17:08:07","uploaded":"2020-05-22 17:14:00","revisionof":"","revisedto":"S2-2004445","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, CT WG3, CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004242.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004247","title":"[DRAFT] LS Reply to LS Reply to LS Reply to LS to SA WG2 Introduction of CHF Address from PCF","source":"Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"LS out","for":"Approval","abstract":"Draft LS Reply to LS Reply to LS Reply to LS to SA WG2 Introduction of CHF Address from PCF","secretary_remarks":"Response to S2-2003515. Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11590,"status":"noted","reservation_date":"2020-05-22 17:34:53","uploaded":"2020-05-22 18:34:51","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"CT3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004247.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004249","title":"Alignment with SA WG5 on Introduction of CHF Address from PCF","source":"Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add CHF address as the Access and mobility related policy information.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11580,"status":"noted","reservation_date":"2020-05-22 17:41:47","uploaded":"2020-05-22 18:34:51","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.503","crspecversion":"16.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":473.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004249.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004250","title":"[DRAFT] LS Reply to LS on Network Area Information in BDT Policy","source":"Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"LS out","for":"Approval","abstract":"Draft LS Reply to LS on Network Area Information in BDT Policy","secretary_remarks":"Response, merging S2-2003868, to S2-2003543. R05 agreed. Revised to S2-2004460","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10680,"status":"revised","reservation_date":"2020-05-22 17:48:44","uploaded":"2020-05-22 18:32:55","revisionof":"","revisedto":"S2-2004460","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004250.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004251","title":"Clarification on Network Area Information","source":"Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the texts to clarify that Network Area Information is part of background data transfer policy","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10700,"status":"noted","reservation_date":"2020-05-22 18:22:08","uploaded":"2020-05-22 18:32:55","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.503","crspecversion":"16.4.1","workitem":[{"winame":"xBDT"}],"crnumber":474.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004251.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004252","title":"Clarification on Network Area Information","source":"Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the texts to clarify that Network Area Information is part of background data transfer policy","secretary_remarks":". Merged into S2-2004402","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10710,"status":"merged","reservation_date":"2020-05-22 18:27:59","uploaded":"2020-05-22 18:32:55","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.4.0","workitem":[{"winame":"xBDT"}],"crnumber":2325.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004252.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004255","title":"Disc on manipulation of CAG Information element by a VPLMN.","source":"Samsung","contact":"Lalith Kumar","contact-id":80547,"tdoctype":"discussion","for":"Agreement","abstract":"The objective of this discussion paper is to address scenario mentioned in CT WG1 LS C1-202617 and propose solutions and a way forward for this scenario.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10370,"status":"noted","reservation_date":"2020-05-22 18:49:20","uploaded":"2020-05-22 19:54:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004255.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004258","title":"Handling manipulation of CAG by VPLMN -Sol 1","source":"Samsung","contact":"Lalith Kumar","contact-id":80547,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Specify that 1. UE updates only VPLMN CAG information received from serving VPLMN. The UE will not touch the CAG information of other PLMNs stored in the UE when CAG information is received on VPLMN. 2. When received from HPLMN UE can update CAG information of all the received PLMN CAG information.","secretary_remarks":"Revised, merging S2-2003601, to S2-2004313","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10390,"status":"revised","reservation_date":"2020-05-22 18:51:57","uploaded":"2020-05-22 19:54:50","revisionof":"","revisedto":"S2-2004313","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":2380.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004258.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004260","title":"Handling manipulation of CAG by VPLMN -Sol 2","source":"Samsung","contact":"Lalith Kumar","contact-id":80547,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Specify that 1. The UE can be pre-configured with trusted PLMN list; and 2. UE will update the allowed CAG information for all the received PLMN CAG information when received from HPLMN or any of the trusted PLMNs configured in the UE. 3. UE updates only VPLMN CAG information received from serving VPLMN if VPLMN is not part of tusted PLMN list.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10420,"status":"noted","reservation_date":"2020-05-22 18:54:19","uploaded":"2020-05-22 19:54:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":2381.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004260.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004261","title":"[DRAFT] Reply LS on manipulation of CAG Information element by a VPLMN","source":"Samsung R&D Institute India","contact":"Lalith Kumar","contact-id":80547,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: SA WG3. Attachments: S2-2x-23.501","secretary_remarks":"Response, merging S2-2003641, to S2-2003535. Revised to S2-2004453.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10350,"status":"revised","reservation_date":"2020-05-22 18:56:39","uploaded":"2020-05-22 19:54:50","revisionof":"","revisedto":"S2-2004453","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004261.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004262","title":"[DRAFT] Reply LS on Updated User Plane Integrity Protection advice","source":"Samsung R&D Institute India","contact":"Lalith Kumar","contact-id":80547,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3. CC: CT WG1","secretary_remarks":"Response to S2-2004308. Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":12080,"status":"noted","reservation_date":"2020-05-22 18:58:54","uploaded":"2020-05-22 19:54:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004262.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004278","title":"[DRAFT] Reply LS on IAB supporting in NPN deployment","source":"Qualcomm Incorperated","contact":"Hong Cheng","contact-id":25668,"tdoctype":"LS out","for":"Approval","abstract":"Response to RAN WG2 on IAB support in NPN.","secretary_remarks":"Response, merging S2-2004161, to S2-2003577. R01 agreed. Revised to S2-2004469","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11120,"status":"revised","reservation_date":"2020-05-22 20:19:51","uploaded":"2020-05-22 22:34:32","revisionof":"","revisedto":"S2-2004469","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"IABARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004278.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004281","title":"IAB support in NPN deployment","source":"Qualcomm Incorporated, AT&T","contact":"Hong Cheng","contact-id":25668,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add clarification that the IAB can operate with the backhaul connectivity is with the SNPN.","secretary_remarks":"R03 agreed. Revised to S2-2004470","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11140,"status":"revised","reservation_date":"2020-05-22 21:14:25","uploaded":"2020-05-22 22:34:32","revisionof":"","revisedto":"S2-2004470","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"IABARC"}],"crnumber":2382.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004281.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004301","title":"[DRAFT] Reply LS on protection of allowed CAG list against MITM Attack","source":"InterDigital, Europe, Ltd.","contact":"Guanzhou Wang","contact-id":72777,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3, CT WG1. Attachments: TS 23.501 CR #xxxx","secretary_remarks":"Response to S2-2004304. R04 agreed. Revised to S2-2004455","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10520,"status":"revised","reservation_date":"2020-05-22 23:34:05","uploaded":"2020-05-22 23:47:00","revisionof":"","revisedto":"S2-2004455","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004301.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004302","title":"Updating the UE with new CAG information","source":"Ericsson??, Qualcomm Incorporated??, China Mobile?? InterDigital","contact":"Guanzhou Wang","contact-id":72777,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified when the network configures the UE with CAG information. Correcting the usage of 'UE 5GMM Core Network Capability'.","secretary_remarks":"Revision of S2-2003249. Confirm Sources! Merged into S2-2004311","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10440,"status":"merged","reservation_date":"2020-05-22 23:38:43","uploaded":"2020-05-22 23:47:00","revisionof":"S2-2003249","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":2135.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004302.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004303","title":"LS from BBF: LS on the applicability of 5G NAS protocol for 5G-RG and FN-RG","source":"BBF","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"Dear colleagues, We understand that CT WG1 has been working on updating several 5G UE to core network interface specifications for Rel-16 functionality, including the wireline access. While we know about multiple agreed CRs specifically addressing the 5G-RG and FN-RG, we believe it is challenging for the 5G-RG and AGF (for FN-RG) implementors to understand which procedures, messages and information elements are relevant for these UE types exactly. We have also seen that during Rel-15, an excellent summary has been provided about applying the protocol for non-3GPP access (then only untrusted access, i.e. N3IWF) in section 4.7 of TS24.501. The Rel-16 version of this TS contains a dedicated section (4.13) for wireline access, but as of the latest version available, that provides a high level overview of the relevant architecture and refers to stage2 \/ TS23.316 for details. Note: For W-AGF to AMF, we also have TS29.413 providing such profiling for the N2AP protocol, provided by RAN WG3, and this has been updated for new access types added in Rel-16. Our expectation has been that CT WG1 will also provide a detailed technical summary to define the wireline specific aspects within non-3GPP access. This would be a key reference item in the WWC specifications provided by BBF. We also assume that such information will be helpful for CableLabs as well and will remove risks for different interpretation between BBF and CableLabs usage of N1 interface. We kindly ask CT WG1 to confirm whether the section 4.13 (or 4.7) of TS24.501 is planned to be updated to provide a technical summary on how to apply the 5G NAS for wireline access, and if so, to provide an estimated timeline for it. Also, please advise if there is any similar summary planned for the other relevant CT WG1 specifications, such as TS24.526 or TS24.193. Thanks, Lincoln Lavoie, Broadband Forum Technical Committee Chair","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10080,"status":"noted","reservation_date":"2020-05-27 05:47:31","uploaded":"2020-05-27 05:47:59","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG2, CableLabs","lsoriginalls":"LIAISE-397-03","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004303.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004304","title":"LS from SA WG3: LS on protection of allowed CAG list against MITM Attack","source":"SA WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 identifies that the allowed CAG list in a UE will be wrongly deleted if the UE is rejected by the AMF and receives a forged list of supported CAG Identifier(s) of the CAG cell broadcasted by a false base station staging a Man-in-the-Middle (MITM) attack. SA WG3 kindly asks SA WG2 to take this information into account. Action: SA WG3 kindly asks SA WG2 group to take the above information into account.","secretary_remarks":"Response drafted in S2-2004301. Final response in S2-2004455","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10510,"status":"replied to","reservation_date":"2020-05-27 05:47:31","uploaded":"2020-05-27 05:47:59","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1","lsoriginalls":"S3-201414","lsreply":"S2-2004455","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004304.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004305","title":"LS from SA WG3: Reply LS on SUCI computation from an NSI","source":"SA WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 would like to thank CT WG1 for the LS (S3-200906\/C1-200938) on SUCI computation from an NSI. [Question from CT WG1] CT WG1 asks SA WG3 to provide reasons for specification of a SUPI of the NSI SUPI type containing an NSI derived from an IMSI in Rel-16. [Answer from SA WG3] SA WG3 does not see a need for a SUPI of the NSI SUPI type containing an NSI derived from an IMSI in Rel-16.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10090,"status":"noted","reservation_date":"2020-05-27 05:47:31","uploaded":"2020-05-27 05:47:59","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"CT WG6, SA WG2, CT WG4","lsoriginalls":"S3-201432","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004305.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004306","title":"LS from SA WG3: LS reply on security context for 5GC to EPC mobility","source":"SA WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 has evaluated the specification misalignment described in the LS. From security point of view, SA WG3 sees no security issue with the current 24.501 specification despite the misalignment.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10070,"status":"noted","reservation_date":"2020-05-27 05:47:31","uploaded":"2020-05-27 05:47:59","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG2","lsoriginalls":"S3-201453","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004306.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004307","title":"LS from SA WG3: LS reply to RAN WG3 LS on AS rekeying handling","source":"SA WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 thanks RAN WG3 for its LS S3-201325 \/ R3-202833 on AS rekeying handling. SA WG3 discussed the two questions and agreed on following answers: Q1. RAN WG3 respectfully asks SA WG3 to feedback whether it is acceptable for the network to give up the AS re-keying procedure and only initiate the emergency fallback procedure when the two procedures collide. SA WG3 Answer: It is acceptable to SA WG3, for the network to give up the AS re-keying procedure and only initiate the emergency fallback procedure when the two procedures collide. Q2. Besides, RAN WG3 would like to ask SA WG3 to feedback whether it should be supported for the NG-RAN node to inform the AMF of the re-keying failure when NG-RAN node received an AS re-keying request via either UE CONTEXT MODIFICATION REQUEST message or PATH SWITCH REQUEST ACKNOWLEDGE message SA WG3 Answer: SA WG3 does not reach an agreement on this question.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10100,"status":"noted","reservation_date":"2020-05-27 05:47:31","uploaded":"2020-05-27 05:47:59","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"SA WG2","lsoriginalls":"S3-201484","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004307.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004308","title":"LS from SA WG3: LS on Updated User Plane Integrity Protection advice","source":"SA WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 has reviewed the information provided by the GSMA regarding user plane integrity protection (UPIP) related attacks on 3GPP 4G and 5G networks. Whilst these attacks are very difficult, require very skilled attackers to exploit and are currently localised attacks based on false base stations, SA WG3 is conscious that once such attacks are known, refinements and the development of tools for less skilled attacks usually follow. SA WG3 advises that it has agreed the following 2 CR's: 1. S3-201442 (attached) - CR to 33.501 (5G security) - Adds an informative annex describing how to secure DNS and ICMP traffic 2. S3-201443 (attached) - CR to TS 33.401 (LTE security) - Adds an informative reference to the informative annex added into TS 33.501 describing how to secure DNS and ICMP traffic Additionally, SA WG3 discussed S3-201457 (attached), but several delegates raised concerns about the impacts of this solution on SA WG2 specifications. SA WG2 are invited to comment as to whether S3-201296 has any adverse impacts. Actions: 1. SA WG3 kindly asks CT WG1 and SA WG2 to review this information and update their specifications from release 16 accordingly. 2. SA WG3 kindly asks SA WG2 to review and comment as to whether S3-201457 has any adverse impacts on their specifications.","secretary_remarks":"Response drafted in S2-2004262.Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":12070,"status":"postponed","reservation_date":"2020-05-27 05:47:31","uploaded":"2020-05-27 05:47:59","revisionof":"","revisedto":"S2-2004776","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, SA WG2","Cc":"TSG SA, TSG RAN","lsoriginalls":"S3-201487","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004308.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004309","title":"LS from SA WG3: LS on security consideration of performance measurement function protocol","source":"SA WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 thanks CT WG1 for the LS C1-196940 on security consideration of performance measurement function protocol. SA WG3 has analysed the security aspects of PMF protocol. According to the analysis, SA WG3 concludes that existing security mechanisms in 5G system are sufficient. However, compromised UEs may send false or incorrect PMF reports, even though the transport to the network is secured. Networks should be aware of this risk when relying on such falsified PMF reports from compromised UEs.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10110,"status":"noted","reservation_date":"2020-05-27 05:47:31","uploaded":"2020-05-27 05:47:59","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG2","lsoriginalls":"S3-201490","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004309.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004311","title":"Updating the UE with new CAG information","source":"Ericsson, Qualcomm Incorporated, China Mobile, InterDigital","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified when the network configures the UE with CAG information. Correcting the usage of 'UE 5GMM Core Network Capability'.","secretary_remarks":"Revision of S2-2003599, merging S2-2004302. This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10460,"status":"agreed","reservation_date":"2020-05-27 15:04:46","uploaded":"2020-05-28 08:50:33","revisionof":"S2-2003599","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":2135.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"SP-200438","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004311.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004313","title":"Handling manipulation of CAG by VPLMN -Sol 1","source":"Samsung, Ericsson, Qualcomm Incorporated, InterDigital","contact":"Lalith Kumar","contact-id":80547,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Specify that 1. UE updates only VPLMN CAG information received from serving VPLMN. The UE will not touch the CAG information of other PLMNs stored in the UE when CAG information is received on VPLMN. 2. When received from HPLMN UE can update CAG information of all the received PLMN CAG information. 3. when the UE gets rejected, the UE will update its stored CAG information based on information received in reject message.","secretary_remarks":"Revision of S2-2004258, merging S2-2003601. R02 agreed. Revised to S2-2004454","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10400,"status":"revised","reservation_date":"2020-05-28 11:55:35","uploaded":"2020-05-28 11:56:00","revisionof":"S2-2004258","revisedto":"S2-2004454","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":2380.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004313.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004315","title":"LS from SA WG1: Reply LS on CMAS\/ETWS and emergency services for SNPNs","source":"SA WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"SA WG1 thanks RAN WG2 for the LS on CMAS\/ETWS and emergency services for SNPNs. In response to the questions from RAN WG2, SA WG1 provides the following: - There are no SA WG1 service requirements related to the support of PWS by SNPNs in Rel-16. - SA WG1 plans to further discuss adding service requirements for the support of PWS by SNPNs from Rel-17 onward. Action: SA WG1 asks RAN WG2 and SA WG2 groups to take the above information into account.","secretary_remarks":"Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10480,"status":"postponed","reservation_date":"2020-05-28 06:05:24","uploaded":"2020-05-28 06:06:10","revisionof":"","revisedto":"S2-2004777","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, SA WG2","Cc":"CT WG1","lsoriginalls":"S1-202220","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004315.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004317","title":"LS from SA WG1: Reply LS on Manual CAG ID selection and granularity of UAC parameters for PNI-NPNs","source":"SA WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 thanks RAN WG2 for their incoming LS on Manual CAG ID selection and granularity of UAC parameters for PNI-NPNs, and related questions. SA WG1 answers are provided below. Question 2.1: Is there a requirement to enable PNI-NPN (CAG ID) specific access control in cells that are shared among PNI-NPNs belonging to the same PLMN? SA WG1 currently does not have a specific requirement to enable PNI-NPN (CAG ID) specific access control in cells that are shared among PNI-NPNs belonging to the same PLMN. Question 2.2: If there is a requirement to enable PNI-NPN (CAG ID) specific access control in cells that are shared among PNI-NPNs belonging to the same PLMN, then is it sufficient to broadcast the Unified Access Control (UAC) parameters per PLMN (assuming that using the operator-defined access categories with access category criteria type set to the S-NSSAI used for PNI-NPN is sufficient to provide CAG specific UAC) or there is need to enable the broadcast of CAG ID specific configuration of UAC parameters? Since the answer to Q2.1 is no, answer to Q2.2 is not needed.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10490,"status":"noted","reservation_date":"2020-05-28 06:05:25","uploaded":"2020-05-28 06:06:10","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"CT WG1, SA WG2, RAN WG3","lsoriginalls":"S1-202265","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004317.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004321","title":"LS from SA WG1: reply LS on UAC applicability to IABs","source":"SA WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 thanks RAN WG2 for the LS noted in the header. In concurrence with the RAN WG2 agreement that IAB-MTs are not under UAC control, SA WG1 has agreed the attached CR for Rel-16. - SA WG1 may further discuss requirements for IAB-MTs in Rel-17.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10050,"status":"noted","reservation_date":"2020-05-28 06:05:25","uploaded":"2020-05-28 06:06:10","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, CT WG1","Cc":"RAN WG3, SA WG2","lsoriginalls":"S1-202274","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004321.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004322","title":"LS from SA WG1: Reply LS on manual CAG selection","source":"SA WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 thanks RAN WG2 for the LS in R2-2003870, and the question for SA WG1 action, i.e.: 'whether the indication that the PLMN allows a user to manually select a CAG-ID supported by the CAG cell but outside the UE's allowed CAG list is per PLMN or per CAG ID'. SA WG1 has discussed about the following existing SA WG1 Rel-16 requirement (from TS 22.261): The 5G system shall support a mechanism for a PLMN to control whether a user of a UE can manually select a non-public network hosted by this PLMN that the UE is not authorized to select automatically. and agreed that the indication allowing to manually select a CAG-ID supported by the CAG cell but outside the UE's allowed CAG list, is per CAG ID.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10540,"status":"noted","reservation_date":"2020-05-28 06:05:25","uploaded":"2020-05-28 06:06:10","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, CT WG1","Cc":"SA WG2, RAN WG3","lsoriginalls":"S1-202277","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004322.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004327","title":"[DRAFT] Reply LS on Clarification on eNA","source":"Nokia, Nokia Shanghai Bell, Huawei, HiSilicon","contact":"Yannick Lair","contact-id":76350,"tdoctype":"LS out","for":"Approval","abstract":"Draft reply LS to CT WG3 on Clarification on eNA","secretary_remarks":"Revision of S2-2003667, merging S2-2003866. Response to S2-2004327. Revised to remove 'draft' in S2-2004482.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11750,"status":"revised","reservation_date":"2020-05-28 14:25:21","uploaded":"2020-05-29 06:07:46","revisionof":"S2-2003667","revisedto":"S2-2004482","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004327.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004328","title":"Corrections for maximum number of objects and Maximum number of SUPIs","source":"Nokia, Nokia Shanghai Bell, Samsung, Huawei","contact":"Yannick Lair","contact-id":76350,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1\/ Make sure that maximum number of objects and maximum number of SUPIs are independent request parameters from the Analytics filters. 2\/ Add Maximum number of objects as an optional parameter for the request for expected UE behavioural parameters analytics.","secretary_remarks":"Revision of S2-2003668, merging S2-2003867. This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11790,"status":"agreed","reservation_date":"2020-05-28 14:25:21","uploaded":"2020-05-29 06:07:46","revisionof":"S2-2003668","revisedto":"","release":"Rel-16","crspec":"23.288","crspecversion":"16.3.0","workitem":[{"winame":"eNA"}],"crnumber":176.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200431","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004328.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004335","title":"Reply LS on manual CAG ID selection and granularity of UAC parameters for PNI-NPNs","source":"SA WG2","contact":"xiaowan ke","contact-id":74585,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2. CC: CT WG1, RAN WG3, SA WG1","secretary_remarks":"Revision of S2-2003640_r01. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10330,"status":"approved","reservation_date":"2020-06-02 07:18:15","uploaded":"2020-06-02 07:32:23","revisionof":"S2-2003640","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2003530","lsto":"RAN WG2","Cc":"CT WG1, RAN WG3, SA WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004335.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004439","title":"Service Area Restriction clarification","source":"Ericsson, Qualcomm","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1.Update clause 5.3.4.1.1 to clarify what services are not allowed and allowed in a Non-Allowed Area. 2.(Editorial)Move priority service description to the beginning of the clause for easy understanding.","secretary_remarks":"Revision of S2-2003712_R13, merging S2-2004204. This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10170,"status":"agreed","reservation_date":"2020-06-08 15:11:20","uploaded":"2020-06-08 15:18:00","revisionof":"S2-2003712","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2243.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-200422","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004439.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004440","title":"Reply LS on service area restriction for CIoT 5GS optimization","source":"SA WG2","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1, SA WG1. Attachments: TS 23.501 CR 2243 (S2-2004439)","secretary_remarks":"Revision of S2-2004199_R06, merging S2-2003711. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10140,"status":"approved","reservation_date":"2020-06-08 15:11:21","uploaded":"2020-06-08 15:18:00","revisionof":"S2-2004199","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2003524","lsto":"CT WG1, SA WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004440.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004441","title":"Interworking between ETSUN and URLLC\/TSN","source":"Huawei, HiSilicon,China Mobile, Nokia, Nokia Shanghai Bell, Ericsson, ZTE","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Defines whether and if yes how ETSUN interworks with features defined for URLLC, TSC and NPN Updated the incorrect reference step.","secretary_remarks":"Revision of S2-2004126. This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11070,"status":"agreed","reservation_date":"2020-06-08 15:11:21","uploaded":"2020-06-08 15:18:00","revisionof":"S2-2004126","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.4.0","workitem":[{"winame":"ETSUN"},{"winame":"5G_URLLC"},{"winame":"Vertical_LAN"}],"crnumber":2322.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200433","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004441.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004442","title":"URLLC - TSN interworking with ETSUN","source":"Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Defines whether and if yes how ETSUN interworks with features defined for URLLC, TSC and NPN.","secretary_remarks":"Revision of S2-2003705. This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11090,"status":"agreed","reservation_date":"2020-06-08 15:11:22","uploaded":"2020-06-08 15:18:00","revisionof":"S2-2003705","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"ETSUN"},{"winame":"Vertical_LAN"},{"winame":"5G_URLLC"}],"crnumber":2371.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200433","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004442.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004443","title":"LS Response on which features cannot interwork with ETSUN","source":"SA WG2","contact":"Fenqin Zhu","contact-id":26772,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. Attachments: 23.501 CR2371, 23.502 CR2322","secretary_remarks":"Revision of S2-2004124_R04. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11040,"status":"approved","reservation_date":"2020-06-08 15:11:23","uploaded":"2020-06-08 15:18:00","revisionof":"S2-2004124","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"ETSUN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2003549","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004443.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004444","title":"Alignment on Alternative QoS Profile","source":"Ericsson, LG Electronics, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify what QoS parameters are included in the Alternative QoS profile.","secretary_remarks":"Revision of S2-2003704. This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11220,"status":"agreed","reservation_date":"2020-06-08 15:11:24","uploaded":"2020-06-08 15:18:00","revisionof":"S2-2003704","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"eV2XARC"}],"crnumber":2370.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200434","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004444.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004445","title":"Reply LS on Stage 3 for V2X QoS","source":"SA WG2","contact":"Chris Pudney","contact-id":1122,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3, CT WG3, CT WG4. Attachments: S2-2004471 (TS 23.501 CR 2379R1)","secretary_remarks":"Revision of S2-2004242_R04. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11240,"status":"approved","reservation_date":"2020-06-08 15:11:25","uploaded":"2020-06-08 15:18:00","revisionof":"S2-2004242","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2003578","lsto":"RAN WG3, CT WG3, CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004445.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004446","title":"Reply LS on early UE capability retrieval for eMTC","source":"SA WG2","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2, RAN WG3, CT WG1. CC: SA WG3","secretary_remarks":"Revision of S2-2004188_R07. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11990,"status":"approved","reservation_date":"2020-06-08 15:11:25","uploaded":"2020-06-08 15:18:00","revisionof":"S2-2004188","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2003575","lsto":"RAN WG2, RAN WG3, CT WG1","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004446.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004447","title":"Reflective QoS","source":"Huawei, HiSilicon, Ericsson, Tencent","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified how the SMF starts and stops Reflective QoS.","secretary_remarks":"Revision of S2-2003864_R05. This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":12120,"status":"agreed","reservation_date":"2020-06-08 15:11:25","uploaded":"2020-06-08 15:18:00","revisionof":"S2-2003864","revisedto":"","release":"Rel-15","crspec":"23.501","crspecversion":"15.9.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2237.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-200420","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004447.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004448","title":"Reflective QoS","source":"Huawei, HiSilicon, Ericsson, Tencent","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: It is clarified how the SMF starts and stops Reflective QoS.","secretary_remarks":"Revision of S2-2003865. This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":12140,"status":"agreed","reservation_date":"2020-06-08 15:11:26","uploaded":"2020-06-08 15:18:00","revisionof":"S2-2003865","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1732.0,"crrevision":5.0,"crcategory":"A","tsg_crp":"SP-200420","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004448.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004451","title":"Reply LS on Service on I-NEF Event Exposure","source":"SA WG2","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3, CT WG4. Attachments: TS 23.501 CR 2374, TS 23.502 CR 2320, TS 23.273 CR 0126","secretary_remarks":"Revision of S2-2004035r01. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10230,"status":"approved","reservation_date":"2020-06-04 15:47:00","uploaded":"2020-06-04 15:47:55","revisionof":"S2-2004035","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2003528","lsto":"CT WG3, CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004451.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004452","title":"Reply LS on NAS Non delivery for RRC Inactive state","source":"SA WG2","contact":"Irfan Ali","contact-id":74090,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3, CT WG4","secretary_remarks":"Revision of S2-2003805r06. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11560,"status":"approved","reservation_date":"2020-06-04 15:47:00","uploaded":"2020-06-04 15:47:55","revisionof":"S2-2003805","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2003531","lsto":"RAN WG3, CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004452.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004453","title":"Reply LS on manipulation of CAG Information element by a VPLMN","source":"SA WG2","contact":"Lalith Kumar","contact-id":80547,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: SA WG3. Attachments: S2-2x-23.501","secretary_remarks":"Revision of S2-2004261, merging S2-2003641. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10360,"status":"approved","reservation_date":"2020-06-08 15:11:27","uploaded":"2020-06-08 15:18:00","revisionof":"S2-2004261","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2003535","lsto":"CT WG1","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004453.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004454","title":"Handling manipulation of CAG by VPLMN -Sol 1","source":"Samsung, Ericsson, Qualcomm Incorporated, InterDigital, Nokia, Nokia Shanghai Bell","contact":"Lalith Kumar","contact-id":80547,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Specify that 1. UE updates only VPLMN CAG information received from serving VPLMN. The UE will not touch the CAG information of other PLMNs stored in the UE when CAG information is received on VPLMN. 2. When received from HPLMN UE can update CAG information of all the received PLMN CAG information. 3. when the UE gets rejected, the UE will update its stored CAG information based on information received in reject message.","secretary_remarks":"Revision of S2-2004313_r02. This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10410,"status":"agreed","reservation_date":"2020-06-08 15:11:27","uploaded":"2020-06-08 15:18:00","revisionof":"S2-2004313","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":2380.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-200438","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004454.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004455","title":"Reply LS on protection of allowed CAG list against MITM Attack","source":"SA WG2","contact":"Guanzhou Wang","contact-id":72777,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3, CT WG1. Attachments: TS 23.501 CR #2380","secretary_remarks":"Revision of S2-2004301_r04. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10530,"status":"approved","reservation_date":"2020-06-08 15:11:28","uploaded":"2020-06-08 15:18:00","revisionof":"S2-2004301","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2004304","lsto":"SA WG3, CT WG1","Cc":"","lsoriginalls":"","lsreply":"C1-205260","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004455.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004456","title":"Reply LS on Clarification of the support of the Frame Routing Feature","source":"SA WG2","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. Attachments: 23.501 CR 2369, 23.502 CR 2319, 23.503 CR0470","secretary_remarks":"Revision of S2-2003657_r02 . Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10570,"status":"approved","reservation_date":"2020-06-08 15:11:28","uploaded":"2020-06-08 15:18:00","revisionof":"S2-2003657","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2003542","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004456.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004457","title":"Clarification of the Support of the Frame Routing Feature","source":"Nokia, Nokia Shanghai Bell, Ericsson, Huawei","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If the SMF receives Framed Routes information both from DN-AAA and from UDM, the information received from DN-AAA takes precedence and supersedes the information received from UDM If the UDM or DN-AAA updates the Framed Routes information during the lifetime of the PDU session, the SMF releases the PDU Session and may include in the release request an indication for the UE to re-establish the PDU session.","secretary_remarks":"Revision of S2-2003655_r03. This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10590,"status":"agreed","reservation_date":"2020-06-08 15:11:28","uploaded":"2020-06-08 15:18:00","revisionof":"S2-2003655","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"5WWC"}],"crnumber":2369.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200427","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004457.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004458","title":"Correction on Framed Route information reporting","source":"Huawei, HiSilicon, Nokia, Nokia Shaghai Bell, Ericsson","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the description that PCF may send the Framed Routes information to the BSF.","secretary_remarks":"Revision of S2-2003886_r04. This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10630,"status":"agreed","reservation_date":"2020-06-08 15:11:29","uploaded":"2020-06-08 15:18:00","revisionof":"S2-2003886","revisedto":"","release":"Rel-16","crspec":"23.503","crspecversion":"16.4.1","workitem":[{"winame":"5WWC"}],"crnumber":470.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200427","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004458.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004459","title":"Correction on Framed Route information reporting","source":"Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Ericsson","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Align the terminology of Framed Route with TS 23.501 and TS 23.503.","secretary_remarks":"Revision of S2-2003888_r05. This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10660,"status":"agreed","reservation_date":"2020-06-08 15:11:29","uploaded":"2020-06-08 15:18:00","revisionof":"S2-2003888","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.4.0","workitem":[{"winame":"5WWC"}],"crnumber":2319.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200427","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004459.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004460","title":"LS Reply to LS on Network Area Information in BDT Policy","source":"SA WG2","contact":"Sherry Shen","contact-id":53713,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3","secretary_remarks":"Revision of S2-2004250_r05 merging S2-2003868. Approved,","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10690,"status":"approved","reservation_date":"2020-06-08 15:11:30","uploaded":"2020-06-08 15:18:00","revisionof":"S2-2004250","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2003543","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004460.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004461","title":"Correction of BDT policy re-negotiation procedure","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: First, remove the analytics parameters such as load and number of UEs in the Network Performance analytics. Second, some others clarifications of the BDT procedures.","secretary_remarks":"Revision of S2-2003870_r04. This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10750,"status":"agreed","reservation_date":"2020-06-08 15:11:30","uploaded":"2020-06-08 15:19:09","revisionof":"S2-2003870","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.4.0","workitem":[{"winame":"eNA"},{"winame":"xBDT"}],"crnumber":2237.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-200431","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004461.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004462","title":"LS Reply on clarification on TSN for Vertical_LAN","source":"SA WG2","contact":"Haiyang Sun","contact-id":79579,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. Attachments: TS 23.502 CR#2297 (S2-2004463)","secretary_remarks":"Revision of S2-2003889_r03, merging S2-2003950 and S2-2004187. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10790,"status":"approved","reservation_date":"2020-06-08 15:11:31","uploaded":"2020-06-08 15:19:09","revisionof":"S2-2003889","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2003546","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004462.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004463","title":"Missing important assumptions on how Npcf_PolicyAuthorization_Notify is used in TSN context","source":"Intel, Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 4.16.5.1: Clarified in step 2 that upon reception of Npcf_PolicyAuthorization_Notify on the pre-configured AF session, the AF shall request creation of a new AF session and shall subscribe for notifications on TSN related events. Annex F.1: Clarified that step 2b (Notify) is used over a pre-configured AF session, and added two more steps (Create and Subscribe, in step 2c and 2d, resp.). Clarify the Nbsf service, the UE MAC address may be DS-TT port MAC address.","secretary_remarks":"Revision of S2-2003891_r08. This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10820,"status":"agreed","reservation_date":"2020-06-08 15:11:31","uploaded":"2020-06-08 15:19:09","revisionof":"S2-2003891","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.4.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":2297.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-200439","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004463.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004464","title":"Reply LS on Presence of PEI in Nudm_UECM_Registration Requests","source":"SA WG2","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. Attachments: TS 23.502 CR#2310 (S2-2004465) and CR#2311 (S2-2004466)","secretary_remarks":"Revision of S2-2004145_r03. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10880,"status":"approved","reservation_date":"2020-06-08 15:11:33","uploaded":"2020-06-08 15:19:09","revisionof":"S2-2004145","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2003547","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004464.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004465","title":"Presence of PEI in Nudm_UECM_Registration Request","source":"Ericsson, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clauses 4.2.2.2.1 : clarify that the AMF shall retrieve PEI if needed. Clause 5.2.3.2.1: Move PEI from 'Input, Required' to 'Input, Optional', add text","secretary_remarks":"Revision of S2-2003614_r04. This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10920,"status":"agreed","reservation_date":"2020-06-08 15:11:33","uploaded":"2020-06-08 15:19:09","revisionof":"S2-2003614","revisedto":"","release":"Rel-15","crspec":"23.502","crspecversion":"15.9.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2310.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200420","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004465.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004466","title":"Presence of PEI in Nudm_UECM_Registration Request","source":"Ericsson, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Clauses 4.2.2.2.1: clarify that the AMF shall retrieve PEI if needed. Clause 5.2.3.2.1: Move PEI from 'Input, Required' to 'Input, Optional', add text.","secretary_remarks":"Revision of S2-2003615, merging S2-2004144. This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10940,"status":"agreed","reservation_date":"2020-06-08 15:11:34","uploaded":"2020-06-08 15:19:09","revisionof":"S2-2003615","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2311.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"SP-200420","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004466.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004467","title":"Reply LS on 'LS on Network Configuration Parameters in Monitoring Events'","source":"SA WG2","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC: CT WG3. Attachments: 23.502 CR2312 (S2-2004468)","secretary_remarks":"Revision of S2-2003616_r05, merging S2-2004027. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":10980,"status":"approved","reservation_date":"2020-06-08 15:11:35","uploaded":"2020-06-08 15:19:09","revisionof":"S2-2003616","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2003548","lsto":"CT WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004467.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004468","title":"Network Parameters Configuration by Parameter Provisioning and Event Exposure Subscription","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 4.15.3.2.3b, Correct the description related to Suggested Number of Downlink Packets to be consistent with clause 4.15.6.3a (i.e. Suggested Number of Downlink Packets are SMF-associated parameters). Clarify how UDM derives the subscribed periodic registration timer and subscribed Active Time. Correct the behavior how UDM derives the Suggested Number of Downlink Packets. Add a warning saying that Event Exposure to configure network parameters is assumed to be used only when the AF does not support Parameter Provision service operation. Clause 4.15.6.3a: Remove the text indicating that parameters Maximum Latency and Maximum Response Time are associated with DNN and S-NSSAI; Clarify that the SMF-associated parameters Suggested Number of Downlink Packets are provided by UDM to SMF; Clarify how the UDM handles multiple requests of Network Configuration parameters for AMF- and SMF-associated parameters. Clauses 5.2.3.6.3, 5.2.3.6.4: Allow Nudm_ParameterProvision_Create and Nudm_ParameterProvision_Delete to handle network configuration parameters.","secretary_remarks":"Revision of S2-2003617_r06. This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11000,"status":"agreed","reservation_date":"2020-06-08 15:11:35","uploaded":"2020-06-08 15:19:09","revisionof":"S2-2003617","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2312.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200422","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004468.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004469","title":"Reply LS on IAB supporting in NPN deployment","source":"SA WG2","contact":"Hong Cheng","contact-id":25668,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2, RAN WG3, TSG SA. CC CT WG1. Attachments: CR 2382 to TS 23.501 (S2-2004470)","secretary_remarks":"Revision of S2-2004278_r01, merging S2-2004161. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11130,"status":"approved","reservation_date":"2020-06-08 15:11:36","uploaded":"2020-06-08 15:19:09","revisionof":"S2-2004278","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"IABARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2003577","lsto":"RAN WG2, RAN WG3, TSG SA","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004469.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004470","title":"IAB support in NPN deployment","source":"Qualcomm Incorporated, AT&T, Ericsson, Nokia, Kyocera","contact":"Hong Cheng","contact-id":25668,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add clarification that the IAB can operate with the backhaul connectivity is with the SNPN.","secretary_remarks":"Revision of S2-2004281_r03. This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11150,"status":"agreed","reservation_date":"2020-06-08 15:11:36","uploaded":"2020-06-08 15:19:10","revisionof":"S2-2004281","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"IABARC"}],"crnumber":2382.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200435","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004470.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004471","title":"Capability for HPLMN to understand whether or not the NG-RAN node supports Alternative QoS Profiles","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: More detail added to the existing requirements on AQP.","secretary_remarks":"Revision of S2-2004228_r04, merging S2-2003910. This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11260,"status":"agreed","reservation_date":"2020-06-08 15:11:37","uploaded":"2020-06-08 15:19:10","revisionof":"S2-2004228","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"eV2XARC"}],"crnumber":2379.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200434","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004471.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004472","title":"Alignment CR for DAPS HO","source":"Qualcomm Incorporated, Ericsson","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - adds new clause 5.5.1.2.2a to support DAPS HO. New changes beyond RAN's spec. - S-RAN requests DAPS HO when DAPS HO is supported by both S-RAN and S-MME. - T-RAN sends the DAPS Information IE If the DAPS HO is supported by both the T-RAN and T-MME.","secretary_remarks":"Revision of S2-2003848_r05. This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11310,"status":"agreed","reservation_date":"2020-06-08 15:11:38","uploaded":"2020-06-08 15:19:10","revisionof":"S2-2003848","revisedto":"","release":"Rel-16","crspec":"23.401","crspecversion":"16.6.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"NR_Mob_enh-Core"},{"winame":"LTE_feMob-Core"}],"crnumber":3602.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"SP-200551","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004472.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004473","title":"Alignment CR for DAPS HO","source":"Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell, CATT","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - adds new clause 4.9.1.3.3a to support DAPS HO. New changes beyond RAN's spec. - S-RAN requests DAPS HO when DAPS HO is supported by both S-RAN and S-AMF. - T-RAN sends the DAPS Information IE If the DAPS HO is supported by both the T-RAN and T-AMF.","secretary_remarks":"Revision of S2-2003860_r07. This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11330,"status":"agreed","reservation_date":"2020-06-08 15:11:39","uploaded":"2020-06-08 15:19:10","revisionof":"S2-2003860","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"NR_Mob_enh-Core"},{"winame":"LTE_feMob-Core"}],"crnumber":2318.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"SP-200551","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004473.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004474","title":"Reply LS on S1\/NG DAPS handover","source":"SA WG2","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"To: TSG CT, TSG SA, CT WG4, RAN WG3. CC: TSG RAN. Attachments: 23.502 CR2318 (S2-2004472) and 23.401 CR3602 (S2-2004473)","secretary_remarks":"Revision of S2-2004010_r04. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11350,"status":"approved","reservation_date":"2020-06-08 15:11:40","uploaded":"2020-06-08 15:19:10","revisionof":"S2-2004010","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"LTE_feMob-Core"},{"winame":"NR_Mob_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2003579","lsto":"TSG CT, TSG SA, CT WG4, RAN WG3","Cc":"TSG RAN","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004474.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004475","title":"Reply LS on subscription to V2X services","source":"SA WG2","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC: CT WG4","secretary_remarks":"Revision of S2-2003908_r08. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11380,"status":"approved","reservation_date":"2020-06-08 15:11:40","uploaded":"2020-06-08 15:19:10","revisionof":"S2-2003908","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2003541","lsto":"CT WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004475.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004476","title":"Reply LS on NSSAAF in slice specific authentication","source":"SA WG2","contact":"Tricci So","contact-id":44974,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3, CT WG1, CT WG3, CT WG4. Attachments: S2-2004477, S2-2003744","secretary_remarks":"Revision of S2-2003745. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11420,"status":"approved","reservation_date":"2020-06-08 15:11:40","uploaded":"2020-06-08 15:19:10","revisionof":"S2-2003745","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"eNS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2003550","lsto":"SA WG3","Cc":"SA WG2, CT WG1, CT WG3, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004476.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004477","title":"Replacing AUSF by NSSAAF to support NSSAA","source":"ZTE, Ericsson, Qualcomm, Nokia, Nokia shanghai Bell","contact":"Tricci So","contact-id":44974,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introducing the new NF, NSSAAF, into Rel-17 network architecture to replace AUSF to support NSSAA by adding\/updating the corresponding clauses to support this new NF.","secretary_remarks":"Revision of S2-2003743_r01. This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11440,"status":"agreed","reservation_date":"2020-06-08 15:11:40","uploaded":"2020-06-08 15:19:10","revisionof":"S2-2003743","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"eNS"}],"crnumber":2372.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200432","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004477.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004478","title":"Reply LS on the applicability of LADN in an SNPN","source":"SA WG2","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: SA WG1","secretary_remarks":"Revision of S2-2003664_r02, merging S2-2003723. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11500,"status":"approved","reservation_date":"2020-06-08 15:11:42","uploaded":"2020-06-08 15:19:09","revisionof":"S2-2003664","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2003526","lsto":"CT WG1","Cc":"SA WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004478.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004479","title":"Reply LS on uniqueness of PEI in certain FN-RG configurations","source":"SA WG2","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3-LI. CC: BBF, CableLabs. Attachments: 23.316 CR2045 (S2-2003683)","secretary_remarks":"Revision of S2-2003684. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11630,"status":"approved","reservation_date":"2020-06-08 15:11:42","uploaded":"2020-06-08 15:19:09","revisionof":"S2-2003684","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2003521","lsto":"SA WG3-LI","Cc":"BBF, Cabelabs","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004479.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004480","title":"Missing parameters in Namf_Communication_NonUeN2MessageTransfer","source":"NTT DOCOMO, one2many","contact":"Atsushi Minokuchi","contact-id":26474,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add Send Write-Replace-Warning-Indication and Send Stop-Warning-Indication as optional input elements to Namf_Communication_NonUeN2MessageTransfer.","secretary_remarks":"Revision of S2-2004066_r01. This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11680,"status":"agreed","reservation_date":"2020-06-08 15:11:42","uploaded":"2020-06-08 15:19:09","revisionof":"S2-2004066","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":2321.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200551","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004480.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004481","title":"Reply PAP\/CHAP and other point-to-point protocols usage in 5GS","source":"SA WG2","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1, SA WG3, CT WG3. CC: CT WG4","secretary_remarks":"Revision of S2-2004196_r06. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11710,"status":"approved","reservation_date":"2020-06-08 15:11:43","uploaded":"2020-06-08 15:19:09","revisionof":"S2-2004196","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5GProtoc16"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2003540","lsto":"CT WG1, SA WG3, CT WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004481.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004482","title":"Reply LS on Clarification on eNA","source":"SA WG2","contact":"Yannick Lair","contact-id":76350,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. Attachments: S2-2003339 (SA WG2#138E), S2-2004328 (SA WG2#139E)","secretary_remarks":"Revision of S2-2004327. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11760,"status":"approved","reservation_date":"2020-06-08 15:11:43","uploaded":"2020-06-08 15:19:09","revisionof":"S2-2004327","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2003544","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004482.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004483","title":"Reply LS on Access Type Report for a MA PDU session","source":"SA WG2","contact":"Belen Pancorbo","contact-id":78666,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3","secretary_remarks":"Revision of S2-2003691_r01, merging S2-2003665. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11840,"status":"approved","reservation_date":"2020-06-08 15:11:44","uploaded":"2020-06-08 15:19:09","revisionof":"S2-2003691","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"ATSSS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2003545","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004483.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004484","title":"UE specific DRX for NB-IoT RAN support clarification based on LS R2-2004057","source":"Qualcomm Incorporated, Ericsson","contact":"Miguel Griot","contact-id":84607,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the possiblity that each cell may or may not indicate support of UE specific DRX for NB-IoT and the UE conditions for using the broadcast DRX cycle or the Accepted DRX parameters.","secretary_remarks":"Revision of S2-2004210_r04. This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":11930,"status":"agreed","reservation_date":"2020-06-08 15:11:44","uploaded":"2020-06-08 15:19:09","revisionof":"S2-2004210","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2378.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200422","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004484.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004485","title":"UE specific DRX for NB-IoT RAN support clarification","source":"Qualcomm Incorporated, Ericsson","contact":"Miguel Griot","contact-id":84607,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the possiblity that each cell may or may not indicate support of UE specific DRX for NB-IoT and the UE rules for using the broadcast DRX cycle and the Accepted DRX parameters.","secretary_remarks":"Revision of S2-2004216_r06. This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":0,"status":"agreed","reservation_date":"2020-06-08 15:11:45","uploaded":"2020-06-08 15:19:09","revisionof":"S2-2004216","revisedto":"","release":"Rel-16","crspec":"23.401","crspecversion":"16.6.0","workitem":[{"winame":"TEI16"},{"winame":"CIoT"}],"crnumber":3604.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200552","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004485.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004486","title":"PCO support for DNS over (D)TLS (avoiding attacks against DNS traffic)","source":"Nokia, Nokia Shanghai Bell, Qualcomm Incorporated","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When DNS over (D)TLS as specified in RFC 7858 and RFC 8310 is supported by the network, PCO may also include the corresponding DNS server security information. WI is new SA WG3 WID UPIP_SEC","secretary_remarks":"Revision of S2-2003654_r03. This CR was agreed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs - Phase 1","tdoc_agenda_sort_order":0,"status":"agreed","reservation_date":"2020-06-08 15:11:47","uploaded":"2020-06-08 15:19:09","revisionof":"S2-2003654","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":2368.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200551","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_139e_Electronic\/Docs\/S2-2004486.zip","group":"S2","meeting":"S2-ah-38172","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]