[{"name":"S2-2401850","title":"LS from TSG RAN: LS on Robust Notification Alert for NTN-NR Rel-19","source":"TSG RAN","contact":"Munira Jaffar","contact-id":77683,"tdoctype":"LS in","for":"Action","abstract":"RAN#102 discussed a candidate features of a robust notification\/paging proposed for the Rel-19 RAN WG2 led NR-NTN-ph3 WI. The robust notification\/paging should be addressed to a particular UE in a cell. The intent is to maximise the probability for a UE to be informed of a mobile terminated call when in very poor SNR conditions which prevent to receive a normal paging message. This feature should: be triggered by the network upon e.g. paging failure (i.e. when no paging response from the UE has been received by the network), or other criteria; and apply only for mobile terminated calls; and inform the user of a mobile terminated call so the user could then try and move to a location with better coverage. It is noted that this feature is highly desirable for satellite networks to reach users experiencing low SNR or NLOS channel conditions. Before some standardisation activity can be started in RAN on the subject, some inputs, guidance and requirements would be needed from relevant SA WGs. Action: SA WG1 and SA WG2 are kindly requested to provide feedback on the above.","secretary_remarks":"Revision of Postponed S2-2400036 from S2#160AH-e. Responses drafted in S2-2401957, S2-2402521, S2-2402657, S2-2402246, S2-2402308, S2-2402394. Final response in S2-2403843","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-05-02 14:59:37","uploaded":"2024-02-07 11:12:48","revisionof":"S2-2400036","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG2","Cc":"TSG SA","lsoriginalls":"RP-234075","lsreply":"S2-2403843","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2401850.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2401851","title":"Reply LS to GSMA on Monitoring of Encrypted 5GS Signalling Traffic","source":"TSG SA","contact":"Lan Zou","contact-id":35534,"tdoctype":"LS in","for":"Information","abstract":"TSG SA thanks GSMA 5GPKIWP for the incoming LS to SA WG2, SA WG3 and SA WG5 on Monitoring of Encrypted 5GS Signalling Traffic. TSG SA has discussed the liaison received by SA WG2, SA WG3 and SA WG5, and is aware that SA WG3 already sent a reply on this topic to share their opinion from the security perspective. TSG SA will further communicate with GSMA regarding this issue with a consolidated view after coordination with SA WG2, SA WG3 and SA WG5.","secretary_remarks":"Revision of Postponed S2-2400037 from S2#160AH-e. Response drafted in S2-2402088. Final response in S2-2403027.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10150,"status":"replied to","reservation_date":"2024-05-02 14:59:37","uploaded":"2024-02-07 11:12:48","revisionof":"S2-2400037","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA 5GPKIWP","Cc":"SA WG3, SA WG5, SA WG2","lsoriginalls":"SP-231668","lsreply":"S2-2402088","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2401851.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2401853","title":"LS from CT WG3: LS on Clarification related to the information exposed by the 5GC to NSCE server","source":"CT WG3","contact":"Rajesh Babu Natarajan","contact-id":89232,"tdoctype":"LS in","for":"Action","abstract":"As per TS 23.288, clause 6.3.1: The NWDAF services as defined in the clause 7.2 and clause 7.3 are used to expose slice load level analytics from the NWDAF to the consumer NF (e.g. PCF, NSSF or AMF) {. . .} Question 1: Which of the network internal information provided in the Network Slice load information\/analytics prediction can be exposed to an external AF or the NSCE Server? (For example, Area of Interest in terms of internal identities (e.g. TAI, Cell ID) sent to the NSCE server). Action: CT WG3 kindly asks SA WG2 and SA WG6 to answer the above questions and update the SA WG2 and SA WG6 specifications respectively, if necessary.","secretary_remarks":"Revision of Postponed S2-2400046 from S2#160AH-e. Responses drafted in S2-2402056, S2-2402997. Final response in S2-2403703","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10060,"status":"replied to","reservation_date":"2024-05-02 14:59:37","uploaded":"2024-02-07 11:12:48","revisionof":"S2-2400046","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG6, CT WG1, C WG4","lsoriginalls":"C3-235717","lsreply":"S2-2403703","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2401853.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2401857","title":"LS from SA WG4: LS on Support of interworking between SA WG4 RTC and IMS","source":"SA WG4","contact":"Yoshihiro Inoue","contact-id":95845,"tdoctype":"LS in","for":"Action","abstract":"SA WG4 is addressing the Real-Time media Communication (RTC) architecture and protocols for realizing WebRTC-based immersive real time media communication services on 5G system in the following Release-18 WIs\/SI {. . .} SA WG4 would like to ask SA WG2 and CT WG3: - Are there any potential impacts on existing IMS specifications from the above NNI-based solution (connecting the WebRTC-based RTC communication network to IMS network, by applying the interworking model specified in 3GPP TS 29.162), considering that the solution uses the interface of existing 3GPP IMS specification without any modifications?. Action: SA WG4 respectfully asks SA WG2 and CT WG3 to provide feedback to the question.","secretary_remarks":"Revision of Postponed S2-2400070 from S2#160AH-e. Responses drafted in S2-2402385, S2-2402477. Final response in S2-2403844","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10340,"status":"replied to","reservation_date":"2024-05-02 14:59:37","uploaded":"2024-02-07 11:12:48","revisionof":"S2-2400070","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG3","Cc":"SA WG1","lsoriginalls":"S4-232055","lsreply":"S2-2403844","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2401857.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2401859","title":"LS from GSMA 5GMRR: LS to 3GPP on data plane control by roaming hubs","source":"GSMA 5GMRR","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"Introduction: GSMA 5GMRR would like to draw the attention of 3GPP to the following requirements again: 1. The RH shall have the ability to intervene in roaming data sessions at any time, in order to limit roaming data usage by limiting throughput and\/or stopping ongoing data sessions as agreed with the client HPMN. This ability to intervene requires anchoring the media in this intermediary. 2. All N32 messages between client MNOs are transferred via the RH. This shall include the ability for the RH to prevent the establishment of, and the termination of N32-c and N32-f connections, for example if this is required due to contractual reasons. As a clarification to requirement 1: The RH shall be able to intervene on roaming data sessions on the basis of individual PDU sessions and across all PDU sessions of the roamers of a given roaming relationship between two PLMNs. Request to 3GPP: GSMA kindly requests SA WG1 and SA WG2 to review these requirements and define solutions. GSMA 5GMRR welcomes an initial response and ongoing collaboration.","secretary_remarks":"Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10660,"status":"postponed","reservation_date":"2024-05-02 14:59:38","uploaded":"2024-02-08 15:02:50","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG2","Cc":"SA WG3, SA WG5, TSG SA, CT WG4","lsoriginalls":"5GMRR Doc 47_14r1","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2401859.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2401862","title":"LS from SA WG4: Reply LS on the clarification on the AR media specification","source":"SA WG4","contact":"Sun Zhao","contact-id":76503,"tdoctype":"LS in","for":"Information","abstract":"SA WG4 thanks CT WG4 for their LS on Clarification on the AR media specification (C4-235475). SA WG4 provides the answer to the following question: Q1: What kind of information is included in the media processing specification for the AR media? SA WG4 Answer: From SA WG4 perspective, the AR media specification is an application-specific string that indicate how MF should assist the AR media rendering function. SA WG4 assumes that corresponding application media processing exists in both the device and AR media rendering function, and exactly how this is indicated does not need to be standardized. Q2: Is the media processing specification for the AR media already specified by SA WG4? A. If the answer on Q2 is yes, CT WG4 kindly asks SA WG4 to provide TS identity. B. If the answer on Q2 is no, does SA WG4 plan to specify the media processing specification for the AR media and in which time frame? SA WG4 Answer: This AR media processing specification is application specific, it should be self-defined at application level between the MF and the AR AS.","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-05-02 14:59:38","uploaded":"2024-02-08 15:02:51","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"SA WG2","lsoriginalls":"S4-240489","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2401862.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2401868","title":"Reply LS on the user consent for trace reporting","source":"SA WG5","contact":" Anonymous","contact-id":4132,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks RAN WG3 for its LS on support the user consent for trace reporting in document R3-237964 with the requirements on user consent have been considered and the workflow for a user consent solution described by SA WG3 has been endorsed by RAN WG3. The endorsements entail amending the current solution on user consent for MDT. SA WG5 has discussed and agreed to specify a new OAM configuration in gNB for user consent check of Management Based MDT and in AMF\/UDM for user consent check of Signalling Based MDT. SA WG5 would like to indicate that, - as specified by TS32.422, the Signalling Based MDT may be initiated by UDM or AMF. Therefore, SA WG5 has specified the new requirements on both AMF and UDM. It would be good if RAN WG3 specifications can also consider the corresponding UDM requirements. - In the agreed RAN WG3 CRs, the terminology data type is used. However, in SA WG5 data type has a different meaning. Therefore, in corresponding SA WG5 user consent procedures, the terminology MDT measurement name is used to align with exist SA WG5 specifications. It would be good if RAN WG3 specifications can use the same terminologies. For more details, please see the agreed CR.","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-05-02 14:59:38","uploaded":"2024-02-09 15:26:43","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"SA WG3, SA WG2, RAN WG2, TSG RAN, SA WG1","lsoriginalls":"S5-241084","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2401868.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2401870","title":"LS from SA WG3: Reply LS on MSISDN exposure","source":"SA WG3","contact":"Ferhat Karakoc","contact-id":86196,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 would like to thank SA WG2 for the LSes on MSISDN exposure to trusted AF and limited MSISDN exposure and provide the following feedback for the questions. SA WG2 question in S2-2311893: SA WG2 would like feedback from SA WG3 regarding the conditions under which exposure of MSISDN to trusted AFs are acceptable. SA WG2 question in S2-2401649: The condition for exposure of the MSISDN (GPSI in the form of MSISDN) is described in clause 4.15.10A in the draft 23.502CR4509. If SA WG3 has any concern with the condition for MSISDN exposure, SA WG3 is requested to provide feedback to SA WG2 before the end of SA WG2#161. SA WG3 response: The condition described is the draft 23.502CR4509 is the following: 'The AF is HPLMN or SNPN operator owned and operated within the operator domain and the AF does not re-expose the GPSI in MSISDN format outside the operator domain.' SA WG3 agreed that the UEID API can expose MSISDN to an authenticated and authorized AF, if the condition above is met and if the UDM\/UDR is configured explicitly to allow this exposure for that subscriber to that AF. SA WG3 would also like to give the feedback that potential security issues related with the usage of the API should be analysed for each use case separately. SA WG3 kindly asks SA WG2 to take the above information into account and inform SA WG3 if anything more is needed. Action: SA WG3 kindly asks SA WG2 to take the above information into account.","secretary_remarks":"Received during meeting. 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-05-02 14:59:38","uploaded":"2024-03-07 14:31:12","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG2","Cc":"SA WG6","lsoriginalls":"S3-240834","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2401870.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2401957","title":"[DRAFT] Reply LS on Robust Notification Alert for NTN-NR Rel-19","source":"NEC Corporation","contact":"Chunhui Zhu","contact-id":103480,"tdoctype":"LS out","for":"Approval","abstract":"The Reply LS on Robust Notification Alert for NTN-NR Rel-19 is proposed.","secretary_remarks":"Response to S2-2401850. Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10230,"status":"not treated","reservation_date":"2024-08-02 01:55:37","uploaded":"2024-02-08 14:44:33","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN","Cc":"TSG SA, SA WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2401957.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2402056","title":"[DRAFT] LS Reply on Clarification related to the information exposed by the 5GC to NSCE server.","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"LS on Clarification related to the information exposed by the 5GC to NSCE server.","secretary_remarks":"Response to S2-2401853. Revised, merging S2-2402997, to S2-2403025.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10070,"status":"revised","reservation_date":"2024-02-13 15:23:13","uploaded":"2024-02-16 13:07:26","revisionof":"","revisedto":"S2-2403025","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NSCALE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"SA WG6, CT WG1, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2402056.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2402057","title":"Clarification related to the information exposed by the 5GC to NSCE server","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add AF as new consumer and clarify the Area of Interest of the analytic Load level information . Besides, add description that NSI ID shall not be provided if the consumer NF is AF.","secretary_remarks":"Revised to S2-2403026.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10110,"status":"revised","reservation_date":"2024-02-13 15:23:13","uploaded":"2024-02-16 13:07:26","revisionof":"","revisedto":"S2-2403026","release":"Rel-18","crspec":"23.288","crspecversion":"18.4.0","workitem":[{"winame":"NSCALE"}],"crnumber":1061.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2402057.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":" 6.3.1, 6.3.3A","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2402086","title":"Tx Profile per PC5 QoS Flow to AS layer","source":"LG Electronics, OPPO","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 3.1 - Add 'NR eTx Profile' for SL CA while removing the EN about NR Tx Profile related to backward compatibility. 5.1.2.1 - Add 'NR eTx Profile'. 5.4.1.1.3 - Clarify that the NR eTx Profile per PC5 QoS Flow is provided by the V2X layer","secretary_remarks":"Revision of S2-2401580 from S2#160AH-e. Revised to S2-2403036.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10640,"status":"revised","reservation_date":"2024-02-14 00:04:18","uploaded":"2024-02-16 00:46:07","revisionof":"S2-2401580","revisedto":"S2-2403036","release":"Rel-18","crspec":"23.287","crspecversion":"18.2.0","workitem":[{"winame":"NR_SL_enh2-Core"}],"crnumber":196.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2402086.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"3.1, 5.1.2.1, 5.4.1.1.3, 5.11, 6.3.1, 6.3.2, 6.3.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2402088","title":"[DRAFT] Reply LS to GSMA on Monitoring of Encrypted 5GS Signalling Traffic","source":"Ericsson Inc.","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Response to SA","secretary_remarks":"Response to S2-2401851. Revised to S2-2403027.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10160,"status":"revised","reservation_date":"2024-02-14 01:30:44","uploaded":"2024-02-16 19:36:29","revisionof":"","revisedto":"S2-2403027","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG3, SA WG5","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2402088.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2402129","title":"[DRAFT] LS on V2X over MBS with SNPN","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Inform CT WG1 that V2X over MBS with SNPN is supported, and have the approved CR attached","secretary_remarks":"Revised to S2-2403030.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10450,"status":"revised","reservation_date":"2024-02-14 19:01:46","uploaded":"2024-02-16 19:28:59","revisionof":"","revisedto":"S2-2403030","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"TEI18_MBS4V2X"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2402129.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2402130","title":"V2X over MBS with SNPN.","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"The contribution discusses and proposes the changes to enable V2X over MBS with SNPN.","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-02-14 19:01:46","uploaded":"2024-02-16 19:28:59","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"TEI18_MBS4V2X"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2402130.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2402131","title":"V2X over MBS with SNPN","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update MBS session announcement to include the NID","secretary_remarks":"Revised to S2-2403029.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10430,"status":"revised","reservation_date":"2024-02-14 19:01:46","uploaded":"2024-02-16 19:28:59","revisionof":"","revisedto":"S2-2403029","release":"Rel-18","crspec":"23.287","crspecversion":"18.2.0","workitem":[{"winame":"TEI18_MBS4V2X"}],"crnumber":198.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2402131.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"3.2, 5.10.2, 5.10.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2402246","title":"[DRAFT] Reply LS on Robust Notification Alert for NTN-NR Rel-19","source":"Honor","contact":"Hanyu Ding","contact-id":104799,"tdoctype":"LS out","for":"Approval","abstract":"To: TSG RAN. CC: SA WG1, TSG SA","secretary_remarks":"Response to S2-2401850. Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10260,"status":"not treated","reservation_date":"2024-02-15 14:05:54","uploaded":"2024-02-16 13:30:42","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN","Cc":"SA WG1, TSG SA","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2402246.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2402308","title":"[DRAFT] Reply LS on Robust Notification Alert for NTN-NR Rel-19","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"This paper proposes a reply LS on robust notification alert","secretary_remarks":"Response to S2-2401850. Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10270,"status":"not treated","reservation_date":"2024-02-15 17:24:19","uploaded":"2024-02-16 19:15:53","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN","Cc":"TSG SA, SA WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2402308.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2402325","title":"Corrections to remove Nnef_UEId Service restrictions","source":"Ericsson, Verizon, AT&T, Vodafone, Deutsche Telekom, Dish Network, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding exposure of GPSI in the format of MSISDN in the Nnef_UEId API by mapping the UE address for trusted AF.","secretary_remarks":"Revision of S2-2401582 from S2#160AH-e. Revised, merging S2-2402557, to S2-2403031.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10470,"status":"revised","reservation_date":"2024-02-15 17:25:47","uploaded":"2024-02-16 19:28:59","revisionof":"S2-2401582","revisedto":"S2-2403031","release":"Rel-18","crspec":"23.501","crspecversion":"18.4.0","workitem":[{"winame":"TEI18"},{"winame":" EDGEAPP"}],"crnumber":5011.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2402325.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.20, 7.2.8","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2402326","title":"Corrections to remove Nnef_UEId Service restrictions","source":"Ericsson, Verizon, AT&T, Vodafone, Deutsche Telekom, Dish Network, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding exposure of GPSI in the form of MSISDN in the Nnef_UEId API by mapping the UE address for trusted AFs within agreed.","secretary_remarks":"Revision of S2-2401583 from S2#160AH-e. Revised, merging S2-2402559, to S2-2403032.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10500,"status":"revised","reservation_date":"2024-02-15 17:25:48","uploaded":"2024-02-16 19:28:59","revisionof":"S2-2401583","revisedto":"S2-2403032","release":"Rel-18","crspec":"23.502","crspecversion":"18.4.0","workitem":[{"winame":"TEI18"},{"winame":" EDGEAPP"}],"crnumber":4509.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2402326.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.15.3.2.13, 4.15.10A (new), 5.2.6.27.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2402385","title":"[DRAFT] Reply LS on Support of interworking between SA WG4 RTC and IMS","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"LS out","for":"Approval","abstract":"This contribution is a LS to SA WG4 to ask questions on interworking between SA WG4 RTC and IMS.","secretary_remarks":"Response to S2-2401857. Revised, merging S2-2402477, to S2-2403028.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10350,"status":"revised","reservation_date":"2024-02-16 01:32:47","uploaded":"2024-02-16 13:48:35","revisionof":"","revisedto":"S2-2403028","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"SA WG1, SA WG3, SA WG5, CT WG1, CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2402385.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2402394","title":"[DRAFT] Reply LS on Robust Notification Alert","source":"OPPO","contact":"Peng Tan","contact-id":101478,"tdoctype":"LS out","for":"Approval","abstract":"To: TSG RAN, SA WG1. CC: TSG SA","secretary_remarks":"Response to S2-2401850. Revised to S2-2403558.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10190,"status":"revised","reservation_date":"2024-02-16 02:06:30","uploaded":"2024-02-16 20:39:27","revisionof":"","revisedto":"S2-2403558","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, SA WG1","Cc":"TSG SA","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2402394.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2402477","title":"[DRAFT] Reply LS on Support of interworking between SA WG4 RTC and IMS","source":"NTT","contact":"Yoshihiro Inoue","contact-id":44190,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG4. CC: SA WG1, CT WG3. Attachments: None.","secretary_remarks":"Revision of S2-2400591 from S2#160AH-e. Response to S2-2401857. Merged into S2-2403028","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10390,"status":"merged","reservation_date":"2024-02-16 06:00:34","uploaded":"2024-02-16 06:53:59","revisionof":"S2-2400591","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"CT WG3, SA WG1, SA WG3-LI","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2402477.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2402521","title":"[DRAFT] Reply LS on Robust Notification Alert for NTN-NR Rel-19","source":"Samsung","contact":"Lalith Kumar","contact-id":80547,"tdoctype":"LS out","for":"Approval","abstract":"To: TSG RAN. CC: TSG SA, SA WG1. Attachments: NA.","secretary_remarks":"Revision of S2-2401312 from S2#160AH-e. Response to S2-2401850. Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10240,"status":"not treated","reservation_date":"2024-02-16 07:37:42","uploaded":"2024-02-16 07:43:48","revisionof":"S2-2401312","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN","Cc":"TSG SA, SA WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2402521.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2402557","title":"Corrections to remove Nnef_UEId Service restrictions","source":"[Ericsson, Verizon, AT&T, Vodafone, Deutsche Telekom, Dish Network, Nokia], Samsung","contact":"Hyesung Kim","contact-id":83054,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding exposure of GPSI in the format of MSISDN in the Nnef_UEId API by mapping the UE address for trusted AF.","secretary_remarks":"Revision of S2-2401582 from S2#160AH-e. Merged into S2-2403031","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10530,"status":"merged","reservation_date":"2024-02-16 09:11:59","uploaded":"2024-02-16 12:38:29","revisionof":"S2-2401582","revisedto":"","release":"Rel-18","crspec":"23.501","crspecversion":"18.4.0","workitem":[{"winame":"EDGEAPP"},{"winame":" TEI18"}],"crnumber":5011.0,"crrevision":6.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2402557.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.20, 7.2.8","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2402559","title":"Corrections to remove Nnef_UEId Service restrictions","source":"[Ericsson, Verizon, AT&T, Vodafone, Deutsche Telekom, Dish Network, Nokia], Samsung","contact":"Hyesung Kim","contact-id":83054,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding exposure of GPSI in the form of MSISDN in the Nnef_UEId API by mapping the UE address for trusted AFs within agreed.","secretary_remarks":"Revision of S2-2401583 from S2#160AH-e. Merged into S2-2403032","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10540,"status":"merged","reservation_date":"2024-02-16 09:14:15","uploaded":"2024-02-16 12:38:29","revisionof":"S2-2401583","revisedto":"","release":"Rel-18","crspec":"23.502","crspecversion":"18.4.0","workitem":[{"winame":"EDGEAPP"},{"winame":" TEI18"}],"crnumber":4509.0,"crrevision":6.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2402559.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.15.3.2.13, 4.15.10A (new), 5.2.6.27.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2402656","title":"On Robust Notification Alert for NTN.","source":"MediaTek Inc.","contact":"Mehrdad Shariat","contact-id":97826,"tdoctype":"discussion","for":"Agreement","abstract":"This contribution discusses Robust Notification Alert for NTN-NR and proposes that NB-IoT be investigated to address the intended operation point. It is a minor update of S2-2400391 from SA WG2#160AHe.","secretary_remarks":"Revision of S2-2400391 from S2#160AH-e. Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10330,"status":"not treated","reservation_date":"2024-02-16 10:52:33","uploaded":"2024-02-16 17:16:03","revisionof":"S2-2400391","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2402656.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2402657","title":"[DRAFT] Reply LS on Robust Notification Alert for NTN-NR Rel-19","source":"MediaTek Inc.","contact":"Mehrdad Shariat","contact-id":97826,"tdoctype":"LS out","for":"Approval","abstract":"LS Reply to RP-234075","secretary_remarks":"Revision of S2-2400392 from S2#160AH-e. Response to S2-2401850. Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10250,"status":"not treated","reservation_date":"2024-02-16 10:52:33","uploaded":"2024-02-16 17:16:03","revisionof":"S2-2400392","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, TSG RAN","Cc":"TSG SA","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2402657.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2402688","title":"[DRAFT] LS reply on the Robust Notification Alert for NTN-NR Rel-19","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Reply to RAN about robust notification alert and SA WG2 timing.","secretary_remarks":"Response to S2-2401850. Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10280,"status":"not treated","reservation_date":"2024-02-16 11:11:59","uploaded":"2024-02-16 14:50:36","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"FS_5GSAT_Ph3_ARCH"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN","Cc":"SA WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2402688.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2402716","title":"[DRAFT] Reply LS on Robust Notification Alert for NTN-NR Rel-19","source":"HUGHES Network Systems Ltd","contact":"Munira Jaffar","contact-id":76312,"tdoctype":"LS out","for":"Approval","abstract":"To: TSG RAN. CC: SA WG1","secretary_remarks":"Response to S2-2401850. Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10290,"status":"not treated","reservation_date":"2024-02-16 12:07:15","uploaded":"2024-02-16 22:20:14","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN","Cc":"SA WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2402716.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2402722","title":"On Robust Notification Alert for Satellite Access.","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"discussion","for":"Agreement","abstract":"This tdoc relates to the incoming LS in S2-2401850","secretary_remarks":"Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10320,"status":"not treated","reservation_date":"2024-02-16 12:16:54","uploaded":"2024-02-16 12:20:53","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2402722.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2402729","title":"[DRAFT] Reply LS to RAN and SA WG1 on Robust notification","source":"vivo","contact":"Amy Zhang","contact-id":105287,"tdoctype":"LS out","for":"Approval","abstract":"LS out on roubust notification for NR NTN","secretary_remarks":"Response to S2-2401850. Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10300,"status":"not treated","reservation_date":"2024-02-16 12:30:23","uploaded":"2024-02-16 12:32:27","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"FS_5GSAT_Ph3_ARCH"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN","Cc":"SA WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2402729.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2402761","title":"[DRAFT] Reply LS on Handling of regulatory prioritized services in Non-allowed areas","source":"Qualcomm","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"Provides further info on support of MPS for the questions CT WG1 asked","secretary_remarks":"Response to S2-2306265 (Replied to at S2-157). Revised to S2-2403035.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10550,"status":"revised","reservation_date":"2024-02-16 12:46:22","uploaded":"2024-02-16 19:23:14","revisionof":"","revisedto":"S2-2403035","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5GProtoc18"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2402761.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2402788","title":"[DRAFT] Reply LS on Robust Notification Alert for NTN-NR Rel-19","source":"Xiaomi","contact":"Yuxin MAO","contact-id":91413,"tdoctype":"LS out","for":"Approval","abstract":"To: TSG RAN, SA WG1. CC: TSG SA","secretary_remarks":"Response to S2-2401850. Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10310,"status":"not treated","reservation_date":"2024-02-16 13:05:27","uploaded":"2024-02-16 15:07:09","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"FS_5GSAT_Ph3_ARCH"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, SA WG1","Cc":"TSG SA","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2402788.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2402798","title":"Non-Allowed areas clarifications related to MPS","source":"Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Samsung","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Clarify the 3GPP access UP resource handling in non-allowed area - Clarify the exceptions for MPS - Clarify support for MPS over non-3GPP access","secretary_remarks":"Revision of S2-2401374 from S2-160AH-e. Revised to S2-2403033.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10580,"status":"revised","reservation_date":"2024-02-16 13:16:00","uploaded":"2024-02-16 19:23:14","revisionof":"S2-2401374","revisedto":"S2-2403033","release":"Rel-17","crspec":"23.501","crspecversion":"17.11.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":5308.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2402798.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.3.4.1.1, 5.16.5","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2402801","title":"Non-Allowed areas clarifications related to MPS","source":"Qualcomm Incorporated, Nokia, Nokia Shanghai Bell,Samsung","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Rel-18 mirror CR: Summary of change: - Clarify the 3GPP access UP resource handling in non-allowed area - Clarify the exceptions for MPS","secretary_remarks":"Revision of S2-2400415 from S2-160AH-e. Revised to S2-2403034.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10610,"status":"revised","reservation_date":"2024-02-16 13:17:45","uploaded":"2024-02-16 19:23:14","revisionof":"S2-2400415","revisedto":"S2-2403034","release":"Rel-18","crspec":"23.501","crspecversion":"18.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI18"}],"crnumber":4660.0,"crrevision":4.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2402801.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2402997","title":"[DRAFT] Reply LS on Clarification related to the information exposed by the 5GC to NSCE server","source":"Nokia, Nokia Shanghai-Bell","contact":"Thomas Belling","contact-id":68266,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC: SA WG6, CT WG1, CT WG4","secretary_remarks":"Response to S2-2401853. Merged into S2-2403025.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10140,"status":"merged","reservation_date":"2024-02-16 21:14:36","uploaded":"2024-02-16 22:17:46","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NSCALE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"SA WG6, CT WG1, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2402997.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403025","title":"[DRAFT] LS Reply on Clarification related to the information exposed by the 5GC to NSCE server.","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"LS on Clarification related to the information exposed by the 5GC to NSCE server.","secretary_remarks":"Revision of S2-2402056, merging S2-2402997. Revised in parallel session to S2-2403701.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10080,"status":"revised","reservation_date":"2024-03-03 17:08:51","uploaded":"2024-03-07 14:31:12","revisionof":"S2-2402056","revisedto":"S2-2403701","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NSCALE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"SA WG6, CT WG1, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2403025.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403026","title":"Clarification related to the information exposed by the 5GC to NSCE server","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add AF as new consumer and clarify the Area of Interest of the analytic Load level information . Besides, add description that NSI ID shall not be provided if the consumer NF is AF.","secretary_remarks":"Revision of S2-2402057. Revised in parallel session to S2-2403700.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10120,"status":"revised","reservation_date":"2024-03-03 17:08:51","uploaded":"2024-03-07 14:31:12","revisionof":"S2-2402057","revisedto":"S2-2403700","release":"Rel-18","crspec":"23.288","crspecversion":"18.4.0","workitem":[{"winame":"NSCALE"}],"crnumber":1061.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2403026.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403027","title":"Reply LS to GSMA on Monitoring of Encrypted 5GS Signalling Traffic","source":"SA WG2","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Response to SA","secretary_remarks":"Revision of S2-2402088. This LS OUT was approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10170,"status":"approved","reservation_date":"2024-03-03 17:08:52","uploaded":"2024-03-07 14:31:12","revisionof":"S2-2402088","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2401851","lsto":"TSG SA","Cc":"SA WG3, SA WG5","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2403027.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403028","title":"Reply LS on Support of interworking between SA WG4 RTC and IMS","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"LS out","for":"Approval","abstract":"This contribution is a LS to SA WG4 to ask questions on interworking between SA WG4 RTC and IMS.","secretary_remarks":"Revision of S2-2402385, merging S2-2402477. Revised in parallel session to S2-2403704.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10360,"status":"revised","reservation_date":"2024-03-03 17:08:52","uploaded":"2024-03-07 14:31:12","revisionof":"S2-2402385","revisedto":"S2-2403704","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"FS_eiRTCW"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"SA WG1, CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2403028.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403029","title":"V2X over MBS with SNPN","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update MBS session announcement to include the NID","secretary_remarks":"Revision of S2-2402131. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10440,"status":"agreed","reservation_date":"2024-03-03 17:08:52","uploaded":"2024-03-07 14:31:12","revisionof":"S2-2402131","revisedto":"","release":"Rel-18","crspec":"23.287","crspecversion":"18.2.0","workitem":[{"winame":"TEI18_MBS4V2X"}],"crnumber":198.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-240136","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2403029.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"3.2, 5.10.2, 5.10.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403030","title":"[DRAFT] LS on V2X over MBS with SNPN","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Inform CT WG1 that V2X over MBS with SNPN is supported, and have the approved CR attached","secretary_remarks":"Revision of S2-2402129. Noted in parallel session","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10460,"status":"noted","reservation_date":"2024-03-03 17:08:53","uploaded":"2024-03-07 14:31:12","revisionof":"S2-2402129","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"TEI18_MBS4V2X"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2403030.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403031","title":"Corrections to remove Nnef_UEId Service restrictions","source":"Ericsson, Verizon, AT&T, Vodafone, Deutsche Telekom, Dish Network, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding exposure of GPSI in the format of MSISDN in the Nnef_UEId API by mapping the UE address for trusted AF.","secretary_remarks":"Revision of S2-2402325, merging S2-2402557. Revised in parallel session to S2-2403706.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10480,"status":"revised","reservation_date":"2024-03-03 17:08:53","uploaded":"2024-03-07 14:31:12","revisionof":"S2-2402325","revisedto":"S2-2403706","release":"Rel-18","crspec":"23.501","crspecversion":"18.4.0","workitem":[{"winame":"EDGEAPP"},{"winame":" TEI18"}],"crnumber":5011.0,"crrevision":7.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2403031.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.20, 7.2.8","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403032","title":"Corrections to remove Nnef_UEId Service restrictions","source":"Ericsson, Verizon, AT&T, Vodafone, Deutsche Telekom, Dish Network, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding exposure of GPSI in the form of MSISDN in the Nnef_UEId API by mapping the UE address for trusted AFs within agreed.","secretary_remarks":"Revision of S2-2402326, merging S2-2402559. Revised in parallel session to S2-2403705.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10510,"status":"revised","reservation_date":"2024-03-03 17:08:54","uploaded":"2024-03-07 14:31:12","revisionof":"S2-2402326","revisedto":"S2-2403705","release":"Rel-18","crspec":"23.502","crspecversion":"18.4.0","workitem":[{"winame":"EDGEAPP"},{"winame":" TEI18"}],"crnumber":4509.0,"crrevision":7.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2403032.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.15.3.2.13, 4.15.10A (new), 5.2.6.27.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403033","title":"Non-Allowed areas clarifications related to MPS","source":"Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Samsung","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Clarify the 3GPP access UP resource handling in non-allowed area - Clarify the exceptions for MPS - Clarify support for MPS over non-3GPP access","secretary_remarks":"Revision of S2-2402798. Revised in parallel session to S2-2403707.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10590,"status":"revised","reservation_date":"2024-03-03 17:08:55","uploaded":"2024-03-07 14:31:12","revisionof":"S2-2402798","revisedto":"S2-2403707","release":"Rel-17","crspec":"23.501","crspecversion":"17.11.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":5308.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2403033.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.3.4.1.1, 5.16.5","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403034","title":"Non-Allowed areas clarifications related to MPS","source":"Qualcomm Incorporated, Nokia, Nokia Shanghai Bell,Samsung","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Rel-18 mirror CR: Summary of change: - Clarify the 3GPP access UP resource handling in non-allowed area - Clarify the exceptions for MPS","secretary_remarks":"Revision of S2-2402801. Revised in parallel session to S2-2403708.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10620,"status":"revised","reservation_date":"2024-03-03 17:08:56","uploaded":"2024-03-07 14:31:12","revisionof":"S2-2402801","revisedto":"S2-2403708","release":"Rel-18","crspec":"23.501","crspecversion":"18.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI18"}],"crnumber":4660.0,"crrevision":5.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2403034.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403035","title":"[DRAFT] Reply LS on Handling of regulatory prioritized services in Non-allowed areas","source":"Qualcomm","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"Provides further info on support of MPS for the questions CT WG1 asked","secretary_remarks":"Revision of S2-2402761. Revised in parallel session to S2-2403709.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10560,"status":"revised","reservation_date":"2024-03-03 17:08:56","uploaded":"2024-03-07 14:31:12","revisionof":"S2-2402761","revisedto":"S2-2403709","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5GProtoc18"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2403035.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403036","title":"Tx Profile per PC5 QoS Flow to AS layer","source":"LG Electronics, OPPO","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 3.1 - Add 'NR eTx Profile' for SL CA while removing the EN about NR Tx Profile related to backward compatibility. 5.1.2.1 - Add 'NR eTx Profile'. 5.4.1.1.3 - Clarify that the NR eTx Profile per PC5 QoS Flow is provided by the V2X layer","secretary_remarks":"Revision of S2-2402086. This CR was agreed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10650,"status":"agreed","reservation_date":"2024-03-03 17:08:57","uploaded":"2024-03-07 14:31:12","revisionof":"S2-2402086","revisedto":"","release":"Rel-18","crspec":"23.287","crspecversion":"18.2.0","workitem":[{"winame":"NR_SL_enh2-Core"}],"crnumber":196.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"SP-240106","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2403036.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"3.1, 5.1.2.1, 5.4.1.1.3, 5.11, 6.3.1, 6.3.2, 6.3.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403558","title":"[DRAFT] Reply LS on Robust Notification Alert","source":"OPPO","contact":"Peng Tan","contact-id":101478,"tdoctype":"LS out","for":"Approval","abstract":"To: TSG RAN, SA WG1. CC: TSG SA","secretary_remarks":"Revision of S2-2402394. Revised in parallel session to S2-2403702.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10200,"status":"revised","reservation_date":"2024-03-03 17:12:39","uploaded":"2024-03-07 14:31:17","revisionof":"S2-2402394","revisedto":"S2-2403702","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, SA WG1","Cc":"TSG SA","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2403558.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403700","title":"Clarification related to the information exposed by the 5GC to NSCE server","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add AF as new consumer and clarify the Area of Interest of the analytic Load level information . Besides, add description that NSI ID shall not be provided if the consumer NF is AF. A clarification that S-NSSAI is considered sensitive i","secretary_remarks":"Revision of S2-2403026. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10130,"status":"agreed","reservation_date":"2024-03-03 17:13:27","uploaded":"2024-03-07 14:31:18","revisionof":"S2-2403026","revisedto":"","release":"Rel-18","crspec":"23.288","crspecversion":"18.4.0","workitem":[{"winame":"NSCALE"},{"winame":" TEI18"}],"crnumber":1061.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-240115","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2403700.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":" 2, 6.3.1, 6.3.3A","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403701","title":"LS Reply on Clarification related to the information exposed by the 5GC to NSCE server","source":"Huawei, HiSilicon","contact":"Haiyang Sun","contact-id":79579,"tdoctype":"LS out","for":"Approval","abstract":"LS on Clarification related to the information exposed by the 5GC to NSCE server.","secretary_remarks":"Revision of S2-2403025. Revised in parallel session to S2-2403703.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10090,"status":"revised","reservation_date":"2024-03-03 17:13:28","uploaded":"2024-03-07 14:31:18","revisionof":"S2-2403025","revisedto":"S2-2403703","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NSCALE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3, SA WG3","Cc":"SA WG6, CT WG1, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2403701.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403702","title":"[DRAFT] Reply LS on Robust Notification Alert","source":"OPPO","contact":"Peng Tan","contact-id":101478,"tdoctype":"LS out","for":"Approval","abstract":"To: TSG RAN, SA WG1. CC: TSG SA","secretary_remarks":"Revision of S2-2403558. Revised to S2-2403843.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10210,"status":"revised","reservation_date":"2024-03-03 17:13:28","uploaded":"2024-03-07 14:31:18","revisionof":"S2-2403558","revisedto":"S2-2403843","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, SA WG1","Cc":"TSG SA","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2403702.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403703","title":"LS Reply on Clarification related to the information exposed by the 5GC to NSCE server.","source":"SA WG2","contact":"Haiyang Sun","contact-id":79579,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC: SA WG6, CT WG1, CT WG4, SA WG3. Attachments: TS 23.288 CR 1061","secretary_remarks":"Revision of S2-2403701. This LS OUT was approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10100,"status":"approved","reservation_date":"2024-03-03 17:13:28","uploaded":"2024-03-07 14:31:18","revisionof":"S2-2403701","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NSCALE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2401853","lsto":"CT WG3","Cc":"SA WG6, CT WG1, CT WG4, SA WG3","lsoriginalls":"TS 23.288 CR 1061","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2403703.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403704","title":"Reply LS on Support of interworking between SA WG4 RTC and IMS","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"LS out","for":"Approval","abstract":"This contribution is a LS to SA WG4 to ask questions on interworking between SA WG4 RTC and IMS.","secretary_remarks":"Revision of S2-2403028. Revised to S2-2403844.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10370,"status":"revised","reservation_date":"2024-03-03 17:13:29","uploaded":"2024-03-07 14:31:18","revisionof":"S2-2403028","revisedto":"S2-2403844","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"FS_eiRTCW"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"SA WG1, CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2403704.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403705","title":"Corrections to remove Nnef_UEId Service restrictions","source":"Ericsson, Verizon, AT&T, Vodafone, Deutsche Telekom, Dish Network, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding exposure of GPSI in the form of MSISDN in the Nnef_UEId API by mapping the UE address for trusted AFs within agreed.","secretary_remarks":"Revision of S2-2403032. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10520,"status":"agreed","reservation_date":"2024-03-03 17:13:29","uploaded":"2024-03-07 14:31:18","revisionof":"S2-2403032","revisedto":"","release":"Rel-18","crspec":"23.502","crspecversion":"18.4.0","workitem":[{"winame":"EDGEAPP"},{"winame":" TEI18"}],"crnumber":4509.0,"crrevision":8.0,"crcategory":"F","tsg_crp":"SP-240115","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2403705.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.15.3.2.13, 4.15.10A (new), 5.2.6.27.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403706","title":"Corrections to remove Nnef_UEId Service restrictions","source":"Ericsson, Verizon, AT&T, Vodafone, Deutsche Telekom, Dish Network, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding exposure of GPSI in the format of MSISDN in the Nnef_UEId API by mapping the UE address for trusted AF.","secretary_remarks":"Revision of S2-2403031. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10490,"status":"agreed","reservation_date":"2024-03-03 17:13:30","uploaded":"2024-03-07 14:31:18","revisionof":"S2-2403031","revisedto":"","release":"Rel-18","crspec":"23.501","crspecversion":"18.4.0","workitem":[{"winame":"EDGEAPP"},{"winame":" TEI18"}],"crnumber":5011.0,"crrevision":8.0,"crcategory":"F","tsg_crp":"SP-240115","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2403706.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.20, 7.2.8","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403707","title":"Non-Allowed areas clarifications related to MPS","source":"Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Samsung, Peraton Labs, CISA ECD","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Clarify the 3GPP access UP resource handling in non-allowed area - Clarify the exceptions for MPS - Clarify support for MPS over non-3GPP access","secretary_remarks":"Revision of S2-2403033. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10600,"status":"agreed","reservation_date":"2024-03-03 17:13:31","uploaded":"2024-03-07 14:31:18","revisionof":"S2-2403033","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.11.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":5308.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-240086","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2403707.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.3.4.1.1, 5.16.5","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403708","title":"Non-Allowed areas clarifications related to MPS","source":"Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Samsung, Peraton Labs, CISA ECD","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Rel-18 mirror CR: Summary of change: - Clarify the 3GPP access UP resource handling in non-allowed area - Clarify the exceptions for MPS","secretary_remarks":"Revision of S2-2403034. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10630,"status":"agreed","reservation_date":"2024-03-03 17:13:32","uploaded":"2024-03-07 14:31:18","revisionof":"S2-2403034","revisedto":"","release":"Rel-18","crspec":"23.501","crspecversion":"18.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":4660.0,"crrevision":6.0,"crcategory":"A","tsg_crp":"SP-240086","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2403708.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403709","title":"Reply LS on Handling of regulatory prioritized services in Non-allowed areas","source":"SA WG2","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachments: TS 23.501 CR 5308 (rel.17), TS 23.501 CR 4660 (rel.18)","secretary_remarks":"Revision of S2-2403035. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10570,"status":"approved","reservation_date":"2024-03-03 17:13:33","uploaded":"2024-03-07 14:31:18","revisionof":"S2-2403035","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5GProtoc18"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2306265","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2403709.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403843","title":"Reply LS on Robust Notification Alert","source":"SA WG2","contact":"Peng Tan","contact-id":101478,"tdoctype":"LS out","for":"Approval","abstract":"To: TSG RAN, SA WG1. CC: TSG SA","secretary_remarks":"Revision of S2-2403702. This LS OUT was 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-03-03 17:14:21","uploaded":"2024-03-07 14:31:19","revisionof":"S2-2403702","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2401850","lsto":"TSG RAN, SA WG1","Cc":"TSG SA","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2403843.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403844","title":"Reply LS on Support of interworking between SA WG4 RTC and IMS","source":"SA WG2","contact":"Yi Jiang","contact-id":40863,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG4. CC: SA WG1, CT WG3","secretary_remarks":"Revision of S2-2403704. 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-03-03 17:14:21","uploaded":"2024-03-07 14:31:19","revisionof":"S2-2403704","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"FS_eiRTCW"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2401857","lsto":"SA WG4","Cc":"SA WG1, CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_161_Athens_2024-02\/Docs\/S2-2403844.zip","group":"S2","meeting":"S2-161","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]