[{"name":"S2-2405852","title":"LS from ETSI ISG MEC: ETSI ISG MEC publication of MEC Phase 3 deliverables","source":"ETSI ISG MEC","contact":"Dario Sabella","contact-id":70636,"tdoctype":"LS in","for":"Information","abstract":"ETSI ISG MEC would like to inform that the group has recently completed the publication of all deliverables related to the MEC Phase 3 work (2021-2023). This has been a major endeavour from the ISG, marking the finalization of a complete set of specifications, in alignment also with other standard bodies and industry groups. The MEC Phase 3 work focused on architectural enhancements, support for federation, application package formats, new APIs, maintenance of existing APIs and other IaaS\/PaaS deliverables, as well as normative work on MEC testing and compliance. MEC Phase 3 also included studies on MEC security, on MEC enterprise deployments, on MEC application slices. Also, the group is already starting some Phase 4 work (2024-2026) with relevant work items paving the way for the next evolution of MEC standards (e.g. MEC 043 on Abstracted APIs for Industries, MEC 036 Study on Constrained Devices, MEC 047 on Distributed Edge Network, MEC-DEC49 on Edge Native Connector , and more to come). Actions: Please take into account the above information provided by ETSI ISG MEC.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10100,"status":"noted","reservation_date":"2024-04-24 06:41:41","uploaded":"2024-04-24 06:43:30","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6, CT WG3, SA WG2, GSMA OPG, GSMA OPAG, LF CAMARA, 5GFF, 5GAA, 5G-ACIA, CCSA, TSDSI, ETSI SDG TFS, ETSI SDG OCF, TM Forum","Cc":"ETSI NFV, ETSI ZSM, ETSI TC CYBER, oneM2M, ETSI TC SmartM2M, ETSI ISG PDL, ETSI ISG QKD, ITU-T SG13, ITU-T SG16, ITU-T SG20, SA WG3, CT WG1","lsoriginalls":"MEC(24)000156r2","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2405852.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405853","title":"LS from ETSI ISG MEC: ETSI ISG MEC publication of MEC Phase 3 specifications related to MEC federation","source":"ETSI ISG MEC","contact":"Dario Sabella","contact-id":70636,"tdoctype":"LS in","for":"Information","abstract":"ETSI ISG MEC would like to inform GSMA OPG and GSMA OPAG that the group has recently completed MEC Phase 3 work (2021-2023) and published a set of specifications related to the MEC Federation. Given the continuous collaboration since the begin of MEC Phase 3, we believe that these topics are relevant for your work on federation.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10110,"status":"noted","reservation_date":"2024-04-24 06:41:41","uploaded":"2024-04-24 06:43:30","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA OPG, GSMA OPAG","Cc":"SA WG6, SA WG2, CAMARA, CT WG3, TSG SA, TSG CT, TMF, ETSI ISG NFV","lsoriginalls":"MEC(23)000158r2","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2405853.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405855","title":"LS from ITU-T SG13: LS on initiation of new work item ITU-T Y.IMT2020-DDP 'Future networks including IMT-2020: requirements and framework of distributed data plane'","source":"ITU-T SG13","contact":"Marco Carugi","contact-id":31658,"tdoctype":"LS in","for":"Information","abstract":"This liaison statement informs ITU-T SG11, ITU-T SG17, SA WG2, ETSI F5G, IETF NMRG, IETF NVO3 about the initiation of the new draft Recommendation ITU-T Y.IMT2020-DDP 'Future networks including IMT-2020: requirements and framework of distributed data plane'.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10120,"status":"noted","reservation_date":"2024-04-24 06:41:41","uploaded":"2024-04-24 06:43:30","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG11, SG17","Cc":"SA WG2, ETSI F5G, IRTF NMRG, IETF NVO3","lsoriginalls":"SG13-LS176","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2405855.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405856","title":"LS from ITU-T SG13: LS on initiation of new work item ITU-T Y.ESBN 'Enhanced service-based network in IMT-2020 networks and beyond'","source":"ITU-T SG13","contact":"Yushuang Hu","contact-id":96973,"tdoctype":"LS in","for":"Information","abstract":"This liaison statement informs about the initiation of new work item ITU-T Y.ESBN 'Enhanced service-based network in IMT-2020 networks and beyond'.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10130,"status":"noted","reservation_date":"2024-04-24 06:41:41","uploaded":"2024-04-24 06:43:30","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG2, SG11","Cc":"SA WG1, SA WG2, ETSI NFV, IETF NMRG","lsoriginalls":"SG13-LS177","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2405856.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405858","title":"LS from CT WG1: Reply LS on Handling of regulatory prioritized services in Non-allowed areas","source":"CT WG1","contact":"Sunghoon Kim","contact-id":87408,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 thanks SA WG2 for the Reply LS to CT WG1 regarding how to handle MPS\/MCX and emergency services in non-allowed area. CT WG1 has agreed CR6152 against TS 24.501 to clarify Allowed PDU session status IE handling for release 18 only (see attached C1-242689). For release-17, CT WG1 agreed not to pursue as it is not FASMO. Action: CT WG1 kindly asks SA WG2 to take the above information into account.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10300,"status":"noted","reservation_date":"2024-04-24 06:41:41","uploaded":"2024-04-24 06:43:30","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C1-242708","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2405858.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405860","title":"LS from CT WG1: LS on the condition for provisioning of the ePDG identity to the UE","source":"CT WG1","contact":"Xingyue Zhou","contact-id":42680,"tdoctype":"LS in","for":"Information","abstract":"The statement with yellow highlighted texts below are excerpted from clause 8.2 of TS 33.402 regarding the procedure of tunnel full authentication and authorization between the UE and the ePDG. The yellow highlighted texts may be interpreted in different ways: in step 6 of figure 8.2.2-1 in clause 8.2.2 of TS 33.402, a) the ePDG identity in successful IKE_AUTH response of the first IKE_AUTH exchange shall be provided to the UE if the UE has requested with a CERTREQ payload; or b) the ePDG identity in successful IKE_AUTH response of the first IKE_AUTH exchange shall be provided to the UE regardless of whether the UE has requested with a CERTREQ payload. CT WG1 would like to ask SA WG3 to confirm which interpretation above is correct.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10140,"status":"noted","reservation_date":"2024-04-24 06:41:41","uploaded":"2024-04-24 06:43:30","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG2","lsoriginalls":"C1-242936","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2405860.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405861","title":"LS from CT WG1: LS affirming CT1s responsibilities for PLMN selection","source":"CT WG1","contact":"ChenHo CHIN","contact-id":80545,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 noticed that SA WG2 in LS S2-2403670\/C1-242045, is requesting clarification to SA WG1 on stage 1 PLMN selection. CT WG1 wishes to indicate that CT WG1 is the only 3GPP WG responsible for developing the stage 2 for PLMN selection. Thus should SA WG1 decide there are any PLMN selection impacts to the question raised by SA WG2 in S2-2403670\/C1-242045, the stage 2 work (in TS 23.122) for PLMN selection regardless of FS, SI or WI, remains the sole responsibility of CT WG1. Action: Please note that CT WG1 will continue in Rel-19 to be the WG responsible for developing further stage 2 service requirements on PLMN selection, if any.","secretary_remarks":"Responses drafted in S2-2405980, S2-2406169. 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-04-24 06:41:41","uploaded":"2024-04-24 06:43:30","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG1","Cc":"","lsoriginalls":"C1-242955","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2405861.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405862","title":"LS from CT WG3: LS on Clarification related to NSI and Target Service Area","source":"CT WG3","contact":"Rajesh Babu Natarajan","contact-id":89232,"tdoctype":"LS in","for":"Information","abstract":"As per S2-2403703, SA WG2 LS reply to LS on Clarification related to the information exposed by the 5GC to NSCE server provided below clarification: {. . .} Action: CT WG3 kindly asks SA WG6 to answer the above questions and update the SA WG6 specifications, if necessary.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10160,"status":"noted","reservation_date":"2024-04-24 06:41:41","uploaded":"2024-04-24 06:43:30","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"SA WG2, SA WG5","lsoriginalls":"C3-242466","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2405862.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405866","title":"LS from CT WG4: Reply LS on the Modified PRINS solution","source":"CT WG4","contact":"Mamdoh Shahin","contact-id":96517,"tdoctype":"LS in","for":"Information","abstract":"CT WG4 thanks TSG SA for their LS on the Modified PRINS solution asking CT WG4 to update Release 18 3GPP TS 29.573 specification in alignment with the SA WG3 CR to support Modified PRINS functionality for earlier releases. CT WG4 has agreed the attached 3GPP TS 29.573 CR to support Modified PRINS functionality for earlier releases.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10170,"status":"noted","reservation_date":"2024-04-24 06:41:41","uploaded":"2024-04-24 06:43:30","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, GSMA 5GMRR","Cc":"SA WG3, SA WG1, SA WG2, TSG CT","lsoriginalls":"C4-241522","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2405866.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405868","title":"LS from CT WG4: LS on Clarification on Dual Registration Indication","source":"CT WG4","contact":"Zhijun Li","contact-id":39295,"tdoctype":"LS in","for":"Information","abstract":"CT WG4 has revisited the specification details of dual registration mode support for EPS interworking, and finds some unclarity which needs clarification from CT WG1 and possibly from SA WG2. {. . .} To assist understanding how the dual registration mode actually works, CT WG4 would like to ask the following questions to CT WG1: Q1: Does a UE operating in dual registration mode only indicate the EMM state of EMM-REGISTERED in the initial registration procedure? Or, should the UE also indicate the EMM registration status in periodic registration procedure or mobility registration procedure? Q2: If a UE's registration mode (single\/dual registration mode) is altered due to it turns off the dual registration mode or detaches from EPS, or if a UE is not registered to EPS during the initial registration to 5GS but later on it registers to the EPS, what information will the UE indicate to the AMF and in which procedure?","secretary_remarks":"Response drafted in S2-2406215. This LS was postponed.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10310,"status":"postponed","reservation_date":"2024-04-24 06:41:41","uploaded":"2024-04-24 06:43:30","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG2","lsoriginalls":"C4-241547","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2405868.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405869","title":"LS from SA WG3LI: LI considerations for TR 33.757 (Study on security for PLMN hosting a NPN)","source":"SA WG3LI","contact":"Mark Canterbury","contact-id":70749,"tdoctype":"LS in","for":"Action","abstract":"SA WG3-LI has studied the current version of TR 33.757 and has the following observations: {. . .} Action: SA WG3-LI kindly asks SA WG3 to take the above into account when evaluating solutions for Key Issue #1 and #3, and for SA WG2 and SA WG3 to coordinate with SA WG3-LI on any subsequent normative work","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10330,"status":"noted","reservation_date":"2024-04-24 06:41:41","uploaded":"2024-04-24 06:43:31","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3","Cc":"","lsoriginalls":"S3i240294","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2405869.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405873","title":"LS from SA WG5: Reply LS on 3GPP Reservation of Edge Resources and Correlation information for API volume based charging","source":"SA WG5","contact":"Maryse Gardella","contact-id":68914,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks GSMA OPAG for both their LSs (LSs OPAG_94_Doc_08\/S5-241341 and OPAG_94_Doc_07\/S5-241342\/) on charging considerations in the context of their Operator Platform. SA WG5 charging has discussed the two LSs and would like to provide preliminary feedback and ask for additional information to GSMA OPAG. {. . .}","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10180,"status":"noted","reservation_date":"2024-04-24 06:41:41","uploaded":"2024-04-24 06:43:31","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA OPAG","Cc":"GSMA OPG, TSG SA, SA WG6, SA WG2","lsoriginalls":"S5-241836","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2405873.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405876","title":"LS from SA WG5: Reply LS on the user consent for trace reporting","source":"SA WG5","contact":"Qiang Zu","contact-id":45967,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks RAN WG3 for its LS on the support of user consent for trace and for updating the User consent handling in MDT for NG-RAN. In the LS, RAN WG3 would like to check with SA WG5 the following approach and provide feedback: - For MDT configurations that contain both MDT measurements subject to user consent and not subject to user consent, the RAN node may select UEs considering user consent and configure MDT measurements that are both subject to use consent and not subject to user consent or the RAN node may select UEs without considering user consent and configure MDT measurements not subject to user consent. SA WG5 has discussed it and would like to provide the following considerations, - If the MDT configuration contains both MDT measurements subject to user consent and not subject to user consent, o If the subscriber provided consent, the gNB shall select the corresponding UE and configure with all the MDT measurements in the MDT configuration. o If the subscriber did not provide consent, the gNB may select the UE and configure it with the MDT measurements not subject to user consent that are contained in the MDT configuration. For more details, please see the agreed CR.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10190,"status":"noted","reservation_date":"2024-04-24 06:41:42","uploaded":"2024-04-24 06:43:26","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"SA WG3, SA WG2, RAN WG2","lsoriginalls":"S5-242221","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2405876.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405877","title":"LS from SA WG6: Reply LS on Clarification related to the predictive slice modification in Inter-PLMN based slice service continuity","source":"SA WG6","contact":"Vasil Aleksiev","contact-id":63195,"tdoctype":"LS in","for":"Information","abstract":"Answers to questions 1 to 6 from SA WG6.","secretary_remarks":"Response drafted in S2-2406663. Final response in S2-2407353","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10350,"status":"replied to","reservation_date":"2024-04-24 06:41:42","uploaded":"2024-04-24 06:43:26","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"SA WG5, SA WG2","lsoriginalls":"S6-241627","lsreply":"S2-2407353","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2405877.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405881","title":"LS from RAN WG2: LS to RAN WG3 on MDT for NPN","source":"RAN WG2","contact":"Ali Parichehreh","contact-id":90468,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 would like to seek guidance for two topics: 1. Collecting logged MDT measurements for 256 PNI-NPN identities\/networks. 2. Logged MDT measurements in SNPN network based on the plmn-indentityList.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10200,"status":"noted","reservation_date":"2024-04-24 06:41:42","uploaded":"2024-04-24 06:43:26","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"SA WG2, SA WG5","lsoriginalls":"R2-2403856","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2405881.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405882","title":"LS from RAN WG2: LS on interpretation when TX profile is not provided","source":"RAN WG2","contact":"Weiqiang Du","contact-id":89595,"tdoctype":"LS in","for":"Action","abstract":"For SL-CA, RAN WG2 discussed the interpretation when TX profile is not provided, and reached the following agreements in RAN WG2#125bis: Interpretation when TX Profile is not provided: 1. A UE assumes backward compatible for the given QoS flow if there is no associated TX profile. 2. Agreed with the wording A UE assumes backward compatible is required for the given QoS flow if there is no associated TX profile. in 38.300. Action: RAN WG2 respectfully requests SA WG2 to take the above RAN WG2 agreements into account, and feedback if any concern.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10390,"status":"noted","reservation_date":"2024-04-24 06:41:42","uploaded":"2024-04-24 06:43:27","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"R2-2403925","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2405882.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405883","title":"LS from GSMA OPG: LS on clarifications on consent management","source":"GSMA OPG","contact":" Anonymous","contact-id":4132,"tdoctype":"LS in","for":"Information","abstract":"An activity on privacy management (e.g. how to capture consent from the end-user) is ongoing as part of the current release of OPG: For privacy reasons, a 3rd party application wanting to access end-user-related sensitive information present in the network, requires capturing the consent from the end-user before the application can use that information for a specific purpose. {. . .}","secretary_remarks":"Postponed in parallel session.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10070,"status":"postponed","reservation_date":"2024-04-24 06:41:42","uploaded":"2024-04-29 13:36:13","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, CT WG4, CT WG3, SA WG6","Cc":"SA WG2, TSG SA","lsoriginalls":"OPG_173_Doc_04","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2405883.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405884","title":"LS from CT WG1: LS on the stage 2 aspects of MINT_Ph2","source":"CT WG1","contact":"Mingxue Li","contact-id":80903,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 has discussed a WID proposal for MINT support in EPS (MINT_Ph2_EPS) in the CT WG1 April meeting, in order to support the following stage 1 service requirement specified in Rel-19 MINT_Ph2 by SA WG1: Subject to regulatory requirements, operator's policy or UE capabilities, the 3GPP system shall be able to support a UE, with 5G-only national roaming access to a VPLMN, to obtain 4G connectivity service (e.g. voice call, mobile data service) from that VPLMN in the area where a Disaster Condition applies. The WID proposal on MINT_Ph2_EPS includes both stage-2 and stage-3 aspects. The failure scenarios of the WID proposal is limited to RAN failure, consistent with the failure scenarios of Rel-17 MINT. With this, similar as working procedure done for Rel-17 MINT, CT WG1 is planning to define 4G PLMN selection for disaster roaming and end-to-end call flow regarding attach procedure after selection of a disaster roaming 4G PLMN. CT WG1 would like to ask TSG SA if there is any concern on this approach and expects any feedback on this way forward so that the normative phase can progress within Rel-19 timeframe.","secretary_remarks":"Response drafted in S2-2405894. Final response in S2-2407313","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10400,"status":"replied to","reservation_date":"2024-04-24 06:41:42","uploaded":"2024-04-29 13:36:13","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"TSG CT, SA WG2, CT WG4","lsoriginalls":"C1-242675","lsreply":"S2-2407313","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2405884.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405885","title":"LS from SA WG3: LS to request clarification on mobile metaverse services","source":"SA WG3","contact":"Rohini Rajendran","contact-id":83984,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 has started the work in TR 33.721 for Study on security aspects of 5G Mobile Metaverse services with the following objectives: - Authentication and authorization of digital identity (non-IMS based) - Support of security aspects of digital asset container - Security and privacy aspects of user sensitive information for Localized Mobile Metaverse Services. As there is no definition of digital identity in TS 22.156 and TR 23.700-21, it is difficult to progress with the study. In order to have authenticated and authorized access to the digital asset, some contributions are considering an identifier digital asset identifier to uniquely identify the digital asset. However during the discussion it was questioned, whether user identifier can be used to identify the digital asset. SA WG3 would like to understand the definition of digital identity\/identifier and its relationship with digital asset(s). SA WG3 has tentatively defined the term digital asset identifier to identify a digital asset, as in the enclosed proposal. {. . .}","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10230,"status":"noted","reservation_date":"2024-04-24 06:41:42","uploaded":"2024-04-29 13:36:13","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG6","Cc":"SA WG2, SA WG4","lsoriginalls":"S3-241497","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2405885.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405890","title":"LS from BBF: Multi-Tenant FWA","source":"BBF","contact":"Lincoln Lavoie","contact-id":39231,"tdoctype":"LS in","for":"Information","abstract":"Dear colleagues, We would like to inform that Broadband Forum has started work on a new specification (WT-507) FWA solution for delivery inside a MDU\/MTU supporting Multi-Tenant Fixed-Wireless Access (MT-FWA), i.e., extending Fixed Wireless Access in Multi-Tenant Buildings or Multi-Dwelling Units. The objective of this work is to utilize 5G Fixed Wireless Access to service multiple customers, utilizing existing in-building infrastructure, supporting multiple subscribers behind a single 5G FWA Modem. We welcome any guidance on 3GPP work, including studies, use cases or requirements, in progress at 3GPP, that may be of relevance to this work. Sincerely, Lincoln Lavoie, Broadband Forum Technical Committee Chair","secretary_remarks":"Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10090,"status":"postponed","reservation_date":"2024-04-24 06:41:42","uploaded":"2024-05-02 07:45:36","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG1, SA WG2","Cc":"","lsoriginalls":"LIAISE-654","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2405890.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405891","title":"LS from ITU-T SG12: LS on contribution about the 'impact of 5G Home Base Routing on conversational Voice Quality'","source":"ITU-T SG12","contact":" Anonymous","contact-id":4132,"tdoctype":"LS in","for":"Action","abstract":"ITU-T Study Group 12 (Performance, QoS and QoE) wishes to inform SA WG2 that, at its meeting in Geneva, 16-25 April 2024, it has received a contribution about the impact of 5G Home Base Routing on conversational Voice Quality. The contribution is shared with 3GPP for information and feedback. ITU-T SG12 kindly requests if SA WG2 can provide any guidance on the following topic: Home Routing plays a pivotal role in optimizing resource utilization, ensuring consistent service quality, enhancing network security, and facilitating billing and management in mobile networks. However, recent observations have revealed significant challenges related to the delay in voice traffic routing to the Home Public Mobile Network (HPMN) with recent 3GPP releases. Specifically, routing delays of up to 320 ms have been identified when routing the voice traffic of a roaming user e.g. from Germany, located in Australia, to a phone number within Australia. This results in a mouth-to-ear delay of up to 520 ms, significantly impacting the quality of voice communication. Furthermore, we note that if in addition a mirrored roaming of the called user takes place in the same call, the delay doubles, exacerbating the issue even further. In light of these challenges, we seek your collaboration. In particular we would like to receive your comments whether this scenario has already been discussed in SA WG2 and if so with which outcome. We trust in your feedback, value your efforts and would appreciate a technical collaboration on this topic The deadline mentioned above would allow us to introduce your feedback into our next SG12 meeting. We again thank SA WG2 for their feedback.","secretary_remarks":"Postponed.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10440,"status":"postponed","reservation_date":"2024-04-24 06:41:42","uploaded":"2024-05-07 14:28:16","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"oLS65","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2405891.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405893","title":"LS from GSMA OGWTS: Reply LS on collaboration and alignment of 3GPP defined application enablers with GSMA Open Gateway","source":"GSMA OGWTS","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"Introduction: GSMA Open Gateway Technical Stream (OGWTS) thanks TSG SA for the LS (3GPP SP-231778) on the collaboration and alignment of 3GPP defined application enablers with GSMA Open Gateway. Feedback to SA WG6\/TSG SA: With reference to the SA WG6 indication about the availability of application enablement standards and the related APIs, OGWTS would require more time to study and conclude the benefits of considering the SA WG6 Application Enablement standards by GSMA Open Gateway architecture. The scope of Open Gateway TS is to define guidelines for a federated exposure platform that needs to integrate with Aggregator\/Channel Partner and offerings targeting near term availability in market. Cooperation should focus on those areas where the capabilities defined by TSG SA\/SA WG6 align with this scope and might be adopted for example as part of transformation functions. OGWTS plans to reach out to TSG SA\/SA WG6 for clarifications when such areas are identified. Similarly, If TSG SA\/SA WG6 identifies such areas OGWTS is available for discussion. OGWTS is available to engage with TSG SA\/SA WG6 for further understanding.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10240,"status":"noted","reservation_date":"2024-04-24 06:41:42","uploaded":"2024-05-21 07:48:08","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG6","Cc":"SA WG2, SA WG5, TSG CT","lsoriginalls":"OGWTS_03_Doc04","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2405893.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405894","title":"[DRAFT] Reply LS on the stage 2 aspects of MINT_Ph2","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS proposal","secretary_remarks":"Response to S2-2405884. Revised to S2-2406878.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10410,"status":"revised","reservation_date":"2024-02-05 09:28:59","uploaded":"2024-05-17 08:13:19","revisionof":"","revisedto":"S2-2406878","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"MINT_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"TSG CT, CT WG1, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2405894.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405980","title":"[DRAFT] Reply LS on affirming CT WG1's responsibilities for PLMN selection","source":"CATT","contact":"Xiaoyan Duan","contact-id":85499,"tdoctype":"LS out","for":"Approval","abstract":"Draft reply LS to CT WG1 on affirming CT WG1's responsibilities for PLMN selection.","secretary_remarks":"Response to S2-2405861. Revised to S2-2406879 (withdrawn). Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10460,"status":"revised","reservation_date":"2024-05-15 05:51:32","uploaded":"2024-05-17 10:06:51","revisionof":"","revisedto":"S2-2406879","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2405980.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2406169","title":"[DRAFT] LS reply to CT WG1 LS about responsibilities on PLMN selection","source":"Huawei, HiSilicon","contact":"Yishan Xu","contact-id":89333,"tdoctype":"LS out","for":"Approval","abstract":"This LS is sent to CT WG1 to reply the LS from CT WG1 about PLMN selection","secretary_remarks":"Response to S2-2405861. Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10480,"status":"not treated","reservation_date":"2024-05-16 13:24:43","uploaded":"2024-05-17 13:06:59","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2406169.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2406215","title":"[DRAFT] Reply LS on Clarification on Dual Registration Indication","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"LS out","for":"Approval","abstract":"Proposes a reply LS on Clarification on Dual Registration Indication","secretary_remarks":"Response to S2-2405868. This response LS was postponed.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10320,"status":"postponed","reservation_date":"2024-05-16 15:18:41","uploaded":"2024-05-17 12:52:48","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI18"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4, CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2406215.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2406367","title":"Cleanup CR for TS 23.503","source":"Huawei (Rapporteur)","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 3.2: adding abbreviations (HR-SBO) Clause 4.1: update (as the interface between the two PCFs is standardized meanwhile) Clause 4.2.6: moving two bullets to clause 4.3.6 (to align with statements in clause 4.3.7) and correcting a reference Clause 4.3.6: adding and reordering references (to better clarify their related specification) Clause 5.2.1: terminology update (PCF for a -> PCF for the ) Clause 5.2.2: adding reference for SEPP; aligning intro text with clause 5.2.1; clarifying terms and meaning of Note 7 Clause 5.3.2: clarifying terms and meaning of Note Clause 5.3.11: simplification (to reduce efforts when further analytics will be added) and removing inconsistency (as the listed names are Analytics Ids) Clause 5.3.12: terminology update (PCF for a -> PCF for the ) and adding of reference (to reduce efforts when further events will be added) Clause 6.1.1.1, 6.1.1.2.2 and 6.1.1.2a: terminology update (PCF for a -> PCF for the ) Clause 6.1.2.2.3: correcting terminology (AF guidance -> application guidance; URSPs -> URSP rules) and adding reference to 23.502 Clause 6.1.2.2.4: extending the table numbers (6.2- -> 6.2.1.3- ) Clause 6.1.3.1: update (as the interface between the two PCFs is standardized meanwhile) Clause 6.1.3.2.4: moving notes to related bullet; correcting terminology (PDU Set Handling Information -> PDU Set Control Information) Clause 6.1.3.18: terminology update (PCF for a -> PCF for the ; QoS monitoring parameter -> QoS Monitoring parameter) Clause 6.1.3.21: correcting typos and terminology; adding reference and correcting reference Clause 6.1.3.22: correcting identation of 4 paragraphs; moving 3 paragraphs to the end of the clause (as they break the logic of the description) Clause 6.1.3.24: aligning terminology with clause 6.3.1. and 23.501 (indication on whether the PDU Session is a redundant PDU Session or not -> indication that the PDU Session is a redundant PDU Session) Clause 6.1.3.27.1: correcting terminology and reference Clause 6.1.3.27.4: aligning terminology with clause 5.37.5 of 23.501 (PDU Set QoS handling -> PDU Set based handling) Clause 6.1.3.27.5: aligning terminology with clause 5.37.8.3 of 23.501 and clause 6.3.1 (Data Burst End Marking Indication -> End of Data Burst Marking Indication) Clause 6.1.3.27.6: undoing Italic text format and aligning terminology with clause 5.37.8 of 23.501 (power saving -> UE power saving) Clause 6.1.4.3: correcting terminology (remaining data rate -> Remaining Maximum Slice Data Rate) Clause 6.1.6: moved to clause 6.1.1.x (as this is not a new type of policy) together with terminology update (PCF for a -> PCF for the ) Clause 6.2.1.3: extending the table numbers (6.2- -> 6.2.1.3- ) Clause 6.2.1.12: correcting terminology and typo Clause 6.2.3: correcting terminology (AF guidance -> application guidance; QoS monitoring parameter -> QoS Monitoring parameter) Clause 6.3.1: correcting references and aligning terminology with clause 5.37.8 of 23.501 (power saving -> UE power saving) Clause 6.4: correcting terminology (PDU session -> PDU Session) and aligning terminology (Authorized Session-AMBR for Offloading -> Authorized DL Session AMBR for Offloading) Clause 6.6.1.1: extending the table numbers (6.6.1- -> 6.6.1.1- ) Clause 6.6.2.1: correcting terminology (PDU session -> PDU Session; traffic descriptor -> Traffic descriptor) Clause 6.6.2.3: correcting terminology (PDU session -> PDU Session; Route Selection Description -> Route Selection Descriptor; Traffic Descriptor -> Traffic descriptor) Clause 6.6.2.4: undoing the additions coming from CR#1120 (approved in S2-2401567 at SA WG2#160AHe) which was obsoleted by CR#1243 (approved in S2-2403461 at SA WG2#161); aligning the logic of the bullets by adding ; or to 2nd and 3rd bullet; adding missing reference Clause 3.2, 4.3.4, 6.1.3.26, 6.1.3.27.3, 6.5.1: correcting typo(s)","secretary_remarks":"Revised to S2-2406880.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10540,"status":"revised","reservation_date":"2024-05-17 04:54:50","uploaded":"2024-05-17 12:02:28","revisionof":"","revisedto":"S2-2406880","release":"Rel-18","crspec":"23.503","crspecversion":"18.5.0","workitem":[{"winame":"TEI18"},{"winame":" 5GS_Ph1"}],"crnumber":1299.0,"crrevision":"","crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2406367.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"3.2, 4.1, 4.2.6, 4.3.4, 4.3.6, 5.2.1, 5.2.2, 5.3.2, 5.3.10, 5.3.11, 5.3.12, 6.1.1.1, 6.1.1.2.2, 6.1.1.2a, 6.1.1.x (new), 6.1.2.2.3, 6.1.2.2.4, 6.1.3.1, 6.1.3.2.4, 6.1.3.18, 6.1.3.21, 6.1.3.22, 6.1.3.24, 6.1.3.26, 6.1.3.27.1, 6.1.3.27.3, 6.1.3.27.4, 6.1.3.27.5, 6.1.3.27.6, 6.1.4.3, 6.1.6, 6.2.1.3, 6.2.1.12, 6.2.3, 6.3.1, 6.4, 6.5, 6.6.1.1, 6.6.2.1, 6.6.2.3, 6.6.2.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2406579","title":"User consent issue on MSISDN exposure.","source":"Samsung","contact":"Hyesung Kim","contact-id":83054,"tdoctype":"discussion","for":"Discussion","abstract":"In Release 18, SA WG2 agreed to support MSISDN exposure via NEF Nnef_UEId service as in the approved CRs [1], [2]. The agreed MSISDN exposure service is provided limitedly to the operator-owned AF within the operator domain. To release this limit, in SA WG2#162, it is endorsed as in [3] that the MSISDN exposure can be allowed for a trusted AF, which is allowed and authorized, using authorization code grant and a user consent mechanism (e.g., as defined in Annex V of TS 33.501) to retrieve the MSISDN. This discussion paper identifies user consent issue for MSISDN exposure in the endorsed CR [3] and provides proposals to address them.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10650,"status":"noted","reservation_date":"2024-05-17 11:23:02","uploaded":"2024-05-17 12:16:03","revisionof":"","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_163_Jeju_2024-05\/Docs\/S2-2406579.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2406580","title":"Corrections to Nnef_UEId Service","source":"[AT&T, Ericsson], Samsung","contact":"Hyesung Kim","contact-id":83054,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies the conditions on the usage of the MSISDN retrieval (clause 4.15.10A) to allow the usage of Nnef_UEId Service for retrieving MSISDN by a trusted and authorized AF by adding reference to TS 33.501.","secretary_remarks":"Revision of S2-2405823 from SA WG2#162. Revised in parallel session to S2-2407110.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10660,"status":"revised","reservation_date":"2024-05-17 11:24:54","uploaded":"2024-05-17 12:16:04","revisionof":"S2-2405823","revisedto":"S2-2407110","release":"Rel-18","crspec":"23.502","crspecversion":"18.5.0","workitem":[{"winame":"EDGEAPP"},{"winame":" TEI18"}],"crnumber":4805.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2406580.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.15.10A, 5.2.3.3.1, 5.2.6.27","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2406662","title":"Editorial cleanup","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Corrected step reference and other editorial modifications for PDU session release PDU Session Id changed to PDU Session ID Removal of redundant and incomplete text in step 3 of 4.16.11.1 Corrected the clause reference 4.22.2.3 to 4.22.2.4 in Clause 4.22.2.4.1. Corrected spelling and aligned some terms Corrected Npcf_UEPolicyControl UpdateNotify Corrected name for PDUSession_Create Corrected unsubscription request to unsubscribe request Corrected Nnsacf_SliceEvent Exposure_Notify","secretary_remarks":"Revised to S2-2406843","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10600,"status":"revised","reservation_date":"2024-05-17 13:38:51","uploaded":"2024-05-20 17:53:52","revisionof":"","revisedto":"S2-2406843","release":"Rel-18","crspec":"23.502","crspecversion":"18.5.0","workitem":[{"winame":"TEI18"}],"crnumber":4823.0,"crrevision":"","crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2406662.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2406663","title":"[DRAFT] Reply LS on Clarification related to the predictive slice modification in Inter-PLMN based slice service continuity","source":"Ericsson","contact":"Peter Hedman","contact-id":27550,"tdoctype":"LS out","for":"Approval","abstract":"Asks SA WG6 question related to the framework for NSCE","secretary_remarks":"Response to S2-2405877. Revised to S2-2406876.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10360,"status":"revised","reservation_date":"2024-05-17 13:38:52","uploaded":"2024-05-17 18:50:13","revisionof":"","revisedto":"S2-2406876","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NSCALE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"CT WG3, SA WG5","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2406663.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2406842","title":"23.501 Cleanup CR","source":"Nokia","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Editorial cleanup in XRM section for improved readability","secretary_remarks":"Revised to S2-2406881.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10570,"status":"revised","reservation_date":"2024-05-20 12:19:10","uploaded":"2024-05-20 12:21:31","revisionof":"","revisedto":"S2-2406881","release":"Rel-18","crspec":"23.501","crspecversion":"18.5.0","workitem":[{"winame":"TEI18"}],"crnumber":5404.0,"crrevision":"","crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2406842.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":false,"clauses_affected":"5.37.5.2, 5.37.8.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2406843","title":"Editorial cleanup","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Corrected step reference and other editorial modifications for PDU session release PDU Session Id changed to PDU Session ID Removal of redundant and incomplete text in step 3 of 4.16.11.1 Corrected the clause reference 4.22.2.3 to 4.22.2.4 in Clause 4.22.2.4.1. Corrected spelling and aligned some terms Corrected Npcf_UEPolicyControl UpdateNotify Corrected name for PDUSession_Create Corrected unsubscription request to unsubscribe request Corrected Nnsacf_SliceEvent Exposure_Notify","secretary_remarks":"Revision of S2-2406662. Revised to S2-2406882.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10610,"status":"revised","reservation_date":"2024-05-20 17:55:28","uploaded":"2024-05-20 18:01:43","revisionof":"S2-2406662","revisedto":"S2-2406882","release":"Rel-18","crspec":"23.502","crspecversion":"18.5.0","workitem":[{"winame":"TEI18"}],"crnumber":4823.0,"crrevision":1.0,"crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2406843.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2406844","title":"LS from ITU-T SG11: LS on initiation of new work item ITU-T Q.IEM_arch_req 'Reference architecture and signalling requirements for interactive emergency messaging through mobile network'","source":"ITU-T SG11","contact":"Ritu Ranjan Mittar","contact-id":71891,"tdoctype":"LS in","for":"Information","abstract":"This Liaison Statement informs ITU-T SG2, SA WG1, SA WG2, ETSI-EMTEL, GSMA that ITU-T SG11 initiated a new work item ITU-T Q.IEM_arch_req Reference architecture and signalling requirements for interactive emergency messaging through mobile network during the Study Group 11 meeting (Geneva, 1-10 May 2024).","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10250,"status":"noted","reservation_date":"2024-05-21 12:34:56","uploaded":"2024-05-21 12:36:50","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG2, SA WG1, SA WG2, ETSI-EMTEL, GSMA","Cc":"","lsoriginalls":"SG11-LS173","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2406844.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2406845","title":"LS from SA WG4: Reply LS on the MBS broadcast service continuity and MBS session identification","source":"SA WG4","contact":"Thomas Stockhammer","contact-id":60397,"tdoctype":"LS in","for":"Information","abstract":"SA WG4 thanks RAN WG2 for the LS on the Reply LS on the MBS broadcast service continuity and MBS session identification providing the details of the radio frequency parameter. SA WG4 recently did a major correction to TS 26.517 to exclusively rely on a JSON based representation of the User Service Description. In a follow-up, the radio frequency parameter was finally corrected. Details can be found in the attached Rel-17 CR. An equivalent correction for Rel-18 is also agreed.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10260,"status":"noted","reservation_date":"2024-05-24 05:16:27","uploaded":"2024-05-24 05:16:53","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"RAN WG3, SA WG2","lsoriginalls":"S4-241257","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2406845.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2406846","title":"LS from SA WG6: LS on Clarification related to Internal 5G Core information expose to trusted AF","source":"SA WG6","contact":"shaowen zheng","contact-id":88792,"tdoctype":"LS in","for":"Action","abstract":"As per S2-2403703, SA WG2 LS reply to LS on Clarification related to the information exposed by the 5GC to NSCE server provided the below clarification: 'As described in TS 33.501 clause 5.9.2.3, NEF and the AF shall fulfil the security requirements that include that 'Internal 5G Core information such as DNN, S-NSSAI etc., shall not be sent outside the 3GPP operator domain.' So SA WG6 would like to consult SA WG2 and SA WG3's view on - Whether a trusted AF of an 3GPP operator is considered within the operator's domain; o If yes, whether it is possible to expose Internal 5G Core information such as DNN, S-NSSAI, etc. to a trusted AF (e.g., a NSCE server). - Whether the NSI (i.e., Network Slice Instance) and\/or NSI ID can be exposed to the trusted AF. Action: SA WG6 asks SA WG2 and SA WG3 to answer the question above.","secretary_remarks":"Response drafted in S2-2406877. Final response in S2-2407354","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10490,"status":"replied to","reservation_date":"2024-05-24 05:16:27","uploaded":"2024-05-24 05:16:53","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3","Cc":"CT WG3, SA WG5","lsoriginalls":"S6-242714","lsreply":"S2-2406877","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2406846.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2406848","title":"LS from SA WG6: Reply LS on request clarification on mobile metaverse services","source":"SA WG6","contact":"Sapan Shah","contact-id":76271,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 would like to thank SA WG3 for sending LS on request clarification on mobile metaverse services. Regarding questions Q-1 to 4, 6 to 11, and 13 to 15, SA WG6 has studied KI #3 and solutions #5, #6 and #7 in TR 23.700-21, and has consider following general information into their study: {. . .}","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10270,"status":"noted","reservation_date":"2024-05-24 05:16:27","uploaded":"2024-05-24 05:16:53","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG3","Cc":"SA WG4, SA WG2","lsoriginalls":"S6-242734","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2406848.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2406854","title":"LS from SA WG3: Reply LS on the condition for provisioning of the ePDG identity to the UE","source":"SA WG3","contact":"Leyi Zhang","contact-id":100809,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 thanks CT WG1 for their LS S3-241729\/ C1-242936, LS on the condition for provisioning of the ePDG identity to the UE. Regarding the two interpretations to step 6 in clause 8.2.2 proposed by CT WG1 in the LS a) the ePDG identity in successful IKE_AUTH response of the first IKE_AUTH exchange shall be provided to the UE if the UE has requested with a CERTREQ payload; or b) the ePDG identity in successful IKE_AUTH response of the first IKE_AUTH exchange shall be provided to the UE regardless of whether the UE has requested with a CERTREQ payload. SA WG3 would like to confirm that option b) is the correct interpretation. TS 33.402 has been updated to clarify this issue, see the attachment.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10150,"status":"noted","reservation_date":"2024-05-24 07:46:09","uploaded":"2024-05-24 07:46:42","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG2","lsoriginalls":"S3-242369","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2406854.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2406855","title":"LS from SA WG3: Reply-LS on clarifications on consent management","source":"SA WG3","contact":"Anja Jerichow","contact-id":68341,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 would like to provide to TSG SA input on the LS S3-241741\/OPG_173_Doc_04 from GSMA OPG, in which OPG specifically asks SA WG3 to respond to questions related to their new work item on privacy management. {. . .}. Action: SA WG3 asks all 3GPP WGs in cc to take above information into account. Additionally, SA WG3 asks TSG SA to consolidate and reply to GSMA OPG considering other WGs' replies.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10080,"status":"noted","reservation_date":"2024-05-24 07:46:09","uploaded":"2024-05-24 07:46:42","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"CT WG4, CT WG3, SA WG6, SA WG2","lsoriginalls":"S3-242374","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2406855.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2406856","title":"LS from SA WG3: Reply LS on limited MSISDN exposure","source":"SA WG3","contact":"Henry LIANG","contact-id":56516,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 would like to thank SA WG2 for the LS on limited MSISDN exposure. SA WG3 prefers that SA WG2 does not use the term 'trusted' in this context, as there is no unique definition of 'trusted' in 3GPP. Thus, SA WG3 would like to suggest to SA WG2 that the condition description in clause 4.15.10A of TS 23.502 can be replaced by the following: Depending on operator policy and local regulation, GPSI in MSISDN format may be exposed through the NEF to an authenticated and authorized AF, in which the selected AF is decided by the operator. Depending on operator policy and local regulation, user consent may be required when exposing MSISDN. RNAA defined in clause 6.5.3 of TS 33.122 can be used for user consent. Action: SA WG3 kindly asks SA WG2 to take the above information into account and inform SA WG3 if further clarifications are needed.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10640,"status":"noted","reservation_date":"2024-05-24 07:46:09","uploaded":"2024-05-24 07:46:42","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"TSG SA, CT WG3, SA WG6","lsoriginalls":"S3-242375","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2406856.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2406857","title":"LS from SA WG3: Reply LS on LI considerations for TR 33.757","source":"SA WG3","contact":"hua song","contact-id":91953,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 would like to thank SA WG3-LI for the LS on LI considerations for TR 33.757. {. . .}","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10340,"status":"noted","reservation_date":"2024-05-24 07:46:09","uploaded":"2024-05-24 07:46:42","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3-LI","Cc":"SA WG2","lsoriginalls":"S3-242376","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2406857.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2406862","title":"LS from RAN WG3: Reply LS on MDT for NPN","source":"RAN WG3","contact":"Angelo Centonza","contact-id":45800,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 thanks RAN WG2 for their LS on MDT for NPN. RAN WG3 has gone through the questions from RAN WG2 and it has converged on the following answers. {. . .}","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10210,"status":"noted","reservation_date":"2024-05-24 09:26:00","uploaded":"2024-05-24 09:26:30","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"SA WG2, SA WG5","lsoriginalls":"R3-243892","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2406862.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2406863","title":"LS from RAN WG3: LS on Indicating Emergency Service Support over NG","source":"RAN WG3","contact":"sen xu","contact-id":83316,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 discussed specification texts specified in clause 5.16.4.1 of TS 23.501 as quoted below. During Registration procedures over 3GPP access in a PLMN, the 5GC includes the Emergency Services Support indicator, valid for the current Registration Area and indicating per RAT that Emergency Services are supported if any of the following conditions is true within the current Registration Area: - the Network is able to support Emergency Services natively over 5GS; - E-UTRA connected to 5GC supports IMS Emergency Services (e.g. voice), and the NG-RAN is able to trigger handover or redirection from NR to E-UTRA connected to 5GC at QoS Flow establishment for IMS Emergency Services (e.g. voice); - NG-RAN is able to trigger handover to EPS at QoS Flow establishment for IMS Emergency Services (e.g. voice); - NG-RAN is able to trigger redirection to EPS at QoS Flow establishment for IMS Emergency Services (e.g. voice); or - NG-RAN is able to trigger 5G SRVCC handover to UTRAN for IMS Emergency Services (i.e. voice). If a certain RAT is restricted for Emergency Services, AMF signals that the corresponding RAT is restricted for Emergency Services Support to the Master RAN Node. This helps assist the Master RAN node determine whether to set up Dual Connectivity for Emergency Services. RAN WG3 found that the above second quoted function specified in TS 23.501 is not supported in TS 38.413 since R15. RAN WG3 has decided that a RAN configuration-based approach applies when some RAT is restricted for emergency service support. Therefore, RAN WG3 does not intend to introduce respective support in TS 38.413. Action: RAN WG3 respectfully asks SA WG2 to take the above into account and consider to align TS 23.501 accordingly","secretary_remarks":"Postponed.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10530,"status":"postponed","reservation_date":"2024-05-24 09:26:00","uploaded":"2024-05-24 09:26:30","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"R3-243933","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2406863.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2406864","title":"LS from RAN WG3: Reply LS to SA WG5 on improved KPIs involving end-to-end data volume transfer time analytics","source":"RAN WG3","contact":"Anna Pantelidou","contact-id":86345,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 thanks SA WG5 for their LS. RAN WG3 evaluated carefully the two specifications and made the following observations with respect to TS 28.552 and TS 28.558: 1. TS 28.558 does not define M4 measurement. 2. There seems to be a misalignment between the two specifications with respect to which entity performs the measurements. In particular, RAN WG3 identified the following cases: - The 'Average delay DL air-interface' is measured by the gNB-DU in TS 28.552 and by NRCellCU (for non-split and 2-split scenario) and GNBCUUPFunction (for 3-split scenario) in TS 28.558. - The 'Average delay DL in gNB-DU' is measured by the gNB-DU in TS 28.552 and by NRCellCU (for non-split and 2-split scenario) and GNBCUUPFunction (for 3-split scenario) in TS 28.558. - The 'UL PDCP SDU Loss Rate' is measured by the GNBCUUPFunction and NRCellCU in TS 28.552 and by GNBCUUPFunction in TS 28.558. From RAN WG3 perspective, the above misalignment should be corrected in TS 28.558 based on TS 28.552. Also, RAN WG3 made the following observations concerning the S-TMSI identifier: - 'S-TMSI' should be modified to '5G-S-TMSI'. - S-TMSI is not available in the gNB-DU and in the gNB-CU-UP. - S-TMSI may not be always available in the gNB-CU-CP.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10280,"status":"noted","reservation_date":"2024-05-24 09:26:00","uploaded":"2024-05-24 09:26:30","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"RAN WG2, CT WG4, CT WG3, SA WG2","lsoriginalls":"R3-243941","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2406864.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2406869","title":"LS from SA WG6: Reply LS on clarifications on consent management","source":"SA WG6","contact":"Niranth Amogh","contact-id":39608,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 reviewed the questions from GSMA OPG in their LS. SA WG6 has specified RNAA as part of CAPIF in Rel.18, the detailed specification for CAPIF RNAA has been specified by SA WG3. Given this context, SA WG6 opined that SA WG3 should provide the response to the questions from GSMA OPG. SA WG6 asks SA to consider the following information to be additionally added into the overall 3GPP response to GSMA OPG: SA WG6 has initiated a Rel.19 study on CAPIF (CAPIF_Ph3) to further enhance CAPIF for user consent management (RNAA). GSMA OPG is invited to provide any feedback to the on-going study captured in TR 23.700-22.","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":"2024-05-26 01:52:24","uploaded":"2024-05-26 01:52:57","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"CT WG3, CT WG4, SA WG3, SA WG2","lsoriginalls":"S6-242504","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2406869.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2406871","title":"LS from SA WG6: LS reply on updated AECC Publications for Future Connected Vehicle Services","source":"SA WG6","contact":"Jian Zhang","contact-id":95096,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 would like to thank AECC for the information about recent publication. Regarding of the provided white papers and technical report, for now, SA WG6 has no concerns about them. {. . .}","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10290,"status":"noted","reservation_date":"2024-05-26 01:52:24","uploaded":"2024-05-26 01:52:57","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG1, SA WG2, SA WG5","lsoriginalls":"S6-242764","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2406871.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2406876","title":"[DRAFT] Reply LS on Clarification related to the predictive slice modification in Inter-PLMN based slice service continuity","source":"Ericsson","contact":"Peter Hedman","contact-id":27550,"tdoctype":"LS out","for":"Approval","abstract":"Asks SA WG6 question related to the framework for NSCE","secretary_remarks":"Revision of S2-2406663. Revised to S2-2407353.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10370,"status":"revised","reservation_date":"2024-05-30 05:19:21","uploaded":"2024-06-03 05:31:13","revisionof":"S2-2406663","revisedto":"S2-2407353","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NSCALE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"CT WG3, SA WG5","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2406876.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2406877","title":"LS Reply on Internal 5G Core information expose to trusted AF","source":"SA WG2","contact":"Tianji Jiang","contact-id":90312,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG6. CC: SA WG3, SA WG5.","secretary_remarks":"Created at meeting. Response to S2-2406846. Revised in parallel session to S2-2407314.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10500,"status":"revised","reservation_date":"2024-05-30 05:19:21","uploaded":"2024-06-03 05:31:13","revisionof":"","revisedto":"S2-2407314","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NSCALE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"SA WG3, SA WG5","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2406877.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2406878","title":"[DRAFT] Reply LS on the stage 2 aspects of MINT_Ph2","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS proposal","secretary_remarks":"Revision of S2-2405894. Revised in parallel session to S2-2407313.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10420,"status":"revised","reservation_date":"2024-05-30 05:19:21","uploaded":"2024-06-03 05:31:13","revisionof":"S2-2405894","revisedto":"S2-2407313","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"MINT_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"TSG CT, CT WG1, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2406878.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2406879","title":"[DRAFT] Reply LS on affirming CT WG1's responsibilities for PLMN selection","source":"CATT","contact":"Xiaoyan Duan","contact-id":85499,"tdoctype":"LS out","for":"Approval","abstract":"Draft reply LS to CT WG1 on affirming CT WG1's responsibilities for PLMN selection.","secretary_remarks":"Revision of S2-2405980. WITHDRAWN","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10470,"status":"withdrawn","reservation_date":"2024-05-30 05:19:21","uploaded":null,"revisionof":"S2-2405980","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG1","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2406880","title":"Cleanup CR for TS 23.503","source":"Huawei (Rapporteur)","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 3.2: adding abbreviations (HR-SBO) Clause 4.1: update (as the interface between the two PCFs is standardized meanwhile) Clause 4.2.6: moving two bullets to clause 4.3.6 (to align with statements in clause 4.3.7) and correcting a reference Clause 4.3.6: adding and reordering references (to better clarify their related specification) Clause 5.2.1: terminology update (PCF for a -> PCF for the ) Clause 5.2.2: adding reference for SEPP; aligning intro text with clause 5.2.1; clarifying terms and meaning of Note 7 Clause 5.3.2: clarifying terms and meaning of Note Clause 5.3.11: simplification (to reduce efforts when further analytics will be added) and removing inconsistency (as the listed names are Analytics Ids) Clause 5.3.12: terminology update (PCF for a -> PCF for the ) and adding of reference (to reduce efforts when further events will be added) Clause 6.1.1.1, 6.1.1.2.2 and 6.1.1.2a: terminology update (PCF for a -> PCF for the ) Clause 6.1.2.2.3: correcting terminology (AF guidance -> application guidance; URSPs -> URSP rules) and adding reference to 23.502 Clause 6.1.2.2.4: extending the table numbers (6.2- -> 6.2.1.3- ) Clause 6.1.3.1: update (as the interface between the two PCFs is standardized meanwhile) Clause 6.1.3.2.4: moving notes to related bullet; correcting terminology (PDU Set Handling Information -> PDU Set Control Information; QoS flow -> QoS Flow) Clause 6.1.3.18: terminology update (PDU session -> PDU Session; QoS flow -> QoS Flow; PCF for a -> PCF for the ; QoS monitoring parameter -> QoS Monitoring parameter) Clause 6.1.3.21: correcting typos and terminology; adding reference and correcting reference Clause 6.1.3.22: correcting identation of 4 paragraphs; moving 3 paragraphs to the end of the clause (as they break the logic of the description) Clause 6.1.3.24: aligning terminology with clause 6.3.1. and 23.501 (indication on whether the PDU Session is a redundant PDU Session or not -> indication that the PDU Session is a redundant PDU Session) Clause 6.1.3.27.1: correcting terminology and reference Clause 6.1.3.27.4: aligning terminology with clause 5.37.5 of 23.501 (PDU Set QoS handling -> PDU Set based handling) Clause 6.1.3.27.5: aligning terminology with clause 5.37.8.3 of 23.501 and clause 6.3.1 (Data Burst End Marking Indication -> End of Data Burst Marking Indication) Clause 6.1.3.27.6: undoing Italic text format and aligning terminology with clause 5.37.8 of 23.501 (power saving -> UE power saving) Clause 6.1.4.3: correcting terminology (remaining data rate -> Remaining Maximum Slice Data Rate) Clause 6.1.6: moved to clause 6.1.1.x (as this is not a new type of policy) together with terminology update (PCF for a -> PCF for the ) Clause 6.2.1.3: extending the table numbers (6.2- -> 6.2.1.3- ) Clause 6.2.1.12: correcting terminology and typo Clause 6.2.3: correcting terminology (AF guidance -> application guidance; QoS monitoring parameter -> QoS Monitoring parameter) Clause 6.3.1: correcting references and aligning terminology with clause 5.37.8 of 23.501 (power saving -> UE power saving) Clause 6.4: correcting terminology (PDU session -> PDU Session) and aligning terminology (Authorized Session-AMBR for Offloading -> Authorized DL Session AMBR for Offloading) Clause 6.6.1.1: extending the table numbers (6.6.1- -> 6.6.1.1- ) Clause 6.6.2.1: correcting terminology (PDU session -> PDU Session; traffic descriptor -> Traffic descriptor) Clause 6.6.2.3: correcting terminology (PDU session -> PDU Session; Route Selection Description -> Route Selection Descriptor; Traffic Descriptor -> Traffic descriptor) Clause 6.6.2.4: undoing the additions coming from CR#1120 (approved in S2-2401567 at SA WG2#160AHe) which was obsoleted by CR#1243 (approved in S2-2403461 at SA WG2#161); aligning the logic of the bullets by adding '; or' to 2nd and 3rd bullet; adding missing reference Clause 3.2, 4.3.4, 6.1.3.26, 6.1.3.27.3, 6.5: correcting typo(s)","secretary_remarks":"Revision of S2-2406367. Revised in parallel session to S2-2407317.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10550,"status":"revised","reservation_date":"2024-05-30 05:19:21","uploaded":"2024-06-03 05:31:13","revisionof":"S2-2406367","revisedto":"S2-2407317","release":"Rel-18","crspec":"23.503","crspecversion":"18.5.0","workitem":[{"winame":"TEI18"},{"winame":" 5GS_Ph1"}],"crnumber":1299.0,"crrevision":1.0,"crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2406880.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"3.2, 4.1, 4.2.6, 4.3.4, 4.3.6, 5.2.1, 5.2.2, 5.3.2, 5.3.10, 5.3.11, 5.3.12, 6.1.1.1, 6.1.1.2.2, 6.1.1.2a, 6.1.1.x (new), 6.1.2.2.3, 6.1.2.2.4, 6.1.3.1, 6.1.3.2.4, 6.1.3.18, 6.1.3.21, 6.1.3.22, 6.1.3.24, 6.1.3.26, 6.1.3.27.1, 6.1.3.27.3, 6.1.3.27.4, 6.1.3.27.5, 6.1.3.27.6, 6.1.4.3, 6.1.6, 6.2.1.3, 6.2.1.12, 6.2.3, 6.3.1, 6.4, 6.5, 6.6.1.1, 6.6.2.1, 6.6.2.3, 6.6.2.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2406881","title":"23.501 Cleanup CR","source":"Nokia","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Editorial cleanup in XRM section for improved readability","secretary_remarks":"Revision of S2-2406842. Revised in parallel session to S2-2407315.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10580,"status":"revised","reservation_date":"2024-05-30 05:19:22","uploaded":"2024-06-03 05:31:13","revisionof":"S2-2406842","revisedto":"S2-2407315","release":"Rel-18","crspec":"23.501","crspecversion":"18.5.0","workitem":[{"winame":"TEI18"}],"crnumber":5404.0,"crrevision":1.0,"crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2406881.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":false,"clauses_affected":"5.37.5.2, 5.37.8.2, 8.3.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2406882","title":"Editorial cleanup","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Corrected step reference and other editorial modifications for PDU session release PDU Session Id changed to PDU Session ID Removal of redundant and incomplete text in step 3 of 4.16.11.1 Corrected the clause reference 4.22.2.3 to 4.22.2.4 in Clause 4.22.2.4.1. Corrected spelling and aligned some terms Corrected Npcf_UEPolicyControl UpdateNotify Corrected name for PDUSession_Create Corrected unsubscription request to unsubscribe request Corrected Nnsacf_SliceEvent Exposure_Notify Use PCF for the UE Use PCF for the PDU Session","secretary_remarks":"Revision of S2-2406843. Revised in parallel session to S2-2407316.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10620,"status":"revised","reservation_date":"2024-05-30 05:19:24","uploaded":"2024-06-03 05:31:13","revisionof":"S2-2406843","revisedto":"S2-2407316","release":"Rel-18","crspec":"23.502","crspecversion":"18.5.0","workitem":[{"winame":"TEI18"}],"crnumber":4823.0,"crrevision":2.0,"crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2406882.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407110","title":"Corrections to Nnef_UEId Service","source":"AT&T, [Ericsson?], Samsung, Nokia, Google, Apple","contact":"Hyesung Kim","contact-id":83054,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies the conditions on the usage of the MSISDN retrieval (clause 4.15.10A) to allow the usage of Nnef_UEId Service for retrieving MSISDN by an authorized AF by adding reference to TS 33.501.","secretary_remarks":"Revision of S2-2406580. Revised in parallel session to S2-2407312.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10670,"status":"revised","reservation_date":"2024-05-30 05:20:00","uploaded":"2024-06-03 05:31:28","revisionof":"S2-2406580","revisedto":"S2-2407312","release":"Rel-18","crspec":"23.502","crspecversion":"18.5.0","workitem":[{"winame":"EDGEAPP"},{"winame":" TEI18"}],"crnumber":4805.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2407110.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.15.10A, 5.2.6.27.2, 2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407312","title":"Corrections to Nnef_UEId Service","source":"AT&T, Ericsson, Samsung, Nokia, Google, Apple","contact":"Hyesung Kim","contact-id":83054,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies the conditions on the usage of the MSISDN retrieval (clause 4.15.10A) to allow the usage of Nnef_UEId Service for retrieving MSISDN by an authorized AF by adding reference to TS 33.501.","secretary_remarks":"Revision of S2-2407110. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10680,"status":"agreed","reservation_date":"2024-03-06 05:15:08","uploaded":"2024-06-03 05:41:10","revisionof":"S2-2407110","revisedto":"","release":"Rel-18","crspec":"23.502","crspecversion":"18.5.0","workitem":[{"winame":"EDGEAPP"},{"winame":" TEI18"}],"crnumber":4805.0,"crrevision":6.0,"crcategory":"F","tsg_crp":"SP-240602","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2407312.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.15.10A, 5.2.6.27.2, 2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407313","title":"Reply LS on the stage 2 aspects of MINT_Ph2","source":"SA WG2","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"LS out","for":"Approval","abstract":"To: TSG SA","secretary_remarks":"Revision of S2-2406878. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10430,"status":"approved","reservation_date":"2024-03-06 05:15:09","uploaded":"2024-06-03 07:31:13","revisionof":"S2-2406878","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"MINT_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2405884","lsto":"TSG SA","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2407313.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407314","title":"LS Reply on Internal 5G Core information expose to trusted AF","source":"SA WG2","contact":"Tianji Jiang","contact-id":90312,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG6. CC: SA WG3, SA WG5.","secretary_remarks":"Revision of S2-2406877. Revised to S2-2407354.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10510,"status":"revised","reservation_date":"2024-03-06 05:15:09","uploaded":"2024-06-03 05:41:10","revisionof":"S2-2406877","revisedto":"S2-2407354","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NSCALE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"SA WG3, SA WG5","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2407314.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407315","title":"23.501 Cleanup CR","source":"Nokia","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Editorial cleanup for improved readability","secretary_remarks":"Revision of S2-2406881. This CR was agreed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10590,"status":"agreed","reservation_date":"2024-03-06 05:15:09","uploaded":"2024-06-03 05:41:10","revisionof":"S2-2406881","revisedto":"","release":"Rel-18","crspec":"23.501","crspecversion":"18.5.0","workitem":[{"winame":"TEI18"}],"crnumber":5404.0,"crrevision":2.0,"crcategory":"D","tsg_crp":"SP-240602","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2407315.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":false,"clauses_affected":"5.37.5.2, 5.37.8.2, 8.3.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407316","title":"Editorial cleanup","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Corrected step reference and other editorial modifications for PDU session release PDU Session Id changed to PDU Session ID Removal of redundant and incomplete text in step 3 of 4.16.11.1 Corrected the clause reference 4.22.2.3 to 4.22.2.4 in Clause 4.22.2.4.1. Corrected spelling and aligned some terms Corrected Npcf_UEPolicyControl UpdateNotify Corrected name for PDUSession_Create Corrected unsubscription request to unsubscribe request Corrected Nnsacf_SliceEvent Exposure_Notify Use PCF for the UE Use PCF for the PDU Session","secretary_remarks":"Revision of S2-2406882. This CR was agreed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10630,"status":"agreed","reservation_date":"2024-03-06 05:15:11","uploaded":"2024-06-03 05:41:10","revisionof":"S2-2406882","revisedto":"","release":"Rel-18","crspec":"23.502","crspecversion":"18.5.0","workitem":[{"winame":"TEI18"}],"crnumber":4823.0,"crrevision":3.0,"crcategory":"D","tsg_crp":"SP-240602","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2407316.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407317","title":"Cleanup CR for TS 23.503","source":"Huawei (Rapporteur)","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 3.2: adding abbreviations (HR-SBO) Clause 4.1: update (as the interface between the two PCFs is standardized meanwhile) Clause 4.2.6: moving two bullets to clause 4.3.6 (to align with statements in clause 4.3.7) and correcting a reference Clause 4.3.6: adding and reordering references (to better clarify their related specification) Clause 5.2.1: terminology update (PCF for a -> PCF for the ) Clause 5.2.2: adding reference for SEPP; aligning intro text with clause 5.2.1; clarifying terms and meaning of Note 7 Clause 5.3.2: clarifying terms and meaning of Note Clause 5.3.11: simplification (to reduce efforts when further analytics will be added) and removing inconsistency (as the listed names are Analytics Ids) Clause 5.3.12: terminology update (PCF for a -> PCF for the ) and adding of reference (to reduce efforts when further events will be added) Clause 6.1.1.1, 6.1.1.2.2 and 6.1.1.2a: terminology update (PCF for a -> PCF for the ) Clause 6.1.2.2.3: correcting terminology (AF guidance -> application guidance; URSPs -> URSP rules) and adding reference to 23.502 Clause 6.1.2.2.4: extending the table numbers (6.2- -> 6.2.1.3- ) Clause 6.1.3.1: update (as the interface between the two PCFs is standardized meanwhile) Clause 6.1.3.2.4: moving notes to related bullet; correcting terminology (PDU Set Handling Information -> PDU Set Control Information; QoS flow -> QoS Flow) Clause 6.1.3.18: terminology update (PDU session -> PDU Session; QoS flow -> QoS Flow; PCF for a -> PCF for the ; QoS monitoring parameter -> QoS Monitoring parameter) Clause 6.1.3.21: correcting typos and terminology; adding reference and correcting reference Clause 6.1.3.22: correcting identation of 4 paragraphs; moving 3 paragraphs to the end of the clause (as they break the logic of the description) Clause 6.1.3.24: aligning terminology with clause 6.3.1. and 23.501 (indication on whether the PDU Session is a redundant PDU Session or not -> indication that the PDU Session is a redundant PDU Session) Clause 6.1.3.27.1: correcting terminology and reference Clause 6.1.3.27.4: aligning terminology with clause 5.37.5 of 23.501 (PDU Set QoS handling -> PDU Set based handling) Clause 6.1.3.27.5: aligning terminology with clause 5.37.8.3 of 23.501 and clause 6.3.1 (Data Burst End Marking Indication -> End of Data Burst Marking Indication) Clause 6.1.3.27.6: undoing Italic text format and aligning terminology with clause 5.37.8 of 23.501 (power saving -> UE power saving) Clause 6.1.4.3: correcting terminology (remaining data rate -> Remaining Maximum Slice Data Rate) Clause 6.1.6: moved to clause 6.1.1.x (as this is not a new type of policy) together with terminology update (PCF for a -> PCF for the ) Clause 6.2.1.3: extending the table numbers (6.2- -> 6.2.1.3- ) Clause 6.2.1.12: correcting terminology and typo Clause 6.2.3: correcting terminology (AF guidance -> application guidance; QoS monitoring parameter -> QoS Monitoring parameter) Clause 6.3.1: correcting references and aligning terminology with clause 5.37.8 of 23.501 (power saving -> UE power saving) Clause 6.4: correcting terminology (PDU session -> PDU Session) and aligning terminology (Authorized Session-AMBR for Offloading -> Authorized DL Session AMBR for Offloading) Clause 6.6.1.1: extending the table numbers (6.6.1- -> 6.6.1.1- ) Clause 6.6.2.1: correcting terminology (PDU session -> PDU Session; traffic descriptor -> Traffic descriptor) Clause 6.6.2.3: correcting terminology (PDU session -> PDU Session; Route Selection Description -> Route Selection Descriptor; Traffic Descriptor -> Traffic descriptor) Clause 6.6.2.4: undoing the additions coming from CR#1120 (approved in S2-2401567 at SA WG2#160AHe) which was obsoleted by CR#1243 (approved in S2-2403461 at SA WG2#161); aligning the logic of the bullets by adding '; or' to 2nd and 3rd bullet; adding missing reference Clause 3.2, 4.3.4, 6.1.3.26, 6.1.3.27.3, 6.5: correcting typo(s)","secretary_remarks":"Revision of S2-2406880. This CR was agreed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10560,"status":"agreed","reservation_date":"2024-03-06 05:15:12","uploaded":"2024-06-03 05:41:10","revisionof":"S2-2406880","revisedto":"","release":"Rel-18","crspec":"23.503","crspecversion":"18.5.0","workitem":[{"winame":"TEI18"}],"crnumber":1299.0,"crrevision":2.0,"crcategory":"D","tsg_crp":"SP-240602","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2407317.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":false,"clauses_affected":"3.2, 4.1, 4.2.6, 4.3.4, 4.3.6, 5.2.1, 5.2.2, 5.3.2, 5.3.10, 5.3.11, 5.3.12, 6.1.1.1, 6.1.1.2.2, 6.1.1.2a, 6.1.1.x (new), 6.1.2.2.3, 6.1.2.2.4, 6.1.3.1, 6.1.3.2.4, 6.1.3.18, 6.1.3.21, 6.1.3.22, 6.1.3.24, 6.1.3.26, 6.1.3.27.1, 6.1.3.27.3, 6.1.3.27.4, 6.1.3.27.5, 6.1.3.27.6, 6.1.4.3, 6.1.6, 6.2.1.3, 6.2.1.12, 6.2.3, 6.3.1, 6.4, 6.5, 6.6.1.1, 6.6.2.1, 6.6.2.3, 6.6.2.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407353","title":"Reply LS on Clarification related to the predictive slice modification in Inter-PLMN based slice service continuity","source":"SA WG2","contact":"Peter Hedman","contact-id":27550,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG6. CC: CT WG3, SA WG5","secretary_remarks":"Revision of S2-2406876. This LS OUT was approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10380,"status":"approved","reservation_date":"2024-03-06 05:15:17","uploaded":"2024-06-03 05:41:10","revisionof":"S2-2406876","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NSCALE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2405877","lsto":"SA WG6","Cc":"CT WG3, SA WG5","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2407353.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2407354","title":"LS Reply on Internal 5G Core information expose to trusted AF","source":"SA WG2","contact":"Tianji Jiang","contact-id":90312,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG6. CC: SA WG3, SA WG5.","secretary_remarks":"Revision of S2-2407314. This LS OUT was approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10520,"status":"approved","reservation_date":"2024-03-06 05:15:17","uploaded":"2024-06-03 05:41:10","revisionof":"S2-2407314","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NSCALE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2406846","lsto":"SA WG6","Cc":"SA WG3, SA WG5","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_163_Jeju_2024-05\/Docs\/S2-2407354.zip","group":"S2","meeting":"S2-163","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]