[{"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}]