[{"name":"S2-2200010","title":"LS from RAN WG2: LS on supporting discontinuous coverage in IoT NTN","source":"RAN WG2","contact":"Abhishek Roy","contact-id":78323,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 would like to inform that RAN WG2 has agreed on supporting discontinuous coverage without excessive UE power consumption and without excessive failures \/ recovery actions. RAN WG2 expects that when not in coverage UE may save power by not attempting cell search or connection establishment. The network is not expected to try to page UEs in an area with no coverage at a certain time, to the extent possible\/reasonable. Due to limited time in Rel-17, it is RAN WG2's understanding that discontinuous coverage in Rel-17 needs to be introduced with minimum specification impact. RAN WG2 has discussed that there may be some impacts to paging, (e)DRX, PSM and PLMN search handling mechanisms and their configurations when the UE is in discontinuous coverage. Action: RAN WG2 respectfully asks SA WG2 and CT WG1 to take the above information into account for possible alignment work and provide feedback, if any.","secretary_remarks":"Revision of Postponed S2-2108271 from S2#148E. Noted","agenda_item_sort_order":70,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":17460,"status":"noted","reservation_date":"2022-01-10 13:42:19","uploaded":"2022-01-10 13:44:26","revisionof":"S2-2108271","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1","Cc":"RAN WG3, CT WG4","lsoriginalls":"R2-2109213","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200010.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200046","title":"Reply LS on EPS support for IoT NTN in Rel-17","source":"CT WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 would like to thank TSG RAN, RAN WG2 and SA WG2 for their LSs on EPS support for IoT NTN in Rel-17. Considering support for discontinuous coverage: CT WG1#132e and 133e discussed and assumes that SA WG2 and RAN\/RAN WG2 should first discuss on the topic and decide whether new functionality needs to be introduced. CT WG1 will align with the decision. Considering support for WUS (response to C1-216539\/S2-2108176): CT WG1 confirms that WUS is not excluded from CT WID. Action: CT WG1 kindly asks groups to consider response given and provide feedback if necessary.","secretary_remarks":"Noted","agenda_item_sort_order":70,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":17570,"status":"noted","reservation_date":"2022-01-10 14:20:56","uploaded":"2022-01-10 16:05:25","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG2, TSG CT, TSG RAN, TSG SA","Cc":"CT WG4, RAN WG3","lsoriginalls":"C1-217258","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200046.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200080","title":"LS from CT WG1: Reply LS on EPS support for IoT NTN in Rel-17","source":"CT WG1","contact":"Marko Niemi","contact-id":16608,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 would like to thank SA WG2 for their LSs on EPS support for IoT NTN in Rel-17 and would like to inform SA WG2 that it will update stage3 according to the latest updates in the SA WG2 WID. Considering changes to TS 23.401 (CR attached S2-2109197) e.g. to sc. 5.3.2.1: 'In case of satellite access for Cellular IoT, the MME may verify the UE location as described in clause 4.X.4. If the UE receives an Attach Reject message with the country in which the UE is located, the UE shall attempt to register to a PLMN that is allowed to operate in the country for the UE location as specified in TS 23.122 [10]'. CT WG1#133bis would like to highlight received LS from SA WG1 (C1-217122) stating that 'There is no impact of the 'indicated country of UE location' on the PLMN selection procedures'. Therefore CT WG1 would kindly ask SA WG2 to consider of rewording of these additions in TS 23.401. Action: CT WG1 kindly asks SA WG2 to consider of rewording TS 23.401 according to received SA WG1 requirement.","secretary_remarks":"Responses drafted in S2-2200571 and S2-2200871. Final response in S2-2201844","agenda_item_sort_order":70,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":17540,"status":"replied to","reservation_date":"2022-01-10 14:20:57","uploaded":"2022-01-25 15:36:02","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, TSG RAN, TSG CT, RAN WG2, SA WG2","Cc":"RAN WG3, CT WG4","lsoriginalls":"C1-220532","lsreply":"S2-2201844","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200080.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200397","title":"IoT NTN: Removal of Indication of country of UE location","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: MME indication of country of UE location is removed (but the cause value is kept) UE PLMN selection based on indicated country of UE location is removed","secretary_remarks":"Postponed","agenda_item_sort_order":70,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":17470,"status":"postponed","reservation_date":"2022-01-27 13:28:45","uploaded":"2022-01-28 15:03:23","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.401","crspecversion":"17.3.0","workitem":[{"winame":"IoT_SAT_ARCH_EPS"}],"crnumber":3682.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200397.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200399","title":"IoT NTN: Alignment of TA Handling for moving cells with NR NTN","source":"MediaTek Inc., Nokia, Nokia Shanghai Bell, Huawei, HiSilicon","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: TA Handling defined for moving cells, incl. handling of forbidden TA (in the same subclause unlike in 23.501 due to discrepancies between 23.401 and 23.501)","secretary_remarks":"r01 agreed. Revised to S2-2201332.","agenda_item_sort_order":70,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":17480,"status":"revised","reservation_date":"2022-01-27 13:28:47","uploaded":"2022-01-28 15:03:23","revisionof":"","revisedto":"S2-2201332","release":"Rel-17","crspec":"23.401","crspecversion":"17.3.0","workitem":[{"winame":"IoT_SAT_ARCH_EPS"}],"crnumber":3683.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200399.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200412","title":"LS from RAN WG2: LS on UE providing Location Information for NB-IoT","source":"RAN WG2","contact":"Jonas Sedin","contact-id":78315,"tdoctype":"LS in","for":"Action","abstract":"Following liaisons with SA WG2, SA WG3 and RAN WG3 (see R2-2109216, R2-2200145, R2-2200149, R2-2202542) on the reporting of UE location information in NR NTN, RAN WG2 has started to discuss location reporting aspects for IoT NTN. For NB-IoT UEs AS security cannot be assumed to be supported. This has lead RAN WG2 to assume that sending a detailed location over AS cannot be supported and RAN WG2 has thus discussed whether to send coarse location. However, in latest received LS by SA WG3 in R2-2200149\/S3-213360 regarding NR NTN location reporting, it is stated that even sending coarse location unprotected should be avoided, so RAN WG2 has assumed that not even coarse location may be reported over AS for NB-IoT. RAN WG2 also discussed the possibility UE providing location to the MME via NAS procedures as an alternative to deliver the location information via AS. RAN WG2 have the following questions to RAN WG3\/SA WG2 and CT WG1: - To RAN WG3\/SA WG2, we ask whether there are any issues from a RAN WG3 and SA WG2 point of view that a NB-IoT UE does not provide any location information over AS to eNB. o RAN WG2 assumes that not providing location over AS may lead to impact on E-UTRAN selecting correct core network, NNSF and constructing the mapped cell ID and any potential ULI. - To RAN WG3\/SA WG2\/CT WG1, if location is not provided over AS and the location is needed for network operation is it feasible from a RAN WG3 and SA WG2 point of view that UE instead provides location to the MME via NAS, which is assumed to be protected. o If providing location over NAS is a viable solution that is acceptable for network operation, then is it feasible that this is introduced in Rel-17. Action: RAN WG2 asks of RAN WG3\/SA WG2\/CT WG1 to kindly consider the questions above and get back to RAN WG2 regarding issues or feasibility of the above.","secretary_remarks":"Response drafted in S2-2201242. Final response in S2-2201333","agenda_item_sort_order":70,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":17580,"status":"replied to","reservation_date":"2022-01-27 15:09:57","uploaded":"2022-01-27 16:01:33","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, SA WG2, CT WG1","Cc":"SA WG3, SA WG3-LI","lsoriginalls":"R2-2201957","lsreply":"S2-2201333","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200412.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200413","title":"LS from RAN WG2: LS on security concerns for UE providing Location Information for NB-IoT","source":"RAN WG2","contact":"Jonas Sedin","contact-id":78315,"tdoctype":"LS in","for":"Information","abstract":"Following liaisons with SA WG2, SA WG3 and RAN WG3 (see R2-2109216, R2-2200145, R2-2200149, R2-2202542) on the reporting of UE location information in NR NTN, RAN WG2 has started to discuss location reporting aspects for IoT NTN. For NB-IoT UEs AS security cannot be assumed to be supported. This has lead RAN WG2 to assume that sending a detailed location over AS cannot be supported and RAN WG2 has thus discussed whether to send coarse location. However, in latest received LS by SA WG3 in R2-2200149\/S3-213360 regarding NR NTN location reporting, it is stated that even sending coarse location unprotected should be avoided, so RAN WG2 has assumed that not even coarse location may be reported over AS for NB-IoT. RAN WG2 also discussed the possibility UE providing location to the MME via NAS procedures as an alternative to deliver the location information via AS, but whether this solves the problem of the network is yet to be confirmed by RAN WG3\/SA WG2. There have also been discussions in RAN WG2 whether a NB-IoT UE would be subject to the same privacy requirements as for a NR UE. RAN WG2 have the following questions\/request for comments to SA WG3: - Given that IoT may not have the same privacy requirements as in NR, is it the correct understanding of RAN WG2 that providing a coarse location regardless of granularity without AS security should also be avoided for NB-IoT. - As RAN WG2 has discussed the location reporting where instead of sending the coarse location over AS, the UE could potentially send location over NAS to MME and even though the feasibility of this is yet to be confirmed by RAN WG3\/SA WG2\/CT WG1, RAN WG2 asks SA WG3 to comment if there are any potential security concerns with providing the location over NAS to MME (where NAS security is assumed to be applied), such as user consent or similar.","secretary_remarks":"Noted","agenda_item_sort_order":70,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":17610,"status":"noted","reservation_date":"2022-01-27 15:09:57","uploaded":"2022-01-27 16:01:33","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, SA WG3-LI","Cc":"RAN WG3, SA WG2, CT WG1","lsoriginalls":"R2-2201958","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200413.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200418","title":"LS from RAN WG3: LS on opens issues for NB-IoT and eMTC support for NTN","source":"RAN WG3","contact":"Steven Xu","contact-id":81642,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 would like to inform SA WG2, SA WG3 and RAN WG2 that RAN WG3 has started specifying NB-IoT and eMTC NTN support for E-UTRAN (including S1 and X2 interfaces), by reusing NR NTN functionality as a baseline. RAN WG3 assumes the relevant functionality will be supported in the EPC. RAN WG3 would like to ask the following questions: 1) To SA WG2 and SA WG3 For a UE using CP CIoT EPS optimization only, RAN WG3 understands that the UE might not be able to provide UE location information to eNB, on the assumption that such information can only be sent after AS security activation. Therefore, the CGI provided in the ULI to MME may only refer to a quite coarse-grained location (e.g., based on the satellite beam footprint) and might not be sufficient to determine the country where the UE is located (and also not close to TN level granularity, as previously requested for NR NTN). RAN WG3 would like thus to ask SA WG2 and SA WG3 whether such a coarse-grained location is sufficient for UEs using only CP CIoT EPS optimization in release 17. RAN WG3 assumes that no such issue will arise for UEs using UP CIoT EPS optimization. 2) To SA WG2 and RAN WG2 RAN WG3 assumes that the LTE-M NTN capable UE indicates category M1 or M2 in its UE Radio Capability, which then the eNB will indicate to the CN as LTE-M Satellite Indication in the UE CAPABILITY INFO INDICATION message. RAN WG3 would ask RAN WG2 and SA WG2 to confirm this assumption. Action: RAN WG3 kindly asks SA WG2 and SA WG3 to provide feedback on above issues.","secretary_remarks":"Postponed","agenda_item_sort_order":70,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":17500,"status":"postponed","reservation_date":"2022-01-27 15:09:57","uploaded":"2022-01-27 16:01:33","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3, RAN WG2","Cc":"","lsoriginalls":"R3-221406","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200418.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200571","title":"[DRAFT]Reply LS on EPS support for IoT NTN in Rel-17","source":"OPPO","contact":"Jingran Chen","contact-id":88895,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to clarify such indication is useful for UE to determine its location.","secretary_remarks":"Response to S2-2200080. Merged into S2-2201844","agenda_item_sort_order":70,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":17550,"status":"merged","reservation_date":"2022-01-28 06:36:25","uploaded":"2022-01-28 06:51:11","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"IoT_SAT_ARCH_EPS"}],"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_149E_Electronic_2022-02\/Docs\/S2-2200571.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200572","title":"IoT NTN: The requirement of the indication of the UE location","source":"OPPO","contact":"Jingran Chen","contact-id":88895,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add a note to clarify the requirement of such indication and clarify how the UE will do if the UE knows the exact country in which it is located is based on the UE implementation","secretary_remarks":"Postponed","agenda_item_sort_order":70,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":17510,"status":"postponed","reservation_date":"2022-01-28 06:41:36","uploaded":"2022-01-28 06:51:11","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.401","crspecversion":"17.3.0","workitem":[{"winame":"IoT_SAT_ARCH_EPS"}],"crnumber":3685.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200572.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200870","title":"Remove indicaiton of country of UE location from TS23.401","source":"Xiaomi","contact":"Yuxin MAO","contact-id":91413,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 'indication of country of UE location' is removed from text in TS 23.401","secretary_remarks":"Postponed","agenda_item_sort_order":70,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":17520,"status":"postponed","reservation_date":"2022-01-28 11:39:16","uploaded":"2022-01-28 12:15:47","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.401","crspecversion":"17.3.0","workitem":[{"winame":"IoT_SAT_ARCH_EPS"}],"crnumber":3686.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200870.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200871","title":"[DRAFT] Reply LS on EPS support for IoT NTN in Rel-17","source":"Xiaomi","contact":"Yuxin MAO","contact-id":91413,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1, RAN WG2, TSG CT, TSG RAN, TSG SA. CC: CT WG4, RAN WG3","secretary_remarks":"Response to S2-2200080. Merged into S2-2201844","agenda_item_sort_order":70,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":17560,"status":"merged","reservation_date":"2022-01-28 11:39:17","uploaded":"2022-01-28 12:15:47","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"IoT_SAT_ARCH_EPS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, RAN WG2, TSG CT, TSG RAN, TSG SA","Cc":"CT WG4, RAN WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200871.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201004","title":"Limited service emergency call over satellite","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: For limited service state emergency call, the UE should select a PLMN that is allowed to operate in the country of the present UE location. The network may verify this choice.","secretary_remarks":"Approved","agenda_item_sort_order":70,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":17530,"status":"agreed","reservation_date":"2022-01-28 14:11:04","uploaded":"2022-01-28 17:05:01","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.401","crspecversion":"17.3.0","workitem":[{"winame":"IoT_SAT_ARCH_EPS"}],"crnumber":3690.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-220061","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201004.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201242","title":"[DRAFT] LS Response to LS on UE providing Location Information for NB-IoT","source":"Qualcomm Incorporated","contact":"Stephen Edge","contact-id":84641,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2. CC: RAN WG3, CT WG1, SA WG3, SA WG3-LI","secretary_remarks":"Response to S2-2200412. r02 agreed. Revised to S2-2201333.","agenda_item_sort_order":70,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":17590,"status":"revised","reservation_date":"2022-01-28 22:42:29","uploaded":"2022-01-28 23:05:20","revisionof":"","revisedto":"S2-2201333","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"RAN WG3, CT WG1, SA WG3, SA WG3-LI","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201242.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201257","title":"LS from RAN WG2: Reply LS on IoT NTN extended NAS supervision timers at satellite access","source":"RAN WG2","contact":"Jonas Sedin","contact-id":78315,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 received an LS from CT WG1 asking about feasibility of the current NAS supervision timer in C1-215074: As the NAS supervision timers control triggering of NAS message re-transmission and determination of NAS procedure failure, updated timing for NAS message transport in AS compared to current NG-RAN needs to be considered. Therefore, CT WG1 would appreciate answers to the following questions: - For all satellite access types (LEO, MEO, GEO) where AS timing is updated, what is the worst-case delay in AS for transport of NAS messages via satellite access, including potential delays due to GNSS fix acquisition: 1) For initial NAS messages in the UL direction; 2) For non-initial NAS messages in the UL direction; and 3) For NAS messages in the DL direction. This was replied to by NR NTN in R2-2111612, where the values for the physical RTT is for LEO and GEO are also applicable for IoT NTN. IoT NTN RAN WG2 has evaluated the possible latencies in the 3 above cases with varying results depending on configuration and notes that it is difficult to converge on a set of numbers that balances worst case scenarios and reasonable configurations. The difference between NR and IoT is that the maximum transmission durations in the most extreme cases for a single PUSCH transmission can be more than 2 seconds and 40 seconds for LTE-M and NB-IoT respectively. While the NTN physical propagation delays are longer than in terrestrial networks, RAN WG2 notes that for GEO scenario the physical propagation delays only constitute roughly 10% and 1% of the total transmission delay for eMTC and NB-IoT respectively for the most extreme transmission durations. Given this, RAN WG2 observes the following: - RAN WG2 assumes existing extended timers designed for eMTC and NB-IoT may be sufficient for IoT NTN to cover additional delays caused by long propagation delays, as the propagation delays are a fraction of the total transmission delays. Furthermore, similar to NR NTN the requirement is that UE shall have a valid GNSS position for synchronization to an NTN cell. This means that the UE might need to perform GNSS acquisition before initial access. In the absolute worst case, the acquisition of a GNSS fix can in a cold state take up to 100 s, from a warm state - 50 s and from hot state - 2 s.","secretary_remarks":"Noted","agenda_item_sort_order":70,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":17450,"status":"noted","reservation_date":"2022-01-31 15:41:47","uploaded":"2022-01-31 15:42:24","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG2","lsoriginalls":"R2-2201951","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201257.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201332","title":"IoT NTN: Alignment of TA Handling for moving cells with NR NTN","source":"MediaTek Inc., Nokia, Nokia Shanghai Bell, Huawei, HiSilicon","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: TA Handling defined for moving cells, incl. handling of forbidden TA (in the same subclause unlike in 23.501 due to discrepancies between 23.401 and 23.501)","secretary_remarks":"Revision of S2-2200399r01. Approved","agenda_item_sort_order":70,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":17490,"status":"agreed","reservation_date":"2022-03-01 08:26:41","uploaded":"2022-03-01 08:41:20","revisionof":"S2-2200399","revisedto":"","release":"Rel-17","crspec":"23.401","crspecversion":"17.3.0","workitem":[{"winame":"IoT_SAT_ARCH_EPS"}],"crnumber":3683.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220061","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201332.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201333","title":"LS Response to LS on UE providing Location Information for NB-IoT","source":"SA WG2","contact":"Stephen Edge","contact-id":84641,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2. CC: RAN WG3, CT WG1, SA WG3, SA WG3-LI","secretary_remarks":"Revision of S2-2201242r02. Approved","agenda_item_sort_order":70,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":17600,"status":"approved","reservation_date":"2022-03-01 08:26:42","uploaded":"2022-03-01 08:41:13","revisionof":"S2-2201242","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5GSAT_ARCH"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2200412","lsto":"RAN WG2","Cc":"RAN WG3, CT WG1, SA WG3, SA WG3-LI","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201333.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]