[{"name":"S2-2311939","title":"LS from RAN WG3: LS on QMC support in RRC_IDLE and RRC_INACTIVE","source":"RAN WG3","contact":"Filip Barac","contact-id":76369,"tdoctype":"LS in","for":"Action","abstract":"To ensure signalling-based and management-based QoE measurement continuity for MBS across RRC states, RAN WG3 agreed that the QoE measurement configuration information should be made available to the gNB serving the UE when the UE transits from the RRC_IDLE to RRC_CONNECTED state. In that respect, RAN WG3 is discussing whether the QoE measurement configuration information should be stored at the UE or at the AMF while the UE is in RRC_IDLE state. After the UE transits from the RRC_IDLE to RRC_CONNECTED state, this information should be provided to the serving gNB. The QoE measurement configuration information to be stored includes the following, per QoE configuration: QoE reference. The IP address or ID of the Measurement Collection Entity. The measConfigAppLayerID. Service type. QoE measurement type (s-based or m-based measurement) for MBS broadcast service. (Working Assumption): available RAN visible QoE metrics. Additional information to be stored is FFS. In addition, RAN WG3 agreed that, after a UE configured for QoE measurements transits from the RRC_IDLE to the RRC_CONNECTED state, the gNB serving of the UE should be aware of the status of MBS QoE measurement session. Action: RAN WG3 respectfully asks SA WG2 to inform RAN WG3 whether there are any technical issues with storing the above listed QoE measurement configuration information at the AMF. The QoE measurement configuration information stored at the AMF would be transparent to the AMF.","secretary_remarks":"Revision of (postponed) S2-2310127 from SA WG2#159. Responses drafted in S2-2312710, S2-2312951, S2-2313009. Final response in S2-2313777","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10150,"status":"replied to","reservation_date":"2023-10-18 06:54:12","uploaded":"2023-10-18 07:21:59","revisionof":"S2-2310127","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, SA WG2","Cc":"SA WG5, SA WG3","lsoriginalls":"R3-234745","lsreply":"S2-2313777, S2-2313777","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2311939.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311946","title":"LS from GSMA 5GMRR: LS reply to S3-233786 and S3-234296 on the introduction of the domain ipxnetwork.org and clarifications of the Outsourced SEPP and Hosted SEPP deployment scenarios","source":"GSMA 5GMRR","contact":"Pieter Veenstra","contact-id":86411,"tdoctype":"LS in","for":"Information","abstract":"GSMA NG 5GMRR thanks SA WG3 for the reply to our LS on the use of the domain ipxnetwork.org in certain GSMA deployment scenarios for 5G SA Roaming. This LS provides some background on the use of the domain ipxnetwork.org in the broader context of the GSMA defined set of 5GS deployment models for 5G SA Roaming, and responds to the questions regarding the Outsourced SEPP and Hosted SEPP deployment scenarios.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10060,"status":"noted","reservation_date":"2023-10-18 06:54:12","uploaded":"2023-10-18 16:42:50","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"TSG SA, SA WG1, SA WG2, CT WG4","lsoriginalls":"5GMRR Doc 44_36r1","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2311946.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311947","title":"LS from IETF TEAS WG: LS on a Framework for Network Slices in Networks Built from IETF Technologies","source":"IETF TEAS WG","contact":"Charles Eckel","contact-id":96384,"tdoctype":"LS in","for":"Information","abstract":"GSMA NG 5GMRR thanks SA WG3 for the reply to our LS on the use of the domain ipxnetwork.org in certain GSMA deployment scenarios for 5G SA Roaming. This LS provides some background on the use of the domain ipxnetwork.org in the broader context of the GSMA defined set of 5GS deployment models for 5G SA Roaming, and responds to the questions regarding the Outsourced SEPP and Hosted SEPP deployment scenarios.","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":"2023-10-18 06:54:13","uploaded":"2023-10-18 16:42:50","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP, TSG CT","Cc":"ITU-T SG15, O-RAN WG1, O-RAN WG6, O-RAN WG9, MEF","lsoriginalls":"LS_IETF_10Oct2023","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2311947.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311956","title":"LS from CT WG1: LS on URSP signalling improvement for recurrent events","source":"CT WG1","contact":"HyunJung Choe","contact-id":98188,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 is under discussion to improve URSP signalling for recurrent events. To be more specific, CT WG1 discussed whether extending a route selection descriptor by introducing: - multiple time windows; - for each time window, optionally a recurrence, e.g. daily, weekly, yearly. Question: CT WG1 would like to kindly check with SA WG2 whether there is any issue in improving URSP signalling for recurrent events. Action: CT WG1 respectfully asks SA WG2 to answer the question above.","secretary_remarks":"Responses drafted in S2-2312085, S2-2312087, S2-2312479, S2-2312733, S2-2312866, S2-2313174. Final response in S2-2313778","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10210,"status":"replied to","reservation_date":"2023-10-18 06:54:13","uploaded":"2023-10-18 16:42:50","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG3","lsoriginalls":"C1-237982","lsreply":"S2-2313778, S2-2313778","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2311956.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311964","title":"LS from RAN WG2: Reply LS on QMC support in RRC_IDLE and RRC_INACTIVE","source":"RAN WG2","contact":"Shuai Gao","contact-id":86061,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 thanks RAN WG3 for the LS in R3-234745 on QMC support in RRC_IDLE and RRC_INACTIVE. Based on RAN WG3 s questions in the LS, RAN WG2 gives replies as below. {. . .}","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10080,"status":"noted","reservation_date":"2023-10-18 06:54:13","uploaded":"2023-10-18 16:42:50","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"SA WG2, SA WG5, SA WG3","lsoriginalls":"R2-2311409","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2311964.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311968","title":"LS from RAN WG3: Reply LS on MBS communication service","source":"RAN WG3","contact":"Xudong Yang","contact-id":47264,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 thanks SA WG4 and SA WG5 for their LSes on QoE measurement for MBS as communication service. RAN WG3 would like to inform SA WG4, SA WG5 and RAN WG2 about the latest agreements on QoE measurement concerning MBS, including: - Following SA WG4 s response, the MBS is considered as a communication service in Rel-18. - QMC is supported for MBS broadcast and multicast. Accordingly, define new extensible IEs with multicast and broadcast in XnAP and NGAP for QMC configuration. - MBS Service Area and MBS Session ID will not be added as explicit IE for MBS related QoE configuration in Rel-18. - No need to indicate PTP transmission or PTM transmission for multicast in the QoE report in Rel-18. - Area scope handling in IDLE and INACTIVE shall wait RAN WG2 decision. - For QoE measurements for sessions carried via the MBS, the gNB serving the UE when the UE returns from RRC_IDLE to RRC_CONNECTED needs to be informed about Area Scope information, for the QoE area scope checking. - For QoE\/RVQoE measurements for sessions carried via the MBS, the gNB serving the UE when the UE returns from RRC_IDLE to RRC_CONNECTED needs to be informed about Area Scope information. - Working Assumption: UE based solution for IDLE QoE configuration retrieve in Rel-18. RAN WG3 also thinks that the above agreements may require further RAN WG2 work, which is up to RAN WG2 decision, e.g.: - Whether UE needs to be aware of whether the MBS related QoE measurement configuration information pertains to multicast or broadcast. Action: RAN WG3 kindly asks SA WG2, SA WG4 and SA WG5 to take the above agreements into account and provide feedback if necessary.","secretary_remarks":"Response drafted in S2-2312448. Postponed in parallel session.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10130,"status":"postponed","reservation_date":"2023-10-18 06:54:13","uploaded":"2023-10-18 16:42:50","revisionof":"","revisedto":"S2-2400015","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4, SA WG5, RAN WG2, SA WG2","Cc":"","lsoriginalls":"R3-235913","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2311968.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311973","title":"LS from SA WG6: LS reply on Support of multiple UEs in Northbound APIs","source":"SA WG6","contact":"shaowen zheng","contact-id":88792,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 thanks CT WG3 for its LS on providing and querying a signaling optimization to provide a list of UE(s) as the target to any API. There are examples in SEAL where providing a list of UEs as the target of an API is identified, where authorized to do so by SA WG3 specifications. Please reference the SEAL specification for specific instances. SA WG6 does not intend to exclude the possibility that other APIs can also support a list of UE(s) as input, if needed, but it may not apply to every northbound API. Therefore, SA WG6 would like to inform that providing a list of UE(s) as the target to any API needs to be considered case by case per API.","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":"2023-10-18 06:54:13","uploaded":"2023-10-18 16:42:50","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"SA WG3, SA WG2","lsoriginalls":"S6-233104","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2311973.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312085","title":"[DRAFT] Reply LS on URSP signalling improvement for recurrent events","source":"Samsung Research America","contact":"Kisuk Kweon","contact-id":80126,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: CT WG3","secretary_remarks":"Response to S2-2311956. Merged into S2-2313244","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10240,"status":"merged","reservation_date":"2023-01-11 05:01:06","uploaded":"2023-11-02 05:14:59","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5GProtoc18"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312085.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312087","title":"[DRAFT] Reply LS on URSP signalling improvement for recurrent events","source":"LG Electronics","contact":"Hong Suk Kim","contact-id":95872,"tdoctype":"LS out","for":"Approval","abstract":"Proposal for reply LS to CT WG1 regarding URSP signalling improvement for recurrent events","secretary_remarks":"Response to S2-2311956. Merged into S2-2313244","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10230,"status":"merged","reservation_date":"2023-01-11 06:38:41","uploaded":"2023-11-03 10:01:25","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5GProtoc18"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312087.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312088","title":"Discussion about LS on URSP signalling improvement for recurrent events.","source":"LG Electronics","contact":"Hong Suk Kim","contact-id":95872,"tdoctype":"discussion","for":"Discussion","abstract":"This paper discusses the LS from CT WG1 on URSP signalling improvement for recurrent events (S2-2311956\/C1-237982).","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10220,"status":"noted","reservation_date":"2023-01-11 06:42:46","uploaded":"2023-11-03 10:01:25","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5GProtoc18"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312088.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312089","title":"UE capability of supporting URSP rules with extended time window","source":"LG Electronics","contact":"Hong Suk Kim","contact-id":95872,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 4.2.2.2.2 - UE capability of supporting URSP rules with extended time window can be included in the UE Policy Container and provided to the PCF via Policy Association.","secretary_remarks":"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":"2023-01-11 06:48:15","uploaded":"2023-11-03 10:01:25","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.502","crspecversion":"18.3.0","workitem":[{"winame":"5GProtoc18"}],"crnumber":4559.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312089.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.2.2.2.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312090","title":"Support for URSP rules including extended time window for periodic services","source":"LG Electronics","contact":"Hong Suk Kim","contact-id":95872,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 6.1.2.2.5 - Description on the Time Window provided to the UE via RSD values in URSP Rules that may include multiple time windows and recurrence pattern. 6.1.2.2.2, 6.2.1.2 - Description on the UE providing the Indication of UE support for URSP rules with extended time window. 6.2.1.3 - Indication of UE support for URSP rules with extended time window added to the UE context policy control subscription information","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":"2023-01-11 06:50:39","uploaded":"2023-11-03 10:01:25","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.503","crspecversion":"18.3.0","workitem":[{"winame":"5GProtoc18"}],"crnumber":1197.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312090.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.1.2.2.2, 6.1.2.2.5, 6.2.1.2, 6.2.1.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312448","title":"[DRAFT] Reply LS on MBS communication Service","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Inform RAN WG3, SA WG5 that QMC support for MBS has been captured in TS 23.247 and 23.501","secretary_remarks":"Response to S2-2311968. Postponed in parallel session.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10140,"status":"postponed","reservation_date":"2023-02-11 15:51:07","uploaded":"2023-11-03 21:22:41","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_QoE_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, SA WG5","Cc":"RAN WG2, SA WG4, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312448.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312449","title":"QMC Support for MBS Multicast and Broadcast","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce QMC support for MBS","secretary_remarks":"Revised to S2-2313242.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10330,"status":"revised","reservation_date":"2023-02-11 15:51:15","uploaded":"2023-11-03 21:22:41","revisionof":"","revisedto":"S2-2313242","release":"Rel-18","crspec":"23.247","crspecversion":"18.3.0","workitem":[{"winame":"NR_QoE_enh-Core"},{"winame":" TEI18"}],"crnumber":346.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312449.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":true,"cn_affected":true,"clauses_affected":"2, 3.2, 6.x (new clause)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312450","title":"Support of QMC configuration information","source":"Qualcomm Incorporated, Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Adding TS 28.405 as new reference in clause 2 - Adding QMC as new abbreviation in clause 3.2 - Adding a new clause about 5GS support QMC","secretary_remarks":"Revision of S2-2310624 from S2#159 Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10350,"status":"not treated","reservation_date":"2023-02-11 15:51:16","uploaded":"2023-11-03 21:22:41","revisionof":"S2-2310624","revisedto":"S2-2400692","release":"Rel-17","crspec":"23.501","crspecversion":"17.10.0","workitem":[{"winame":"NR_QoE_enh-Core"},{"winame":" TEI18"}],"crnumber":4991.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312450.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":true,"cn_affected":true,"clauses_affected":"2; 3.2; 5.25.x (new clause)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312451","title":"Support of QMC configuration information","source":"Qualcomm Incorporated, Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Rel-18 mirror CR: Summary of change: - Adding TS 28.405 as new reference in clause 2 - Adding QMC as new abbreviation in clause 3.2 - Adding a new clause about 5GS support QMC","secretary_remarks":"Revision of S2-2310625 from S2#159 Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10360,"status":"not treated","reservation_date":"2023-02-11 15:51:27","uploaded":"2023-11-03 21:22:41","revisionof":"S2-2310625","revisedto":"S2-2400696","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"NR_QoE_enh-Core"},{"winame":" TEI18"}],"crnumber":4992.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312451.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":true,"cn_affected":true,"clauses_affected":"2; 3.2; 5.25.x (new clause)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312479","title":"[DRAFT] Reply LS on URSP signalling improvement for recurrent events","source":"MediaTek Inc.","contact":"Mehrdad Shariat","contact-id":97826,"tdoctype":"LS out","for":"Approval","abstract":"Draft reply LS on URSP signalling improvement for recurrent events","secretary_remarks":"Response to S2-2311956. Merged into S2-2313244","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10250,"status":"merged","reservation_date":"2023-02-11 18:24:37","uploaded":"2023-11-03 17:01:42","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"eUEPO"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312479.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312545","title":"Corrections to remove Nnef_UEId Service restrictions","source":"Ericsson, Verizon, AT&T, Vodafone","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-2311259 from S2#159 Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10400,"status":"not treated","reservation_date":"2023-02-11 22:27:34","uploaded":"2023-11-03 21:18:49","revisionof":"S2-2311259","revisedto":"S2-2400345","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"TEI18"},{"winame":" EDGEAPP"}],"crnumber":5011.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312545.zip","group":"S2","meeting":"S2-160","year":2023,"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-2312546","title":"Corrections to remove Nnef_UEId Service restrictions","source":"Ericsson, Verizon, AT&T, Vodafone","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-2311260 from S2#159 Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10410,"status":"not treated","reservation_date":"2023-02-11 22:27:35","uploaded":"2023-11-03 21:18:49","revisionof":"S2-2311260","revisedto":"S2-2400346","release":"Rel-18","crspec":"23.502","crspecversion":"18.3.0","workitem":[{"winame":"TEI18"},{"winame":" EDGEAPP"}],"crnumber":4509.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312546.zip","group":"S2","meeting":"S2-160","year":2023,"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-2312710","title":"[DRAFT] Reply LS on QMC support in RRC_IDLE and RRC_INACTIVE","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3. CC: RAN WG2, SA WG5, SA WG3","secretary_remarks":"Response to S2-2311939. Revised, merging S2-2312951 and S2-2313009, to S2-2313243.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10180,"status":"revised","reservation_date":"2023-03-11 07:45:33","uploaded":"2023-11-03 09:57:21","revisionof":"","revisedto":"S2-2313243","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_QoE_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"RAN WG2, SA WG5, SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312710.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312711","title":"Clarification on eDRX handling with emergency PDU Session","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that when the UE has PDU Session associated with emergency services the AMF shall not provide the UE's accepted idle mode eDRX values to NG-RAN. When the PDU Session associated with emergency services is released, the AMF provides the UE's accepted idle mode eDRX values to NG-RAN.","secretary_remarks":"Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10420,"status":"not treated","reservation_date":"2023-03-11 07:45:33","uploaded":"2023-11-03 09:57:21","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":5150.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312711.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312733","title":"[DRAFT] Reply LS on URSP signalling improvement for recurrent events","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Reply to CT WG1 on URSP signalling improvement for recurrent events.","secretary_remarks":"Response to S2-2311956. Merged into S2-2313244","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10260,"status":"merged","reservation_date":"2023-03-11 08:05:52","uploaded":"2023-11-03 09:17:36","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312733.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312866","title":"[DRAFT] Reply LS on URSP signalling improvement for recurrent events","source":"Nokia, Nokia Shanghai Bell","contact":"Srinivas Garikipati","contact-id":100437,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on URSP signalling improvement for recurrent events","secretary_remarks":"Response to S2-2311956. Merged into S2-2313244","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10270,"status":"merged","reservation_date":"2023-03-11 10:48:42","uploaded":"2023-11-03 12:42:49","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"eUEPO"},{"winame":" 5GProtoc18"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312866.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312951","title":"[DRAFT] Reply LS on QMC support in RRC_IDLE and RRC_INACTIVE","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on QMC support in RRC_IDLE and RRC_INACTIVE","secretary_remarks":"Response to S2-2311939. Merged into S2-2313243","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10160,"status":"merged","reservation_date":"2023-03-11 11:56:36","uploaded":"2023-11-03 15:43:19","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_QoE_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"RAN WG2, SA WG5, SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312951.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313003","title":"Discussion on support of QMC in SA WG2.","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"discussion","for":"Discussion","abstract":"This contribution discusses the supportive of QMC in SA WG2 for Rel-17 and Rel-18.","secretary_remarks":"Revision of S2-2310622 from S2#159 Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10370,"status":"not treated","reservation_date":"2023-03-11 12:39:20","uploaded":"2023-11-03 13:42:10","revisionof":"S2-2310622","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313003.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313009","title":"[DRAFT] Reply LS on QMC support in RRC_IDLE and RRC_INACTIVE","source":"Qualcomm Technologies Int","contact":"Juan Zhang","contact-id":73274,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3. CC: RAN WG2, SA WG5, SA WG3. Attachments: -","secretary_remarks":"Revision of S2-2310623 from S2#159. Response to S2-2311939. Merged into S2-2313243","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10170,"status":"merged","reservation_date":"2023-03-11 12:45:31","uploaded":"2023-11-03 13:42:10","revisionof":"S2-2310623","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_QoE_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"RAN WG2, SA WG5, SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313009.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313012","title":"Support of QMC configuration information","source":"Qualcomm Incorporated, Ericsson","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - adding TS 28.405 as a new reference in clause 2 - adding AMF provides QMC Configuration information to 5G-AN in N2 signalling in registration procedure in clause 4.2.2.2.2 - adding AMF provides QMC Configuration information to 5G-AN in N2 signalling in Service Request procedure in clause 4.2.3.2 - adding QMC Configuration information as UE subscription in clause 5.2.3.3.1","secretary_remarks":"Revision of S2-2310626 from S2#159 Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10380,"status":"not treated","reservation_date":"2023-03-11 12:48:08","uploaded":"2023-11-03 13:42:10","revisionof":"S2-2310626","revisedto":"S2-2400709","release":"Rel-17","crspec":"23.502","crspecversion":"17.10.0","workitem":[{"winame":"TEI18"},{"winame":" NR_QoE_enh-Core"}],"crnumber":4495.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313012.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"2; 4.2.2.2.2, 4.2.3.2, 5.2.3.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313015","title":"Support of QMC configuration information","source":"Qualcomm Incorporated, Ericsson","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Rel-18 mirror CR: Summary of change: - adding TS 28.405 as a new reference in clause 2 - adding AMF provides QMC Configuration information to 5G-AN in N2 signalling in registration procedure in clause 4.2.2.2.2 - adding AMF provides QMC Configuration information to 5G-AN in N2 signalling in Service Request procedure in clause 4.2.3.2 - adding QMC Configuration information as UE subscription in clause 5.2.3.3.1","secretary_remarks":"Revision of S2-2310632 from S2#159 Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10390,"status":"not treated","reservation_date":"2023-03-11 12:50:23","uploaded":"2023-11-03 13:42:10","revisionof":"S2-2310632","revisedto":"S2-2400712","release":"Rel-18","crspec":"23.502","crspecversion":"18.3.0","workitem":[{"winame":"TEI18"},{"winame":" NR_QoE_enh-Core"}],"crnumber":4499.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313015.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"2; 4.2.2.2.2, 4.2.3.2, 5.2.3.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313174","title":"[DRAFT] Reply LS on URSP signalling improvement for recurrent events","source":"Qualcomm Incorporated","contact":"Hong Cheng","contact-id":25668,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on URSP signaling improvement for recurrent events.","secretary_remarks":"Response to S2-2311956. Revised, merging S2-2312087, S2-2312085, S2-2312479, S2-2312733 and S2-2312866, to S2-2313244.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10280,"status":"revised","reservation_date":"2023-03-11 18:04:51","uploaded":"2023-11-03 18:29:42","revisionof":"","revisedto":"S2-2313244","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"eUEPO"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313174.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313226","title":"LS from GSMA 5GMRR: Elaborated LS reply to S3-234350 on IPX Service Hub requirements as applicable to the Modified PRINS solution","source":"GSMA 5GMRR","contact":"Pieter Veenstra","contact-id":86411,"tdoctype":"LS in","for":"Information","abstract":"GSMA NG 5GMRR thanks SA WG3 for further improving PRINS as we already welcomed in our initial reply to SA. This LS is acknowledging SA WG3 s objective for 5G SA roaming to address certain security shortcomings in 2G-4G roaming, most notably the lack of end-to-end security in the signalling between VPLMN and HPLMN. This design principle is also the ultimate objective for the work in GSMA NG 5GMRR, which seeks a solution that achieves this objective while still allowing IPX Service Hub business. We informed 3GPP in earlier LSs about the business and operational issues identified with the deployment of PRINS as defined currently in TS 33.501 (i.e., prior to the SA WG3 modified PRINS CR). GSMA NG 5GMRR continues to evaluate the technical solution of the SA WG3 CR. This LS outlines which key problems appear to remain unresolved based on the required business and technical requirements for how the GSMA defined IPX Service Hub service is used by operators.","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":"2023-06-11 12:58:05","uploaded":"2023-11-06 12:58:32","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"TSG SA, SA WG1, SA WG2, TSG CT, CT WG4","lsoriginalls":"5GMRR Doc 45_14r7","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313226.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313227","title":"LS from GSMA 5GPKI: LS to 3GPP re Monitoring of Encrypted 5GS Signalling Traffic","source":"GSMA 5GPKI","contact":"Pieter Veenstra","contact-id":86411,"tdoctype":"LS in","for":"Action","abstract":"During discussions in several GSMA groups, mobile operators have reported implementation issues with the monitoring of their 5GS signalling traffic between the NFs both on their internal SBI and the signalling via the external N32 and N9 interfaces due to the encrypted information transfer with (m)TLS, which generally applies across all the SBA interfaces. This LS seeks guidance from 3GPP on the implementation alternatives for feeding network monitoring systems in the best manner respecting the security by design principle adopted for 5GS and providing the operational staff with a real-time monitoring capability for their network surveillance tasks, traceback actions and error diagnostic research actions. Action: GSMA kindly asks SA WG2, SA WG3 and SA WG5 to take the above information into account and to comment on the above implementation options. Specific feedback on option 2 would be welcomed with technical references and guidance on implementation best practices. GSMA also welcomes 3GPP s thoughts on whether there are differences to consider per use case like intra-PLMN\/inter-PLMN, voice\/data, control\/user plane monitoring. Lastly, GSMA would be grateful if 3GPP could consider defining a standard interface for monitoring systems in future releases.","secretary_remarks":"Postponed.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10430,"status":"postponed","reservation_date":"2023-08-11 09:20:15","uploaded":"2023-11-08 09:22:33","revisionof":"","revisedto":"S2-2400021","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG5","Cc":"SA WG3","lsoriginalls":"LS Monitoring of Encrypted 5GS Signalling Traffic","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313227.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313229","title":"LS from ITU-T SG13: LS on initiation of draft new Recommendation ITU-T Y.U2USM-req-fra 'Future networks including IMT-2020: Requirements and framework for the support of UE-to-UE session management'","source":"ITU-T SG13","contact":"Marco Carugi","contact-id":31658,"tdoctype":"LS in","for":"Information","abstract":"This liaison statement informs 3GPP, ITU-R WP5D, ITU-R SG5, ITU-T SG11, SG16 and SG17 that ITU-T SG13 initiated the draft new Recommendation Y.U2USM-req-fra Future networks including IMT-2020: Requirements and framework for the support of UE-to-UE session management at the ITU-T SG13 meeting, Geneva, 23 October 3 November 2023.","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":"2023-12-11 12:45:38","uploaded":"2023-11-12 12:46:07","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG11, SG16, SG17, SA WG1, SA WG2, ITU-R WP5D, ITU-R SG5","Cc":"","lsoriginalls":"SG13-LS124","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313229.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313231","title":"LS from SA WG3: Reply LS on Monitoring of Encrypted 5GS Signalling Traffic","source":"SA WG3","contact":"Niraj Rathod","contact-id":98988,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 would like to thank GSMA 5GPKIWP for the LS on monitoring of encrypted 5GS signalling traffic. The LS asks the following questions: GSMA kindly asks SA WG2, SA WG3 and SA WG5 to take the above information into account and to comment on the above implementation options. Specific feedback on option 2 would be welcomed with technical references and guidance on implementation best practices. GSMA also welcomes 3GPP s thoughts on whether there are differences to consider per use case like intra-PLMN\/inter-PLMN, voice\/data, control\/user plane monitoring. Lastly, GSMA would be grateful if 3GPP could consider defining a standard interface for monitoring systems in future releases. SA WG3 would like to respond as follows. SA WG3 agrees with GSMA 5GPKIWP evaluation of Option 2 for its operational and security merits. SA WG3 has noted that Option 2 solution capabilities, interfaces, and techniques reside within virtualization infrastructure that is outside the scope of 3GPP. Therefore, no further analysis regarding differences per use case was done. SA WG3 does not plan to standardize operational security solution for signalling monitoring systems.","secretary_remarks":"Postponed.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10440,"status":"postponed","reservation_date":"2023-12-11 18:08:10","uploaded":"2023-11-12 18:09:06","revisionof":"","revisedto":"S2-2400023","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA 5GPKIWP","Cc":"GSMA 5GMRR, GSMA NRG, GSMA DESS, SA WG2, SA WG5","lsoriginalls":"S3-235009","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313231.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313238","title":"LS reply for LS on QMC support in RRC_IDLE and RRC_INACTIVE","source":"SA WG3","contact":"Rakshesh P. Bhatt","contact-id":96811,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 would like to thank RAN WG3 for including SA WG3 in LS R3-224745 on QMC support in RRC_IDLE and RRC_INACTIVE. SA WG3 would like to bring it to the notice of RAN WG3 that the QoE measurement configuration information, when stored in UE when it is in RRC_IDLE state, should be stored in a manner to ensure that the privacy of the user is preserved. Also the RAN node cannot be sure that the UE does not modify the data before returning it.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10090,"status":"noted","reservation_date":"2023-12-11 18:08:10","uploaded":"2023-11-12 18:09:06","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"SA WG5, SA WG2, RAN WG2","lsoriginalls":"S3-235102","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313238.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313242","title":"QMC Support for MBS Multicast and Broadcast","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce QMC support for MBS","secretary_remarks":"Revision of S2-2312449. Postponed in parallel session","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10340,"status":"postponed","reservation_date":"2023-11-16 19:54:03","uploaded":"2023-11-20 12:31:09","revisionof":"S2-2312449","revisedto":"S2-2400143","release":"Rel-18","crspec":"23.247","crspecversion":"18.3.0","workitem":[{"winame":"NR_QoE_enh-Core"},{"winame":" TEI18"}],"crnumber":346.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313242.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":true,"cn_affected":true,"clauses_affected":"2, 3.2, 6.x (new clause)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313243","title":"[DRAFT] Reply LS on QMC support in RRC_IDLE and RRC_INACTIVE","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3. CC: RAN WG2, SA WG5, SA WG3","secretary_remarks":"Revision of S2-2312710, merging S2-2312951 and S2-2313009. Revised in parallel session to S2-2313777.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10190,"status":"revised","reservation_date":"2023-11-16 19:54:04","uploaded":"2023-11-20 12:31:09","revisionof":"S2-2312710","revisedto":"S2-2313777","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_QoE_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"RAN WG2, SA WG5, SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313243.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313244","title":"[DRAFT] Reply LS on URSP signalling improvement for recurrent events","source":"Qualcomm Incorporated","contact":"Hong Cheng","contact-id":25668,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on URSP signaling improvement for recurrent events.","secretary_remarks":"Revision of S2-2313174, merging S2-2312087, S2-2312085, S2-2312479, S2-2312733 and S2-2312866. Revised in parallel session to S2-2313778.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10290,"status":"revised","reservation_date":"2023-11-16 19:54:04","uploaded":"2023-11-20 12:31:09","revisionof":"S2-2313174","revisedto":"S2-2313778","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"eUEPO"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313244.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313777","title":"Reply LS on QMC support in RRC_IDLE and RRC_INACTIVE","source":"SA WG2","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3. CC: RAN WG2, SA WG5, SA WG3","secretary_remarks":"Revision of S2-2313243. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10200,"status":"approved","reservation_date":"2023-11-16 19:58:17","uploaded":"2023-11-20 12:41:10","revisionof":"S2-2313243","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_QoE_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2311939","lsto":"RAN WG3","Cc":"RAN WG2, SA WG5, SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313777.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313778","title":"Reply LS on URSP signalling improvement for recurrent events","source":"SA WG2","contact":"Hong Cheng","contact-id":25668,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on URSP signaling improvement for recurrent events.","secretary_remarks":"Revision of S2-2313244. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10300,"status":"approved","reservation_date":"2023-11-16 19:58:17","uploaded":"2023-11-20 12:41:10","revisionof":"S2-2313244","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"eUEPO"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2311956","lsto":"CT WG1","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313778.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400012","title":"LS from CT WG4: Reply LS on Enhancement on the attribute for 5GLAN management","source":"CT WG4","contact":"RONG WANG","contact-id":87346,"tdoctype":"LS in","for":"Information","abstract":"CT WG4 thanks SA WG5 for their liaison S5-235780 (C4-234376) in which SA WG5 asks CT WG4 two questions. Q1: Please clarify which identifiers is used to support 5G LAN-type services, as stated in TS 29.510, the attribute of internalGroupId has already defined and supported by the trusted AF in Table 6.1.6.2.96-1: Definition of type TrustAfInfo. However, 5g-vn-groups is used in TS 29.503. A: SA WG2 specified that the External Group ID and Internal Group ID are used to identify the 5G VN group (refer to clause 5.29.2 of 3GPP TS23.501). For Internal Group ID, CT WG4 defined the internalGroupIdentifier to uniquely identify a 5G VN group in UDM (Please refer to clause 6.5.6.2.6 of 3GPP TS29.503). {. . .} Q2: SA WG5 would kindly ask CT WG4 to make the necessary updates to their specifications to enable 5G LAN-type services (e.g., enhancement for the AmfInfo\/SmfInfo\/NrfInfo). A: CT WG4 didn t see the need to define the 5G LAN-type service in NRF for AmfInfo\/SmfInfo\/NrfInfo, since such information is not used for node selection.","secretary_remarks":"Revision of Postponed S2-2311959 from SA WG2#160. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10090,"status":"noted","reservation_date":"2023-12-19 12:45:40","uploaded":"2023-12-19 13:12:22","revisionof":"S2-2311959","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"SA WG2","lsoriginalls":"C4-234414","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400012.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400014","title":"LS from RAN WG3: Reply LS on the usage of paging subgrouping information in RAN in case of abnormal scenario","source":"RAN WG3","contact":"Feng Han","contact-id":73581,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 thanks to CT WG1 for their LS on the usage of paging subgrouping information in RAN in case of abnormal scenario. RAN WG3 discussed the two abnormal scenarios identified by CT WG1, and concluded that the handling of the abnormal scenarios can be left to the AMF implementation for paging the UE and therefore don t need RAN WG3 action. {. . .}","secretary_remarks":"Revision of Postponed S2-2311966 from SA WG2#160. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10100,"status":"noted","reservation_date":"2023-12-19 12:45:40","uploaded":"2023-12-19 13:12:20","revisionof":"S2-2311966","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG2, RAN WG2","lsoriginalls":"R3-235883","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400014.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400019","title":"LS from RAN WG2: Reply LS on paging","source":"RAN WG2","contact":"Lili Zheng","contact-id":80379,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 would like to thank RAN WG3 for their LS on the enhancements to restricting paging in a limited area. RAN WG2 discussed Q1 and would like to provide the following answer. {. . .}","secretary_remarks":"Revision of Postponed S2-2311982 from SA WG2#160. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10110,"status":"noted","reservation_date":"2023-12-19 12:45:40","uploaded":"2023-12-19 13:12:20","revisionof":"S2-2311982","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"SA WG2","lsoriginalls":"R2-2311591","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400019.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400021","title":"LS from GSMA 5GPKI: LS to 3GPP re Monitoring of Encrypted 5GS Signalling Traffic","source":"GSMA 5GPKI","contact":"Pieter Veenstra","contact-id":86411,"tdoctype":"LS in","for":"Action","abstract":"During discussions in several GSMA groups, mobile operators have reported implementation issues with the monitoring of their 5GS signalling traffic between the NFs both on their internal SBI and the signalling via the external N32 and N9 interfaces due to the encrypted information transfer with (m)TLS, which generally applies across all the SBA interfaces. This LS seeks guidance from 3GPP on the implementation alternatives for feeding network monitoring systems in the best manner respecting the security by design principle adopted for 5GS and providing the operational staff with a real-time monitoring capability for their network surveillance tasks, traceback actions and error diagnostic research actions. Action: GSMA kindly asks SA WG2, SA WG3 and SA WG5 to take the above information into account and to comment on the above implementation options. Specific feedback on option 2 would be welcomed with technical references and guidance on implementation best practices. GSMA also welcomes 3GPP s thoughts on whether there are differences to consider per use case like intra-PLMN\/inter-PLMN, voice\/data, control\/user plane monitoring. Lastly, GSMA would be grateful if 3GPP could consider defining a standard interface for monitoring systems in future releases.","secretary_remarks":"Revision of Postponed S2-2313227 from SA WG2#160. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10320,"status":"noted","reservation_date":"2023-12-19 12:45:40","uploaded":"2023-12-19 13:12:20","revisionof":"S2-2313227","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG5","Cc":"SA WG3","lsoriginalls":"LS Monitoring of Encrypted 5GS Signalling Traffic","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400021.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400023","title":"LS from SA WG3: Reply LS on Monitoring of Encrypted 5GS Signalling Traffic","source":"SA WG3","contact":"Niraj Rathod","contact-id":98988,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 would like to thank GSMA 5GPKIWP for the LS on monitoring of encrypted 5GS signalling traffic. The LS asks the following questions: GSMA kindly asks SA WG2, SA WG3 and SA WG5 to take the above information into account and to comment on the above implementation options. Specific feedback on option 2 would be welcomed with technical references and guidance on implementation best practices. GSMA also welcomes 3GPP s thoughts on whether there are differences to consider per use case like intra-PLMN\/inter-PLMN, voice\/data, control\/user plane monitoring. Lastly, GSMA would be grateful if 3GPP could consider defining a standard interface for monitoring systems in future releases. SA WG3 would like to respond as follows. SA WG3 agrees with GSMA 5GPKIWP evaluation of Option 2 for its operational and security merits. SA WG3 has noted that Option 2 solution capabilities, interfaces, and techniques reside within virtualization infrastructure that is outside the scope of 3GPP. Therefore, no further analysis regarding differences per use case was done. SA WG3 does not plan to standardize operational security solution for signalling monitoring systems.","secretary_remarks":"Revision of Postponed S2-2313231 from SA WG2#160. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10330,"status":"noted","reservation_date":"2023-12-19 12:45:40","uploaded":"2023-12-19 13:12:20","revisionof":"S2-2313231","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA 5GPKIWP","Cc":"GSMA 5GMRR, GSMA NRG, GSMA DESS, SA WG2, SA WG5","lsoriginalls":"S3-235009","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400023.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400024","title":"LS from SA WG3: Reply LS on providing a new 5G-GUTI in the REGISTRATION REJECT message to the UE","source":"SA WG3","contact":"Saurabh Khare","contact-id":90999,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 would like to thank CT WG1 for their LS C1-236521\/S3-234448 LS on providing a new 5G-GUTI in the REGISTRATION REJECT message to the UE SA WG3 would like CT WG1 to know that SA WG3 discussed the LS in C1-236521\/S3-234448 and decided to remove the GUTI from the Registration Reject and updated the SA WG3 specs. Agreed CR is available on the S3 235045.","secretary_remarks":"Revision of Postponed S2-2313232 from SA WG2#160. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10120,"status":"noted","reservation_date":"2023-12-19 12:45:40","uploaded":"2023-12-19 13:12:20","revisionof":"S2-2313232","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG2","lsoriginalls":"S3-235071","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400024.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400031","title":"LS from ETSI TC CYBER: Comments from ETSI TC CYBER on GSMA Solutions for Monitoring of Encrypted 5GS Signaling Traffic","source":"ETSI TC CYBER","contact":"Alex Leadbeater","contact-id":71428,"tdoctype":"LS in","for":"Information","abstract":"TC CYBER has observed the Liaison Statement S3 234467 from GSMA to SA WG3 and the corresponding reply S3 235009. A number of groups within ETSI, have invested large efforts into studies and normative work on the topic of inspection of encrypted traffic and would like to provide some comments for GSMA consideration.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10350,"status":"noted","reservation_date":"2023-12-19 12:45:40","uploaded":"2023-12-20 16:45:40","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA FASG, GSMA 5GMRR, GSMA 5GPKIWP","Cc":"SA WG2, SA WG3","lsoriginalls":"CYBER(23)35d008r1","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400031.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400032","title":"LS from GSMA OPG: LS reply on LS on MSISDN exposure to trusted AF","source":"GSMA OPG","contact":"Magnus Olsson","contact-id":74324,"tdoctype":"LS in","for":"Information","abstract":"GSMA OPG would like to thank SA WG2 for the LS on MSISDN exposure to trusted AF (OPG_157_Doc_03_S2-2311893). GSMA OPG have consulted GSMA OPAG and would like to provide the following feedback: The API in GSMA PRD OPG.03 section 3 tries to solve a similar problem. i.e., how to obtain the subscriber s identity based on their public IP address. The problem seems real: many of the APIs defined in CAMARA rely on the IP address to refer to the subscriber. For the realisation of that API, different solutions are provided in section 3.2. because there seems to be no one size fits all approach that would work on all networks. i.e., regardless of the way in which NAT is realised, etc. The solution proposed by SA WG2 solution is useful. as may be brought by a 3GPP API removing the restriction on sharing the MSISDN to trusted AFs. When defined, it would take a while for such a solution to be generally available. It requires universal adoption of the NEF, the API without the restriction and the underlying core network functions to realise it. It can thus not replace, the existing solutions defined in GSMA PRD OPG.03 section 3.2 in the short term. When defined by 3GPP, initially OPAG could refer to 3GPP s API as an additional solution in GSMA PRD OPG.03 section 3.2. i.e., as a solution that operators could adopt when their network (i.e., NEF, core network functions, etc.) supports it. Once universally available, such an API could replace the API defined in GSMA PRD OPG.03 section 3. GSMA OPG kindly ask SA WG2 and SA WG3 to take the above information into consideration.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10360,"status":"noted","reservation_date":"2023-12-19 12:45:40","uploaded":"2023-12-20 16:45:40","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3","Cc":"SA WG6","lsoriginalls":"OPG_159_Doc_03","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400032.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400033","title":"LS from ITU-T SG13: LS on initiation of the new work item ITU-T Y.IMT2020-EE-CFW 'Requirements and capability framework of IMT-2020 networks and beyond from the energy efficiency perspective'","source":"ITU-T SG13","contact":"Marco Carugi","contact-id":31658,"tdoctype":"LS in","for":"Information","abstract":"This Liaison Statement informs about the initiation of the new work item 'Requirements and capability framework of IMT-2020 networks and beyond from the energy efficiency perspective' at the SG13 meeting, Geneva, 23 October - 3 November 2023.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10030,"status":"noted","reservation_date":"2023-12-19 12:45:40","uploaded":"2023-12-20 16:45:41","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG5, SG11, ETSI NFV, SA WG2, SA WG5","Cc":"","lsoriginalls":"SG13-LS125","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400033.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400035","title":"LS from GSMA UPG: LS from NG to 3GPP SA3-LI on Lawful Interception of IMS Data Channel","source":"GSMA UPG","contact":" Anonymous","contact-id":4132,"tdoctype":"LS in","for":"Information","abstract":"Release 16 of 3GPP TS 26.114 introduced IMS data channel. It defines 'data' media component for real-time interaction which is transported using SCTP (IETF RFC 4960) over DTLS (IETF RFC 8261) as described by WebRTC data channels (IETF RFC 8831). Now some Communication Service Providers are performing IMS data channel service trials and might be planning commercial deployment. However, it is still not clear how the Lawful Interception of IMS data channel media is performed in HPMN or VPMN. GSMA IR.65 states that the general principle should be observed that the local regulation needs to be supported , and during the work on GSMA NG.129 white paper it was confirmed that this principle is applicable to the IMS data channel. Therefore where required the local authority in VPMN (or HPMN) SHALL be able to intercept the IMS data channel content. Not being able to do so will effectively block the commercial launch of the related services due to lack of the compliance to the local laws. According to clause 4.2 of 3GPP TS 26.114, IMS data channel use SCTP (RFC 4960) over DTLS (RFC 8261) protocol stack detailed in IETF RFC 8831. It means that the communication contents transferred over IMS data channels, including a bootstrap data channels and application data channels, are encrypted on the end to end basis both in roaming and non-roaming scenarios. GSMA IR.65 that states It should be mentioned that in current deployments typically only SIP signalling is encrypted in VoLTE. The actual RTP voice media is only encrypted over the air and is thus not encrypted when passed from the eNodeB to the SGW in the EPC . In the similar spirit section 20.1.1 of 3GPP TS 33.107, it states that A condition required for the operation of S8HR LI is that the IMS signalling messages and the media packets are not encrypted at S-GW\/BBIFF. Neither of those clearly answers the question how to deal with new IMS media type data which is end to end encrypted. Section 6.2.1.5 of GSMA PRD NG.134 states 'The data channels are subject to the Lawful Interception requirements based on the national regulations. The technical solution will be profiled in this document once SA WG3 work is completed'","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10040,"status":"noted","reservation_date":"2023-12-19 12:45:40","uploaded":"2023-12-20 16:45:41","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3-LI","Cc":"SA WG2, SA WG3","lsoriginalls":"UPG08_127 LS from NG to 3GPP SA3-LI on Lawful Inte","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400035.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400037","title":"Reply LS to GSMA on Monitoring of Encrypted 5GS Signalling Traffic","source":"TSG SA","contact":" Anonymous","contact-id":4132,"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":"Need co-ordinated response via TSG SA. Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10340,"status":"postponed","reservation_date":"2023-12-19 12:45:40","uploaded":"2023-12-20 16:45:41","revisionof":"","revisedto":"S2-2401851","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":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400037.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400038","title":"LS from TSG SA: LS on collaboration and alignment of 3GPP defined application enablers with GSMA Open Gateway","source":"TSG SA","contact":"Suresh Chitturi","contact-id":61003,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 specified Application Enablement standards including, service frameworks (CAPIF, EDGEAPP, SEAL services including NSCE, ADAE, SEALDD) and vertical application enabler architectures (V2XAPP, UASAPP, 5GMARCH, PINAPP), to enable various industry vertical applications over 3GPP networks. For a quick overview, you can refer to Application Enablement Standards in 3GPP, and SA WG6 R18 5G Critical Communications and Application Enablement Standards. You may also find additional information on the SA WG6 page . . .","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10060,"status":"noted","reservation_date":"2023-12-19 12:45:40","uploaded":"2023-12-20 16:45:41","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA Open Gateway","Cc":"GSMA OPG, SA WG2, SA WG5, SA WG6, TSG CT","lsoriginalls":"SP-231778","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400038.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400039","title":"LS from CT WG1: LS on URSP handling for UE configured with EHPLMN list","source":"CT WG1","contact":"Osama Lotfallah","contact-id":84634,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 would like to inform you about the attached agreed CRs to handle URSP and mapped S-NSSAIs for UE configured with EHPLMN list. Action: CT WG1 asks SA WG2 and CT WG3 to take the above information into consideration.","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":"2023-12-19 12:45:41","uploaded":"2023-12-20 16:45:41","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG3","Cc":"","lsoriginalls":"C1-239320","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400039.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400046","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":"Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10140,"status":"postponed","reservation_date":"2023-12-19 12:45:41","uploaded":"2023-12-20 16:45:42","revisionof":"","revisedto":"S2-2401853","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":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400046.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400052","title":"LS from RAN WG2: LS to SA2 on Tx profile for SL CA","source":"RAN WG2","contact":"Li Zhao","contact-id":97789,"tdoctype":"LS in","for":"Action","abstract":"Tx profile was agreed to be introduced to solve the backward compatible issue for broadcast and groupcast of SL CA. RAN WG2 discussed the granularity of Tx profile and agreed that upper layer should indicate the Tx profile per QoS flow to AS layer. Action: RAN WG2 respectfully asks SA WG2 to take the above agreement into account in the related work.","secretary_remarks":"Response drafted in S2-2400113. Final response in S2-2401581","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10260,"status":"replied to","reservation_date":"2023-12-19 12:45:41","uploaded":"2023-12-20 16:45:43","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1","lsoriginalls":"R2-2313622","lsreply":"S2-2401581","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400052.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400053","title":"LS from RAN WG2: LS to SA WG2 on QoS to Carrier Mapping for SL CA","source":"RAN WG2","contact":"Martino Freda","contact-id":92683,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 has discussed how the QoS flow to carrier mapping provided by upper layers is ensured by the AS layer. RAN WG2 agreed that transmissions of data from a SLRB can occur only on the intersection of the carriers that are allowed among the QoS flows mapped to that SLRB. As a consequence of this agreement, it is RAN WG2 s understanding that upper layers and network ensure appropriate intersection of carriers for the QoS flows mapped to the same SLRB. Action: RAN WG2 respectfully asks SA WG2 to take the above agreement into account in SA WG2 work.","secretary_remarks":"Response drafted in S2-2401247. Final response in S2-2401579","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10230,"status":"replied to","reservation_date":"2023-12-20 16:43:11","uploaded":"2023-12-20 16:45:43","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG6","lsoriginalls":"R2-2313623","lsreply":"S2-2401579","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400053.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400062","title":"LS from RAN WG3: Reply LS on the user consent for trace reporting","source":"RAN WG3","contact":"Angelo Centonza","contact-id":45800,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 thanks SA WG3 for the answers provided in their LS on user consent for trace reporting. The answers provided by SA WG3 are listed below: A1: The existing user consent mechanism is only intended for internal use within the 3GPP operators (controllers) domain for collection MDT measurements at the RAN and reporting them to the Trace Collection Entity. A2: Further, user consent is given to the operator so that the 3GPP system can be provisioned\/configured based on the operator-subscriber agreed permissions stored in UDM to make it feasible for the 3GPP system to comply with local laws and regulations. Whether the RAN needs to check if user consent is required for a specific type of information\/data of a subscriber for a particular purpose can be configured by the OAM. Such configuration is done based on local regulations, which is likely to change infrequently. From the UDM, per UE basis, the RAN receives the yes\/no information on whether a user has given consent for the information\/data configured by the OAM to be used by the RAN for a particular purpose. The steps described above include the method detailed in Q2. Hence the method is feasible. RAN WG3 would like to inform SA WG3, SA WG2 and SA WG5 that the requirements on user consent have been taken into account 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. RAN WG3 converged to a solution on user consent that follows the steps below: For Management Based MDT: Step 1: The OAM configures the RAN with information stating whether user consent is required\/not required for a specific type of information\/data of a subscriber for a particular purpose Step 2: If user consent is available for a UE, the RAN receives from the AMF the Management Based MDT PLMN List IE, which indicates that the UE gave consent for the measurements subject to user consent. Step 3: Upon the reception of a Management Based MDT configuration from OAM, the RAN can, according to the OAM configured information, perform the following: - If the configured MDT data are subject to user consent, select UEs on the basis of the received user consent information represented by the Management Based MDT PLMN List IE. - If the configured MDT data are not subject to user consent, the RAN does not need to consider user consent when selecting UEs and it can select UEs including those for which the Management Based MDT PLMN List was not received. Step 4: Following legacy behavior, the RAN configures the UE with a plmn-IdentityList derived from the MDT PLMN List contained in the Management Based MDT Activation signalled by the OAM to the NG-RAN For Signalling Based MDT: Step 1: The OAM configures the AMF with information stating whether user consent is required\/not required for a specific type of information\/data of a subscriber for a particular purpose Step 2: The OAM signals to the AMF a Signalling Based MDT configuration - If the configured MDT data are subject to user consent, and if the AMF determines (from data acquired from the UDM) that user consent is available for the UE, the AMF shall trigger a Trace Activation for the UE. - If the configured MDT data are not subject to user consent, the AMF shall trigger a Trace Activation, including the Signalling Based MDT PLMN List IE, even if user consent is not available for the UE. Step 3: Following legacy behavior, the NG-RAN will configure the UE with a plmn-IdentityList derived from the Signalling Based MDT PLMN List received from the AMF. Technically endorsed CRs are attached. Action: RAN WG3 kindly asks SA WG5 and SA WG2 to provide feedback on the solution described above. If the solution is feasible, RAN WG3 kindly asks SA WG5 and SA WG2 to take the above progress into account and to amend their specifications so to align with the guidance provided by SA WG3 and with the solution agreed by RAN WG3.","secretary_remarks":"Responses drafted in S2-2400421, S2-2400747, S2-2400803. Final response in S2-2401575","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10160,"status":"replied to","reservation_date":"2023-12-20 16:43:11","uploaded":"2023-12-20 16:45:39","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG5, SA WG3","Cc":"RAN WG2, TSG RAN, SA WG1","lsoriginalls":"R3-237964","lsreply":"S2-2401575","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400062.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400067","title":"LS from SA WG1: Reply LS on requirements for slice-based PLMN selection","source":"SA WG1","contact":"Kurt Bischinger","contact-id":26063,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 thank CT WG1 for their LS S1-233012 asking SA WG1 for clarification and guidance with regards to the requirement related to slice-based PLMN selection as defined in 3GPP TS 22.261 as follows: For a roaming UE activating a service\/application requiring a network slice not offered by the serving network but available in the area from other network(s), the HPLMN shall be able to provide the UE with prioritization information of the VPLMNs with which the UE may register for the network slice. SA WG1 has agreed to remove the requirement in Rel. 18 and will coordinate with CT WG1 about any future service requirements on this topic.","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":"2023-12-20 16:43:11","uploaded":"2023-12-20 16:45:40","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG2, TSG CT, TSG SA","lsoriginalls":"S1-233272","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400067.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400070","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":"Response drafted in S2-2400591. Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10210,"status":"postponed","reservation_date":"2023-12-20 16:43:11","uploaded":"2023-12-20 16:45:40","revisionof":"","revisedto":"S2-2401857","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-2402385","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400070.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400071","title":"LS from SA WG5: Further Reply LS on Enhancement on the attribute for 5GLAN management","source":"SA WG5","contact":"Yushuang Hu","contact-id":96973,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks CT WG4 for the reply LS on Enhancement on the attribute for 5GLAN management. SA WG5 would like to provide CT WG4 with the following information. Firstly, purely appreciate for the clarification on the usage of the attribute internalGroupId and 5g-vn-groups. SA WG5 has been already working on management aspect of 5GLAN in R18 and has specified new performance measurement, related KPIs and attributes at the VN group level in TS 28.552 and TS 28.554. The consistent usage of Internal Group ID in different group of 3GPP can be more convenient for understanding. Secondly, SA WG5 also intends to specify the enhanced NRM to support the management of 5G LAN-type services, including the configuration management of 5G NF. Based on your feedback that 'CT WG4 didn't see the need to define the 5G LAN-type service in NRF for AmfInfo\/SmfInfo\/NrfInfo, since such information is not used for node selection.', and the further information issued as follows: The definition of AmfInfo\/SmfInfo\/NrfInfo\/TrustAfInfo in TS29.510 is used for node selection but not for identifying a 5G VN group. Since there is a 1:1 mapping between a 5G VN group and the combination of SNSSAI and DNN, the SNSSAI and DNN will be used for the SMF\/NRF selection in serving a 5G VN group member. That is why CT WG4 didn't define any 5G VN group-related information in SmfInfo\/NrfInfo. AMF node selection in serving a 5G VN group member is based on SNSSAI. The AmfInfo is only used by other SBI-based NF instances (e.g., SMF) to select AMF. So, CT WG4 does not need to define any 5G VN group-related information in AmfInfo. This means that the existing NFInfo, SNSSAI, and DNN may already support the management of 5G LAN-type services. Therefore, SA WG5 will follow the conclusion of CT WG4 and complete the related work in R18 without any enhanced NRM for 5GLAN management.","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":"2023-12-20 16:43:11","uploaded":"2023-12-20 16:45:40","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"SA WG2","lsoriginalls":"S5-238099","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400071.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400073","title":"LS from SA WG5: LS on the progress update of AI\/ML Management specifications in SA WG5","source":"SA WG5","contact":"Hassan Al-kanani","contact-id":47274,"tdoctype":"LS in","for":"Action","abstract":"SA WG5 has been following the progress of study on Artificial Intelligence (AI) \/ Machine Learning (ML) for NR air interface (FS_NR_AIML_air) as documented in TR38.843, RAN intelligence function (NR_AIML_NGRAN-Core) support for AI\/ML-based services (AIMLsys) as documented in TS 23.288 and would like to draw your attention to the relevant work that SA WG5 has been conducting on the specifications of AI\/ML management, addressing OAM support for the AI\/ML features and capabilities in 5GS including the RAN domain. The study on management of AI\/ML has been completed and documented in TR28.908 while the corresponding Rel-18 normative specifications are currently progressing and being documented in TS28.105. The Release 18 version of the 3GPP TS 28.105 is planned to be completed and published during the first quarter of 2024. {. . .} Action: SA WG5 looks forward to cooperating with and kindly request RAN WG1, RAN WG2, RAN WG3 and SA WG2 to take the above information into consideration for their work and provide SA WG5 management and orchestration related requirements to support AI\/ML capabilities in the network if any.","secretary_remarks":"Moved to 4.1 as relates to several studies\/work items: AIMLsys, eNA_Ph3 and FS_AIML_CN. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10150,"status":"noted","reservation_date":"2023-12-20 16:43:11","uploaded":"2023-12-20 16:45:40","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG1, RAN WG2, RAN WG3, SA WG2","Cc":"SA WG1, TSG SA, TSG RAN","lsoriginalls":"S5-238107","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400073.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400075","title":"LS from IETF TSVWG: LS on draft-ietf-tsvwg-ecn-encap-guidelines and draft-ietf-tsvwg-rfc6040updateshim","source":"IETF TSVWG","contact":" Anonymous","contact-id":4132,"tdoctype":"LS in","for":"Information","abstract":"The IETF Transport and Services Working Group (TSVWG) [1] has prepared the following drafts and included previous inputs from the 3rd Generation Partnership Project (3GPP) on topics relating to Explicit Congestion Notification (ECN): draft-ietf-tsvwg-ecn-encap-guidelines [2] draft-ietf-tsvwg-rfc6040update-shim [3] These drafts have been revised in IETF Review and are now thought ready to be published. The drafts mention the GPRS Tunnelling Protocol (GTP), which is under the control of 3GPP, and clarify that GTP is in scope of RFC6040. The drafts are currently in the RFC-editor queue. 3GPP was involved at the start of the process; therefore, TSVWG thought it may be useful for 3GPP to be notified of the conclusion.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10050,"status":"noted","reservation_date":"2023-12-22 08:31:53","uploaded":"2023-12-22 08:32:10","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG4, CT WG1, CT WG3, CT WG4, RAN WG2","Cc":"","lsoriginalls":"Liaison_from_IETF_21Dec2023","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400075.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400113","title":"[DRAFT] Reply LS on Tx profile for SL CA","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"LS out","for":"Approval","abstract":"[Draft] Reply LS on Tx profile for SL CA","secretary_remarks":"Response to S2-2400052. r00 + clean up agreed. Revised to S2-2401581.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10270,"status":"revised","reservation_date":"2024-09-01 08:34:51","uploaded":"2024-01-12 10:05:26","revisionof":"","revisedto":"S2-2401581","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_SL_enh2-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400113.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400114","title":"Tx Profile per PC5 QoS Flow to AS layer","source":"LG Electronics","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":"r02 Agreed. Revised to S2-2401580, merging S2-2400505","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10290,"status":"revised","reservation_date":"2024-09-01 08:36:03","uploaded":"2024-01-12 10:05:26","revisionof":"","revisedto":"S2-2401580","release":"Rel-18","crspec":"23.287","crspecversion":"18.2.0","workitem":[{"winame":"NR_SL_enh2-Core"}],"crnumber":196.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400114.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","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-2400188","title":"Support for periodicity in the Route Selection Description","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The PCF may decide that a Route Selection Description applies periodically, i.e., it applies at repeated time intervals. In such a case, the PCF may provide a Route Selection Description applicable at the first time window, then the PCF","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10450,"status":"noted","reservation_date":"2024-10-01 19:43:58","uploaded":"2024-01-12 20:49:26","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.503","crspecversion":"18.4.0","workitem":[{"winame":"TEI18"},{"winame":" eUEPO"}],"crnumber":1239.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400188.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400345","title":"Corrections to remove Nnef_UEId Service restrictions","source":"Ericsson, Verizon, AT&T, Vodafone, Deutsche Telekom, Dish Network","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 (unhandled) S2-2312545. CC#3: r04 endorsed. r04 Agreed. Revised to S2-2401582.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10370,"status":"revised","reservation_date":"2024-11-01 14:52:02","uploaded":"2024-01-12 20:39:29","revisionof":"S2-2312545","revisedto":"S2-2401582","release":"Rel-18","crspec":"23.501","crspecversion":"18.4.0","workitem":[{"winame":"TEI18"},{"winame":" EDGEAPP"}],"crnumber":5011.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400345.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400346","title":"Corrections to remove Nnef_UEId Service restrictions","source":"Ericsson, Verizon, AT&T, Vodafone, Deutsche Telekom, Dish Network","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 (unhandled) S2-2312546. CC#3: r04 was endorsed. r04 Agreed. Revised to S2-2401583.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10390,"status":"revised","reservation_date":"2024-11-01 14:52:03","uploaded":"2024-01-12 20:39:29","revisionof":"S2-2312546","revisedto":"S2-2401583","release":"Rel-18","crspec":"23.502","crspecversion":"18.4.0","workitem":[{"winame":"TEI18"},{"winame":" EDGEAPP"}],"crnumber":4509.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400346.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","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-2400421","title":"[DRAFT] Reply LS on the user consent for trace reporting","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Provides SA WG2 answer related to endorsed solution provided in the incoming LS","secretary_remarks":"Response to S2-2400062. r00 + clean up agreed. Revised to S2-2401578, merging S2-2400747 and S2-2400803","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10170,"status":"revised","reservation_date":"2024-11-01 19:28:16","uploaded":"2024-01-12 20:56:19","revisionof":"","revisedto":"S2-2401578","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_ENDC_SON_MDT_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, SA WG5","Cc":"SA WG1, RAN, RAN WG2, SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400421.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400505","title":"Tx Profile for SL CA","source":"OPPO","contact":"Fei Lu","contact-id":87831,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: An extended Tx profile is introduced to indicate whether the service supports SL CA. V2X layer provides the Tx profile to the AS layer per QoS flow.","secretary_remarks":"Merged into S2-2401580","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10310,"status":"merged","reservation_date":"2024-12-01 02:12:45","uploaded":"2024-01-12 13:56:01","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.287","crspecversion":"18.2.0","workitem":[{"winame":"NR_SL_enh2"}],"crnumber":197.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400505.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","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","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400525","title":"UE MSISDN exposure to trusted AF","source":"Samsung","contact":"Kisuk Kweon","contact-id":80126,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Modification on AF specific UE ID retrieval procedures to support providng the MSISDN","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10430,"status":"noted","reservation_date":"2024-12-01 02:16:37","uploaded":"2024-01-12 04:24:54","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.502","crspecversion":"18.4.0","workitem":[{"winame":"TEI18"}],"crnumber":4692.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400525.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.15.10, 5.2.6.27","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400526","title":"UE MSISDN exposure to trusted AF","source":"Samsung","contact":"Kisuk Kweon","contact-id":80126,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Modification on AF specific UE ID retrieval procedures to support providng the MSISDN","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-12-01 02:19:34","uploaded":"2024-01-12 04:24:54","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.501","crspecversion":"18.4.0","workitem":[{"winame":"TEI18"}],"crnumber":5242.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400526.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.8.2.17, 5.20, 7.2.8","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400591","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":"Response to S2-2400070. Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10220,"status":"postponed","reservation_date":"2024-12-01 04:57:00","uploaded":"2024-01-12 05:08:49","revisionof":"","revisedto":"S2-2402477","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"CT WG3, SA WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400591.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400747","title":"[DRAFT] LS on the user consent for trace reporting","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"[draft] LS on the user consent for trace reporting","secretary_remarks":"Response to S2-2400062. Merged into S2-2401578","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10190,"status":"merged","reservation_date":"2024-12-01 08:40:06","uploaded":"2024-01-12 16:16:30","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_ENDC_SON_MDT_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"RAN WG3, SA WG1, SA WG5, CT WG5, RAN, RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400747.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400803","title":"[DRAFT] Reply LS on the user consent for trace reporting","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"It is proposed to reply the LS on the user consent for trace reporting R3-237964","secretary_remarks":"Response to S2-2400062. Merged into S2-2401578","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10200,"status":"merged","reservation_date":"2024-12-01 09:52:15","uploaded":"2024-01-12 15:39:27","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_ENDC_SON_MDT_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, SA WG3, SA WG5","Cc":"SA WG1, RAN, RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400803.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2401247","title":"[DRAFT] Reply LS on QoS to Carrier Mapping for SL CA","source":"Qualcomm Incorporated","contact":"Hong Cheng","contact-id":25668,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to LS to SA WG2 on QoS to Carrier Mapping for SL CA (R2-2313623\/S2-2400053).","secretary_remarks":"Response to S2-2400053. r05 Agreed. Revised to S2-2401579.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10240,"status":"revised","reservation_date":"2024-12-01 17:38:50","uploaded":"2024-01-12 21:34:25","revisionof":"","revisedto":"S2-2401579","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_SL_enh2-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"SA WG6","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2401247.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2401576","title":"[DRAFT] LS on limited MSISDN exposure","source":"Ericsson","contact":"Magnus Olsson","contact-id":37766,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3. Attachments: 23.501CR5011r04, 23.502CR4509r04","secretary_remarks":"Created at CC#3","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10410,"status":"revised","reservation_date":"2024-01-28 14:03:29","uploaded":"2024-01-31 09:11:14","revisionof":"","revisedto":"S2-2401649","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2401576.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2401578","title":"Reply LS on the user consent for trace reporting","source":"SA WG2","contact":"Qian Chen","contact-id":83135,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3, SA WG5. CC: SA WG1, SA WG3, TSG RAN, RAN WG2","secretary_remarks":"Revision of S2-2400421r00 + clean up, merging S2-2400747 and S2-2400803. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10180,"status":"approved","reservation_date":"2024-01-28 14:03:29","uploaded":"2024-01-30 19:11:24","revisionof":"S2-2400421","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_ENDC_SON_MDT_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2400062","lsto":"RAN WG3, SA WG5","Cc":"SA WG1, SA WG3, TSG RAN, RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2401578.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2401579","title":"Reply LS on QoS to Carrier Mapping for SL CA","source":"SA WG2","contact":"Hong Cheng","contact-id":25668,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2. CC: CT WG1, SA WG6","secretary_remarks":"Revision of S2-2401247r05. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10250,"status":"approved","reservation_date":"2024-01-28 14:03:30","uploaded":"2024-01-30 19:11:24","revisionof":"S2-2401247","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_SL_enh2-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2400053","lsto":"RAN WG2","Cc":"CT WG1, SA WG6","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2401579.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2401580","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-2400114r02, merging S2-2400505. Approved. Revised at S2#161 in S2-2402086","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10300,"status":"revised","reservation_date":"2024-01-28 14:03:30","uploaded":"2024-01-31 09:11:14","revisionof":"S2-2400114","revisedto":"S2-2402086","release":"Rel-18","crspec":"23.287","crspecversion":"18.2.0","workitem":[{"winame":"NR_SL_enh2-Core"}],"crnumber":196.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2401580.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","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-2401581","title":"Reply LS on Tx profile for SL CA","source":"SA WG2","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"LS out","for":"Approval","abstract":"[Draft] Reply LS on Tx profile for SL CA","secretary_remarks":"Revision of S2-2400113r00 + clean up. 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-01-28 14:03:31","uploaded":"2024-01-30 19:11:24","revisionof":"S2-2400113","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_SL_enh2-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2400052","lsto":"RAN WG2","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2401581.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2401582","title":"Corrections to remove Nnef_UEId Service restrictions","source":"Ericsson, Verizon, AT&T, Vodafone, Deutsche Telekom, Dish Network, Nokia","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-2400345r04. Endorsed. Revised at S2#161 in S2-2402325","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10380,"status":"revised","reservation_date":"2024-01-28 14:03:31","uploaded":"2024-01-31 09:11:14","revisionof":"S2-2400345","revisedto":"S2-2402325, S2-2402557","release":"Rel-18","crspec":"23.501","crspecversion":"18.4.0","workitem":[{"winame":"TEI18"},{"winame":" EDGEAPP"}],"crnumber":5011.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2401582.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","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-2401583","title":"Corrections to remove Nnef_UEId Service restrictions","source":"Ericsson, Verizon, AT&T, Vodafone, Deutsche Telekom, Dish Network, Nokia","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-2400346r04. Endorsed. Revised at S2#161 in S2-2402326","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10400,"status":"revised","reservation_date":"2024-01-28 14:03:31","uploaded":"2024-01-31 09:11:14","revisionof":"S2-2400346","revisedto":"S2-2402326, S2-2402559","release":"Rel-18","crspec":"23.502","crspecversion":"18.4.0","workitem":[{"winame":"TEI18"},{"winame":" EDGEAPP"}],"crnumber":4509.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2401583.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","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-2401649","title":"LS on limited MSISDN exposure","source":"SA WG2","contact":"Magnus Olsson","contact-id":37766,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3. Attachments: Draft 23.502CR4509\/S2-2400346r04","secretary_remarks":"Revision of S2-2401576r02 + clean up. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10420,"status":"approved","reservation_date":"2024-01-30 06:30:56","uploaded":"2024-01-30 19:11:24","revisionof":"S2-2401576","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"EDGEAPP"},{"winame":" TEI18"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2401649.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]