[{"name":"S2-2509870","title":"LS from RAN WG2: Reply LS on signalling feasibility of dataset and parameter sharing","source":"RAN WG2","contact":"Milos Tesanovic","contact-id":66723,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 would like to thank SA WG2 for their reply-LS on signalling feasibility of dataset and parameter sharing, contents of which are noted. In the reply-LS, SA WG2 asked RAN WG2 about the difference between Option 3 and the other two options, and in particular, how Option 3 (gNB -> OAM\/CN -> UE-side training entity) and Option 2 (CN -> UE-side training entity) are different from the CN entity perspective. RAN WG2 made the assumption in Rel-19 that the NW-side dataset\/model parameter collection entity may reside in the OAM, a CN function, or the gNB - these three options correspond to Options 1\/2\/3 to which the SA WG2 LS refers to and which were provided in Table 1 of LS in R2-2503169. For the two-sided model, a sharing of dataset and model parameters between the NW-side dataset\/model parameter collection entity and the UE-side training entity is envisaged. RAN WG2 did not analyse details of data transfer path involved in each of these options. RAN WG2 believes this is within SA WG2 or SA WG5 remit. RAN WG2 has not discussed the content of the dataset\/model parameters. Moreover, RAN WG2 has not discussed if the difference between the options has any standardization impact, which RAN WG2 assumes is in the scope of SA WG2 or SA WG5. For the data content of dataset\/model parameter, the previous RAN WG1 LS R1-2410922 can be referred to. Regarding the request from SA WG2 for any further information from RAN WG2\/ RAN WG1\/RAN plenary on the requirements, RAN WG2 wishes to inform SA WG2 that RAN WG2 has no new or additional requirements identified at present. 2 Action: RAN WG2 respectfully requests SA WG2 to take the above reply into account in future discussion.","secretary_remarks":"Review after discussing the additional related WT planning. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10170,"status":"noted","reservation_date":"2025-10-23 14:57:36","uploaded":"2025-10-27 05:53:03","revisionof":"","revisedto":"","release":"Rel-20","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG5, SA WG3, RAN WG3, RAN WG1","lsoriginalls":"R2-2507929","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_172_Dallas_2025-11\/Docs\/S2-2509870.zip","group":"S2","meeting":"S2-172","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2509877","title":"LS from SA WG5: Reply LS on specification of dataset and model parameters exchange","source":"SA WG5","contact":" Anonymous","contact-id":4132,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks RAN for the incoming LS on specification of dataset and model parameters exchange. SA WG5 recalls that it has already provided an initial reply on this topic in Rel-19 (S5-254083\/RP-251920 in response to R2-2503169\/S5-253287), confirming that non-OTA approaches involving OAM is feasible subject to further evaluation. Further to the discussion during SA#109, SA WG5 would like to confirm that the investigation of dataset and model parameter exchange, as highlighted by RAN WG2, is part of the ongoing Rel-20 Study on AI\/ML management phase 3. SA WG5 plans to coordinate with SA WG2, RAN WG1 and RAN WG2 on the progress of their investigation and will keep both SA and RAN updated.","secretary_remarks":"Review after discussing the additional related WT planning. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10180,"status":"noted","reservation_date":"2025-10-23 14:57:36","uploaded":"2025-10-27 05:53:03","revisionof":"","revisedto":"","release":"Rel-20","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, TSG RAN, TSG SA","Cc":"RAN WG1, SA WG3, SA WG2","lsoriginalls":"S5-254846","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_172_Dallas_2025-11\/Docs\/S2-2509877.zip","group":"S2","meeting":"S2-172","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2509878","title":"LS from SA WG6: LS on URL for downloading the DC Application list","source":"SA WG6","contact":"Yue Liu","contact-id":80533,"tdoctype":"LS in","for":"Information","abstract":"The DC application profiles related procedures, including downloading on UE and updating on UE are specified in 3GPP TS 23.392 by SA WG6. When the number of DC applications is large, the UE may need to download them via pagination, or search for and download only the specific DC applications requested by the user. Since the selection of DC application is heavily depends on the service policy of MMTel service provider, it is not suitable to leave this issue to implement specific. Therefore, providing a standardized mechanism to search the DC Applications for users is necessary. SA WG6 is studying this use case in FS_MMTel_Ph2_APP as KI#2 (and related sol#1) in Rel-20. To support this use case, the UE would need to modify the URL for downloading the DC application list, e.g., by adding some query parameters. However, the current version of TS 26.114, the URL for downloading the DC application list is described in clause 6.2.10.1 as below: The data channel application accessible at the HTTP root ('\/') URL through a bootstrap data channel describes the graphical user interface and the logic needed to handle any further data channel usage beyond the bootstrap data channel itself. The meaning of the 'authority' (host) part of the URL and consequently the 'Host' HTTP header are not defined, shall be ignored on reception, and shall be set to the empty value by a DCMTSI client in terminal. Based on this description, it appears that all accessible data channel applications need to be downloaded from this URL, and the URL cannot carry parameters. Question 1: Could SA WG4 clarify whether this URL can be modified to carry query parameters to support SA WG6's study on DC application list search? Question 2: If the answer to Question 1 is No, then could SA WG4 update the above clause to support the use case of DC Application list search?","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10060,"status":"noted","reservation_date":"2025-10-23 14:57:36","uploaded":"2025-10-27 14:06:18","revisionof":"","revisedto":"","release":"Rel-20","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"SA WG2","lsoriginalls":"S6-254794","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_172_Dallas_2025-11\/Docs\/S2-2509878.zip","group":"S2","meeting":"S2-172","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2509925","title":"LS from CT WG4: LS on Clarification on 5G VN group","source":"CT WG4","contact":"RONG WANG","contact-id":87346,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 has studied some optimization solutions for UPF data collection in FS_PAIDC_UPF. For 5G VN group, CT WG4 would like to ask SA WG2 the following questions: Q1: Can a UE, that is not member (temporary\/permanently) of any 5G VN group, have an SM subsc","secretary_remarks":"Revision of postponed S2-2508173 from SA WG2-171. Responses drafted in S2-2510055, S2-2510371, S2-2510545. This was postponed.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10070,"status":"postponed","reservation_date":"2025-10-29 14:27:50","uploaded":"2025-10-29 14:45:35","revisionof":"S2-2509847","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG3","lsoriginalls":"C4-253576","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_172_Dallas_2025-11\/Docs\/S2-2509925.zip","group":"S2","meeting":"S2-172","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2509929","title":"LS from SA WG3: LS on business model and architecture for SNPN cellular hotspots","source":"SA WG3","contact":"Charles Eckel","contact-id":96384,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 received an LS from the Wireless Broadband Alliance (S3-221740) on 'Facilitating roaming adoption across 3GPP NPN deployments'. Wireless Broadband Alliance specifies and operates OpenRoaming. OpenRoaming is a cloud federation-based framework that f","secretary_remarks":"Revision of postponed S2-2508184 from SA WG2-171. Response drafted in S2-2510353. Final response in S2-2510353.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10130,"status":"replied to","reservation_date":"2025-10-29 14:27:50","uploaded":"2025-10-29 14:45:35","revisionof":"S2-2509851","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG2","Cc":"","lsoriginalls":"S3-253046","lsreply":"S2-2511233, S2-2511233","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_172_Dallas_2025-11\/Docs\/S2-2509929.zip","group":"S2","meeting":"S2-172","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2510032","title":"Availability of IMS Emergency Services","source":"Nokia, Ericsson","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To enable a more robust emergency service in failure cases, as an implementation option in the UE, the UE is allowed to select another PLMN to obtain emergency services, even if the UE is currently camping on the HPLMN.","secretary_remarks":"Revised to S2-2511148 (withdrawn). This was Postponed.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10220,"status":"postponed","reservation_date":"2025-11-05 03:11:28","uploaded":"2025-11-07 12:53:01","revisionof":"","revisedto":"S2-2511148","release":"Rel-19","crspec":"23.167","crspecversion":"19.1.1","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI19"}],"crnumber":379.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_172_Dallas_2025-11\/Docs\/S2-2510032.zip","group":"S2","meeting":"S2-172","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2510055","title":"[DRAFT] Reply LS on Clarification on 5G VN group","source":"China Mobile","contact":"Dan Wang","contact-id":87155,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on Clarification on 5G VN group","secretary_remarks":"Revision of (Postponed) S2-2508626. Response to S2-2509925. Revised in parallel session to S2-2511232 (withdrawn). This was postponed.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10090,"status":"postponed","reservation_date":"2025-11-05 12:58:48","uploaded":"2025-11-07 14:49:36","revisionof":"S2-2508626","revisedto":"S2-2511232","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_172_Dallas_2025-11\/Docs\/S2-2510055.zip","group":"S2","meeting":"S2-172","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2510173","title":"Discussion about 5G VN Group","source":"China Mobile","contact":"Dan Wang","contact-id":87155,"tdoctype":"discussion","for":"Information","abstract":"Discussion about 5G VN Group","secretary_remarks":"Companies were asked to discuss this and try to come to a common understanding of the issues. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10080,"status":"noted","reservation_date":"2025-11-06 11:24:53","uploaded":"2025-11-07 14:49:36","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_172_Dallas_2025-11\/Docs\/S2-2510173.zip","group":"S2","meeting":"S2-172","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2510209","title":"AUSF Selection with Default Routing Indicator","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The description of the AUSF selection for SUCIs using the default value of the Routing Indicator is completed so that If the SUCI uses null-scheme then the AMF can derive the SUPI from the SUCI and then select the AUSF based on the SU","secretary_remarks":"Revised to S2-2511147.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10190,"status":"revised","reservation_date":"2025-11-06 14:17:56","uploaded":"2025-11-07 21:12:29","revisionof":"","revisedto":"S2-2511147","release":"Rel-19","crspec":"23.501","crspecversion":"19.5.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI19"}],"crnumber":6471.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_172_Dallas_2025-11\/Docs\/S2-2510209.zip","group":"S2","meeting":"S2-172","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.3.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2510353","title":"[DRAFT] Reply LS on business model and architecture for SNPN cellular hotspots","source":"Samsung, Cisco Systems, Nokia","contact":"Sang-Jun Moon","contact-id":30993,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on business model and architecture for SNPN cellular hotspots","secretary_remarks":"Revision of (Unhandled) S2-2509719. Response to S2-2509929. Revised to S2-2511146.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10140,"status":"revised","reservation_date":"2025-11-07 04:12:06","uploaded":"2025-11-07 15:10:17","revisionof":"S2-2509719","revisedto":"S2-2511146","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"eNPN_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_172_Dallas_2025-11\/Docs\/S2-2510353.zip","group":"S2","meeting":"S2-172","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2510371","title":"[DRAFT] Reply LS on Clarification on 5G VN group","source":"Samsung","contact":"Sang-Jun Moon","contact-id":30993,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on Clarification on 5G VN group","secretary_remarks":"Revision of (Unhandled) S2-2508728. Response to S2-2509925. Noted in parallel session","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10110,"status":"noted","reservation_date":"2025-11-07 04:16:34","uploaded":"2025-11-07 15:10:17","revisionof":"S2-2508728","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"GMEC"},{"winame":" FS_PAIDC_UPF"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_172_Dallas_2025-11\/Docs\/S2-2510371.zip","group":"S2","meeting":"S2-172","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2510545","title":"[DRAFT] Reply LS on Clarification on 5G VN group","source":"Nokia","contact":"Georgios Gkellas","contact-id":68310,"tdoctype":"LS out","for":"Approval","abstract":"[Draft] Reply LS on Clarification on 5G VN group","secretary_remarks":"Revision of (Unhandled) S2-2508909. Response to S2-2509925. Noted in parallel session","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10120,"status":"noted","reservation_date":"2025-11-07 09:58:06","uploaded":"2025-11-07 10:02:28","revisionof":"S2-2508909","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"GMEC"},{"winame":" FS_PAIDC_UPF"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_172_Dallas_2025-11\/Docs\/S2-2510545.zip","group":"S2","meeting":"S2-172","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2511146","title":"[DRAFT] Reply LS on business model and architecture for SNPN cellular hotspots","source":"Samsung, Cisco Systems, Nokia","contact":"Sang-Jun Moon","contact-id":30993,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on business model and architecture for SNPN cellular hotspots","secretary_remarks":"Revision of S2-2510353. Revised in parallel session to S2-2511233.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10150,"status":"revised","reservation_date":"2025-11-20 20:06:50","uploaded":"2025-11-24 07:01:14","revisionof":"S2-2510353","revisedto":"S2-2511233","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"eNPN_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_172_Dallas_2025-11\/Docs\/S2-2511146.zip","group":"S2","meeting":"S2-172","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2511147","title":"AUSF\/UDM Selection with Default Routing Indicator","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The description of the AUSF\/UDM selection for SUCIs using the default value of the Routing Indicator is completed so that If the SUCI uses null-scheme then the AMF can derive the SUPI from the SUCI and then select the AUSF\/UDM based on the SUPI. This is already covered in TS 23.003 (clause 2.2B, NOTE 2). If the SUCI uses a protection scheme other than null-scheme, then the AMF selects an AUSF\/UDM instance as follows If AMF discovers a group of AUSF\/UDM instances that explicitly indicates support for the default value of the routing indicator within the NF profile registered in NRF, then the AMF selects one of these instances. This is, the operator can leave the subscriptions for which it has not been possible to provide an appropriate routing indicator in a given AUSF\/UDM group and characterize these AUSF\/UDM instances to support explicitly the default value of the routing indicator. The AMF, then uses the default value of the routing indicator as any other value during AUSF\/UDM selection. Otherwise, the AMF selects any AUSF instance within the home network as defined in the baseline. The proposed updates do not require any stage 3 change. Rev1: Similar updates apply to UDM selection section.","secretary_remarks":"Revision of S2-2510209. Revised in parallel session to S2-2511234.<br\/><br\/>Source modified on 24\/11\/2025. Original source : Ericsson","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10200,"status":"revised","reservation_date":"2025-11-20 20:06:50","uploaded":"2025-11-24 07:01:14","revisionof":"S2-2510209","revisedto":"S2-2511234","release":"Rel-19","crspec":"23.501","crspecversion":"19.5.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI19"}],"crnumber":6471.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_172_Dallas_2025-11\/Docs\/S2-2511147.zip","group":"S2","meeting":"S2-172","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.3.4; 6.3.8","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2511148","title":"Availability of IMS Emergency Services","source":"Nokia, Ericsson","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To enable a more robust emergency service in failure cases, as an implementation option in the UE, the UE is allowed to select another PLMN to obtain emergency services, even if the UE is currently camping on the HPLMN.","secretary_remarks":"Revision of S2-2510032. WITHDRAWN","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10230,"status":"withdrawn","reservation_date":"2025-11-20 20:06:51","uploaded":null,"revisionof":"S2-2510032","revisedto":"","release":"Rel-19","crspec":"23.167","crspecversion":"19.1.1","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI19"}],"crnumber":379.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-172","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2511232","title":"[DRAFT] Reply LS on Clarification on 5G VN group","source":"China Mobile","contact":"Dan Wang","contact-id":87155,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on Clarification on 5G VN group","secretary_remarks":"Revision of S2-2510055. WITHDRAWN","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10100,"status":"withdrawn","reservation_date":"2025-11-20 20:10:02","uploaded":null,"revisionof":"S2-2510055","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-172","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2511233","title":"Reply LS on business model and architecture for SNPN cellular hotspots","source":"SA WG2","contact":"Sang-Jun Moon","contact-id":30993,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on business model and architecture for SNPN cellular hotspots","secretary_remarks":"Revision of S2-2511146. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10160,"status":"approved","reservation_date":"2025-11-20 20:10:02","uploaded":"2025-11-24 07:01:15","revisionof":"S2-2511146","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"eNPN_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2509929","lsto":"SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_172_Dallas_2025-11\/Docs\/S2-2511233.zip","group":"S2","meeting":"S2-172","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2511234","title":"AUSF Selection with Default Routing Indicator","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The description of the AUSF selection for SUCIs using the default value of the Routing Indicator is completed so that If the SUCI uses null-scheme then the AMF can derive the SUPI from the SUCI and then select the AUSF based on the SUPI. This is already covered in TS 23.003 (clause 2.2B, NOTE 2). If the SUCI uses a protection scheme other than null-scheme, then the AMF selects an AUSF instance as follows If AMF discovers a group of AUSF instances that explicitly indicates support for the default value of the routing indicator within the NF profile registered in NRF, then the AMF selects one of these instances. This is, the operator can leave the subscriptions for which it has not been possible to provide an appropriate routing indicator in a given AUSF group and characterize these AUSF instances to support explicitly the default value of the routing indicator. The AMF, then uses the default value of the routing indicator as any other value during AUSF selection. Otherwise, the AMF selects any AUSF instance within the home network as defined in the baseline. The proposed updates do not require any stage 3 change.","secretary_remarks":"Revision of S2-2511147. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10210,"status":"agreed","reservation_date":"2025-11-20 20:10:02","uploaded":"2025-11-24 07:01:15","revisionof":"S2-2511147","revisedto":"","release":"Rel-19","crspec":"23.501","crspecversion":"19.5.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI19"}],"crnumber":6471.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-251334","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_172_Dallas_2025-11\/Docs\/S2-2511234.zip","group":"S2","meeting":"S2-172","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.3.4","crsinpack":null,"crsinpacknumber":0}]