[{"name":"S2-2000012","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":"Postponed S2-1910885 from SA2#136. Postponed","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10810,"status":"postponed","reservation_date":"2019-12-18 15:23:43","uploaded":"2020-01-06 08:48:38","revisionof":"S2-1910885","revisedto":"S2-2001735, S2-2001776","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5, SA WG2","Cc":"TSG SA, SA WG3-LI, RAN WG3","lsoriginalls":"LI(19)P52055","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000012.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000024","title":"LS from CT WG1: LS on configured NSSAI handling","source":"CT WG1","contact":"Sung Hwan Won","contact-id":70307,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 would like to thank SA WG2 for the reply LS in S2-1906758 including a remark and a request requiring responses from CT WG1. In light of this, CT WG1 provides responses as follows: Remark from SA WG2 - if any of S-NSSAIs included in the requested NSSAI is allowed to the UE, the AMF includes such S-NSSAIs as-is in the allowed NSSAI; SA WG2 needs more information on what exactly CT WG1 means by this to be able to provide an answer. Response from CT WG1 In Rel-15, the AMF needs to include, in the allowed NSSAI, an S-NSSAI for the current PLMN and a mapped S-NSSAI (if available), which are included in the requested NSSAI and are allowed to the UE, and in this case, the S-NSSAI for the current PLMN and the mapped S-NSSAI (if available) included in the allowed NSSAI are the same as the ones included in the requested NSSAI because if the UE receives allowed NSSAI not including exactly the same S-NSSAI and the same mapped S-NSSAI (if available) associated with an existing PDU session, the PDU session is locally released. For Rel-16 UE behaviour, please refer to C1-1988910. Request from SA WG2 SA WG2 has agreed to introduce a NOTE in TS 23.501 stating that 'the support of the continuation of PDU sessions upon mobility to a target 5GS PLMN or from EPS to the 5GS when neither the Configured NSSAI nor the Allowed NSSAI are available for the target PLMN, is not guaranteed'. Taking the above into account, CT WG1 is asked to consider resolving this issue in Rel-16 in their specifications. Response from CT WG1 CT WG1 discussed a resolution for this issue in Rel-16 and agreed CRs attached. Action: CT WG1 kindly asks SA WG2 to take the responses into account.","secretary_remarks":"Postponed S2-1911957 from SA2#136. Response drafted in S2-2001069. Final response in S2-2001110","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10510,"status":"replied to","reservation_date":"2019-12-18 15:23:44","uploaded":"2020-01-06 08:48:38","revisionof":"S2-1911957","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C1-199063","lsreply":"S2-2001110","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000024.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000234","title":"Access type and RAT type per Non-3GPP accesses","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Definition of RAT Type used in case of Non-3GPP accesses and of how the RAT Type value is determined","secretary_remarks":"Revision of unhandled S2-1911334 from S2#136. Revised in parallel session to S2-2001065.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10680,"status":"revised","reservation_date":"2020-01-03 15:45:46","uploaded":"2020-01-07 13:10:27","revisionof":"S2-1911334","revisedto":"S2-2001065","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5WWC"}],"crnumber":1950.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000234.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000255","title":"Access type and RAT type per Non-3GPP accesses","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The definition of RAT type is added. The Access and Global N3IWF Node ID, Global TNGF Node ID and Global W-AGF Node ID for Non-3GPP Accesse as been added and clarified that the RAT type also includes the Non-3GPP Accesses","secretary_remarks":"Revised in parallel session to S2-2001064.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10620,"status":"revised","reservation_date":"2020-01-03 15:59:09","uploaded":"2020-01-06 08:25:29","revisionof":"","revisedto":"S2-2001064","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5WWC"}],"crnumber":2033.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000255.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000256","title":"Access type and RAT type per Non-3GPP accesses","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The Access and Global N3IWF Node ID, Global TNGF Node ID and Global W-AGF Node ID for Non-3GPP Accesse as been added and clarified that the RAT type also include the Non-3GPP Accesses","secretary_remarks":"Not Handled","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10670,"status":"not treated","reservation_date":"2020-01-03 15:59:09","uploaded":"2020-01-06 08:25:29","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5WWC"}],"crnumber":1971.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000256.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000287","title":"Applicability of Data Off to Non-3GPP PDU Session and Multi Access PDU Session .","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"This paper discusses the implications of Data Off not applied to the non-3GPP access in MA PDU Session and not applied to non-3GPP PDU Session, and propose to send an LS to SA WG1 asking to clarify the requirement if needed.","secretary_remarks":"Not Handled","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10680,"status":"not treated","reservation_date":"2020-01-03 22:06:56","uploaded":"2020-01-07 04:54:42","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"ATSSS"},{"winame":"PS_Data_Off"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000287.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000288","title":"[DRAFT] LS on Data Off applicability to non-3GPP PDU Session and MA PDU Session","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"This LS asks SA WG1 to clarify the Data Off applicability to non-3GPP PDU Session and MA PDU Session.","secretary_remarks":"Revised in parallel session to S2-2001063.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10700,"status":"revised","reservation_date":"2020-01-03 22:06:56","uploaded":"2020-01-07 04:54:42","revisionof":"","revisedto":"S2-2001063","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"ATSSS"},{"winame":"PS_Data_Off"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000288.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000325","title":"Applicability of PS data off to ATSSS and MA PDU sessions","source":"OPPO","contact":"ChenHo CHIN","contact-id":80545,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is specified that 3GPP PS data off does not apply to non-3GPP access aspects of MA PDU sessions establsihed under ATSSS","secretary_remarks":"Revision of postponed S2-1911084 from S2#136. Postponed in parallel session. Revised at S2#137E in S2-2002190 (agreed)","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10740,"status":"revised","reservation_date":"2020-01-05 13:26:51","uploaded":"2020-01-07 13:01:34","revisionof":"S2-1911084","revisedto":"S2-2002190","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1782.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000325.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000363","title":"Requested NSSAI provided at the AS layer","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The UE provides the Requested NSSAI in AS layer subject to the Access Stratum Connection Establishment NSSAI Inclusion Mode setting. 5G-S-TMSI is included in the AS layer.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10580,"status":"noted","reservation_date":"2020-01-06 09:06:37","uploaded":"2020-01-07 13:06:22","revisionof":"","revisedto":"","release":"Rel-15","crspec":"23.501","crspecversion":"15.8.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2037.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000363.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000364","title":"Requested NSSAI provided at the AS layer","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: The UE provides the Requested NSSAI in AS layer subject to the Access Stratum Connection Establishment NSSAI Inclusion Mode setting. 5G-S-TMSI is included in the AS layer.","secretary_remarks":"Revised in parallel session to S2-2001070.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10590,"status":"revised","reservation_date":"2020-01-06 09:06:42","uploaded":"2020-01-07 13:06:22","revisionof":"","revisedto":"S2-2001070","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2038.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000364.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000399","title":"Addition of PSCell ID in E-RAB modification procedure","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: PSCell reporting in E-RAB MODIFICATION procedure is added.","secretary_remarks":"Not Handled. Revised at S2#137E in S2-2002254","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10850,"status":"revised","reservation_date":"2020-01-06 11:29:01","uploaded":"2020-01-07 14:40:05","revisionof":"","revisedto":"S2-2002254","release":"Rel-16","crspec":"23.401","crspecversion":"16.5.0","workitem":[{"winame":"EDCE5"},{"winame":"TEI16"},{"winame":"LI15"}],"crnumber":3578.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000399.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000566","title":"[DRAFT] LS on Applicability of PS Data Off to non-3GPp access technologies","source":"Qualcomm Austria RFFE GmbH","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG1. CC:","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10750,"status":"noted","reservation_date":"2020-01-07 01:11:27","uploaded":"2020-01-07 09:32:43","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000566.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000700","title":"Clarification on the use of reference points N14 and N26","source":"Telecom Italia","contact":"Mario Madella","contact-id":23765,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarified that reference point N14 between two AMFs can be used for AMF re-allocation and AMF to AMF information transfer. This reference point can be used either intra-PLMN or inter PLMN (e.g. in the case of inter PLMN mobility). Clarified that the N26 interface may be either intra-PLMN or inter PLMN (e.g. to enable inter PLMN mobility).","secretary_remarks":"Revised in parallel session to S2-2001067.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10820,"status":"revised","reservation_date":"2020-01-07 08:24:41","uploaded":"2020-01-07 10:00:29","revisionof":"","revisedto":"S2-2001067","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":2087.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000700.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000793","title":"Policy update on DNN replacement.","source":"Samsung","contact":"Hoyeon Lee","contact-id":62489,"tdoctype":"discussion","for":"Discussion","abstract":"This contribution discusses policy update on DNN replacement.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10760,"status":"noted","reservation_date":"2020-01-07 10:49:46","uploaded":"2020-01-07 11:16:26","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000793.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000868","title":"Access type and RAT type per Non-3GPP accesses","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Depending on the Non 3GPP 5G AN technology and on local configuration, the 5G AN may at the establishment of a N2 connection for a UE provide the 5GC with RAT Type information giving information on the features of the Non 3GPP Access (e.g. the Trusted access relies on WLAN, the Wireline access corresponds to Cable, etc\u2026).","secretary_remarks":"Revised in parallel session to S2-2001066.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10700,"status":"revised","reservation_date":"2020-01-07 12:52:50","uploaded":"2020-01-07 13:10:27","revisionof":"","revisedto":"S2-2001066","release":"Rel-16","crspec":"23.316","crspecversion":"16.2.0","workitem":[{"winame":"5WWC"}],"crnumber":1833.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000868.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000894","title":"Correction on Control and User Plane Protocol Stacks","source":"Samsung","contact":"Kisuk Kweon","contact-id":80126,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Editorial correction on Control and User Plane Protocol Stacks","secretary_remarks":"Not Handled","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10840,"status":"not treated","reservation_date":"2020-01-07 14:24:42","uploaded":"2020-01-07 14:30:36","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2114.0,"crrevision":"","crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000894.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001063","title":"[DRAFT] LS on Data Off applicability to non-3GPP PDU Session and MA PDU Session","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"This LS asks SA WG1 to clarify the Data Off applicability to non-3GPP PDU Session and MA PDU Session.","secretary_remarks":"Revision of S2-2000288. Revised in parallel session to S2-2001107.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10710,"status":"revised","reservation_date":"2020-01-14 20:13:26","uploaded":"2020-01-18 01:47:52","revisionof":"S2-2000288","revisedto":"S2-2001107","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"ATSSS"},{"winame":"PS_Data_Off"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001063.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001064","title":"Access type and RAT type per Non-3GPP accesses","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The definition of RAT type is added. The Access and Global N3IWF Node ID, Global TNGF Node ID and Global W-AGF Node ID for Non-3GPP Accesse as been added and clarified that the RAT type also includes the Non-3GPP Accesses In clause 5.31.11 it is clarified that is applicale on when RAT type corresponds to 3GPP accesses to avoid wrong secification","secretary_remarks":"Revision of S2-2000255. Revised in parallel session to S2-2001105.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10630,"status":"revised","reservation_date":"2020-01-14 20:13:26","uploaded":"2020-01-18 01:47:52","revisionof":"S2-2000255","revisedto":"S2-2001105","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5WWC"}],"crnumber":2033.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001064.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001065","title":"Access type and RAT type per Non-3GPP accesses","source":"Nokia, Nokia Shanghai Bell, Huawei, HiSilicon","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Refer to 23.501 Definition of RAT Type used in case of Non-3GPP accesses and of how the RAT Type value is determined","secretary_remarks":"Revision of S2-2000234. Agreed in parallel session. Block approved","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10690,"status":"agreed","reservation_date":"2020-01-14 20:13:27","uploaded":"2020-01-18 01:47:52","revisionof":"S2-2000234","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5WWC"}],"crnumber":1950.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-200068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001065.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001066","title":"Access type and RAT type per Non-3GPP accesses","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Depending on the Non 3GPP 5G AN technology and on local configuration, the 5G AN may at the establishment of a N2 connection for a UE provide the 5GC with RAT Type information giving information on the features of the Non 3GPP Access (e.g. the Trusted access relies on WLAN, the Wireline access corresponds to Cable, etc\u2026).","secretary_remarks":"Revision of S2-2000868. Revised in parallel session to S2-2001106.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10710,"status":"revised","reservation_date":"2020-01-14 20:13:28","uploaded":"2020-01-18 01:47:52","revisionof":"S2-2000868","revisedto":"S2-2001106","release":"Rel-16","crspec":"23.316","crspecversion":"16.2.0","workitem":[{"winame":"5WWC"}],"crnumber":1833.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001066.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001067","title":"Clarification on the use of reference points N14 and N26","source":"Telecom Italia, Deutsche Telekom","contact":"Mario Madella","contact-id":23765,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarified that N14 interface is used for AMF re-allocation and AMF to AMF information transfer. This interface may be either intra-PLMN or inter-PLMN (e.g. in the case of inter-PLMN mobility). Clarified that the N26 interface may be either intra-PLMN or inter-PLMN (e.g. to enable inter-PLMN mobility).","secretary_remarks":"Revision of S2-2000700. Agreed in parallel session. Block approved","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10830,"status":"agreed","reservation_date":"2020-01-14 20:13:29","uploaded":"2020-01-18 01:47:52","revisionof":"S2-2000700","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":2087.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200078","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001067.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001069","title":"[DRAFT] Reply LS to LS on configured NSSAI handling","source":"Ericsson","contact":"Peter Hedman","contact-id":27550,"tdoctype":"LS out","for":"Approval","abstract":"To: . CC: . Attachments: .","secretary_remarks":"Created at meeting. Response to S2-2000024. Revised in parallel session to S2-2001110.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10520,"status":"revised","reservation_date":"2020-01-14 20:13:31","uploaded":"2020-01-18 01:47:52","revisionof":"","revisedto":"S2-2001110","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5GProtoc16"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001069.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001070","title":"Requested NSSAI provided at the AS layer","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The UE provides the Requested NSSAI in AS layer subject to the clause 5.15.9 where the Access Stratum Connection Establishment NSSAI Inclusion Mode is described. 5G-S-TMSI is included in the AS layer.","secretary_remarks":"Revision of S2-2000364. Revised in parallel session to S2-2001111.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10600,"status":"revised","reservation_date":"2020-01-14 20:13:31","uploaded":"2020-01-18 01:47:52","revisionof":"S2-2000364","revisedto":"S2-2001111","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2038.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001070.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001105","title":"Access type and RAT type per Non-3GPP accesses","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The definition of RAT type is added. The Access and Global N3IWF Node ID, Global TNGF Node ID and Global W-AGF Node ID for Non-3GPP Accesse as been added and clarified that the RAT type also includes the Non-3GPP Accesses In clause 5.31.11 it is clarified that is applicale on when RAT type corresponds to 3GPP accesses to avoid wrong secification","secretary_remarks":"Revision of S2-2001064. Confirm CR Revision - CR states 1! Revised in parallel session to S2-2001149.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10640,"status":"revised","reservation_date":"2020-01-16 02:40:33","uploaded":"2020-01-18 01:47:54","revisionof":"S2-2001064","revisedto":"S2-2001149","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5WWC"}],"crnumber":2033.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001105.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001106","title":"Access type and RAT type per Non-3GPP accesses","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Depending on the Non 3GPP 5G AN technology and on local configuration, the 5G AN may at the establishment of a N2 connection for a UE provide the 5GC with RAT Type information giving information on the features of the Non 3GPP Access (e.g. the Trusted access relies on WLAN, the Wireline access corresponds to Cable, etc\u2026).","secretary_remarks":"Revision of S2-2001066. Agreed in parallel session. Block approved. Revised at S2#137E in S2-2002142 (noted)","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10720,"status":"agreed","reservation_date":"2020-01-16 02:40:35","uploaded":"2020-01-18 01:47:54","revisionof":"S2-2001066","revisedto":"S2-2002142","release":"Rel-16","crspec":"23.316","crspecversion":"16.2.0","workitem":[{"winame":"5WWC"}],"crnumber":1833.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-200068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001106.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001107","title":"[DRAFT] LS on Data Off applicability to non-3GPP PDU Session and MA PDU Session","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"This LS asks SA WG1 to clarify the Data Off applicability to non-3GPP PDU Session and MA PDU Session.","secretary_remarks":"Revision of S2-2001063. Revised in parallel session to S2-2001108.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10720,"status":"revised","reservation_date":"2020-01-16 02:40:37","uploaded":"2020-01-18 01:47:54","revisionof":"S2-2001063","revisedto":"S2-2001108","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"ATSSS"},{"winame":"PS_Data_Off"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001107.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001108","title":"[DRAFT] LS on Data Off applicability to non-3GPP PDU Session and MA PDU Session","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"This LS asks SA WG1 to clarify the Data Off applicability to non-3GPP PDU Session and MA PDU Session.","secretary_remarks":"Revision of S2-2001107. Revised in parallel session to S2-2001137.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10730,"status":"revised","reservation_date":"2020-01-16 02:42:02","uploaded":"2020-01-18 01:47:54","revisionof":"S2-2001107","revisedto":"S2-2001137","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"ATSSS"},{"winame":"PS_Data_Off"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001108.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001110","title":"Reply LS on configured NSSAI handling","source":"SA WG2","contact":"Peter Hedman","contact-id":27550,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Revision of S2-2001069. Agreed in parallel session. Block approved","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10530,"status":"approved","reservation_date":"2020-01-16 02:42:04","uploaded":"2020-01-18 01:47:54","revisionof":"S2-2001069","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5GProtoc16"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2000024","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001110.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001111","title":"Requested NSSAI provided at the AS layer","source":"Huawei, HiSilicon, Ericsson","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: The UE provides the Requested NSSAI in AS layer subject to the clause 5.15.9 where the Access Stratum Connection Establishment NSSAI Inclusion Mode is described. remove the text regarding 5G-S-TMSI in that paragraph.","secretary_remarks":"Revision of S2-2001070. Agreed in parallel session. Block approved","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10610,"status":"agreed","reservation_date":"2020-01-16 02:42:04","uploaded":"2020-01-18 01:47:54","revisionof":"S2-2001070","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2038.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-200078","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001111.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001137","title":"LS on Data Off applicability to non-3GPP PDU Session and MA PDU Session","source":"SA WG2","contact":"George Foti","contact-id":41317,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG1","secretary_remarks":"Revision of S2-2001108. Agreed in parallel session. Block approved","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10740,"status":"approved","reservation_date":"2020-01-18 01:19:17","uploaded":"2020-01-18 01:47:55","revisionof":"S2-2001108","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"ATSSS"},{"winame":"PS_Data_Off"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001137.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001149","title":"Access type and RAT type per Non-3GPP accesses","source":"Huawei, HiSilicon, Nokia, Nokia Shanghai Bell","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The definition of RAT type is added. The RAT determinatioin by AMF is defined In clause 5.31.11 it is clarified that this clause is applicale on when RAT type corresponds to 3GPP accesses to avoid wrong secification.","secretary_remarks":"Revision of S2-2001105. This was left for e-mail approval. e-mail revision 6 approved. Revised to S2-2001685.","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10650,"status":"revised","reservation_date":"2020-01-18 01:19:30","uploaded":"2020-01-18 01:47:55","revisionof":"S2-2001105","revisedto":"S2-2001685","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5WWC"}],"crnumber":2033.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001149.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001685","title":"Access type and RAT type per Non-3GPP accesses","source":"Huawei, HiSilicon, Nokia, Nokia Shanghai Bell","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The definition of RAT type is added. The RAT determinatioin by AMF is defined. The full list of RAT Type applicable to 5GC is expected to be documented in Stage 3 TS 29.571 (clause 5.4.3.2) including different values for Non-3GPP accesses. In clause 5.31.11 it is clarified that this clause is applicable only when RAT type corresponds to 3GPP accesses.","secretary_remarks":"e-mail revision 6 of S2-2001149. This CR was agreed","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"General aspects, concepts and reference models","tdoc_agenda_sort_order":10660,"status":"agreed","reservation_date":"2020-01-27 09:23:45","uploaded":"2020-01-27 09:28:18","revisionof":"S2-2001149","revisedto":"S2-2002141","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5WWC"}],"crnumber":2033.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-200068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001685.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]