[{"name":"S2-2006791","title":"LS from RAN WG2: LS on AS RAI and optimization of release","source":"RAN WG2","contact":"Tuomas Tirronen","contact-id":73195,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 discussed whether UE power consumption can be optimized further when AS RAI is indicated if eNB can release the UE immediately, i.e., without waiting for an acknowledgement from the MME\/AMF if the UE indicates AS RAI implying that no further data are expected from the CN. RAN WG2 thinks the optimization can be beneficial to increase UE power savings in some cases, however some companies doubt power consumption gain, if any, would be significant. Some companies have expressed concerns with eNB immediately releasing UE could in some cases lead to state mismatch between UE and CN with increased power consumption and signalling load. Action: RAN WG2 kindly asks SA WG2 to take the above observations into account.","secretary_remarks":"Revision of postponed S2-2004804 from S2#140E. Postponed","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":11930,"status":"postponed","reservation_date":"2020-09-22 08:22:50","uploaded":"2020-09-22 09:22:30","revisionof":"S2-2004804","revisedto":"S2-2008333","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"R2-2005839","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006791.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006799","title":"LS from RAN WG2: Reply LS on early UE capability retrieval for eMTC","source":"RAN WG2","contact":"Veera Prasada Kadiri","contact-id":72325,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 thanks SA WG2 for their reply LS confirming that SA WG2 has not identified any technical issues to support early UE capability retrieval for eMTC UEs for EPS from system architecture perspective. RAN WG2 discussed the concerns raised by SA WG2 for 5GS and would like to provide the responses as follows: SA WG2 LS indicated: - Concerns to enable use of truncated 5G-S-TMSI for all UEs accessing ng-eNBs connected to 5GC as this would reduce the available AMF Set ID number space, AMF Pointer number space and TMSI number space (due to truncation) for all UEs. RAN WG2 response: RAN WG2 has a potential solution to identify in Msg3 to include InitialUE-Identity-5GC which enables ng-eNB to differentiate between BL UEs and non-BL UEs in CE mode. Such solution would allow AMF to allocate 40-bit truncated 5G-S-TMSI only for BL UEs. SA WG2 LS indicated: - Concerns about truncated 5G-S-TMSIs being used, with no additional checks, to retrieve the UE capabilities for all UEs and the high levels of coordination required between operators in RAN sharing cases for eMTC UEs using CP optimisations. - Concerns about introducing to EPS capabilities that are not supported by 5GS, or no clear path exists for its addition to 5GS. RAN WG2 thinks the above two concerns are out of RAN WG2 scope and up to SA WG2 to address. Action: RAN WG2 respectfully asks SA WG2 to take above response into consideration.","secretary_remarks":"Revision of postponed S2-2006778 from S2#140E. Responses drafted in S2-2007209 and S2-2007665. Postponed","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":11820,"status":"postponed","reservation_date":"2020-09-22 08:22:50","uploaded":"2020-09-22 09:22:30","revisionof":"S2-2006778","revisedto":"S2-2008336","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG3, CT WG1","lsoriginalls":"R2-2008238","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006799.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006807","title":"LS from CT WG4: LS on Event Configuration Synchronization between 4G&5G","source":"CT WG4","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"TS 23.501 clause 5.17.5.2.1 has described Support of Interworking for Monitoring Event with N26 interface, which requiring monitoring event configuration to be transferred between AMF and MME during inter system mobility procedures. When trying to implement at stage 3, CT WG4 has detected some issues on current stage 2 requirements: 1. Event Monitoring in 5GS based on SBI subscribe\/notify model is different to EPS, a 5GS AMF Event subscription by UDM\/NEF cannot be created with information from N26; 2. Information elements requirement for Monitoring event configuration are not equivalent between EPS and 5GS, i.e. monitoring event configurations cannot be transparently exchanged via N26, e.g. SCEF address is not required in 5GS; UDM\/NEF HTTP notification callback URI(s) are not available in EPS. 3. Events applicability may be different in EPS and in 5GS, i.e. some event may be only applicable in 5GS which will not be provisioned when UE is in EPS. A synchronization between AMF and UDM\/NEF shall be considered when UE moves to 5GS. Before stage 3 implementation can be started, CT WG4 expects more clarifications on the above issues, or even possibly adaptation of current stage 2 requirements after considering CT WG4 findings. Action: CT WG4 kindly asks SA WG2 group to take the above findings into account, and further provide clarifications or possible adaptations on current stage 2 requirements for Monitoring Event interworking with N26.","secretary_remarks":"Response drafted in S2-2007256. Final response in S2-2008002","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":11880,"status":"replied to","reservation_date":"2020-09-22 08:22:50","uploaded":"2020-09-22 15:39:21","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG3","lsoriginalls":"C4-204338","lsreply":"S2-2008002","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006807.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006819","title":"LS from SA WG1: Reply LS on service area restriction for CIoT 5GS optimization","source":"SA WG1","contact":"Francesco Pica","contact-id":57089,"tdoctype":"LS in","for":"Action","abstract":"SA WG1 thanks SA WG2 for their LS (S2-2004440) on service area restriction for CIoT 5GS optimization, which includes a question addressed to SA WG1, as highlighted below: ------------ CT WG1 has asked the following question (to SA WG2): Is the UE using CP CIoT or UP CIoT optimization allowed to send or receive data in a non-allowed area, including exception data? SA WG2 Answer: the service area restriction is applicable to CIoT 5GS optimizations. The attached CR (TS 23.501 CR 2243) clarifies these points. SA WG2 kindly ask SA WG1: Does SA WG1 see any need for the UE to be able to send MO exception data in non-allowed area? ------------ SA WG1 would like to clarify that currently there are no SA WG1 requirements related to CIoT UEs (supporting CIoT 5GS optimization) sending or receiving data, including exception data, in a non-allowed area. Action: Please take the above information into account.","secretary_remarks":"Response drafted in S2-2007144. Final response in S2-2008011","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":11780,"status":"replied to","reservation_date":"2020-09-22 08:22:51","uploaded":"2020-09-22 15:39:21","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1","lsoriginalls":"S1-203274","lsreply":"S2-2008011","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006819.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2007144","title":"[DRAFT] LS on exception data reporting in non-allowed area","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"LS to CT WG1 to inform the SA WG2 specificaiton on exception data reporting handling in non-allowed area","secretary_remarks":"R01 agreed. Revised to S2-2008011","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":11790,"status":"revised","reservation_date":"2020-09-30 22:09:16","uploaded":"2020-10-02 19:25:58","revisionof":"","revisedto":"S2-2008011","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_141e_Electronic\/Docs\/S2-2007144.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2007145","title":"Exception data reporting and connected state","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update clause 5.3.4.1.1 to indicate exception data reporting is not allowed in non-allowed area. Remove the text contradicting NOTE 5","secretary_remarks":"Approved","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":11810,"status":"agreed","reservation_date":"2020-09-30 22:09:16","uploaded":"2020-10-02 19:25:58","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.6.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2476.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200947","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2007145.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2007205","title":"Correction to the downlink data notification with V-SMF and I-SMF","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: During the PDU session establishment or modifcation, if the PCF provisions the related PCRT to the SMF, SMF provisions the corresponding indication to the I-SMF. When the I-SMF receives the subscription request and the UPF is configured","secretary_remarks":"Postponed","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":11940,"status":"postponed","reservation_date":"2020-10-01 12:20:55","uploaded":"2020-10-02 06:35:52","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.6.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2418.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2007205.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2007206","title":"Correction on Enhanced Coverage Restriction","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that the AMF decides the Enhanced Coverage Restriction information based on the UE capability indication. Also add the AMF function description on this feature.","secretary_remarks":"Approved","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":11950,"status":"agreed","reservation_date":"2020-10-01 12:20:56","uploaded":"2020-10-02 06:35:52","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.6.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2481.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200947","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2007206.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2007207","title":"Correction on Enhanced Coverage Restriction","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that the AMF decides the Enhanced Coverage Restriction information based on the UE capability indication. Also add the Enhanced Coverage Restriction information for NB-IoT in UE context of AMF side.","secretary_remarks":"R01 agreed. Revised to S2-2008012","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":11960,"status":"revised","reservation_date":"2020-10-01 12:20:57","uploaded":"2020-10-02 06:35:52","revisionof":"","revisedto":"S2-2008012","release":"Rel-16","crspec":"23.502","crspecversion":"16.6.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2419.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2007207.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2007208","title":"Discussion on use of truncated 5G-S-TMSI to retrieve UE Capabilities.","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"discussion","for":"Agreement","abstract":"A discussion on the use of UE capability retrieval based solely on truncated 5G-S-TMSI, a comparison to NB-IoT use of truncated 5G-S-TMSI and the problems it introduces.","secretary_remarks":"Noted","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":11830,"status":"noted","reservation_date":"2020-10-01 12:20:58","uploaded":"2020-10-02 06:35:52","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"LTE_eMTC5-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2007208.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2007209","title":"[DRAFT] Reply LS on early UE capability retrieval for eMTC","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to RAN WG2's Reply LS to SA WG2's Reply LS on RAN WG2's LS about early UE capability retrieval for eMTC","secretary_remarks":"Response to S2-2006799. This was postponed.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":11860,"status":"postponed","reservation_date":"2020-10-01 12:20:58","uploaded":"2020-10-02 06:35:52","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"LTE_eMTC5-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"RAN WG3. CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2007209.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2007256","title":"[DRAFT] Reply LS on 'Event Configuration Synchronization between","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Provide feedback on how to event synchronizatiat UE mobility between EPC and 5GC","secretary_remarks":"Response to S2-2006807. Agreed. Revised to clean up in S2-2008002","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":11890,"status":"revised","reservation_date":"2020-10-01 16:41:22","uploaded":"2020-10-02 19:25:58","revisionof":"","revisedto":"S2-2008002","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_141e_Electronic\/Docs\/S2-2007256.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2007257","title":"Event Configuration Synchronization between 4G&5G","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: At EPS to 5GS mobility, if the AMF does not have event subscription information when registering in UDM, the AMF indicates the situation to the UDM so that UDM can decide if the event subscriptions should be provisioned; if the AMF has","secretary_remarks":"Approved","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":11910,"status":"agreed","reservation_date":"2020-10-01 16:41:22","uploaded":"2020-10-02 19:25:58","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.6.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2482.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200947","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2007257.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2007258","title":"Event Configuration Synchronization between 4G&5G","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: At EPS to 5GS mobility, if the AMF does not have event subscription information when registering in UDM, the AMF indicates the situation to the UDM so that UDM can decide if the event subscriptions should be provisioned; if the AMF has","secretary_remarks":"Approved","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":11920,"status":"agreed","reservation_date":"2020-10-01 16:41:25","uploaded":"2020-10-02 19:25:58","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.6.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2421.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200947","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2007258.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2007259","title":"Correction to Network Configuration Parameter handling","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clauses 4.15.6.2 and 4.15.6.3a, remove description related to network configuration parameters as AMF-associated parameters. In clause 5.2.3.3.1, remove AMF-associated network configuration parameters.","secretary_remarks":"This was postponed.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":11980,"status":"postponed","reservation_date":"2020-10-01 16:41:26","uploaded":"2020-10-02 19:25:58","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.6.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2422.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2007259.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2007484","title":"Correction on header compression for CP Optimisation","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarified the UE and SMF behaviours on header compression for CP Optimisation, including that the UE may include additional header compression context setup information in the Header Compression Configuration, and the SMF may establish","secretary_remarks":"R03 agreed. Revised to S2-2008013","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":11990,"status":"revised","reservation_date":"2020-10-02 08:57:54","uploaded":"2020-10-02 12:00:51","revisionof":"","revisedto":"S2-2008013","release":"Rel-16","crspec":"23.502","crspecversion":"16.6.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2433.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2007484.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2007630","title":"Discussion on early UE radio capability retrieval.","source":"Qualcomm Inc, ZTE, Sanechips, Sierra Wireless, Thales, Turkcell, Aselsan, Sequans","contact":"Miguel Griot","contact-id":84607,"tdoctype":"discussion","for":"Agreement","abstract":"This contribution concludes that given RAN WG2 reply there should be no SA WG2 concerns to specify early UE capability retrieval in eMTC.","secretary_remarks":"Noted","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":11840,"status":"noted","reservation_date":"2020-10-02 14:36:57","uploaded":"2020-10-02 18:26:15","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"TEI16"},{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2007630.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2007631","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":"Postponed","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":11850,"status":"postponed","reservation_date":"2020-10-02 14:40:03","uploaded":"2020-10-02 18:26:15","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.6.0","workitem":[{"winame":"TEI16"},{"winame":"5G_CIoT"}],"crnumber":2507.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2007631.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2007665","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":"Replies to RAN WG2 that Sa2 agrees to specify the system aspects for early UE capability retrieval.","secretary_remarks":"Response to S2-2006799. This was postponed.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":11870,"status":"postponed","reservation_date":"2020-10-02 15:55:57","uploaded":"2020-10-02 18:26:15","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"TEI16"},{"winame":"FS_5G_CIoT_CH"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"RAN WG3, CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2007665.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2007682","title":"Clarifications for GUTI re-allocation","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: clause 4.2.2.2.2: Upon receiving a Registration Request message of type 'Initial Registration' from the UE, the AMF shall include a new 5G-GUTI in the Registration Accept message. Upon receiving Registration Request message of type 'per","secretary_remarks":"R03 agreed. Revised to S2-2008014","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":12010,"status":"revised","reservation_date":"2020-10-02 16:10:52","uploaded":"2020-10-02 16:15:37","revisionof":"","revisedto":"S2-2008014","release":"Rel-16","crspec":"23.502","crspecversion":"16.6.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2448.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2007682.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2008002","title":"Reply LS on 'Event Configuration Synchronization between 4G&5G'","source":"SA WG2","contact":"Qian Cheng","contact-id":85809,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC: CT WG3. Attachments: 23.501 CR2482 (S2-2007257) and 23.502 CR2421 (S2-2007258)","secretary_remarks":"Revision of S2-2007256. Approved","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":11900,"status":"approved","reservation_date":"2020-10-19 05:20:07","uploaded":"2020-10-20 07:13:49","revisionof":"S2-2007256","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2006807","lsto":"CT WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2008002.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2008011","title":"LS on exception data reporting in non-allowed area","source":"SA WG2","contact":"Qian Cheng","contact-id":85809,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachment: 23.501 CR 2476","secretary_remarks":"Revision of S2-2007144R01. Approved","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":11800,"status":"approved","reservation_date":"2020-10-19 05:20:13","uploaded":"2020-10-20 07:13:49","revisionof":"S2-2007144","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2006819","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2008011.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2008012","title":"Correction on Enhanced Coverage Restriction","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that the AMF decides the Enhanced Coverage Restriction information based on the UE capability indication. Also add the Enhanced Coverage Restriction information for NB-IoT in UE context of AMF side and align with stage 3 for NB-","secretary_remarks":"Revision of S2-2007207R01. Approved","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":11970,"status":"agreed","reservation_date":"2020-10-19 05:20:13","uploaded":"2020-10-20 07:13:49","revisionof":"S2-2007207","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.6.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2419.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200947","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2008012.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2008013","title":"Correction on header compression for CP Optimisation","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarified the UE and SMF behaviours on header compression for CP Optimisation, including that the UE may include additional header compression context setup information in the Header Compression Configuration, and the SMF may establish","secretary_remarks":"Revision of S2-2007484R03. Approved","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":12000,"status":"agreed","reservation_date":"2020-10-19 05:20:15","uploaded":"2020-10-20 07:13:49","revisionof":"S2-2007484","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.6.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2433.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200947","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2008013.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2008014","title":"Clarifications for GUTI re-allocation","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: clause 4.2.2.2.2: Upon receiving a Registration Request message of type 'Initial Registration' from the UE, the AMF shall include a new 5G-GUTI in the Registration Accept message. Upon receiving Registration Request message of type 'per","secretary_remarks":"Revision of S2-2007682R03. Approved","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":12020,"status":"agreed","reservation_date":"2020-10-19 05:20:16","uploaded":"2020-10-20 07:13:49","revisionof":"S2-2007682","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.6.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2448.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200947","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2008014.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]