[{"name":"S2-2403867","title":"LS from GSMA 5GMRR: LS to 3GPP on data plane control by roaming hubs","source":"GSMA 5GMRR","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"Introduction: GSMA 5GMRR would like to draw the attention of 3GPP to the following requirements again: 1. The RH shall have the ability to intervene in roaming data sessions at any time, in order to limit roaming data usage by limiting throughput and\/or stopping ongoing data sessions as agreed with the client HPMN. This ability to intervene requires anchoring the media in this intermediary. 2. All N32 messages between client MNOs are transferred via the RH. This shall include the ability for the RH to prevent the establishment of, and the termination of N32-c and N32-f connections, for example if this is required due to contractual reasons. As a clarification to requirement 1: The RH shall be able to intervene on roaming data sessions on the basis of individual PDU sessions and across all PDU sessions of the roamers of a given roaming relationship between two PLMNs. Request to 3GPP: GSMA kindly requests SA WG1 and SA WG2 to review these requirements and define solutions. GSMA 5GMRR welcomes an initial response and ongoing collaboration.","secretary_remarks":"Revision of postponed S2-2401859 from S2#161. Response drafted in S2-2404814. Final response in S2-2405815","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10250,"status":"replied to","reservation_date":"2024-03-26 09:41:09","uploaded":"2024-03-26 09:50:50","revisionof":"S2-2401859","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG2","Cc":"SA WG3, SA WG5, TSG SA, CT WG4","lsoriginalls":"5GMRR Doc 47_14r1","lsreply":"S2-2405815, S2-2405815","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403867.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403868","title":"LS from AECC: LS on Updated AECC Publications for Future Connected Vehicle Services","source":"Automotive Edge Computing Consortium (AECC)","contact":"Lei Zhong","contact-id":85285,"tdoctype":"LS in","for":"Action","abstract":"The Automotive Edge Computing Consortium (AECC, https:\/\/aecc.org\/) would like to share the recent publications with TSG SA and corresponding WGs for alignment of the potential connected vehicle services in the future. AECC is greatly interested in accelerating the deployment of connected vehicle services based on distributed computing infrastructure. Such a goal is also achieved by identifying, developing and accessing functional and performance requirements of mobile networks and compute platforms, that are deemed important to enable prioritized and high-value automotive services. To this extent, AECC will require standardized solutions which are industry-wide aligned and introduced in the market. The newest version of the white paper AECC General Principle and Vision, available at https:\/\/aecc.org\/wp-content\/uploads\/2024\/02\/AECC_General_Principle_and_Vision_v4.0.3-rev02.pdf is updated with three new services scenarios and use cases. The Green Mobility scenario in chapter 3.6.4 priorities the necessity of optimization across transportation system, energy system and ICT system, as the demanding of renewable energy, new energy powered vehicles and sustainable ICT infrastructures. The Digital Twin scenario in chapter 3.5 briefly illustrates the technical requirements of data fidelity, just-in-time Inference and action planning to realize the mobility digital twin use cases. The Vehicle Teleoperation service scenario defined in chapter 3.4 is becoming increasing important before the autonomous driving is fully realized. It can improve the availability and efficiency of mobility services through vehicle remote driving and in-car monitoring. Various network performances are discussed to meet the teleoperation requirements. The new version of the Driving Data to the Edge: The Challenge of Traffic Distribution Technical Report, available at https:\/\/aecc.org\/wp-content\/uploads\/2023\/12\/AECC_E2ENW_TR_v2.6.pdf is updated with two new key issues identified by the AECC technical solution WG. The service continuity and Geolocation services are of importance to connected vehicle services, further solution analysis are provided from the AECC end-to-end service architecture perspective. The new white paper entitled Connected Infrastructure for the Realization of the Green Mobility Society, available at https:\/\/aecc.org\/wp-content\/uploads\/2023\/11\/20230915_EN_Connected_infrastructure_for_the_realization_of_Green_Mobility_Society.Designed_10.20pdf.pdf is dedicated to investigate the green mobility challenges for the future society. In the publication, the trend of AI-powered mobility services and new energy shifting in the transportation are highlighted, which bring up the green mobility society vision to address the energy consumption challenges. It shows the essential role of mobile network and IT infrastructure, referred to as 'connected infrastructure,' in supporting the evolution of green mobility and the adoption of new technologies such as Generative AI in the automotive industry. Actions: AECC kindly invites SA WGs to review and provide feedback to the new contents of AECC publications.","secretary_remarks":"Response drafted in S2-2404609. Final response in S2-2405816","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10290,"status":"replied to","reservation_date":"2024-03-26 09:41:09","uploaded":"2024-03-26 09:50:50","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG1, SA WG2, SA WG5, SA WG6","lsoriginalls":"AECC_3GPP_LS_Mar2024","lsreply":"S2-2405816, S2-2405816","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403868.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403878","title":"LS from CT WG3: Reply LS on Support of interworking between SA4 RTC and IMS","source":"CT WG3","contact":"Haruka Eitoku","contact-id":73702,"tdoctype":"LS in","for":"Information","abstract":"CT WG3 thanks SA WG4 for the LS on Support of interworking between SA WG4 RTC and IMS. CT WG3 would like to inform the following answers to the question from SA WG4. {. . .}","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10050,"status":"noted","reservation_date":"2024-03-26 09:41:10","uploaded":"2024-03-26 18:43:10","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"SA WG1, SA WG2","lsoriginalls":"C3-241567","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403878.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403879","title":"LS from CT WG3: LS on handling UEs accessing to GERAN\/UTRAN over Gn\/Gp","source":"CT WG3","contact":"Susana Fernandez","contact-id":42321,"tdoctype":"LS in","for":"Action","abstract":"CT WG3 has discussed the scenarios related to the UE accessing GERAN\/UTRAN over Gn\/Gp interfaces based on the following text in clause 5.17.2.4 of TS 23.501: NOTE 4: GERAN\/UTRAN Mobility Management Bearer Synchronisation procedures will release any dedicated QoS Flows established in 5GS. NOTE 5: When the UE access the network via GERAN\/UTRAN over Gn\/Gp interface, Secondary PDP Context Activation Procedure is not supported. According to these notes, the following concern was raised in CT WG3: Both AF and PCF may need to be aware of UE is accessing the network via GERAN\/UTRAN over Gn\/Gp interface in order to avoid the reservation of resources till the UE moves back to a network that supports dedicated QoS flows. Otherwise, the 2G3GIWK over Gn\/Gp interface may not work properly. CT WG3 would like to ask SA WG2: Question 1: Whether the PCF and\/or AF should identify the SGSN type change, and revert to normal handling when the UE moves back to a network with dedicated bearer\/QoS flow support. Action: CT WG3 kindly request SA WG2 to answer the above question and update the impacted Technical Specifications if needed.","secretary_remarks":"Responses drafted in S2-2404406, S2-2404833. Final response in S2-2405817","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10330,"status":"replied to","reservation_date":"2024-03-26 09:41:10","uploaded":"2024-03-26 18:43:10","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C3-241569","lsreply":"S2-2405817, S2-2405817","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403879.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403880","title":"LS from CT WG3: LS on Clarification related to the predictive slice modification in Inter-PLMN based slice service continuity.","source":"CT WG3","contact":"Rajesh Babu Natarajan","contact-id":89232,"tdoctype":"LS in","for":"Information","abstract":"Overall description As per TS 23.435, cl 9.13 {. . .} Question 1: How does the VAL server know which target PLMN the UE would move, when HPLMN has roaming agreements with multiple VPLMNs? For e.g. HPLMN (PLMN1) can have roaming agreement with multiple VPLMNs, how is PLMN2 selected? (even as per TS 23.434, cl 5, HPLMN can have roaming agreement with multiple PLMNs) Question 2: Assumption 4 indicate NSCE server connects to only the OAM of PLMN1 and PLMN2, but in the call flow, it interacts with 5GC. Please clarify? Question 3: From step 1, is slice#1 in PLMN1 and slice#2 in PLMN2 created based on VAL server request? Question 4: How does the NSCE server respond in step 2, even before determining to query the underlying 5G system on slice availability in the step 3? Question 5: From step 3a, such predicted UE mobility information is within the scope of the PLMN only. Who does the correlation of predicted UE mobility from each PLMN and then predict the inter PLMN mobility? Question 6: What about slice service continuity within the PLMN? What if the slice is not available in the predicted UE mobility path within the PLMN1 itself? Will NSCE server provide slice modification request to the slice within PLMN1?","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10060,"status":"noted","reservation_date":"2024-03-26 09:41:10","uploaded":"2024-03-26 18:43:10","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"SA WG2, SA WG5","lsoriginalls":"C3-241577","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403880.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403883","title":"LS from CT WG4: Reply LS on Authorization of NF service consumer for data collection via DCCF","source":"CT WG4","contact":"Bruno Landais","contact-id":68755,"tdoctype":"LS in","for":"Information","abstract":"CT WG4 thanks CT WG3 for their LS (C3-235594) on Authorization of NF service consumer for data collection via DCCF. Clause X.2 of TS 33.501 specifies how to handle the case where a new Data Consumer requests the DCCF to access data for which the DCCF already created a subscription to the NF Service Producer: NOTE 6: In the case a new NF Service Consumer comes at a later stage to request the data, which is already being collected by DCCF, steps 1-10 apply. When the request is received by the NF Service Producer (i.e. the data producer), it authenticates the NF Service Consumer and verifies the access token provided along with the service request and sends to DCCF the access token verification response. DCCF based upon the response received, either updates the subscription info to include the new NF Service Consumer as well and sends the data to both the consumers (as specified in Clause 6.2.6.3.2 in TS 23.288 [105]), or in the case of access token verification failure, the DCCF rejects the request received by the NF Service Consumer. Accordingly, CT WG4 has agreed the attached 29.500 CR clarifying how a Data Source (NF Service Producer) authorizes a new Data Consumer (Source NF Instance), when a new Data Consumer requests the DCCF to access data for which the DCCF already created a subscription to the NF Service Producer.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10070,"status":"noted","reservation_date":"2024-03-26 09:41:10","uploaded":"2024-03-26 18:43:10","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"SA WG3, SA WG2","lsoriginalls":"C4-240623","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403883.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403884","title":"LS from CT WG4: LS reply on defining new GTP-U Extension Header for PDU Set related information","source":"CT WG4","contact":"Yong Yang","contact-id":42295,"tdoctype":"LS in","for":"Information","abstract":"CT WG4 thanks RAN WG3 for their LSs (R3-237845) on 'defining new GTP-U Extension Header for PDU Set related information'. CT WG4 agreed to define a new GTP-U Extension Header 'PDU Set Information Container' in 3GPP TS 29.281 as in attached CR.","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-03-26 09:41:10","uploaded":"2024-03-26 18:43:10","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"SA WG2","lsoriginalls":"C4-240800","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403884.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403887","title":"LS from RAN WG2: Reply LS on SL-PRS resource allocation","source":"RAN WG2","contact":"XIAOWEI JIANG","contact-id":66759,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 would like to thank RAN WG1 and RAN WG3 for the LS on SL-PRS resource allocation, and would like to ask RAN WG1 and RAN WG3 to take the following RAN WG2 feedback into consideration: RAN WG2 made the following agreements related to the request for specific SL-PRS resource characteristic(s)\/SL-PRS resource configuration for scheme 1: Agreement 1. Include the SL-PRS bandwidth in the SL-PRS resource request MAC CE for aperiodic SL-PRS transmission and RRC UAI message for periodic SL-PRS transmission. 2. RAN WG2 will not specify anything in this release for SL-PRS bandwidth indication from LMF to gNB. 3. Indicate in the LS to RAN WG3 that the LMF is not involved in SL-PRS resource allocation.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10090,"status":"noted","reservation_date":"2024-03-26 09:41:11","uploaded":"2024-03-26 18:43:10","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG1, RAN WG3","Cc":"SA WG2","lsoriginalls":"R2-2401643","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403887.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403892","title":"LS from RAN WG3: Reply LS on user consent for trace reporting","source":"RAN WG3","contact":"Centonza Angelo","contact-id":46148,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 would like to thank SA WG5 for its LS on the support of user consent for trace and for updating the User consent handling in MDT for NG-RAN. RAN WG3 has discussed the received LS and would like to indicate that: - Descriptions on requirements to the UDM is not in scope of RAN WG3 specifications. - RAN WG3 has updated the user consent description by substituting the term data types with MDT measurements instead. The latter terminology is better suited and in line with current RAN WG3 specifications. It should be noted that RAN WG3 specifications never refer to MDT Measurement name . 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.","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-03-26 09:41:11","uploaded":"2024-03-26 18:43:10","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"RAN WG2, SA WG2, SA WG3","lsoriginalls":"R3-241115","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403892.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403895","title":"LS from RAN WG3: Reply LS on the progress update of AI\/ML Management specifications in SA5","source":"RAN WG3","contact":"Jiajun Chen","contact-id":84462,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 thanks SA WG5 for the LS in R3-240032 (S5-238107) on the progress update of AI\/ML management specifications in SA WG5. RAN WG3 did not work on lifecycle management of AI\/ML model in R18, and RAN WG3 mainly focused on the normative work on the data needed to support AI\/ML based use cases during Rel-18 phase. No requirement was identified related to lifecycle management of AI\/ML model from RAN WG3 perspective in R18.","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-03-26 09:41:11","uploaded":"2024-03-26 18:43:10","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"TSG RAN, RAN WG1, RAN WG2, TSG SA, SA WG1, SA WG2","lsoriginalls":"R3-241183","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403895.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403901","title":"LS from SA WG1: Reply LS to S1-240153\/ RP-234075 on Robust Notification Alert for NTN-NR","source":"SA WG1","contact":"Munira Jaffar","contact-id":76312,"tdoctype":"LS in","for":"Action","abstract":"SA WG1 thanks TSG RAN for the LS in S1-240153\/RP-234075. SA WG1 does not have requirement relating to the Robust Notification Alert for NTN-NR. SA has frozen the stage 1 of Release 19. SA WG1 has agreed the study on Satellite Access Phase 4 for Release 20 (FS_5GSAT_Ph4), a study for 5G system with satellite access, where one of the objectives include to study ability to notify the user that a mobile terminated communication (e.g. MMTel call) had failed when the UE was unreachable in satellite access. Action: SA WG1 kindly asks TSG RAN and SA WG2 to take the above information into consideration.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10240,"status":"noted","reservation_date":"2024-03-26 09:41:11","uploaded":"2024-03-26 18:43:10","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, SA WG2","Cc":"TSG SA","lsoriginalls":"S1-240309","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403901.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403902","title":"LS from SA WG3: Reply LS on Issues related to user consent for retrieving data stored in the ADRF\/NWDAF","source":"SA WG3","contact":"Wu Rong","contact-id":49499,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 thanks CT WG3 the LS on Issues related to user consent for retrieving data stored in the ADRF\/NWDAF. SA WG3 would like to respond with the corresponding answers. {. . .}","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-03-26 09:41:11","uploaded":"2024-03-26 18:43:10","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"SA WG2","lsoriginalls":"S3-240829","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403902.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403903","title":"LS from SA WG3: Reply LS on Authorization of NF service consumer for data collection via DCCF","source":"SA WG3","contact":"Wu Rong","contact-id":49499,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 thanks CT WG3 the LS on Authorization of NF service consumer for data collection via DCCF. There is a note in TS 33.501 clause Annex.X.2 as following: NOTE 6: In the case a new NF Service Consumer comes at a later stage to request the data, which is already being collected by DCCF, steps 1-10 apply. When the request is received by the NF Service Producer (i.e. the data producer), it authenticates the NF Service Consumer and verifies the access token provided along with the service request and sends to DCCF the access token verification response. DCCF based upon the response received, either updates the subscription info to include the new NF Service Consumer as well and sends the data to both the consumers (as specified in Clause 6.2.6.3.2 in TS 23.288 [105]), or in the case of access token verification failure, the DCCF rejects the request received by the NF Service Consumer. Therefore, the DCCF shall update the subscription information to include the new NF Service Consumer(s)\/source Data Consumer(s) after the authorization is successful performed by the NF Service Producer\/Data Source. In other words, the Data Source can get and\/or authorize the CCA of the new Data Consumer(s) to retrieve the same data in step10 of Annex X.2 of TS 33.501.","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-03-26 09:41:11","uploaded":"2024-03-26 18:43:10","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"CT WG4, SA WG2","lsoriginalls":"S3-240830","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403903.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403904","title":"LS from SA WG3: LS on UUAA Status Information availability for SMF","source":"SA WG3","contact":"Sheeba Backia Mary Baskaran","contact-id":86031,"tdoctype":"LS in","for":"Information","abstract":"Thanks for the clarification question asked in LS C4-230790 related to the need of uavAuthenticated information element. CT WG4 Question: CT WG4 kindly asks SA WG3 to clarify why the functionality of uavAuthenticated information element is needed. SA WG3 Answer: According to SA WG3 UUAA is to authenticate the UAV for security reasons, and we do not see any security benefits in repeating. But in the latest SA WG2 TS 23.256 V18.2.0, texts were removed related to AMF and SMF relations on UUAA execution [See SP-231244]. In its current form UUAA is triggered during registration and PDU session establishment independently. To align with latest SA WG2 TS 23.256 V18.2.0, SA WG3 agreed the Rel.17 and Rel.18 CRs which are attached here for your information.","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-03-26 09:41:11","uploaded":"2024-03-26 18:43:10","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"SA WG2, CT WG1","lsoriginalls":"S3-240835","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403904.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403906","title":"LS from SA WG3: Reply LS on AKMA service restrictions","source":"SA WG3","contact":"Xiaoting Huang","contact-id":78337,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 thanks CT WG3 for the LS on clarification on AKMA service restrictions. SA WG3 provides the following response: Question1: Is Rel-17 AKMA services supported for the UE connected via Non-3GPP access? Answer1: Yes, AKMA services is used regardless of access type. Question2: If the answer to Question 1 is affirmative, then how the network could identify the PDU session is related to roaming UE and deny AKMA services? Answer2: SA WG3 would like to confirm that AKMA roaming is not considered by Rel-17 AKMA architecture and procedures. For Rel-18, the necessary stage 2 modifications in TS 33.535 to control if AKMA is turned on or off in roaming are implemented in the attached CR S3-240915.","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-03-26 09:41:11","uploaded":"2024-03-26 18:43:10","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"SA WG2, SA WG3-LI","lsoriginalls":"S3-240837","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403906.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403907","title":"LS from SA WG3: Reply LS on IPX Service Hub requirements as applicable to the Modified PRINS solution","source":"SA WG3","contact":"Hongyi Pu","contact-id":97938,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 received several LSes from GSMA 5GMRR related to the recent work on the modified PRINS solution. SA WG3 assumes that SA will coordinate a single reply to GSMA. Therefore, SA WG3 would like to provide the following feedback on the requests included in S3-240209 on IPX Service Hubs and IPX Providers: {. . .}","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-03-26 09:41:11","uploaded":"2024-03-26 18:43:10","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG1, SA WG2, TSG CT, CT WG4","lsoriginalls":"S3-240888","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403907.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403911","title":"LS from SA WG3: Reply LS on AKMA service restrictions","source":"SA WG3","contact":"Xiaoting Huang","contact-id":78337,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 thanks CT WG3 for the LS on clarification on AKMA service restrictions. SA WG3 provides the following response: Question1: Is Rel-17 AKMA services supported for the UE connected via Non-3GPP access? Answer1: Yes, AKMA services is used regardless of access type. Question2: If the answer to Question 1 is affirmative, then how the network could identify the PDU session is related to roaming UE and deny AKMA services? Answer2: SA WG3 would like to confirm that AKMA roaming is not considered by Rel-17 AKMA architecture and procedures. For Rel-18, the necessary stage 2 modifications in TS 33.535 to control if AKMA is turned on or off in roaming are implemented in the attached CR S3-240915.","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-03-26 09:41:12","uploaded":"2024-03-26 18:43:10","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"SA WG2, SA WG3-LI","lsoriginalls":"S3-241042","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403911.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403912","title":"LS from ETSI ISG THz: LSout to Key SDOs on the publication of GR THz 001 and GR THz 002","source":"ETSI ISG THz","contact":"Thomas K\u00fcrner","contact-id":98605,"tdoctype":"LS in","for":"Information","abstract":"With this Liaison Statement ETSI s Industry Specification Group on Terahertz Communications (THz) wants to inform that it has achieved its first milestone and published the first two Group Reports: - ETSI GR THz 001 on Identification of use cases for THz communication systems identifies and describes use cases either enabled by or highly benefiting from the use of THz communications. Aspects addressed in the present document include deployment scenarios, potential requirements, relevant operational environments and their associated propagation characteristics and\/or measurements. https:\/\/www.etsi.org\/deliver\/etsi_gr\/THz\/001_099\/001\/01.01.01_60\/gr_THz001v010101p.pdf - ETSI GR THz 002 on Identification of frequency bands of interests for THz communication system identifies frequency bands of interest in the sub-THz and THz range, describes the current regulatory situation and identifies the incumbent services to be considered for coexistence studies https:\/\/www.etsi.org\/deliver\/etsi_gr\/THz\/001_099\/002\/01.01.01_60\/gr_THz002v010101p.pdf ETSI ISG THz renews its encouragement for a continual exchange with relevant standardisation groups\/bodies (either inside or outside of ETSI) to ensure they are informed and consider the work of ISG THz in their further relevant technology specifications developments. Further information on the ISG THz terms of reference, work programme, planned deliverables, and other documentations are available through the ISG portal: Link to ISG THz Portal. Actions: To inform us about any future deliverables, that will deal with THz use cases and spectrum for THz communications and consider how our deliverables could contribute to your ongoing work.","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-03-26 09:41:12","uploaded":"2024-04-02 08:23:07","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP, SA WG1, TSG RAN, Key SDOs","Cc":"","lsoriginalls":"THz(24)000048r2","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403912.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403913","title":"LS from ITU-T SG17: LS on the proposal for a new work item: Security guidelines for data of coordination of networking and computing","source":"ITU-T SG17","contact":" Anonymous","contact-id":4132,"tdoctype":"LS in","for":"Information","abstract":"This liaison statement is aimed to inform SA WG1, SA WG2 and ITU-T SG13 on the initiation of new work item ITU-T TR.sd-cnc: 'Security guidelines for data of coordination of networking and computing'.","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-03-26 09:41:12","uploaded":"2024-04-02 08:23:07","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG13, SA WG1, SA WG2","Cc":"","lsoriginalls":"sp17-sg17-oLS-00096","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403913.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403914","title":"LS from ITU-T SG17: LS on the proposal for a new work item: Security considerations for interconnection of computing power centers","source":"ITU-T SG17","contact":" Anonymous","contact-id":4132,"tdoctype":"LS in","for":"Information","abstract":"This liaison statement informs ITU-T SG2, SG11, SG13, SA WG2, SA WG3 and IETF CATS on the initiation of new work item ITU-T TR.sec-int-cpc: 'Security considerations for interconnection of computing power centers'.","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-03-26 09:41:12","uploaded":"2024-04-02 08:23:07","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG2, SG11, SG13, SA WG2, SA WG3, IETF CATS","Cc":"","lsoriginalls":"SG17-LS99-TD1957R1","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403914.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403917","title":"LS from TSG SA: LS on the Modified PRINS solution","source":"TSG SA","contact":"Susana Sabater","contact-id":31269,"tdoctype":"LS in","for":"Information","abstract":"TSG SA would like to thank GSMA 5GMRR for their collaboration on the topic of modified PRINS. TSG SA would like to inform GSMA 5GMRR about the progress on modified PRINS across the different groups. TSG SA has agreed that the solution for Modified PRINS functionality, as specified by SA WG3 group in TS 33.501 for Release 18, can be applicable to Release 16 and 17 deployments, as per the attached CR. The protocol implementation as specified by CT WG4 group in TS 29.573 has also been approved. These enable the desired functionality on N32 interconnect, i.e. intermediaries are able to be informed about errors on N32f, send errors themselves as well as originate applicative requests over N32f. It is the understanding of TSG SA that these modifications enable GSMA to endorse deployment of PRINS for interconnect scenarios, in which an intermediary, especially a Roaming Hub, is required. Additionally, TSG SA wants to provide, on behalf of SA WG3, the following answers to GSMA 5GMRR: Answer to Q 1 in 5GMRR Doc 45_13r7: Regarding the definition of Roaming Hub, SA WG3 has agreed a CR S3-240891 for TS 33.501 on the definition of Roaming Hub according to the LS S3-240208 received from GSMA. Answer to Q 2.b in 5GMRR Doc 45_13r7: Regarding the requirement related to the RH ability to prevent the establishment of, and to terminate the N32-c and N32-f connections, SA WG3 believes that the RH can request SEPP to terminate the N32-c and N32-f connections if necessary, as described in clause 5.5, TS 29.573, based on the error message received from the RH. Answer to Q 1 in 5GMRR Doc 45_14r7: Regarding the definition of IPX Service Hub and IPX Provider, SA WG3 finds that the definition of IPX Service Hub is unclear, and would like GSMA to clarify the definition of IPX Service Hub. Answer to Q 2.b in 5GMRR Doc 45_14r7: Regarding the requirement of IPX Service Hub to aggregate N32 signalling traffic and use common identities, SA WG3 would like GSMA to clarify what does the aggregation mean. Finally, TSG SA wants to kindly inform GSMA 5GMRR that 3GPP welcome liaisons correspondence, however, TSG SA would like to remind GSMA 5GMRR that work is based on direct contributions made by 3GPP members.","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-03-26 09:41:12","uploaded":"2024-04-08 06:00:36","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4, GSMA 5GMRR","Cc":"SA WG1, SA WG3, SA WG2, TSG CT","lsoriginalls":"SP-240503","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403917.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403918","title":"LS from GSMA OPG: LS on GSMA OPG PRDs publication","source":"GSMA OPG","contact":"Sandra Ondrusova","contact-id":77474,"tdoctype":"LS in","for":"Information","abstract":"GSMA OPG would like to notify 3GPP and ETSI of the publication of new documents and recent release of several GSMA PRDs: {. . .} Actions: GSMA OPG kindly ask 3GPP and ETSI to take the above into consideration.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10210,"status":"noted","reservation_date":"2024-03-26 09:41:12","uploaded":"2024-04-08 06:00:36","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG5, SA WG6, ETSI ISG MEC, ETSI ISG NFV","Cc":"TSG SA, SA WG3","lsoriginalls":"OPG_172_Doc_03","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403918.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403919","title":"LS from ITU-T SG13: LS on consent of draft new Recommendation ITU-T Y.3162 (ex Y.IMT-2020-EIL) 'Evaluating intelligence capability for network slice management and orchestration in IMT-2020 network and beyond'","source":"ITU-T SG13","contact":"Yushuang Hu","contact-id":96973,"tdoctype":"LS in","for":"Information","abstract":"This liaison statement informs about the progress of new Recommendation ITU-T Y.3162 'Evaluating intelligence capability for network slice management and orchestration in IMT-2020 network and beyond'.","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-03-26 09:41:12","uploaded":"2024-04-11 11:30:55","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG2, SG11, SA WG2, SA WG5, ETSI ZSM","Cc":"","lsoriginalls":"SG13-LS167","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403919.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404406","title":"[DRAFT] Response LS on handling UEs accessing to GERAN\/UTRAN over Gn\/Gp","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Response LS On handling UEs accessing to GERAN\/UTRAN over Gn\/Gp","secretary_remarks":"Response to S2-2403879. Revised, merging S2-2404833, to S2-2405208.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10340,"status":"revised","reservation_date":"2024-04-04 14:39:30","uploaded":"2024-04-05 15:48:39","revisionof":"","revisedto":"S2-2405208","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"TEI18"},{"winame":" 5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404406.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404407","title":"Clarification on UEs accessing to GERAN\/UTRAN over Gn\/Gp","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that when the UE move from 5GS to GPRS network, the dedicated QoS flow esablished at the 5GC network need be released. This is done by the SMF+PGW-C trigger this release and not need PCF or AF triggered. For the 2nd PDP context activation via Gn\/Gp access, the SMF+PGW-C reject the request if UE request it.","secretary_remarks":"Revised to S2-2405209.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10380,"status":"revised","reservation_date":"2024-04-04 14:39:30","uploaded":"2024-04-05 15:48:39","revisionof":"","revisedto":"S2-2405209","release":"Rel-18","crspec":"23.501","crspecversion":"18.5.0","workitem":[{"winame":"TEI18"},{"winame":" 5GS_Ph1"}],"crnumber":5369.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404407.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.17.2.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404526","title":"CBC deployment at shared networks for CBS.","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Decision","abstract":"It is observed that use of multiple CBC in 5GS shared network scenarios suffer from the same issues as in EPS shared network scenarios, and it is proposed to capture the use of a single common CBC in 5GS shared network scenarios as is captured for EPS shared network scenarios.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10400,"status":"noted","reservation_date":"2024-05-04 02:00:39","uploaded":"2024-04-05 22:38:05","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404526.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404527","title":"[DRAFT] LS on 5GS missing CBC support for shared networks","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Draft LS proposal to CT WG1","secretary_remarks":"Revised to S2-2405210.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10410,"status":"revised","reservation_date":"2024-05-04 02:00:39","uploaded":"2024-04-05 22:38:05","revisionof":"","revisedto":"S2-2405210","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG1, RAN WG2, RAN WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404527.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404609","title":"[DRAFT] Reply LS from SA WG2 on Updated AECC Publications for Future Connected Vehicle Services","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"LS out","for":"Approval","abstract":"[Draft] Reply LS from SA WG2 on Updated AECC Publications for Future Connected Vehicle Services","secretary_remarks":"Response to S2-2403868. Revised to S2-2405207.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10300,"status":"revised","reservation_date":"2024-05-04 07:48:45","uploaded":"2024-04-05 09:27:20","revisionof":"","revisedto":"S2-2405207","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA","Cc":"SA WG1, SA WG5, SA WG6","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404609.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404733","title":"MSISDN exposure through NEF UEId Service.","source":"Apple","contact":"Sudeep M Vamanan","contact-id":103491,"tdoctype":"discussion","for":"Endorsement","abstract":"-","secretary_remarks":"Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10430,"status":"not treated","reservation_date":"2024-05-04 10:37:28","uploaded":"2024-04-05 20:23:59","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"TEI18"},{"winame":" EDGEAPP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404733.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404814","title":"[DRAFT] Reply LS on data plane control by roaming hubs","source":"Samsung","contact":"Jicheol Lee","contact-id":87580,"tdoctype":"LS out","for":"Approval","abstract":"SA WG2 suggests SA to coordinate the LS reply on this issue.","secretary_remarks":"Response to S2-2403867. Revised to S2-2405206.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10260,"status":"revised","reservation_date":"2024-05-04 13:46:10","uploaded":"2024-04-05 14:38:16","revisionof":"","revisedto":"S2-2405206","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG1, SA WG3, SA WG5, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404814.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404833","title":"[DRAFT] Reply LS on handling UEs accessing to GERAN\/UTRAN over Gn\/Gp","source":"Samsung","contact":"Jicheol Lee","contact-id":87580,"tdoctype":"LS out","for":"Approval","abstract":"SA WG2 replies to CT WG3 with the answer that the PCF can support the identified scenario using the existing specification and features.","secretary_remarks":"Response to S2-2403879. Merged into S2-2405208.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10370,"status":"merged","reservation_date":"2024-05-04 13:54:51","uploaded":"2024-04-05 14:38:17","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404833.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404983","title":"Corrections to Nnef_UEId Service","source":"AT&T, Ericsson","contact":"Rohit Abhishek","contact-id":95292,"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 and adds reference to TS 33.501.","secretary_remarks":"Revised to S2-2405211.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10440,"status":"revised","reservation_date":"2024-05-04 20:45:07","uploaded":"2024-04-05 20:54:09","revisionof":"","revisedto":"S2-2405211","release":"Rel-18","crspec":"23.502","crspecversion":"18.5.0","workitem":[{"winame":"TEI18"},{"winame":" EDGEAPP"}],"crnumber":4805.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404983.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405000","title":"Removal of Emergency Relay UE Location","source":"Nokia, Nokia Shanghai Bell","contact":"Mao Cai","contact-id":89487,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The misleading statement is removed.","secretary_remarks":"Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10510,"status":"not treated","reservation_date":"2024-05-04 23:41:41","uploaded":"2024-04-05 23:56:16","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"18.5.1","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":440.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405000.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.4.4.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405004","title":"NI-LR removal","source":"Nokia, Nokia Shanghai Bell","contact":"Mao Cai","contact-id":89487,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update clause 5.5.2 to remove the NI-LR.","secretary_remarks":"Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10520,"status":"not treated","reservation_date":"2024-05-04 23:41:44","uploaded":"2024-04-05 23:56:16","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.586","crspecversion":"18.3.0","workitem":[{"winame":"Ranging_SL"}],"crnumber":134.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405004.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.5.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405206","title":"Reply LS on data plane control by roaming hubs","source":"Samsung","contact":"Jicheol Lee","contact-id":87580,"tdoctype":"LS out","for":"Approval","abstract":"SA WG2 suggests SA to coordinate the LS reply on this issue.","secretary_remarks":"Revision of S2-2404814. Revised in parallel session to S2-2405815.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10270,"status":"revised","reservation_date":"2024-04-22 09:38:01","uploaded":"2024-04-22 10:01:23","revisionof":"S2-2404814","revisedto":"S2-2405815","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405206.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405207","title":"[DRAFT] Reply LS from SA WG2 on Updated AECC Publications for Future Connected Vehicle Services","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"LS out","for":"Approval","abstract":"[Draft] Reply LS from SA WG2 on Updated AECC Publications for Future Connected Vehicle Services","secretary_remarks":"Revision of S2-2404609. Revised in parallel session to S2-2405816.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10310,"status":"revised","reservation_date":"2024-04-22 09:38:01","uploaded":"2024-04-22 10:01:23","revisionof":"S2-2404609","revisedto":"S2-2405816","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA","Cc":"SA WG1, SA WG5, SA WG6","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405207.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405208","title":"[DRAFT] Response LS on handling UEs accessing to GERAN\/UTRAN over Gn\/Gp","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Response LS On handling UEs accessing to GERAN\/UTRAN over Gn\/Gp","secretary_remarks":"Revision of S2-2404406, merging S2-2404833. Revised in parallel session to S2-2405817.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10350,"status":"revised","reservation_date":"2024-04-22 09:38:01","uploaded":"2024-04-22 10:01:23","revisionof":"S2-2404406","revisedto":"S2-2405817","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"TEI18"},{"winame":" 5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405208.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405209","title":"Clarification on UEs accessing to GERAN\/UTRAN over Gn\/Gp","source":"Huawei, HiSilicon, Vodafone","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that when the UE moves from 5GS to GPRS network, the dedicated QoS flow established at the 5GC network needs to be released. This is done by the SMF+PGW-C triggering this release and does not need to be PCF or AF triggered. For","secretary_remarks":"Revision of S2-2404407. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10390,"status":"agreed","reservation_date":"2024-04-22 09:38:01","uploaded":"2024-04-22 10:01:20","revisionof":"S2-2404407","revisedto":"","release":"Rel-18","crspec":"23.501","crspecversion":"18.5.0","workitem":[{"winame":"TEI18"}],"crnumber":5369.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-240602","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405209.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.17.2.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405210","title":"LS on 5GS missing CBC support for shared networks","source":"SA WG2","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: RAN WG2, RAN WG3, SA WG1. Attachments: Discussion Document S2-2404526","secretary_remarks":"Revision of S2-2404527. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10420,"status":"approved","reservation_date":"2024-04-22 09:38:02","uploaded":"2024-04-22 10:01:16","revisionof":"S2-2404527","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"RAN WG2, RAN WG3, SA WG1","lsoriginalls":"","lsreply":"C1-243110, C1-243686","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405210.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405211","title":"Corrections to Nnef_UEId Service","source":"AT&T, Ericsson","contact":"Rohit Abhishek","contact-id":95292,"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 and by addings reference to TS 33.501.","secretary_remarks":"Revision of S2-2404983. Revised in parallel session to S2-2405818","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10450,"status":"revised","reservation_date":"2024-04-22 09:38:03","uploaded":"2024-04-22 10:01:23","revisionof":"S2-2404983","revisedto":"S2-2405818","release":"Rel-18","crspec":"23.502","crspecversion":"18.5.0","workitem":[{"winame":"TEI18"},{"winame":" EDGEAPP"}],"crnumber":4805.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405211.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405500","title":"[DRAFT] LS on limited MSISDN exposure","source":"AT&T","contact":"Rohit Abhishek","contact-id":95292,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3","secretary_remarks":"Created at meeting. Revised in parallel session to S2-2405819.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10480,"status":"revised","reservation_date":"2024-04-22 09:40:39","uploaded":"2024-04-22 10:01:21","revisionof":"","revisedto":"S2-2405819","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405500.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405815","title":"Reply LS on data plane control by roaming hubs","source":"SA WG2","contact":"Jicheol Lee","contact-id":87580,"tdoctype":"LS out","for":"Approval","abstract":"To: TSG SA. CC: SA WG1, SA WG3","secretary_remarks":"Revision of S2-2405206. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10280,"status":"approved","reservation_date":"2024-04-22 09:43:05","uploaded":"2024-04-22 10:01:18","revisionof":"S2-2405206","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2403867","lsto":"TSG SA","Cc":"SA WG1, SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405815.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405816","title":"Reply LS from SA WG2 on Updated AECC Publications for Future Connected Vehicle Services","source":"SA WG2","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"LS out","for":"Approval","abstract":"To: TSG SA. CC: SA WG1, SA WG5, SA WG6","secretary_remarks":"Revision of S2-2405207. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10320,"status":"approved","reservation_date":"2024-04-22 09:43:05","uploaded":"2024-04-22 10:01:18","revisionof":"S2-2405207","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2403868","lsto":"TSG SA","Cc":"SA WG1, SA WG5, SA WG6","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405816.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405817","title":"Response LS on handling UEs accessing to GERAN\/UTRAN over Gn\/Gp","source":"SA WG2","contact":"Fenqin Zhu","contact-id":26772,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3","secretary_remarks":"Revision of S2-2405208. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10360,"status":"approved","reservation_date":"2024-04-22 09:43:05","uploaded":"2024-04-22 10:01:19","revisionof":"S2-2405208","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"TEI18"},{"winame":" 5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2403879","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405817.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405818","title":"Corrections to Nnef_UEId Service","source":"AT&T, Ericsson","contact":"Rohit Abhishek","contact-id":95292,"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-2405211. Revised to S2-2405823","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10460,"status":"revised","reservation_date":"2024-04-22 09:43:06","uploaded":"2024-04-22 10:01:21","revisionof":"S2-2405211","revisedto":"S2-2405823","release":"Rel-18","crspec":"23.502","crspecversion":"18.5.0","workitem":[{"winame":"TEI18"},{"winame":" EDGEAPP"}],"crnumber":4805.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405818.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405819","title":"[DRAFT] LS on limited MSISDN exposure","source":"AT&T","contact":"Rohit Abhishek","contact-id":95292,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3","secretary_remarks":"Revision of S2-2405500. Revised to S2-2405824.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10490,"status":"revised","reservation_date":"2024-04-22 09:43:07","uploaded":"2024-04-22 10:01:21","revisionof":"S2-2405500","revisedto":"S2-2405824","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405819.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405823","title":"Corrections to Nnef_UEId Service","source":"AT&T, Ericsson, Samsung","contact":"Rohit Abhishek","contact-id":95292,"tdoctype":"CR","for":"Endorsement","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-2405818. This CR was endorsed. Revised at S2#163 in S2-2406580","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10470,"status":"revised","reservation_date":"2024-04-22 09:43:08","uploaded":"2024-04-22 10:01:25","revisionof":"S2-2405818","revisedto":"S2-2406580","release":"Rel-18","crspec":"23.502","crspecversion":"18.5.0","workitem":[{"winame":"TEI18"},{"winame":" EDGEAPP"}],"crnumber":4805.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405823.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.15.10A","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405824","title":"LS on limited MSISDN exposure","source":"SA WG2","contact":"Rohit Abhishek","contact-id":95292,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3. CC: SA WG6, CT WG3, TSG SA. Attachments: Draft 23.502 CR4805\/S2-2405823","secretary_remarks":"Revision of S2-2405819. This LS OUT was approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10500,"status":"approved","reservation_date":"2024-04-22 09:43:09","uploaded":"2024-04-22 10:01:19","revisionof":"S2-2405819","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG6, CT WG3, TSG SA","lsoriginalls":"","lsreply":"S3-242204, S3-242315","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405824.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]