[{"name":"S2-2407394","title":"LS from CT WG4: LS on Clarification on Dual Registration Indication","source":"CT WG4","contact":"Zhijun Li","contact-id":39295,"tdoctype":"LS in","for":"Information","abstract":"CT WG4 has revisited the specification details of dual registration mode support for EPS interworking, and finds some unclarity which needs clarification from CT WG1 and possibly from SA WG2. {. . .} To assist understanding how the dual registration mode actually works, CT WG4 would like to ask the following questions to CT WG1: Q1: Does a UE operating in dual registration mode only indicate the EMM state of EMM-REGISTERED in the initial registration procedure? Or, should the UE also indicate the EMM registration status in periodic registration procedure or mobility registration procedure? Q2: If a UE's registration mode (single\/dual registration mode) is altered due to it turns off the dual registration mode or detaches from EPS, or if a UE is not registered to EPS during the initial registration to 5GS but later on it registers to the EPS, what information will the UE indicate to the AMF and in which procedure?","secretary_remarks":"Revision of postponed S2-2405868 from S2#163. This LS was postponed.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10160,"status":"postponed","reservation_date":"2024-06-26 08:28:38","uploaded":"2024-06-27 13:54:03","revisionof":"S2-2405868","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG2","lsoriginalls":"C4-241547","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2407394.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407399","title":"LS from GSMA OPG: LS on clarifications on consent management","source":"GSMA OPG","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"An activity on privacy management (e.g. how to capture consent from the end-user) is ongoing as part of the current release of OPG: For privacy reasons, a 3rd party application wanting to access end-user-related sensitive information present in the network, requires capturing the consent from the end-user before the application can use that information for a specific purpose. {. . .}","secretary_remarks":"Revision of postponed S2-2405883 from S2#163. Response drafted in S2-2408478. For e-mail approval. Final response in S2-2409440","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10180,"status":"replied to","reservation_date":"2024-06-26 08:28:39","uploaded":"2024-06-27 13:54:03","revisionof":"S2-2405883","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, CT WG4, CT WG3, SA WG6","Cc":"SA WG2, TSG SA","lsoriginalls":"OPG_173_Doc_04","lsreply":"S2-2409440","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2407399.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407402","title":"LS from BBF: Multi-Tenant FWA","source":"BBF","contact":"Lincoln Lavoie","contact-id":39231,"tdoctype":"LS in","for":"Information","abstract":"Dear colleagues, We would like to inform that Broadband Forum has started work on a new specification (WT-507) FWA solution for delivery inside a MDU\/MTU supporting Multi-Tenant Fixed-Wireless Access (MT-FWA), i.e., extending Fixed Wireless Access in Multi-Tenant Buildings or Multi-Dwelling Units. The objective of this work is to utilize 5G Fixed Wireless Access to service multiple customers, utilizing existing in-building infrastructure, supporting multiple subscribers behind a single 5G FWA Modem. We welcome any guidance on 3GPP work, including studies, use cases or requirements, in progress at 3GPP, that may be of relevance to this work. Sincerely, Lincoln Lavoie, Broadband Forum Technical Committee Chair","secretary_remarks":"Revision of postponed S2-2405890 from S2#163. Response drafted in S2-2407606. Final response in S2-2409546","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10220,"status":"replied to","reservation_date":"2024-06-26 08:28:39","uploaded":"2024-06-27 13:54:03","revisionof":"S2-2405890","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG1, SA WG2","Cc":"","lsoriginalls":"LIAISE-654","lsreply":"S2-2409546","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2407402.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407403","title":"LS from ITU-T SG12: LS on contribution about the 'impact of 5G Home Base Routing on conversational Voice Quality'","source":"ITU-T SG12","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"ITU-T Study Group 12 (Performance, QoS and QoE) wishes to inform SA WG2 that, at its meeting in Geneva, 16-25 April 2024, it has received a contribution about the impact of 5G Home Base Routing on conversational Voice Quality. The contribution is shared with 3GPP for information and feedback. ITU-T SG12 kindly requests if SA WG2 can provide any guidance on the following topic: Home Routing plays a pivotal role in optimizing resource utilization, ensuring consistent service quality, enhancing network security, and facilitating billing and management in mobile networks. However, recent observations have revealed significant challenges related to the delay in voice traffic routing to the Home Public Mobile Network (HPMN) with recent 3GPP releases. Specifically, routing delays of up to 320 ms have been identified when routing the voice traffic of a roaming user e.g. from Germany, located in Australia, to a phone number within Australia. This results in a mouth-to-ear delay of up to 520 ms, significantly impacting the quality of voice communication. Furthermore, we note that if in addition a mirrored roaming of the called user takes place in the same call, the delay doubles, exacerbating the issue even further. In light of these challenges, we seek your collaboration. In particular we would like to receive your comments whether this scenario has already been discussed in SA WG2 and if so with which outcome. We trust in your feedback, value your efforts and would appreciate a technical collaboration on this topic The deadline mentioned above would allow us to introduce your feedback into our next SG12 meeting. We again thank SA WG2 for their feedback.","secretary_remarks":"Revision of postponed S2-2405891 from S2#163. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10170,"status":"noted","reservation_date":"2024-06-26 08:28:39","uploaded":"2024-06-27 13:54:03","revisionof":"S2-2405891","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"oLS65","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2407403.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407409","title":"LS from RAN WG3: LS on Indicating Emergency Service Support over NG","source":"RAN WG3","contact":"sen xu","contact-id":83316,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 discussed specification texts specified in clause 5.16.4.1 of TS 23.501 as quoted below. During Registration procedures over 3GPP access in a PLMN, the 5GC includes the Emergency Services Support indicator, valid for the current Registration Area and indicating per RAT that Emergency Services are supported if any of the following conditions is true within the current Registration Area: - the Network is able to support Emergency Services natively over 5GS; - E-UTRA connected to 5GC supports IMS Emergency Services (e.g. voice), and the NG-RAN is able to trigger handover or redirection from NR to E-UTRA connected to 5GC at QoS Flow establishment for IMS Emergency Services (e.g. voice); - NG-RAN is able to trigger handover to EPS at QoS Flow establishment for IMS Emergency Services (e.g. voice); - NG-RAN is able to trigger redirection to EPS at QoS Flow establishment for IMS Emergency Services (e.g. voice); or - NG-RAN is able to trigger 5G SRVCC handover to UTRAN for IMS Emergency Services (i.e. voice). If a certain RAT is restricted for Emergency Services, AMF signals that the corresponding RAT is restricted for Emergency Services Support to the Master RAN Node. This helps assist the Master RAN node determine whether to set up Dual Connectivity for Emergency Services. RAN WG3 found that the above second quoted function specified in TS 23.501 is not supported in TS 38.413 since R15. RAN WG3 has decided that a RAN configuration-based approach applies when some RAT is restricted for emergency service support. Therefore, RAN WG3 does not intend to introduce respective support in TS 38.413. Action: RAN WG3 respectfully asks SA WG2 to take the above into account and consider to align TS 23.501 accordingly","secretary_remarks":"Revision of postponed S2-2406863 from S2#163. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10270,"status":"noted","reservation_date":"2024-06-26 08:28:39","uploaded":"2024-06-27 13:54:03","revisionof":"S2-2406863","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"R3-243933","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2407409.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407417","title":"LS from CT WG1: Reply LS on 5GS missing CBC support for shared networks","source":"CT WG1","contact":"Ivo Sedlacek","contact-id":41880,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 would like to thank SA WG2 for the LS S2-2405210 on '5GS missing CBC support for shared networks'. CT WG1 agreed the attached TS 23.041 CR to provide solution for CBC support for shared networks in 2G, 3G, 4G and 5G 3GPP systems. In order to avoid overlapping requirements, CT WG1 decided to refer to TS 23.251 for solution for CBC support for shared networks in 2G, 3G and 4G. Action: CT WG1 would like to ask SA WG2 to take the above into consideration.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10260,"status":"noted","reservation_date":"2024-06-26 08:28:39","uploaded":"2024-06-28 07:01:36","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG2, RAN WG3, SA WG1. Attachment: C1-243532","lsoriginalls":"C1-243686","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2407417.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407420","title":"LS from CT WG1: Reply LS on Clarification on Dual Registration Indication","source":"CT WG1","contact":"Vivek Gupta","contact-id":91167,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 thanks CT WG4 for their LS (C1-243009 \/ C4-241547) on Clarification on Dual Registration Indication. CT WG1 has discussed the issue and provides the following response to questions from CT WG4. {. .}","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10340,"status":"noted","reservation_date":"2024-06-26 08:28:39","uploaded":"2024-06-28 07:01:36","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"SA WG2","lsoriginalls":"C1-243691","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2407420.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407425","title":"LS from IETF IETF TEAS WG: LS on RFC 9543, 'A Framework for Network Slices in Networks Built from IETF Technologies'","source":"IETF TEAS WG","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"As a follow up to the liaison statement [1] that was posted on 2023-10-09, the IETF TEAS WG [2] would like to inform 3GPP and the SDOs in the Cc list about the publication of a new informational RFC - RFC9543, 'A Framework for Network Slices in Networks Built from IETF Technologies' [3]. This document describes network slicing in the context of networks built from IETF technologies. It establishes the general principles of network slicing in the IETF context. The following is the mailing list where discussions related to this framework take place [4]. Feedback on RFC9543 can be shared directly on the mailing list.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10350,"status":"noted","reservation_date":"2024-06-26 08:28:39","uploaded":"2024-06-28 07:01:36","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3, SA WG5, RAN WG3","Cc":"","lsoriginalls":"liaison-teas-3gpp-framework","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2407425.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407426","title":"LS from IETF IETF TEAS WG: LS on 'A Realization of Network Slices for 5G Networks Using Current IP\/MPLS Technologies'","source":"IETF TEAS WG","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"As a follow up to the liaison statement [1] that was posted on 2023-10-09, the IETF TEAS WG [2] would like to inform 3GPP about the progress of 'A Realization of IETF Network Slices for 5G Networks Using Current IP\/MPLS Technologies' [3], an informational document that has completed Working Group Last Call. This document describes a Network Slice realization model for IP\/MPLS networks with a focus on the Transport Network fulfilling 5G slicing connectivity service objectives. The realization model reuses many building blocks currently commonly used in service provider networks. In addition to stating that the reader should refer to 'TS 23.501: System architecture for the 5G System (5GS)' [4] for a definitive description of 3GPP network architectures, the document also includes an Appendix [5] that provides a brief 5G overview for the reader's convenience. Action: The TEAS WG would like to request 3GPP to review the document and provide confirmation that the brief 5G overview included in the Appendix is accurate. The TEAS WG would like to request that feedback on this is provided in an LS by the deadline. The TEAS WG also encourages the use of the TEAS WG mailing list [6] for individuals to send comments, raise concerns and seek clarification on the document.","secretary_remarks":"Response drafted in S2-2407889. Final response in S2-2408691","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10360,"status":"replied to","reservation_date":"2024-06-26 08:28:39","uploaded":"2024-06-28 07:01:36","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3, SA WG5, RAN WG3","Cc":"","lsoriginalls":"liaison-teas-realization","lsreply":"S2-2408691","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2407426.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407431","title":"LS from TSG RAN: LS on Avoiding Cross-TSG TEI","source":"TSG RAN","contact":"Hans Van der Veen","contact-id":62851,"tdoctype":"LS in","for":"Action","abstract":"TSG RAN has had an approved TEI handling procedure since March 2021 (RAN#91e). The latest approved version is RP-240858 (attached). The main purpose of this procedure is to improve transparency and traceability of TEI work. In line with previous inter-TSG agreement, it is not possible to trigger work in RAN WGs via TEI CRs coming from TSG SA\/CT or SA\/CT WGs. The same applies for the reverse direction. However, on several occasions in the recent past, RAN WGs received LSs from a WG of another TSG, with a request to introduce changes, based on an attached TEIxx CR. Please note that if SA (WGs) or CT (WGs) need RAN (WGs) to undertake work, a SA (WGs) or CT (WGs) Work Item with a Work Item Description (that is not only TEIxx) is required. Please note that MCC has given guidance that the receiving RAN groups should then use: either - the same SA\/CT WI code that was in the incoming LS; - the SA\/CT WI code and a RAN WI code related to that. Action: TSG RAN asks TSG CT (WGs) and TSG SA (WGs) to use an appropriate SA (WGs) or CT (WGs) WI code other than 'TEIxx' when asking RAN (WGs) to undertake any necessary work required.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10390,"status":"noted","reservation_date":"2024-06-26 08:28:39","uploaded":"2024-06-28 07:01:28","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG CT, CT WG1, CT WG3, CT WG4, CT WG6, TSG SA, SA WG1, SA WG2, SA WG3, SA WG4, SA WG5, SA WG6","Cc":"RAN WG1, RAN WG2, RAN WG3, RAN WG4, RAN WG5","lsoriginalls":"RP-241686","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2407431.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407432","title":"LS from SA WG1: Reply LS on clarification on mobile metaverse services","source":"SA WG1","contact":"Alice Li","contact-id":88646,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 thanks SA WG3 for their LS in S3-241497 to request clarification on mobile metaverse services. Considering the related SA WG1 normative work on Mobile Metaverse Services (TS 22.156) following the feasibility study (TR 22.856 'Feasibility Study on Localized Mobile Metaverse Services'), SA WG1 would like to provide the following answers to the questions raised by SA WG3. SA WG1 has also considered the input from SA WG6 in S6-242734 as part of this reply. {. .}","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10040,"status":"noted","reservation_date":"2024-06-26 08:28:39","uploaded":"2024-06-28 07:01:29","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, SA WG6","Cc":"SA WG2, SA WG4","lsoriginalls":"S1-241351","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2407432.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407433","title":"LS from SA WG5: Reply LS from SA5 on Updated AECC Publications for Future Connected Vehicle Services","source":"SA WG5","contact":"Jean-Michel CORNILY","contact-id":96535,"tdoctype":"LS in","for":"Information","abstract":"The Automotive Edge Computing Consortium (AECC) sent the LS on Updated AECC Publications for Future Connected Vehicle Services to TSG SA while CCing SA WG1, SA WG2, SA WG5 and SA WG6. As a result of discussing the AECC LS at TSG SA#103 (March 2024), WGs were asked to coordinate any replies to this AECC LS through TSG SA rather than responding individually. Therefore, SA WG5 would like to provide feedback on the AECC LS to TSG SA as below: {. .}","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10050,"status":"noted","reservation_date":"2024-06-26 08:28:39","uploaded":"2024-06-28 07:01:29","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG1, SA WG2, SA WG6","lsoriginalls":"S5-243069","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2407433.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407435","title":"LS from SA WG5: LS on GSMA OPG PRDs publication","source":"SA WG5","contact":"Maryse Gardella","contact-id":68914,"tdoctype":"LS in","for":"Action","abstract":"The GSMA Operator Platform Group (OPG) sent the LS on GSMA OPG PRDs publication to SA WG2, SA WG5 and SA WG6, ETSI ISG MEC and ETSI IGS NFV, with CC to TSG SA and SA WG3. Therefore, SA WG5 would like to provide feedback on the GSMA OPG LS to TSG SA as below: {. .}","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10400,"status":"noted","reservation_date":"2024-06-26 08:28:40","uploaded":"2024-06-28 07:01:30","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG2, SA WG3, SA WG6","lsoriginalls":"S5-243436","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2407435.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407436","title":"LS from TSG SA: Reply LS on GSMA OPG PRDs publication","source":"TSG SA","contact":"Lan Zou","contact-id":35534,"tdoctype":"LS in","for":"Information","abstract":"TSG SA thanks GSMA OPG for providing the publication of new documents and recent release of GSMA PRDs. TSG SA would like to convey the following reply from SA WG5: - The newly available GSMA PRD OPG.07 Southbound Interface Charging Function APIs version 1.0 is in particular interest of SA WG5 Charging, and will be taken into consideration for further exchanges related to charging aspects. - For GSMA PRD OPG.08 Southbound Interface for Operation, Administration and Maintenance APIs, SA WG5 suggests to use Rel-18 version of TS 28.532 (reference [6] in the PRD) for stage 2 (sections 2.1.3.1-2.1.3.8 in the PRD) instead of using Rel-17. Please note that Rel-18 version of TS 28.532 (reference [6] in the PRD) is already used for stage 3 reference in PRD (section 2.1.4).","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":"2024-06-26 08:28:40","uploaded":"2024-06-28 07:01:31","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA OPG","Cc":"SA WG2, SA WG3, SA WG5, SA WG6, ETSI ISG MEC, ETSI ISG NFV","lsoriginalls":"SP-240946","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2407436.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407437","title":"LS from TSG SA: Reply LS on Updated AECC Publications for Future Connected Vehicle Services","source":"TSG SA","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"LS in","for":"Information","abstract":"TSG SA thanks AECC regarding the LS on Updated AECC Publications for Future Connected Vehicle Services. TSG SA would like to provide feedback in Annexes below.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10070,"status":"noted","reservation_date":"2024-06-26 08:28:40","uploaded":"2024-06-28 07:01:33","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"AECC","Cc":"SA WG1, SA WG2, SA WG5, SA WG6","lsoriginalls":"SP-240948","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2407437.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407438","title":"LS from TSG SA: Reply LS on alignment of eCall over IMS with CEN","source":"TSG SA","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS in","for":"Information","abstract":"TSG SA has discussed the LS from TSG CT on alignment of eCall over IMS with CEN (SP-240941\/CP-241307). TSG SA agreed that CT WG1 should take the lead on analysing the gaps in the LS from CEN (in SP-240522). Depending on this analysis by CT WG1, TSG SA will determine which SA WGs in addition to SA WG2 will need to be involved, and these SA WGs need to review CT WG1 provided results. TSG SA will decide when these SA WGs need to review the CT WG1 provided results. TSG SA will also decide when SA WGs need to start new Rel-19 Work Item(s) for this topic. As indicated above, before concluding the study, CT WG1 should consult with SA WG2 on the SA WG2 stage 2 specification impacts and consult with SA for final decision on how to proceed with normative work.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10080,"status":"noted","reservation_date":"2024-06-26 08:28:40","uploaded":"2024-06-28 07:01:34","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG1, SA WG2, TSG CT","lsoriginalls":"SP-240973","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2407438.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407439","title":"LS from TSG SA: Reply LS on the stage 2 aspects of MINT_Ph2","source":"TSG SA","contact":"Biao Long","contact-id":65732,"tdoctype":"LS in","for":"Information","abstract":"TSG SA thanks CT WG1 for the LS (SP-240538 \/ C1-242675) on the stage 2 aspects of MINT_Ph2. TSG SA has considered the input from SA WG2 (SP-240558 \/ S2-2407313) and discussed the matter in their SA#104 meeting. TSG SA kindly asks CT WG1 to perform a study for MINT_Ph2_EPS. The context of the proposed scope differs compared to the Rel-17 MINT study in overall system aspects in that 4G\/EPS is now the target system. {. .}","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10090,"status":"noted","reservation_date":"2024-06-26 08:28:40","uploaded":"2024-06-28 07:01:35","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, SA WG1","Cc":"SA WG2, TSG CT, CT WG4","lsoriginalls":"SP-241013","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2407439.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407440","title":"LS from TSG SA: Reply LS on data plane control by roaming hubs","source":"TSG SA","contact":"Yannick Lair","contact-id":76350,"tdoctype":"LS in","for":"Information","abstract":"TSG SA thanks GSMA 5GMRR for their LS on data plane control by roaming hubs. TSG SA reviewed the requirements listed in the LS from GSMA 5GMRR and would like to inform GSMA 5GMRR that there was no corresponding work in 3GPP WGs in Rel-18 and that there is currently no corresponding planned work in 3GPP WGs for Rel-19. TSG SA would like to remind GSMA 5GMRR that work in 3GPP is based on direct contributions made by 3GPP members. TSG SA expects GSMA 5GMRR to document appropriate architecture and service flows for data plane control by roaming hubs in GSMA's roaming specifications.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10100,"status":"noted","reservation_date":"2024-06-26 08:28:40","uploaded":"2024-06-28 07:01:35","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA 5GMRR","Cc":"SA WG1, SA WG2, SA WG3, SA WG5, CT WG4","lsoriginalls":"SP-241014","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2407440.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407443","title":"LS from GSMA URSWPI: LS to 3GPP on publication of NG.141","source":"GSMA URSWPI","contact":"Ralf Keller","contact-id":11142,"tdoctype":"LS in","for":"Information","abstract":"GSMA URSPWI would like to inform 3GPP about the publication of the GSMA PRD NG.141 'URSP Guidelines' on https:\/\/www.gsma.com\/. GSMA has decided to move the definition of traffic categories from GSMA PRD NG.135 to section 3.8 of GSMA PRD NG.141, and that the further maintenance of the definitions will be done in GSMA PRD NG.141.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10110,"status":"noted","reservation_date":"2024-06-26 08:28:40","uploaded":"2024-06-28 07:01:36","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, SA WG2","Cc":"","lsoriginalls":"URSPWI 09_002r2","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2407443.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407450","title":"LS from SA WG3-LI: Reply LS on LI considerations for TR 33.757","source":"SA WG3-LI","contact":"Mark Canterbury","contact-id":70749,"tdoctype":"LS in","for":"Information","abstract":"SA WG3-LI kindly thanks SA WG3 for their LS, and for adding LI considerations to TR 33.757. Regarding TR 33.757 Key Issue #3 (SUPI privacy), SA WG3-LI is grateful for SA WG3's clarifications (in particular that for the purposes of this study it is assumed that both the hosting PLMN and the hosted NPN belong to the same regulatory domain) and for undertaking to ensure that either SUPI-based LI is supported or that the feature is optional to deploy. Regarding TR 33.757 Key Issue #1 (Security for dedicated UPF interacting with PLMN through N4 interface), SA WG3-LI notes following question: Question 1: SA WG3 would like to ask SA WG3-LI to clarify what the detailed issues and specific impacts the proxy related mechanisms may bring for the LI_T2\/LI_T3 interfaces. SA WG3-LI is pleased to attempt to provide the necessary clarifications below. {. . .}","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10120,"status":"noted","reservation_date":"2024-06-26 08:28:40","uploaded":"2024-07-29 07:15:17","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG2","lsoriginalls":"S3i240502","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2407450.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407451","title":"LS from ITU-T SG2: LS\/r on initiation of new work item ITU-T Q.IEM_arch_req 'Reference architecture and signalling requirements for interactive emergency messaging through mobile network' and ITU-T Q.Req_Frame_RRDN, 'Requirements and framework for rapid r","source":"ITU-T SG2","contact":"Philip Rushton","contact-id":91211,"tdoctype":"LS in","for":"Information","abstract":"This Liaison Statement responds to a liaison from ITU-T SG11 (SG11-LS173) outlining the activity within ITU-T SG2 in emergency communications.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10130,"status":"noted","reservation_date":"2024-06-26 08:28:40","uploaded":"2024-07-29 07:15:17","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG11. SA WG1, SA WG2, ETSI-EMTEL, GSMA","Cc":"","lsoriginalls":"SG2-LS105","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2407451.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407453","title":"LS from GSMA TSG: Newly published data channel GSMA PRD TS.66","source":"GSMA TSG","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"The IMS data channel has been introduced in 3GPP Release-16 TS 26.114 and provides the ability to establish a real-time communication path between two endpoints to exchange any form of data and enables new types of IMS interactive services. {. .} Action: GSMA would like to ask feedback on whether work is planned or ongoing to develop security controls for IMS Data Channel (and more generally for new type of communication services).","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10410,"status":"noted","reservation_date":"2024-06-26 08:28:40","uploaded":"2024-07-30 11:36:32","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3, SA WG4, SA WG6, RAN WG5","Cc":"TSG SA, SA WG1, TSG CT, CT WG1, CT WG3, CT WG4","lsoriginalls":"TSG56_059v3","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2407453.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407454","title":"LS from ETSI TC EMTEL: Reply LS to ITU-T SG11 on initiation of new work item ITU-T Q.IEM_arch_req","source":"ETSI TC EMTEL","contact":"Peter Sanders","contact-id":33850,"tdoctype":"LS in","for":"Information","abstract":"TC EMTEL thanks ITU-T SG11 for its LS on the reference architecture and signalling requirements for interactive emergency messaging through mobile network. TC EMTEL would like to provide the following information for your consideration in the development of signalling requirements: - The Delivery Notification in SMS confirms that the message has been successfully delivered to the mobile device; it does not confirm that the user has read the message. - A Delivery Notification, as that exists for SMS, does not exist for CB. CB is a broadcast delivery mechanism that delivers the message concurrently to possibly millions of mobile devices. All devices confirming successful delivery of a message delivered via CB may overload the network. - If a Delivery Notification mechanism for CB would exist, then it would confirm successful delivery to the mobile device, but if Device-Based Geo-Fencing is used and the mobile device is outside the alert area, the message is not presented to the user. - The Interactive emergency messaging described includes Emergency alert, Alert acknowledgement, and Alert Coverage Feedback. But it is important to understand that there is no provision in the current CB standards for collecting information on the acknowledgement of messages. Any changes to CB standards that would enable acknowledgement would have significant privacy issues, specially from UE based location that may be transmitted to authorities, and performance implications in disaster areas with high density of population. - SMS allows the user to respond interactively by sending an SMS in return or dialling the number of the sender. The CB message text may contain a number or a URL that the user can click to respond interactively. - Cell Broadcast messages are sent over the Control Plane in System Information Blocks (SIB) that can carry only a limited amount of data, which is not enough to carry for example image files or videos.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10140,"status":"noted","reservation_date":"2024-06-26 08:28:40","uploaded":"2024-08-01 13:12:51","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG1","Cc":"SA WG1, SA WG2, GSMA, ITU-T SG2","lsoriginalls":"EMTEL(24)000034r4","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2407454.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407456","title":"LS from SA WG6: LS on collaboration and alignment of 3GPP defined CAPIF with GSMA Open Gateway","source":"SA WG6","contact":"Yanmei Yang","contact-id":37039,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 thanks OGW TS for the reply LS in S6a240005. SA WG6 would like to provide more clarification about for the following content mentioned in the reply LS. {. . .} SA WG6 would like to ask GSMA OGW TG to evaluate the usage of CAPIF in their work and provide any feedback on the gaps, if identified. SA WG6 is continuing to investigate more such features that might be of relevance to GSMA OGWTS and SA WG6 would be sharing them in subsequent meetings","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10150,"status":"noted","reservation_date":"2024-04-07 07:14:01","uploaded":"2024-08-02 08:15:56","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA OGWTS","Cc":"GSMA OPG, OPAG, TSG SA, SA WG2, SA WG5, TSG CT","lsoriginalls":"S6a240333","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2407456.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407552","title":"Lack of indication of Emergency Service Support over NG","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Aligns with stage-3 regarding the restriction of specific RAT for Emergency Services based on a configuration approach","secretary_remarks":"Revised, merging S2-2408113, to S2-2408689.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10280,"status":"revised","reservation_date":"2024-07-19 10:34:10","uploaded":"2024-07-24 14:14:19","revisionof":"","revisedto":"S2-2408689","release":"Rel-18","crspec":"23.501","crspecversion":"18.6.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI18"}],"crnumber":5418.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2407552.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407553","title":"Lack of indication of Emergency Service Support over NG","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Rel-19 mirror CR: Summary of change: Aligns with stage-3 regarding the restriction of specific RAT for Emergency Services based on a configuration approach","secretary_remarks":"Revised, merging S2-2408114, to S2-2408690.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10300,"status":"revised","reservation_date":"2024-07-19 10:36:57","uploaded":"2024-07-24 14:14:19","revisionof":"","revisedto":"S2-2408690","release":"Rel-19","crspec":"23.501","crspecversion":"19.0.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI18"}],"crnumber":5419.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2407553.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"5.16.4.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407606","title":"[DRAFT] LS on Multi-Tenant FWA","source":"Nokia","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"LS on Multi-Tenant FWA","secretary_remarks":"Response to S2-2407402. Revised to S2-2408688.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10230,"status":"revised","reservation_date":"2024-01-08 18:06:47","uploaded":"2024-08-09 09:53:04","revisionof":"","revisedto":"S2-2408688","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"BBF","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2407606.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407792","title":"Correction on MSISDN exposure","source":"Samsung, AT&T","contact":"Hyesung Kim","contact-id":83054,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the text related to MSISDN exposure in clause 5.20","secretary_remarks":"This CR was agreed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10430,"status":"agreed","reservation_date":"2024-08-08 06:33:44","uploaded":"2024-08-09 07:01:39","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.501","crspecversion":"18.6.0","workitem":[{"winame":"EDGEAPP"},{"winame":" TEI18"}],"crnumber":5458.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-241261","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2407792.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.20 ","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407793","title":"Correction on MSISDN exposure","source":"Samsung, AT&T","contact":"Hyesung Kim","contact-id":83054,"tdoctype":"CR","for":"Approval","abstract":"Rel-19 mirror CR: Summary of change: Update the text related to MSISDN exposure in clause 5.20","secretary_remarks":"This CR was agreed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10440,"status":"agreed","reservation_date":"2024-08-08 06:34:47","uploaded":"2024-08-09 07:01:39","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.501","crspecversion":"19.0.0","workitem":[{"winame":"EDGEAPP"},{"winame":" TEI18"}],"crnumber":5459.0,"crrevision":"","crcategory":"A","tsg_crp":"SP-241261","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2407793.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.20","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407889","title":"[DRAFT] LS Reply on 'A Realization of Network Slices for 5G Networks Using Current IP\/MPLS Technologies'","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"It is proposed to reply the LS on 'A Realization of Network Slices for 5G Networks Using Current IP\/MPLS Technologies'","secretary_remarks":"Response to S2-2407426. Revised to S2-2408691.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10370,"status":"revised","reservation_date":"2024-08-08 15:03:52","uploaded":"2024-08-09 16:39:56","revisionof":"","revisedto":"S2-2408691","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA","Cc":"SA WG3, SA WG5, RAN WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2407889.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2408113","title":"Emergency service supported in NG-RAN","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Certain RAT is restricted for emertgency service via configuration.","secretary_remarks":"Merged into S2-2408689","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10320,"status":"merged","reservation_date":"2024-09-08 05:32:55","uploaded":"2024-08-09 15:11:35","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.501","crspecversion":"18.6.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI18"}],"crnumber":5529.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2408113.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.16.4.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2408114","title":"Emergency service supported in NG-RAN","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Rel-19 mirror CR: Summary of change: Certain RAT is restricted for emertgency service via configuration.","secretary_remarks":"Merged into S2-2408690","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10330,"status":"merged","reservation_date":"2024-09-08 05:33:13","uploaded":"2024-08-09 15:11:35","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.501","crspecversion":"19.0.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI18"}],"crnumber":5530.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2408114.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.16.4.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2408478","title":"[DRAFT] Reply LS on clarifications on consent management","source":"Samsung","contact":"Hyesung Kim","contact-id":83054,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on clarifications on consent management","secretary_remarks":"Response to S2-2407399. Revised to S2-2408687.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10190,"status":"revised","reservation_date":"2024-09-08 13:48:10","uploaded":"2024-08-09 14:03:53","revisionof":"","revisedto":"S2-2408687","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG3, SA WG6, CT WG3, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2408478.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2408687","title":"[DRAFT] Reply LS on clarifications on consent management","source":"Samsung","contact":"Hyesung Kim","contact-id":83054,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on clarifications on consent management","secretary_remarks":"Revision of S2-2408478. Revised to S2-2409545.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10200,"status":"revised","reservation_date":"2024-08-25 18:29:46","uploaded":"2024-08-25 18:31:06","revisionof":"S2-2408478","revisedto":"S2-2409545","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG3, SA WG6, CT WG3, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2408687.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2408688","title":"[DRAFT] LS on Multi-Tenant FWA","source":"Nokia","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"LS on Multi-Tenant FWA","secretary_remarks":"Revision of S2-2407606. Revised to S2-2409546.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10240,"status":"revised","reservation_date":"2024-08-25 18:29:47","uploaded":"2024-08-25 18:31:06","revisionof":"S2-2407606","revisedto":"S2-2409546","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"BBF","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2408688.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2408689","title":"Lack of indication of Emergency Service Support over NG","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Aligns with stage-3 regarding the restriction of specific RAT for Emergency Services based on a configuration approach","secretary_remarks":"Revision of S2-2407552, merging S2-2408113. This CR was agreed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10300,"status":"agreed","reservation_date":"2024-08-25 18:29:47","uploaded":"2024-08-25 18:31:06","revisionof":"S2-2407552","revisedto":"","release":"Rel-18","crspec":"23.501","crspecversion":"18.6.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI18"}],"crnumber":5418.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-241278","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2408689.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2408690","title":"Lack of indication of Emergency Service Support over NG","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Rel-19 mirror CR: Summary of change: Aligns with stage-3 regarding the restriction of specific RAT for Emergency Services based on a configuration approach","secretary_remarks":"Revision of S2-2407553, merging S2-2408114. Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10310,"status":"postponed","reservation_date":"2024-08-25 18:29:49","uploaded":"2024-08-25 18:31:06","revisionof":"S2-2407553","revisedto":"SP-241304","release":"Rel-19","crspec":"23.501","crspecversion":"19.0.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI18"}],"crnumber":5419.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2408690.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2408691","title":"[DRAFT] LS Reply on 'A Realization of Network Slices for 5G Networks Using Current IP\/MPLS Technologies'","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"It is proposed to reply the LS on 'A Realization of Network Slices for 5G Networks Using Current IP\/MPLS Technologies'","secretary_remarks":"Revision of S2-2407889. This LS OUT was approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10380,"status":"approved","reservation_date":"2024-08-25 18:29:50","uploaded":"2024-08-25 18:31:06","revisionof":"S2-2407889","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2407426","lsto":"SA","Cc":"SA WG3, SA WG5, RAN WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2408691.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409440","title":"Reply LS on clarifications on consent management","source":"SA WG2","contact":"Hyesung Kim","contact-id":83054,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on clarifications on consent management","secretary_remarks":"Revision of S2-2409545r07. This LS OUT was e-mail approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10220,"status":"approved","reservation_date":"2024-08-25 18:37:33","uploaded":"2024-08-31 06:45:08","revisionof":"S2-2409545","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2407399","lsto":"TSG SA","Cc":"SA WG3, SA WG6, CT WG3, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2409440.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409545","title":"[DRAFT] Reply LS on clarifications on consent management","source":"Samsung","contact":"Hyesung Kim","contact-id":83054,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on clarifications on consent management","secretary_remarks":"Revision of S2-2408687. For e-mail approval. r07 agreed. Revised to S2-2409440.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10210,"status":"revised","reservation_date":"2024-08-25 18:38:12","uploaded":"2024-08-25 18:41:14","revisionof":"S2-2408687","revisedto":"S2-2409440","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG3, SA WG6, CT WG3, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2409545.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409546","title":"LS on Multi-Tenant FWA","source":"SA WG2","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"LS on Multi-Tenant FWA","secretary_remarks":"Revision of S2-2408688. This LS OUT was approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10250,"status":"approved","reservation_date":"2024-08-25 18:38:12","uploaded":"2024-08-25 18:41:14","revisionof":"S2-2408688","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2407402","lsto":"BBF","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_164_Maastricht_2024-08\/Docs\/S2-2409546.zip","group":"S2","meeting":"S2-164","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]