[{"name":"S2-2500010","title":"LS from CT WG1: LS on UEs user plane availability status for LCS-UPP","source":"CT WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"In TS 24.572, the cause value 'user plane not available' was introduced for UE to reject the network initiated user plane connection establishment procedure when the user plane is not available or release the established user plane connection when the user plane availability is changed to 'not available', e.g. due to the activation of the PS data off for the UE. However, currently there is no dedicated procedure specified to inform the LMF when the UE's user plane availability changes from 'unavailable' to 'available'. What currently is supported: - The UE can initiate UE requested user plane connection establishment procedure, which may not be appropriate unless the UE has UL positioning signalling, i.e. either such notification is delayed or user plane positioning resources are unnecessarily established; - The LMF can attempt reactivation of user plane positioning using the network initiated user plane connection establishment procedure. This leads to extra unsuccessful user plane connection establishment procedure attempts over the air interface until the user plane is 'available'. CT WG1 would like to ask the following questions: 1. Would the above issue need to be resolved? 2. If the answer to the question 1 is yes, CT WG1 would like to ask for SA WG2 guidance on resolving the issue. Action: CT WG1 kindly asks SA WG2 to take above information into account and provide guidance on above issue.","secretary_remarks":"Response drafted in S2-2500733. FInal response in S2-2501178","agenda_item_sort_order":78,"ainumber":"9.6.2","ainame":"5GC LoCation Services Phase 3 (eLCS_Ph3)","tdoc_agenda_sort_order":11150,"status":"replied to","reservation_date":"2024-12-06 13:48:12","uploaded":"2024-12-29 12:18:51","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C1-246023","lsreply":"S2-2501178","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500010.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500035","title":"LS from CT WG1: LS on Requesting allocation of new TCP port for Location Services User Plane Protocol (LCS-UPP)","source":"CT WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"In the scope of 5G_eLCS_Ph3, CT WG1 has identified the need to use a TCP port number between the UE and the LMF to establish the TLS connection used by a LCS secured user plane connection. CT WG1 has agreed a CR to TS 24.572 for this enhancement which uses a standardized port number. CT WG1 investigated the alternatives captured in TR 29.941 and concluded that the allocation of new TCP port number for LCS-UPP over TLS\/TCP in Rel18 cannot meet IANA requirements for the port number allocation. Therefore, CT WG1 believes that a new 3GPP allocated TCP port number is the preferred way forward (i.e., 3GPP TR 29.941 solution #6; 3GPP allocated port number solution), and therefore CT WG1 would like to request allocation of new 3GPP allocated port number with the following information for filing the table 5-1 of 3GPP TS 29.641: a) The service name is Location Services User Plane Protocol (LCS-UPP); b) The transport protocol is TCP; c) The description is LCS-UPP; d) New port number will be used for 3GPP NL11 interface between UE and LMF, this solution will work only for intra-domain interface; e) Respective Work Item Code (WIC) is 5G_eLCS_Ph3 (unique identifier: 980003).","secretary_remarks":"Noted in e-mail session","agenda_item_sort_order":78,"ainumber":"9.6.2","ainame":"5GC LoCation Services Phase 3 (eLCS_Ph3)","tdoc_agenda_sort_order":11140,"status":"noted","reservation_date":"2024-12-06 13:48:12","uploaded":"2024-12-29 12:18:51","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"TSG CT","lsoriginalls":"C1-247157","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500035.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500370","title":"Analysis on the number of LCS-UPP connections.","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Discussion","abstract":"In SA WG2#165 SA WG2 meeting CR has been postponed defining the number of LCS-UPP connections per UE. Now this discussion paper analyses the situation and proposes the possible way forward.","secretary_remarks":"Noted in e-mail session","agenda_item_sort_order":78,"ainumber":"9.6.2","ainame":"5GC LoCation Services Phase 3 (eLCS_Ph3)","tdoc_agenda_sort_order":11200,"status":"noted","reservation_date":"2025-01-13 12:33:40","uploaded":"2025-01-14 22:25:20","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.273","crspecversion":"","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500370.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500371","title":"Clarify number of user plane connections for user plane positioning","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Clarify that in rel-18 shall have maximum one LCS-UPP connection.","secretary_remarks":"LATE DOC: Not provided. WITHDRAWN","agenda_item_sort_order":78,"ainumber":"9.6.2","ainame":"5GC LoCation Services Phase 3 (eLCS_Ph3)","tdoc_agenda_sort_order":11220,"status":"withdrawn","reservation_date":"2025-01-13 12:33:40","uploaded":null,"revisionof":"","revisedto":"S2-2501608","release":"Rel-18","crspec":"23.273","crspecversion":"18.8.0","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":645.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500372","title":"Clarify number of user plane connections for user plane positioning","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Rel-19 mirror CR: Summary of change: Adding that UE shall have maximum one LCS-UPP connection towards each LMF.","secretary_remarks":"WI Code should be 5G_eLCS_Ph3! Postponed in e-mail session","agenda_item_sort_order":78,"ainumber":"9.6.2","ainame":"5GC LoCation Services Phase 3 (eLCS_Ph3)","tdoc_agenda_sort_order":11210,"status":"postponed","reservation_date":"2025-01-13 12:33:41","uploaded":"2025-01-14 22:25:20","revisionof":"","revisedto":"S2-2501609","release":"Rel-19","crspec":"23.273","crspecversion":"19.1.0","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":646.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500372.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.18.0, 6.18.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500373","title":"Move NOTE 2 back to the user plane positioning text","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Move NOTE 2 under the related text.","secretary_remarks":"Approved","agenda_item_sort_order":78,"ainumber":"9.6.2","ainame":"5GC LoCation Services Phase 3 (eLCS_Ph3)","tdoc_agenda_sort_order":11270,"status":"agreed","reservation_date":"2025-01-13 12:33:42","uploaded":"2025-01-14 22:01:43","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.273","crspecversion":"19.1.0","workitem":[{"winame":"5G_eLCS_Ph3"},{"winame":" TEI19"}],"crnumber":647.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-250037","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500373.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.3.8","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500694","title":"Supporting of Paging Policy Differentiation for Positioning Service","source":"China Telecom","contact":"XIAOQIAN JIA","contact-id":102960,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Support the mechanism where the LMF sets the DSCP value (TOS in IPv4 \/ TC in IPv6) to indicate a specific Paging Policy for packets related to supplementary services messages and Location Presence Procedure (LPP) messages.","secretary_remarks":"WI Code should be 5G_eLCS_Ph3! Noted in e-mail session","agenda_item_sort_order":78,"ainumber":"9.6.2","ainame":"5GC LoCation Services Phase 3 (eLCS_Ph3)","tdoc_agenda_sort_order":11230,"status":"noted","reservation_date":"2025-01-14 09:08:29","uploaded":"2025-01-14 09:35:19","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.273","crspecversion":"18.8.0","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":655.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500694.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500733","title":"[DRAFT] Reply LS on UE's user plane availability status for LCS-UPP","source":"vivo","contact":"Wen Wang","contact-id":75748,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: -. Attachments:.","secretary_remarks":"Response to S2-2500010. r00 agreed. Revised in e-mail session to S2-2501178.","agenda_item_sort_order":78,"ainumber":"9.6.2","ainame":"5GC LoCation Services Phase 3 (eLCS_Ph3)","tdoc_agenda_sort_order":11160,"status":"revised","reservation_date":"2025-01-14 09:38:43","uploaded":"2025-01-14 10:57:38","revisionof":"","revisedto":"S2-2501178","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"TEI19"},{"winame":" 5G_eLCS_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500733.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500856","title":"Clarification on charging aspects for LCS UP positioning","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarification that LMF can support to record charging information in the case of UE initiated location request via established user plane.","secretary_remarks":"Postponed in e-mail session","agenda_item_sort_order":78,"ainumber":"9.6.2","ainame":"5GC LoCation Services Phase 3 (eLCS_Ph3)","tdoc_agenda_sort_order":11240,"status":"postponed","reservation_date":"2025-01-14 13:21:29","uploaded":"2025-01-14 13:58:53","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.273","crspecversion":"18.8.0","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":659.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500856.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.6, 6.11.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500857","title":"Clarification on charging aspects for LCS UP positioning","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Rel-19 mirror CR: Summary of change: Clarification that LMF can support to record charging information in the case of UE initiated location request via established user plane.","secretary_remarks":"Postponed in e-mail session","agenda_item_sort_order":78,"ainumber":"9.6.2","ainame":"5GC LoCation Services Phase 3 (eLCS_Ph3)","tdoc_agenda_sort_order":11250,"status":"postponed","reservation_date":"2025-01-14 13:21:31","uploaded":"2025-01-14 13:58:53","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.273","crspecversion":"19.1.0","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":660.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500857.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.6, 6.11.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500858","title":"[DRAFT] LS on Support of charing for LCS UP positioning","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"LSOut LS on Support of charing for LCS UP positioning","secretary_remarks":"Postponed in e-mail session","agenda_item_sort_order":78,"ainumber":"9.6.2","ainame":"5GC LoCation Services Phase 3 (eLCS_Ph3)","tdoc_agenda_sort_order":11260,"status":"postponed","reservation_date":"2025-01-14 13:21:32","uploaded":"2025-01-14 13:58:53","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500858.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500859","title":"Clarification on LMF re-selection of LCS UP positioning","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify in step 1b of clause 6.18.3 that AMF *should* perform LMF reselection if a target LMF identification received from source LMF for user plane positioning, or AMF *may* perform LMF reselection if a UE established an LCS UP connect","secretary_remarks":"Approved","agenda_item_sort_order":78,"ainumber":"9.6.2","ainame":"5GC LoCation Services Phase 3 (eLCS_Ph3)","tdoc_agenda_sort_order":11180,"status":"agreed","reservation_date":"2025-01-14 13:21:32","uploaded":"2025-01-14 13:58:53","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.273","crspecversion":"18.8.0","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":661.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-250031","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500859.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.18.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500860","title":"Clarification on LMF re-selection of LCS UP positioning","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Rel-19 mirror CR: Summary of change: Clarify in step 1b of clause 6.18.3 that AMF *should* perform LMF reselection if a target LMF identification received from source LMF for user plane positioning, or AMF *may* perform LMF reselection if a UE established","secretary_remarks":"Approved","agenda_item_sort_order":78,"ainumber":"9.6.2","ainame":"5GC LoCation Services Phase 3 (eLCS_Ph3)","tdoc_agenda_sort_order":11190,"status":"agreed","reservation_date":"2025-01-14 13:21:33","uploaded":"2025-01-14 13:58:53","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.273","crspecversion":"19.1.0","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":662.0,"crrevision":"","crcategory":"A","tsg_crp":"SP-250031","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500860.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.18.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500974","title":"Emergency SUPL Reference Alignment with 23.271","source":"Nokia, Nokia Shanghai Bell","contact":"Mao Cai","contact-id":89487,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the same reference in TS 23.271 in order to keep alignment of Locatoin Continuity in Clause 6.10.3.","secretary_remarks":"Noted in e-mail session","agenda_item_sort_order":78,"ainumber":"9.6.2","ainame":"5GC LoCation Services Phase 3 (eLCS_Ph3)","tdoc_agenda_sort_order":11280,"status":"noted","reservation_date":"2025-01-14 16:05:45","uploaded":"2025-01-14 16:23:40","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.273","crspecversion":"18.8.0","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":663.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500974.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"2, 6.10.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500975","title":"Emergency SUPL Reference Alignment with 23.271","source":"Nokia, Nokia Shanghai Bell","contact":"Mao Cai","contact-id":89487,"tdoctype":"CR","for":"Approval","abstract":"Rel-19 mirror CR: Summary of change: Add the same reference in TS 23.271 in order to keep alignment of Locatoin Continuity in Clause 6.10.3.","secretary_remarks":"Noted in e-mail session","agenda_item_sort_order":78,"ainumber":"9.6.2","ainame":"5GC LoCation Services Phase 3 (eLCS_Ph3)","tdoc_agenda_sort_order":11290,"status":"noted","reservation_date":"2025-01-14 16:05:46","uploaded":"2025-01-14 16:23:40","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.273","crspecversion":"19.1.0","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":664.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500975.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"2, 6.10.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2501178","title":"Reply LS on UE's user plane availability status for LCS-UPP","source":"SA WG2","contact":"Wen Wang","contact-id":75748,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Revision of S2-2500733r00. Approved","agenda_item_sort_order":78,"ainumber":"9.6.2","ainame":"5GC LoCation Services Phase 3 (eLCS_Ph3)","tdoc_agenda_sort_order":11170,"status":"approved","reservation_date":"2025-01-25 09:54:47","uploaded":"2025-01-27 09:03:58","revisionof":"S2-2500733","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"TEI19"},{"winame":" 5G_eLCS_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2500010","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2501178.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]