[{"name":"S2-2409575","title":"LS from ITU-T SG13: LS on consent of draft new Recommendation ITU-T Y.3144 (ex.Y.IMT2020-DCN) 'Future networks including IMT-2020 - Requirements and functional architecture of distributed core network'","source":"ITU-T SG13","contact":"Marco Carugi","contact-id":31658,"tdoctype":"LS in","for":"Information","abstract":"This liaison statement informs about the consent of new Recommendation ITU-T Y.3144 (ex.Y.IMT2020-DCN) 'Future networks including IMT-2020 - Requirements and functional architecture of distributed core network'.","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-09-23 09:35:13","uploaded":"2024-09-23 10:06:21","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG2, ITU-T SG11, ITU-T SG17, ITU-R WP 5D, SA WG1, SA WG2, SA WG5","Cc":"","lsoriginalls":"SG13-LS212","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2409575.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409576","title":"LS from ITU-T SG13: LS on initiation of new work item ITU-T Y.NSF 'Requirements and framework of network slicing federation in IMT-2020 networks and beyond'","source":"ITU-T SG13","contact":"Yushuang Hu","contact-id":96973,"tdoctype":"LS in","for":"Information","abstract":"This liaison statement informs about the initiation of new work item ITU-T Y.NSF 'Requirements and framework of network slicing federation in IMT-2020 networks and beyond'","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-09-23 09:35:13","uploaded":"2024-09-23 10:06:21","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG2, ITU-T SG11, SA WG2, SA WG5","Cc":"","lsoriginalls":"SG13-LS223","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2409576.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409577","title":"LS from ITU-T SG13: LS on consent of draft new Recommendation ITU-T Y.3163 (ex.Y.NAEC) 'Network accelerating for edge computing in IMT-2020 networks and beyond'","source":"ITU-T SG13","contact":"Yushuang Hu","contact-id":96973,"tdoctype":"LS in","for":"Information","abstract":"This liaison statement informs about the progress of new Recommendation ITU-T Y.3163 (ex.Y.NAEC) 'Network accelerating for edge computing in IMT-2020 networks and beyond'","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-09-23 09:35:13","uploaded":"2024-09-23 10:06:21","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG2, SG11, ETSI GS NFV, SA WG2, SA WG5, SA WG6","Cc":"","lsoriginalls":"SG13-LS233","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2409577.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409578","title":"LS from TSG SA: Reply LS on Newly published data channel GSMA PRD TS.66","source":"TSG SA","contact":"Atle Monrad","contact-id":79349,"tdoctype":"LS in","for":"Information","abstract":"The IMS data channel was 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. Related with this, 3GPP has received an LS from GSMA. GSMA Networks Group (NG) and GSMA Terminal Steering Group (TSG) have worked on the data channel related aspects and during the years 2021-2023 GSMA Networks Group (NG) has published two documents: GSMA PRD NG.134 - IMS Data Channel and GSMA NG.129 - IMS Data Channel White Paper. This LS asks a number of questions to this feature, and below is a consolidated reply from TSG SA to the questions targeted for the SA WGs. {. . .}. Action: TSG SA kindly requests GSMA TSG to consider the above feedback.","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-09-23 09:35:13","uploaded":"2024-09-23 10:06:21","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA\u00a0TSG","Cc":"SA WG2, SA WG3, SA WG4, SA WG6, RAN WG5, SA WG1, TSG CT, CT WG1, CT WG3, CT WG4","lsoriginalls":"SP-241404","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2409578.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409579","title":"LS from TSG SA: LS on maintaining specification consistency between GSMA and 3GPP on 5G roaming over roaming intermediaries","source":"TSG SA","contact":"Malla Reddy Sama","contact-id":65885,"tdoctype":"LS in","for":"Information","abstract":"TSG SA would like to emphasise the importance of maintaining consistency between GSMA and 3GPP specifications on 5G roaming over roaming intermediaries for operators and the ecosystems. It is TSG SA's understanding that (a) Prior to the formation of 5GMRR, GSMA defined the requirement of end-to-end protection of signalling messages between VPLMN and HPLMN in 5G, based on which SA WG3 specified and mandated the use of the application layer security solution PRINS for 5G roaming over roaming intermediaries; and (b) for 5G, GSMA specifies deployment options and models, as well as the interconnect architecture, while all specification of network function and SEPP behaviour is done within 3GPP. 3GPP security specifications provide a mechanism to fulfil the security requirements provided by GSMA. TSG SA would like to point out that certain behaviours of interconnect nodes may influence the functionality and behaviour of network functions. In order to ensure compatibility of the ongoing 5G development in 3GPP with the deployment options and models defined by the GSMA, it is necessary that the behaviour of the intermediaries is well-defined, specified and aligned with the behaviour of the network functions. 3GPP specified an application layer security solution, namely PRINS, for 5G roaming over roaming intermediaries in Release 15, based on the requirements from GSMA on the end-to-end signalling security between HPLMN and VPLMN. While GSMA 5GMRR maintains that such end-to-end signalling security is its ultimate objective, it recently informed 3GPP that it has developed another type of solution for 5G roaming, so called 'hop-by-hop TLS'. Such hop-by-hop solution does not comply with TS 33.501 and does not meet the end-to-end security requirements for 5G roaming (see SP-241340), which mandates application layer end-to-end security using PRINS for roaming over roaming intermediaries. TSG SA kindly asks GSMA 5GMRR and its member companies to work closely in and with the relevant 3GPP groups, especially SA WG2, SA WG3, and CT WG4 to avoid market fragmentation and incompatibilities.","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-09-23 09:35:13","uploaded":"2024-09-23 10:06:21","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA 5GMRR, GSMA NRG, GSMA NG","Cc":"SA WG1, SA WG2, SA WG3, SA WG5, CT WG4","lsoriginalls":"SP-241405","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2409579.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409580","title":"Reply LS on Multi-Tenant FWA","source":"TSG SA","contact":"Yannick Lair","contact-id":76350,"tdoctype":"LS in","for":"Information","abstract":"TSG SA thanks BBF for their LS on Multi-Tenant FWA (BBF (LIAISE-654)). TSG SA have discussed it and would like to provide the following feedback: SA WG2 has worked on FWA as part of Wireless and Wireline Convergence for the 5G system architecture, as specified in 3GPP TS 23.316, but has not studied yet the Multi-Tenant FWA aspects raised by BBF LS. TSG SA welcome BBF work and inputs in this area, noting though that any consequent 3GPP work would be subject to the approval of a SA WG2 Work Item for a release that could, at the earliest, be Release 20.","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-09-23 09:35:13","uploaded":"2024-09-23 10:06:21","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"BBF","Cc":"SA WG2, SA WG1","lsoriginalls":"SP-241418","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2409580.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409582","title":"Reply LS on CEN's requirements for eCall over IMS","source":"TSG SA","contact":"Alessio Casati","contact-id":82456,"tdoctype":"LS in","for":"Action","abstract":"TSG SA thanks CT WG1 for their LS reply analyzing the gaps in the LS from CEN (in SP-240522) and for providing their findings gathered during their discussion. TSG SA would like to provide the following answers to the finding provided by CT WG1. {. . .}. Action: TSG SA politely ask SA WG2 to provide answer to Question 4 from CT WG1 and any feedback to Question 6 from CT WG1. Action: TSG SA kindly propose SA WG1 and SA WG2 to discuss Rel-19 impacts to address cases #1 to #5.","secretary_remarks":"Responses drafted in S2-2410311, S2-2410587. Final response in S2-2411246","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10210,"status":"replied to","reservation_date":"2024-09-23 09:35:13","uploaded":"2024-09-23 10:06:21","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG1, CT WG1","Cc":"RAN WG5, SA WG3, TSG CT","lsoriginalls":"SP-241421","lsreply":"S2-2411246","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2409582.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409583","title":"LS from TSG SA: LS on alignment of eCall over IMS with CEN","source":"TSG SA","contact":"Xiaobao Chen","contact-id":13274,"tdoctype":"LS in","for":"Information","abstract":"TSG SA would like to inform CEN TC 278 WG 15 of the progress of the work in CT WG1 Working Group in relation to the LS from CEN on Next Generation eCall. TSG CT has approved a work item and the necessary changes on the relevant specifications. There is still ongoing work in 3GPP working groups. Initial finding on CEN Case #1: test call is a normal IMS call based on CEN requirements. CT WG1 considered that using dedicated URNs can work. However, as the test call is executed as a normal IMS call, then in a home routed scenario, the home P-CSCF (possibly located outside of local regulation) need to be profiled to recognise that the normal call is actually to be treated as a test emergency call else, for example, the MSD transfer would not be possible or allowed.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10230,"status":"noted","reservation_date":"2024-09-23 09:35:13","uploaded":"2024-09-23 10:06:21","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CEN TC 278 WG 15","Cc":"SA WG2, CT WG1","lsoriginalls":"SP-241423","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2409583.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409585","title":"LS from CT WG1: Reporting back on CENs requirements for eCall over IMS","source":"CT WG1","contact":"ChenHo CHIN","contact-id":80545,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 thanks TSG SA for the LS (SP-240973\/C1-244033) tasking CT WG1 to analyse the gaps in our TSes to meet CEN's requirements in CEN's case #1 to #9 and communicate back to SA (cc to SA WG1 and SA WG2) its findings. CT WG1 understands that CT WG1 leaves up to TSG SA the 'final decision on how to proceed with normative work'. {. . .}","secretary_remarks":"Response drafted in S2-2410587. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10220,"status":"noted","reservation_date":"2024-09-23 09:35:13","uploaded":"2024-09-23 13:55:46","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"TSG CT, SA WG1, SA WG2","lsoriginalls":"C1-245057","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2409585.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409591","title":"LS from CT WG4: RAN support of QoS monitoring capability","source":"CT WG4","contact":"RONG WANG","contact-id":87346,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 is working on the CT aspects of 5GS enhancement on QoS monitoring enhancement (TEI19_QME) based on the agreed CRs in SA WG2. CT WG4 have agreed the attached CR clarifying particular conditions for sending the NG RAN QoS monitoring capability parameter over N11, N16 and N16a. CT WG4 would like to ask SA WG2 to take this information into account and come back to CT WG4 if any comments. Action: CT WG4 kindly asks SA WG2 to take this information into account and come back to CT WG4 if they have any comments.","secretary_remarks":"Response drafted in S2-2410171. Final response in S2-2411247","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10430,"status":"replied to","reservation_date":"2024-09-23 09:35:13","uploaded":"2024-09-23 13:55:46","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG3","lsoriginalls":"C4-243669","lsreply":"S2-2411247","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2409591.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409593","title":"LS from RAN WG2: Reply LS on the UE role list in RSPP-Metadata","source":"RAN WG2","contact":"Yu Pan","contact-id":87666,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 thanks CT WG1 for pointing out the issue existed in TS38.355-i10. The issue has already been fixed in 38.355-i20: {. . .}","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-09-23 09:35:13","uploaded":"2024-09-23 13:55:46","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG2","lsoriginalls":"R2-2407718","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2409593.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409596","title":"LS from RAN WG3: Reply LS on the Realization of Network Slices for 5G Networks Using Current IP\/MPLS Technologies","source":"RAN WG3","contact":"Feng Han","contact-id":73581,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 thanks IETF TEAS for the LS on 'A Realization of Network Slices for 5G Networks Using Current IP\/MPLS Technologies' and for the updates on the drafting of the informational document on Network Slice realization model for IP\/MPLS networks. The TEAS WG has requested 3GPP to review the document and provide confirmation that the brief 5G overview included in the Appendix is accurate. RAN WG3 would like to provide the following feedback. {. . .}","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-09-23 09:35:13","uploaded":"2024-09-23 13:55:46","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG CT","Cc":"SA WG2, SA WG3, SA WG5","lsoriginalls":"R3-244785","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2409596.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409599","title":"LS from RAN WG5: Response LS on Newly published data channel GSMA PRD TS.66","source":"RAN WG5","contact":"zhaobing yang","contact-id":80062,"tdoctype":"LS in","for":"Information","abstract":"RAN WG5 would like to thank GSMA TSG for the LS (TSG56_059) notifying the approval and publication of GSMA PRD TS.66 - IMS data channel API specification. RAN WG5 would also appreciate high level description in the LS about the TS.66 contents and association with GSMA PRD NG.134. RAN WG5#104 meeting endorsed a new Conformance Work Item (WI) proposal for IMS Data Channel in Rel-18. The main objective of this Conformance WI is to explicitly verify signalling conformance of UE core requirements for IMS Data Channel feature defined by CT WG1 in TS 24.186 and TS 24.229 (SIP and SDP aspects). An additional objective is to implicitly verify core requirements for data channel media type defined by SA WG4 in 3GPP TS 26.114. IMS Data Channel API conformance testing is outside the scope of RAN WG5, hence won't be covered in this WI. RAN WG5 expects proponents of the new IMS Data Channel Conformance WI to submit the RAN WG5 endorsed WI proposal to the upcoming RAN Plenary#104 meeting (Melbourne, Australia 9 - 12 September 2024) for approval. Once the Conformance WI is approved, RAN WG5 will start IMS Data Channel conformance test development from RAN WG5#105 meeting (18 - 22 November 2024). Details of conformance test methodology and environment shall be figured out during the IMS Data Channel conformance test development work. At this stage, RAN WG5 is not expecting to invoke JavaScript APIs for IMS Data Channel conformance testing.","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-09-23 09:35:13","uploaded":"2024-09-23 13:55:47","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA TSG","Cc":"TSG SA, SA WG2, SA WG3, SA WG4, SA WG6, TSG CT, CT WG1, CT WG3, CT WG4","lsoriginalls":"R5-245464","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2409599.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409602","title":"LS from SA WG3: Reply LS on LI considerations for TR 33.757","source":"SA WG3","contact":"hua song","contact-id":91953,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 would like to thank SA WG3-LI for the reply LS on LI considerations for TR 33.757 and the clarifications. Regarding Key Issue #1, SA WG3 confirms that SA WG3-LI's understanding described in S3i-240502 is correct, and no further clarifications are required by SA WG3. SA WG3 understands that it's not SA WG3's responsibility to define the functions needed by SA WG3-LI. SA WG3 will take the information provided by SA WG3-LI into consideration to evaluate solutions and draw conclusion.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10160,"status":"noted","reservation_date":"2024-09-23 09:35:14","uploaded":"2024-09-23 13:55:47","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3-LI","Cc":"SA WG2","lsoriginalls":"S3-243410","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2409602.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409603","title":"LS from SA WG3: Reply LS on Newly published data channel GSMA PRD TS.66","source":"SA WG3","contact":"Vlasios Tsiatsis","contact-id":76181,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 would like to thank GSMA TSG for their LS on Newly published data channel GSMA PRD TS.66. Since GSMA has sent this LS to multiple TSG SA workgroups, SA WG3 addresses this response to TSG SA for TSG SA to respond back to GSMA after coordination with the rest of the TSG SA groups. {. . .}","secretary_remarks":"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-09-23 09:35:14","uploaded":"2024-09-23 13:55:47","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG2, SA WG4, SA WG6, RAN WG5","lsoriginalls":"S3-243411","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2409603.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409606","title":"LS from 5G-ACIA: 5G-ACIA LS on DetNet for 5G Industrial Use Cases","source":"5G-ACIA","contact":"Andreas Mueller","contact-id":81087,"tdoctype":"LS in","for":"Action","abstract":"5G-ACIA is glad to inform SA WG2 about the publication of its white paper on 'DetNet-based deterministic IP communication over 5G network for industrial applications', published in September 2024 (link). The document includes insights on the applicability of DetNet for 5G Industrial use cases, as well as related deployment scenarios from 5G-ACIA viewpoint. The white paper includes a summary of the 3GPP standardization to support DetNet in 5G (Release 18) and identifies several extensions that would make DetNet over 5G more reliable and flexible in industrial scenarios: - Supporting the DetNet service sublayer with its PREOF feature. - Enabling the DetNet controller to manage explicit route configurations. - Enabling the control signaling to support the IP routing protocols. Action: Please consider the published white paper and the above-mentioned possible extensions for future 3GPP standardization work related to DetNet, which would increase the relevance and potential of 5G for industrial use cases with DetNet.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10420,"status":"noted","reservation_date":"2024-09-23 09:35:14","uploaded":"2024-10-01 07:41:14","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2409606.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409608","title":"LS from SA WG4: LS Reply on Newly Published data channel GSMA PRD TS.66","source":"SA WG4","contact":"Huan-yu Su","contact-id":79844,"tdoctype":"LS in","for":"Information","abstract":"SA WG4 thanks GSMA for the LS on newly published data channel GSMA PRD TS.66 (S4-241435) and would like to provide the feedback as following: {. . .}","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10180,"status":"noted","reservation_date":"2024-09-23 09:35:14","uploaded":"2024-09-23 13:55:47","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA TSG","Cc":"SA WG2, SA WG3, SA WG4, SA WG6, RAN WG5, TSG SA, SA WG1, TSG CT, CT WG1, CT WG3, CT WG4","lsoriginalls":"S4-241684","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2409608.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409615","title":"LS from SA WG5: LS reply to IETF Traffic Engineering Architecture and Signaling Working Group on A Realization of Network Slices for 5G Networks Using Current IP\/MPLS Technologies","source":"SA WG5","contact":"Kai Zhang","contact-id":97593,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to thank the IETF TEAS WG for the LS on 'A Realization of Network Slices for 5G Networks Using Current IP\/MPLS Technologies'. {. . .}","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10190,"status":"noted","reservation_date":"2024-09-23 09:35:14","uploaded":"2024-09-23 13:55:46","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"IETF","Cc":"TSG SA, SA WG2, SA WG3, RAN WG3","lsoriginalls":"S5-244662","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2409615.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409616","title":"LS from SA WG5: LS Reply on Internal 5G Core information expose to trusted AF","source":"SA WG5","contact":"Yushuang Hu","contact-id":96973,"tdoctype":"LS in","for":"Action","abstract":"SA WG5 would like to thank SA WG6,SA WG2 for the LS on Clarification related to Internal 5G Core information expose to trusted AF. Based on the latest LS from SA WG2(S2-2407354), for the following clarification request from SA WG6 about the information exposed by the 5GC to NSCE server: 'As described in TS 33.501 clause 5.9.2.3, NEF and the AF shall fulfil the security requirements that include that 'Internal 5G Core information such as DNN, S-NSSAI etc., shall not be sent outside the 3GPP operator domain.' {. . .} Action: SA WG5 kindly requests SA WG6 and SA WG2 to take the information above into account and inform SA WG5 if further clarifications are needed","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10380,"status":"noted","reservation_date":"2024-09-23 09:35:14","uploaded":"2024-09-23 13:55:46","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG6","Cc":"SA WG3","lsoriginalls":"S5-245162","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2409616.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409617","title":"LS from SA WG6: Reply LS on SA WG2 questions on the predictive slice modification in Inter-PLMN based slice service continuity","source":"SA WG6","contact":"Vasil Aleksiev","contact-id":63195,"tdoctype":"LS in","for":"Action","abstract":"SA WG6 thanks SA WG2 for the LS on Reply LS on Clarification related to the predictive slice modification in Inter-PLMN based slice service continuity. SA WG6 discussed the SA WG2 LS and decided to provide the following answers: {. . .} Action: SA WG6 kindly requests SA WG2 to consider the above feedback.","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-09-23 09:35:14","uploaded":"2024-09-23 13:55:46","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG5, CT WG3","lsoriginalls":"S6-243352","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2409617.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409618","title":"LS from SA WG6: LS on SA6 Answer to GSMA LS on Newly published data channel GSMA PRD TS.66","source":"SA WG6","contact":" Anonymous","contact-id":4132,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 received a LS on newly published data channel GSMA PRD TS.66 (S6-243012) from GSMA TSG (Terminal Steering Group). SA WG6 was asked to review GSMA PRD TS.66 and answer two question listed below. {. . .} Action: SA WG6 would like ask TSG SA to discuss the suitable text which combines the work on IMS Data Channel API aspect in both SA WG2, SA WG4 and SA WG6 to reply to GSMA. SA WG6 would like to ask TSG SA to discuss the suitable text which combines the work on reference implementation to test IMS Data Channel services in both SA WG4, SA WG6 and RAN WG5 to reply to GSMA.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10200,"status":"noted","reservation_date":"2024-09-23 09:35:14","uploaded":"2024-09-23 13:55:46","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG2, SA WG3, SA WG4","lsoriginalls":"S6-243763","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2409618.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409620","title":"LS from GSMA OPG: LS on GSMA OPG PRDs publication and document restructuring","source":"GSMA OPG","contact":"Sandra Ondrusova","contact-id":77474,"tdoctype":"LS in","for":"Information","abstract":"GSMA OPG would like to notify 3GPP and ETSI of the recent release of several GSMA PRDs:. - OPG.02 Operator Platform: Requirements and Architecture version 7.0. - OPG.04 East-Westbound Interface APIs version 5.0. - OPG.09 NBI APIs Realisation in the SBI version 2.0. GSMA OPG and its subgroups started working on the new releases of the documents mentioned above. Several topics are being discussed: - Document restructuring: The idea is to split the requirements from the GSMA PRD OPG.02 into several documents. OPG.02 would be dedicated to the platform requirements only, while new documents would focus on edge related requirements and other services. - Aggregator routing requirements - OP roles and functional definitions - Operate APIs from TM Forum. Actions: GSMA OPG kindly ask 3GPP and ETSI to take the above into consideration.","secretary_remarks":"Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10060,"status":"postponed","reservation_date":"2024-09-23 09:35:14","uploaded":"2024-10-14 09:20:44","revisionof":"","revisedto":"S2-2411285","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG5, SA WG6, ETSI ISG MEC, ETSI ISG NFV","Cc":"TSG SA","lsoriginalls":"OPG_197_Doc_03","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2409620.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2409960","title":"[DRAFT] Further LS Reply on Internal 5G Core information expose to trusted AF","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"LS out","for":"Approval","abstract":"Further LS Reply on Internal 5G Core information expose to trusted AF","secretary_remarks":"Response to S2-2406846 (Replied to at S2#163). Revised to S2-2410813.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10390,"status":"revised","reservation_date":"2024-02-10 03:28:17","uploaded":"2024-10-04 00:01:16","revisionof":"","revisedto":"S2-2410813","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NSCALE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"SA WG3, SA WG5","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2409960.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2410171","title":"[DRAFT] Reply LS on RAN support of QoS monitoring capability","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"LS out","for":"Approval","abstract":"Proposes a Reply LS on RAN support of QoS monitoring capability","secretary_remarks":"Response to S2-2409591. Revised to S2-2410814.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10450,"status":"revised","reservation_date":"2024-03-10 15:11:30","uploaded":"2024-10-04 13:25:31","revisionof":"","revisedto":"S2-2410814","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"TEI19_QME"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2410171.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2410172","title":"Clarification on the QoS monitoring capability","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifying the value of NG RAN QoS monitoring capability.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10440,"status":"noted","reservation_date":"2024-03-10 15:11:30","uploaded":"2024-10-04 13:25:31","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.501","crspecversion":"19.1.0","workitem":[{"winame":"TEI19_QME"}],"crnumber":5731.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2410172.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.45.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2410311","title":"[DRAFT] Reply LS on CEN's requirements for eCall over IMS","source":"Nokia","contact":"Pallab Gupta","contact-id":87959,"tdoctype":"LS out","for":"Approval","abstract":"S2-2409582\/SP-241421, Reply LS on CEN's requirements for eCall over IMS","secretary_remarks":"Response to S2-2409582. Merged into S2-2411246","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10240,"status":"merged","reservation_date":"2024-04-10 06:58:24","uploaded":"2024-10-04 13:04:07","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, TSG SA","Cc":"SA WG1, SA WG3, RAN WG5","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2410311.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2410312","title":"Alignment for eCall and test eCall with CEN requirements","source":"Nokia","contact":"Pallab Gupta","contact-id":87959,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updates References Updates functional description of UE to support test eCall Updates functional description of ProxyCSCF to support test eCall Clarifies that inband MSD reception over packet switched networks is an optional feature for a PSAP Clarifies that transfer of an updated MSD procedure is also applicable during an incoming IMS call for PSAP call back","secretary_remarks":"Merged into S2-2410881","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10250,"status":"merged","reservation_date":"2024-04-10 06:58:24","uploaded":"2024-10-04 13:04:07","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.167","crspecversion":"18.2.0","workitem":[{"winame":"eCallCEN"}],"crnumber":374.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2410312.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"2, 6.1, 6.2.1, 7.7.2, 7.7.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2410462","title":"SA guidance to SA WG2","source":"SA WG2 Chair","contact":"Andy Bennett","contact-id":70253,"tdoctype":"other","for":"Information","abstract":"SA guidance to SA WG2","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10480,"status":"noted","reservation_date":"2024-04-10 12:11:45","uploaded":"2024-10-04 14:25:36","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2410462.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2410463","title":"WA#64 outcome from SA#105","source":"SA WG2 Chair","contact":"Andy Bennett","contact-id":70253,"tdoctype":"other","for":"Information","abstract":"WA#64 outcome from SA#105","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10490,"status":"noted","reservation_date":"2024-04-10 12:11:45","uploaded":"2024-10-04 14:25:36","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2410463.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2410587","title":"[DRAFT] Reply to LS on CEN's requirements for eCall over IMS","source":"Qualcomm Incorporated","contact":"Stephen Edge","contact-id":84641,"tdoctype":"LS out","for":"Approval","abstract":"Reply to LS on CEN's requirements for eCall over IMS","secretary_remarks":"Response to S2-2409582 and S2-2409585. Revised to S2-2410878.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10260,"status":"revised","reservation_date":"2024-04-10 20:54:13","uploaded":"2024-10-04 22:17:41","revisionof":"","revisedto":"S2-2410878","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"eCallCEN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, CT WG1","Cc":"TSG CT, SA WG1, SA WG3, RAN WG5","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2410587.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2410588","title":"Alignment of eCall over IMS with CEN","source":"Qualcomm Incorporated","contact":"Stephen Edge","contact-id":84641,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add support for the three cases above to align with CEN..","secretary_remarks":"Revised to S2-2410879.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10290,"status":"revised","reservation_date":"2024-04-10 21:01:40","uploaded":"2024-10-04 22:17:41","revisionof":"","revisedto":"S2-2410879","release":"Rel-19","crspec":"23.167","crspecversion":"18.2.0","workitem":[{"winame":"eCallCEN"},{"winame":" TEI19"}],"crnumber":375.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2410588.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":false,"clauses_affected":"7.7.2, Annex H.6","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2410589","title":"Support of MSD transfer for a PSAP Callback for eCall over IMS","source":"Qualcomm Incorporated","contact":"Stephen Edge","contact-id":84641,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add support for updated MSD transfer for a PSAP callback for a previous eCall over IMS where the PSAP may be either NG capable and in the PS domain or non NG capable and in the CS domain.","secretary_remarks":"Revised to S2-2410880.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10320,"status":"revised","reservation_date":"2024-04-10 21:08:09","uploaded":"2024-10-04 22:17:41","revisionof":"","revisedto":"S2-2410880","release":"Rel-19","crspec":"23.167","crspecversion":"18.2.0","workitem":[{"winame":"eCallCEN"},{"winame":" TEI19"}],"crnumber":376.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2410589.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":false,"clauses_affected":"7.7.a (new), 7.7.b (new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2410590","title":"Support of a Test eCall over IMS","source":"Qualcomm Incorporated","contact":"Stephen Edge","contact-id":84641,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add support for establishment of a test eCall over IMS from a UE to a test point with transfer of initial MSD and transfer of updated MSD. Add support for a callback from a test point to a UE with transfer of updated MSD.","secretary_remarks":"Revised, merging S2-2410312, to S2-2410881.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10350,"status":"revised","reservation_date":"2024-04-10 21:14:27","uploaded":"2024-10-04 22:17:41","revisionof":"","revisedto":"S2-2410881","release":"Rel-19","crspec":"23.167","crspecversion":"18.2.0","workitem":[{"winame":"eCallCEN"},{"winame":" TEI19"}],"crnumber":377.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2410590.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":false,"clauses_affected":"Annex X (new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2410813","title":"Further LS Reply on Internal 5G Core information expose to trusted AF","source":"SA WG2","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"LS out","for":"Approval","abstract":"Response to S2-2406846 (S6-242714) - SA WG2#164. To: SA WG6. CC: SA WG3, SA WG5","secretary_remarks":"Revision of S2-2409960. This LS OUT was approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10400,"status":"approved","reservation_date":"2024-10-15 06:47:42","uploaded":"2024-10-20 10:31:12","revisionof":"S2-2409960","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NSCALE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2406846","lsto":"SA WG6","Cc":"SA WG3, SA WG5","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2410813.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2410814","title":"[DRAFT] Reply LS on RAN support of QoS monitoring capability","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"LS out","for":"Approval","abstract":"Proposes a Reply LS on RAN support of QoS monitoring capability","secretary_remarks":"Revision of S2-2410171. Revised to S2-2411247.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10460,"status":"revised","reservation_date":"2024-10-15 06:47:42","uploaded":"2024-10-20 10:31:12","revisionof":"S2-2410171","revisedto":"S2-2411247","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"TEI19_QME"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2410814.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2410878","title":"[DRAFT] Reply to LS on CEN's requirements for eCall over IMS","source":"Qualcomm Incorporated","contact":"Stephen Edge","contact-id":84641,"tdoctype":"LS out","for":"Approval","abstract":"Reply to LS on CEN's requirements for eCall over IMS","secretary_remarks":"Revision of S2-2410587. Revised, merging S2-2410311, to S2-2411246.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10270,"status":"revised","reservation_date":"2024-10-18 02:10:12","uploaded":"2024-10-20 10:31:14","revisionof":"S2-2410587","revisedto":"S2-2411246","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"eCallCEN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, CT WG1","Cc":"TSG CT, SA WG1, SA WG3, RAN WG5","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2410878.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2410879","title":"Alignment of eCall over IMS with CEN","source":"Qualcomm Incorporated, Ericsson, Nokia, Deutsche Telekom","contact":"Stephen Edge","contact-id":84641,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add support for the three cases above to align with CEN..","secretary_remarks":"Revision of S2-2410588. Revised to S2-2411243.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10300,"status":"revised","reservation_date":"2024-10-18 02:10:12","uploaded":"2024-10-20 10:31:14","revisionof":"S2-2410588","revisedto":"S2-2411243","release":"Rel-19","crspec":"23.167","crspecversion":"18.2.0","workitem":[{"winame":"eCallCEN"},{"winame":" TEI19"}],"crnumber":375.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2410879.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2410880","title":"Support of MSD transfer for a PSAP Callback for eCall over IMS","source":"Qualcomm Incorporated, Deutsche Telekom","contact":"Stephen Edge","contact-id":84641,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add support for updated MSD transfer for a PSAP callback for a previous eCall over IMS where the PSAP may be either NG capable and in the PS domain or non NG capable and in the CS domain.","secretary_remarks":"Revision of S2-2410589. Revised to S2-2411244.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10330,"status":"revised","reservation_date":"2024-10-18 02:10:13","uploaded":"2024-10-20 10:31:14","revisionof":"S2-2410589","revisedto":"S2-2411244","release":"Rel-19","crspec":"23.167","crspecversion":"18.2.0","workitem":[{"winame":"eCallCEN"},{"winame":" TEI19"}],"crnumber":376.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2410880.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2410881","title":"Support of a Test eCall over IMS","source":"Qualcomm Incorporated, Ericsson, Nokia, Deutsche Telekom","contact":"Stephen Edge","contact-id":84641,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add support for establishment of a test eCall over IMS from a UE to a test point with transfer of initial MSD and transfer of updated MSD. Add support for a callback from a test point to a UE with transfer of updated MSD.","secretary_remarks":"Revision of S2-2410590, merging S2-2410312. Revised to S2-2411245.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10360,"status":"revised","reservation_date":"2024-10-18 02:10:14","uploaded":"2024-10-20 10:31:14","revisionof":"S2-2410590","revisedto":"S2-2411245","release":"Rel-19","crspec":"23.167","crspecversion":"18.2.0","workitem":[{"winame":"eCallCEN"},{"winame":" TEI19"}],"crnumber":377.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2410881.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411243","title":"Alignment of eCall over IMS with CEN","source":"Qualcomm Incorporated, Ericsson, Nokia, Deutsche Telekom","contact":"Stephen Edge","contact-id":84641,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add support for the three cases above to align with CEN..","secretary_remarks":"Revision of S2-2410879. This CR was agreed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10310,"status":"agreed","reservation_date":"2024-10-20 09:22:56","uploaded":"2024-10-20 10:31:16","revisionof":"S2-2410879","revisedto":"","release":"Rel-19","crspec":"23.167","crspecversion":"18.2.0","workitem":[{"winame":"eCallCEN"},{"winame":" TEI19"}],"crnumber":375.0,"crrevision":2.0,"crcategory":"C","tsg_crp":"SP-241484","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2411243.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411244","title":"Support of MSD transfer for a PSAP Callback for eCall over IMS","source":"Qualcomm Incorporated, Deutsche Telekom","contact":"Stephen Edge","contact-id":84641,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add support for updated MSD transfer for a PSAP callback for a previous eCall over IMS where the PSAP may be either NG capable and in the PS domain or non NG capable and in the CS domain.","secretary_remarks":"Revision of S2-2410880. This CR was agreed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10340,"status":"agreed","reservation_date":"2024-10-20 09:22:57","uploaded":"2024-10-20 10:31:16","revisionof":"S2-2410880","revisedto":"","release":"Rel-19","crspec":"23.167","crspecversion":"18.2.0","workitem":[{"winame":"eCallCEN"},{"winame":" TEI19"}],"crnumber":376.0,"crrevision":2.0,"crcategory":"C","tsg_crp":"SP-241484","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2411244.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411245","title":"Support of a Test eCall over IMS","source":"Qualcomm Incorporated, Ericsson, Nokia, Deutsche Telekom","contact":"Stephen Edge","contact-id":84641,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add support for establishment of a test eCall over IMS from a UE to a test point with transfer of initial MSD and transfer of updated MSD. Add support for a callback from a test point to a UE with transfer of updated MSD.","secretary_remarks":"Revision of S2-2410881. This CR was agreed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10370,"status":"agreed","reservation_date":"2024-10-20 09:22:57","uploaded":"2024-10-20 10:31:16","revisionof":"S2-2410881","revisedto":"","release":"Rel-19","crspec":"23.167","crspecversion":"18.2.0","workitem":[{"winame":"eCallCEN"},{"winame":" TEI19"}],"crnumber":377.0,"crrevision":2.0,"crcategory":"C","tsg_crp":"SP-241484","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2411245.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411246","title":"Reply to Reply LS on CEN's requirements for eCall over IMS","source":"SA WG2","contact":"Stephen Edge","contact-id":84641,"tdoctype":"LS out","for":"Approval","abstract":"Response to S2-2409582 (SP-241421) and S2-2409585 (C1-245057). To: TSG SA, CT WG1. CC: TSG CT, SA WG1, SA WG3, RAN WG5. Attachments: S2-2411243 (TS 23.167 CR0375), S2-2411244 (TS 23.167 CR0376), S2-2411245 (TS 23.167 CR0377)","secretary_remarks":"Revision of S2-2410878, merging S2-2410311. This LS OUT was approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10280,"status":"approved","reservation_date":"2024-10-20 09:22:58","uploaded":"2024-10-20 10:31:16","revisionof":"S2-2410878","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"eCallCEN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2409582","lsto":"TSG SA, CT WG1","Cc":"TSG CT, SA WG1, SA WG3, RAN WG5","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2411246.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411247","title":"Reply LS on RAN support of QoS monitoring capability","source":"SA WG2","contact":"Zhendong Li","contact-id":38521,"tdoctype":"LS out","for":"Approval","abstract":"Response to S2-2409591 (C4-243669). To: CT WG4. CC: CT WG3","secretary_remarks":"Revision of S2-2410814. This LS OUT was approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10470,"status":"approved","reservation_date":"2024-10-20 09:22:58","uploaded":"2024-10-20 10:31:16","revisionof":"S2-2410814","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"TEI19_QME"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2409591","lsto":"CT WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"C4-245437","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_165_Hyderabad_2024-10\/Docs\/S2-2411247.zip","group":"S2","meeting":"S2-165","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]