[{"name":"S2-2201932","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":"Revision of Postponed S2-2200418 from S2#149E. Response drafted in S2-2202006, S2-2202875. Final response in S2-2203064","agenda_item_sort_order":35,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":14050,"status":"replied to","reservation_date":"2022-03-25 17:03:58","uploaded":"2022-03-28 08:00:13","revisionof":"S2-2200418","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":"S2-2203064, S2-2203064","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2201932.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202003","title":"TN-NTN NB-IoT mobility for CP-CIoT","source":"Qualcomm","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"discussion","for":"Approval","abstract":"Discusses the issue of inter-RAT mobility between NB-IoT TN and NB-IoT NTN using CP CIoT and proposes a way forward","secretary_remarks":"Noted","agenda_item_sort_order":35,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":14140,"status":"noted","reservation_date":"2022-03-27 19:40:55","uploaded":"2022-03-29 18:45:05","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"IoT_SAT_ARCH_EPS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202003.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202004","title":"NB-IOT TN-NTN mobility for CP-CIoT","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Endorsement","abstract":"Summary of change: Define new update type 'access change' for the TAU request for the UE using CP CIoT and performing inter-RAT mobility between TN and NTN. Upon receiving TAU request with the new update type, the MME triggers MME CP Realocation Indication procedure, followed by normal TAU procedure.","secretary_remarks":"Postponed","agenda_item_sort_order":35,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":14160,"status":"postponed","reservation_date":"2022-03-27 19:43:22","uploaded":"2022-03-29 18:45:05","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.401","crspecversion":"17.4.0","workitem":[{"winame":"IoT_SAT_ARCH_EPS"}],"crnumber":3693.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202004.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202005","title":"NB-IoT Control Plane Relocation procedure upon NTN to TN mobility","source":"Qualcomm","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"NB-IoT Control Plane Relocation procedure upon NTN to TN mobility","secretary_remarks":"Noted","agenda_item_sort_order":35,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":14090,"status":"noted","reservation_date":"2022-03-27 19:46:16","uploaded":"2022-03-29 18:45:05","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"IoT_SAT_ARCH_EPS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, CT WG1, SA WG3, RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202005.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202006","title":"Reply LS on opens issues for NB-IoT and eMTC support for NTN","source":"Qualcomm","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"Replies to LS R3-221406","secretary_remarks":"Response to S2-2201932. r02 agreed. Revised to S2-2203064, merging S2-2202875","agenda_item_sort_order":35,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":14070,"status":"revised","reservation_date":"2022-03-27 19:49:31","uploaded":"2022-03-29 18:45:05","revisionof":"","revisedto":"S2-2203064","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"LTE_NBIOT_eMTC_NTN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202006.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202007","title":"Removal of unecessary LTE-M satellite Indication in S1-AP","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove unecessary 'LTE-M Satellite Indication'","secretary_remarks":"r03 agreed. Revised to S2-2203065","agenda_item_sort_order":35,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":14170,"status":"revised","reservation_date":"2022-03-27 19:51:20","uploaded":"2022-03-29 18:45:05","revisionof":"","revisedto":"S2-2203065","release":"Rel-17","crspec":"23.401","crspecversion":"17.4.0","workitem":[{"winame":"IoT_SAT_ARCH_EPS"}],"crnumber":3694.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202007.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202237","title":"IoT NTN: Correction of last visited TAI requirement","source":"Apple","contact":"Robert Zaus","contact-id":85311,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) Missing condition is added. 2+3) wrong terminology is corrected.","secretary_remarks":"Postponed","agenda_item_sort_order":35,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":14190,"status":"postponed","reservation_date":"2022-03-28 18:47:02","uploaded":"2022-03-29 11:58:50","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.401","crspecversion":"17.4.0","workitem":[{"winame":"IoT_SAT_ARCH_EPS"}],"crnumber":3697.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202237.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202395","title":"IoT NTN: Alignment of TA handling for moving cells with NR NTN","source":"OPPO","contact":"Jingran Chen","contact-id":88895,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Align with the description in 5.4.11.7 in 23.501 that E-UTRAN provides TAI(s) corresponding to Selected PLMN when the E-UTRAN broadcasts multiple TACs.","secretary_remarks":"Approved","agenda_item_sort_order":35,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":14200,"status":"agreed","reservation_date":"2022-03-29 07:59:59","uploaded":"2022-03-29 08:17:39","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.401","crspecversion":"17.4.0","workitem":[{"winame":"IoT_SAT_ARCH_EPS"}],"crnumber":3698.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-220405","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202395.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202777","title":"LS from CT WG1: Reply LS on UE providing Location Information for NB-IoT","source":"CT WG1","contact":"Vivek Gupta","contact-id":91167,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 thanks RAN WG2 for their LS (C1-221022 \/ R2-2201957) on UE providing location information for NB-IoT. CT WG1 has concerns about providing UE location information reliably in initial NAS messages as these messages are not secure. Subsequently, after NAS security is established, the UE location information can be provided by NAS. Regarding feasibility of introducing a solution at this fairly late stage in Rel-17 timeframe, any potential new solution in CT WG1 requires stage 2 requirements for Rel-17. Action: CT WG1 kindly asks RAN WG2\/RAN WG3\/SA WG2 to take the above response into account.","secretary_remarks":"Noted","agenda_item_sort_order":35,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":14100,"status":"noted","reservation_date":"2022-03-29 15:34:29","uploaded":"2022-03-29 17:47:55","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3, SA WG2","Cc":"SA WG3, SA WG3-Li","lsoriginalls":"C1-222100","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202777.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202787","title":"LS from RAN WG3: Reply LS on UE providing Location Information for NB-IoT","source":"RAN WG3","contact":"Gino Masini","contact-id":23120,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 thanks RAN WG2 for the progress report on location reporting aspects for IoT NTN, and would like to provide the following information. Regarding the question on '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': The location information provided by the UE is used by the RAN node, together with other information, as input for the NNSF for selecting the appropriate MME at UE attach (Sec. 5.9.2 of TS 36.410 and the endorsed BL CR, R3-221601). Therefore, RAN WG3 can confirm RAN WG2's assumption that the lack of this information may have an impact on NNSF. However, the eNB should still be able to select the appropriate MME in most cases. Furthermore, the initial mapped cell ID reported over S1 might not have the required granularity level. Regarding the question: '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', and whether it is feasible to introduce it in Rel-17: Once the MME has been selected, UE location information is not required by RAN for initial access anymore. Action: RAN WG3 asks RAN WG2 and SA WG2 to take the above into account.","secretary_remarks":"Noted","agenda_item_sort_order":35,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":14110,"status":"noted","reservation_date":"2022-03-29 15:34:29","uploaded":"2022-03-29 17:47:55","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, SA WG2","Cc":"CT WG1, SA WG3, SA WG3LI","lsoriginalls":"R3-222858","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202787.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202788","title":"LS from RAN WG3: Reply LS on UE location during initial access in NTN","source":"RAN WG3","contact":"Nicolas Chuberre","contact-id":21633,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 thanks RAN WG2 for its Liaison in which the following questions was submitted: Is it acceptable that no UE location information is reported at the NG-RAN in a NTN network during initial access ? RAN WG3's response can be found below: Without knowledge of the UE location during the initial access, the gNB may not be able to select the correct AMF. If this happens, the incorrect AMF de-registers the UE, asks the UE to re-register and may inform NG-RAN with an appropriate NGAP cause value in the NGAP UE CONTEXT RELEASE COMMAND message. On subsequent network access attempt by the UE, the NG-RAN may be able to select the right AMF based on the information from the UE. This translates into a risk of extended UE registration (or connection set-up), but only in extreme cases of large radio cell covering more than 1 country, and only at the transition to RRC CONNECTED state or after significant UE movement. In addition, the initial mapped cell ID reported over NGAP may not be able to provide the level of granularity that has been requested by SA groups, but it has previously been clarified that this is acceptable at initial access. There are no significant impacts in RAN WG3 specifications resulting from this change. Overall RAN WG3 confirms that the above is acceptable from RAN WG3 point of view.","secretary_remarks":"Noted","agenda_item_sort_order":35,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":14120,"status":"noted","reservation_date":"2022-03-29 15:34:29","uploaded":"2022-03-29 17:47:55","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"CT WG1, SA WG3, SA WG2","lsoriginalls":"R3-222861","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202788.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202795","title":"LS from SA WG3: Reply LS on security concerns for UE providing Location Information for NB-IoT","source":"SA WG3","contact":"Wei Lu","contact-id":90295,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 would like to thank RAN WG2 for their LS R2-2201958 on security concerns for UE providing location information for NB-IoT. SA WG3 would like to provide the following answers regarding the specific questions asked by RAN WG2: - From the aspect of privacy, SA WG3 does not think that the privacy requirements for NB-IoT UE are much different from the privacy requirements for NR UE. Therefore, the same feedback provided for NR UE (in S3-214360) applies to NB-IoT UE. - Regarding the potential solution of sending UE location over NAS to the MME, SA WG3 does not see any potential security concern with such solution as long as the location information is sent after NAS security is established. Even after NAS security establishment, RAN WG2 should be aware that user consent for obtaining UE location information may also be required depending on regional regulation and policy.","secretary_remarks":"Noted","agenda_item_sort_order":35,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":14130,"status":"noted","reservation_date":"2022-03-29 15:34:29","uploaded":"2022-03-29 17:47:55","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"CT WG1, SA WG2, RAN WG3, SA WG3-LI","lsoriginalls":"S3-220544","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202795.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202875","title":"[DRAFT] Reply LS on open issues for NB-IoT and eMTC support for NTN","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"LS out","for":"Approval","abstract":"Relevant to: IoT_SAT_ARCH_EPS Common Reply LS to: R3-221406, S3-220543\/S2-220453, R2-2204108\/S2-2201950 Informing about the removal of the indication of country of UE location, for NR NTN and IoT NTN","secretary_remarks":"Response to S2-2201932. Merged into S2-2203064","agenda_item_sort_order":35,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":14060,"status":"merged","reservation_date":"2022-03-29 17:01:19","uploaded":"2022-03-29 18:31:06","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"IoT_SAT_ARCH_EPS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3, SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202875.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203064","title":"Reply LS on opens issues for NB-IoT and eMTC support for NTN","source":"Qualcomm","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"Replies to LS R3-221406","secretary_remarks":"Revision of S2-2202006r02, merging S2-2202875. Approved","agenda_item_sort_order":35,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":14080,"status":"approved","reservation_date":"2022-04-13 09:52:24","uploaded":"2022-04-13 15:41:12","revisionof":"S2-2202006","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"LTE_NBIOT_eMTC_NTN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2201932","lsto":"RAN WG3","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203064.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203065","title":"Removal of unecessary LTE-M satellite Indication in S1-AP","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove unecessary 'LTE-M Satellite Indication' Reinstate 4.13.3 (Heading Type 3)","secretary_remarks":"Revision of S2-2202007r03. Approved","agenda_item_sort_order":35,"ainumber":"8.27","ainame":"Architecture support for NB-IoT\/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)","tdoc_agenda_sort_order":14180,"status":"agreed","reservation_date":"2022-04-13 09:52:24","uploaded":"2022-04-14 09:01:19","revisionof":"S2-2202007","revisedto":"","release":"Rel-17","crspec":"23.401","crspecversion":"17.4.0","workitem":[{"winame":"IoT_SAT_ARCH_EPS"}],"crnumber":3694.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220405","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203065.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]