[{"name":"S2-2300039","title":"LS from RAN WG1: Reply LS on Positioning Reference Units","source":"RAN WG1","contact":"Ren Da","contact-id":70182,"tdoctype":"LS in","for":"Action","abstract":"RAN WG1 would like to thank SA WG2 for the LS (R1-2210824\/S2-2209590) on Positioning Reference Units, in which SA WG2 asks RAN WG1 s view on the following conclusion. SA WG2 has concluded that the PRU information stored in core network at least includes PRU location, mobility state (i.e. fixed or mobile) and PRU capability. The PRU capability indicates the capability of a PRU for supporting positioning activities, which includes the positioning signal transmission capability and positioning measurement capability on Uu and possibly PC5. Based on that information, the PRU could be selected by an LMF to obtain measurements of RAN nodes to help improve location accuracy for all UEs and\/or to assist the positioning of specific other UEs. SA WG2 has also asked RAN WG1 the following questions: - Question#1: Whether there is additional information that needs to be stored in the core network? If yes, what is the information? - Question#2: Whether a PRU can be allowed to support the positioning signal transmission capability and signal measurement capability on PC5? RAN WG1 has discussed the SA WG2 s LS in RAN WG1#111 and would like to provide the following responses. Regarding SA WG2 s conclusion on PRU, RAN WG1 would suggest the following modification: o Based on that information, the PRU could be selected by an LMF to obtain measurements of RAN nodes, or to transmit the reference signals for positioning on Uu and possibly PC5, to help improve location accuracy for all UEs and\/or to assist the positioning of specific other UEs . Regarding SA WG2 s first question, RAN WG1 would suggest SA WG2 to check with RAN WG2 or RAN WG3 for the answer. Regarding SA WG2 s second question, RAN WG1 responds as follows: o From RAN WG1's perspective, a UE (which could be a PRU) that supports SL positioning can be allowed to support the positioning reference signal transmission capability and signal measurement capability on PC5, if the capability is introduced in R18. Action: RAN WG1 respectfully requests SA WG2 to take the above information into account during the work for PRU.","secretary_remarks":"Noted","agenda_item_sort_order":83,"ainumber":"9.6.1","ainame":"Study on 5GC LoCation Services Phase 3 (FS_eLCS_Ph3)","tdoc_agenda_sort_order":15130,"status":"noted","reservation_date":"2022-12-19 08:34:55","uploaded":"2022-12-19 12:42:51","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG2, RAN WG3","lsoriginalls":"R1-2212715","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300039.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300040","title":"LS from RAN WG1: Reply LS on LPHAP information delivery to RAN","source":"RAN WG1","contact":"Su Huang","contact-id":78335,"tdoctype":"LS in","for":"Action","abstract":"RAN WG1 thanks SA WG2 for providing the information on providing LPHAP indication to RAN and the question regarding a possible early indication of LPHAP to RAN before positioning procedure is triggered. RAN WG1 has discussed such an issue and provided the reply as below. Q: Is it necessary to provide LPHAP indication to RAN at an earlier time, before positioning procedure is triggered? A: RAN WG1 currently has not identified the need from the physical layer perspective for SA WG2 to consider LPHAP information delivery to RAN before the positioning procedure is triggered. Action: RAN WG1 respectfully requests SA WG2 to take the above response into account in their future work.","secretary_remarks":"Noted","agenda_item_sort_order":83,"ainumber":"9.6.1","ainame":"Study on 5GC LoCation Services Phase 3 (FS_eLCS_Ph3)","tdoc_agenda_sort_order":15150,"status":"noted","reservation_date":"2022-12-19 08:34:56","uploaded":"2022-12-19 12:42:51","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG2, RAN WG3","lsoriginalls":"R1-2212725","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300040.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300051","title":"LS from RAN WG2: Reply LS on LPHAP information delivery to RAN","source":"RAN WG2","contact":"Yinghao Guo","contact-id":72226,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 thanks SA WG2 s questions on LPHAP and would like to provide answer to the following question: Question: Is it necessary to provide LPHAP indication to RAN at an earlier time, before positioning procedure is triggered? Answer: RAN WG2 has not identified need for LPHAP indication from AMF to RAN before positioning procedures. RAN impacts will be discussed in the WI phase, including aspects of early indication before positioning procedure is triggered. Action: RAN WG2 respectively asks SA WG2 to take the above into account in the future discussion for LPHAP.","secretary_remarks":"Noted","agenda_item_sort_order":83,"ainumber":"9.6.1","ainame":"Study on 5GC LoCation Services Phase 3 (FS_eLCS_Ph3)","tdoc_agenda_sort_order":15160,"status":"noted","reservation_date":"2022-12-19 08:34:57","uploaded":"2022-12-19 12:42:51","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG3, RAN WG1","lsoriginalls":"R2-2213327","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300051.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300059","title":"LS from RAN WG3: LS on Study on expanded and improved NR positioning","source":"RAN WG3","contact":"Philippe Reininger","contact-id":35013,"tdoctype":"LS in","for":"Action","abstract":"During the discussion on the Study of Expanded and Improved NR Positioning for Release-18, RAN WG3 has identified potential impacts on RAN WG3 specifications. The details are attached in R3-226887. Action: RAN WG3 respectfully requests RAN, RAN WG1, RAN WG2 and SA WG2 to take above into account.","secretary_remarks":"Noted","agenda_item_sort_order":83,"ainumber":"9.6.1","ainame":"Study on 5GC LoCation Services Phase 3 (FS_eLCS_Ph3)","tdoc_agenda_sort_order":15140,"status":"noted","reservation_date":"2022-12-19 08:34:57","uploaded":"2022-12-19 12:42:51","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, RAN WG1, RAN WG2, SA WG2","Cc":"","lsoriginalls":"R3-226889","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300059.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]