[{"name":"C4-225017","title":"LS on clarification for UE_NOT_FOUND cause code for UP in CT1","source":"CT1","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":50170,"status":"noted","reservation_date":"2022-10-20 10:13:39","uploaded":"2022-10-20 12:46:26","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"TEI18"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA3","Cc":"CT4","lsoriginalls":"C1-226279","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_113_Toulouse\/Docs\/C4-225017.zip","group":"C4","meeting":"C4-113","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-225021","title":"LS to 3GPP - Hosted SEPP","source":"GSMA DESS","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":50210,"status":"noted","reservation_date":"2022-10-20 10:24:44","uploaded":"2022-10-20 12:46:26","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA3","Cc":"SA2, CT4","lsoriginalls":"GSMA DESS LS to 3GPP SA3 on SEPP certificates","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_113_Toulouse\/Docs\/C4-225021.zip","group":"C4","meeting":"C4-113","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-225022","title":"EAP-5G change; Answer to S2-2109043","source":"Broadband Forum","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Discussion","abstract":"n your previous liaison, you noted \u2018SA2 assumes that the changes in TR-456 would only impact the way EAP-5G is transported between RG and W-AGF and has no impacts to EAP-5G as such.\u2019\n\nWe would like to confirm that the changes in TR-456 do NOT impact EAP-5G. \nEAP-5G is no longer used in the W-5GAN procedures between AGF and 5G-RG. EAP-5G is deprecated in TR-456 issue 2.\n\nAs previously communicated, we have come to realize that the use of EAP-5G over PPP for W-CP initiation is an unsuitable choice for 5G-RG support over wireline. \nAs such we have modified our call flows to initiate the VSNP procedures to establish reliable NAS transport with fragmentation and reassembly support earlier in the call flow sequence; and communicate the key elements of the EAP-5G exchange as part of W-CP initiation dialog within our framework of VSNP messaging.\n\nWe note the above change will have a number of impacts on TS23.316. We have documented the updated procedures in issue 2 of TR-456, which is now published at https:\/\/www.broadband-forum.org\/technical\/download\/TR-456_Issue-2.pdf.\n\nWe would like to inform 3GPP that WWC phase 2 is now finished and includes the following published documents: TR-470i2 \u2013 5G Wireless Wireline Convergence Architecture, TR-124i7 - Functional Requirements for Broadband Residential Gateway Devices , TR-456i2 - AGF Functional Requirements, available at https:\/\/www.broadband-forum.org\/technical-reports. \n\nWe look forward to continuing our fruitful relationship.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":50220,"status":"noted","reservation_date":"2022-10-20 10:26:47","uploaded":"2022-10-20 12:46:26","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2, CT4, CT1","Cc":"","lsoriginalls":"LIAISE-508-02","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_113_Toulouse\/Docs\/C4-225022.zip","group":"C4","meeting":"C4-113","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-225023","title":"Research highlighting potential need for granular level checks using \"Additional scope\" under the OAuth2.0 Token Access","source":"GSMA CVD PoE","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Discussion","abstract":"The GSMA\u2019s CVD programme has been made aware, through a researcher submission (attached to this LS), of a potential security vulnerability within 5G network functions that encompass OAuth2.0. More specifically the research highlights how certain gaps in RFC 6749 can lead to unauthorized access. The compounding effect of these gaps in OAuth2.0 could result in potential end point manipulation within the 5G SBA.\nSubmission date: The researcher (Imran Saleem at Mobileum) shared his initial research to GSMA 5GSTF on 25 October 2021. A formal disclosure to the GSMA CVD programme was made by the researcher on 09 August 2022 with a vulnerability ID CVD-2022-0063.\nSimilar research was also submitted recently to the GSMA CVD programme by group of university researchers, Seaver Thorn, K. Virgil English, William Enck, Kevin R.B. Butler from North Carolina State University & University of Florida, under CVD-2022-0061, CVD-2022-0062. The disclosures were made on 26 July 2022.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":50230,"status":"postponed","reservation_date":"2022-10-20 10:28:48","uploaded":"2022-10-20 12:46:26","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA3, CT4","Cc":"","lsoriginalls":"LS to 3GPP OAuth Token Scopes v4","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_113_Toulouse\/Docs\/C4-225023.zip","group":"C4","meeting":"C4-113","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-225024","title":"Reply LS on FS_REDCAP_Ph2 option feasibility","source":"RAN2","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":50270,"status":"noted","reservation_date":"2022-10-20 10:32:20","uploaded":"2022-10-20 12:46:26","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"FS_REDCAP_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2, RAN3","Cc":"CT4, CT1","lsoriginalls":"R2-2209243","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_113_Toulouse\/Docs\/C4-225024.zip","group":"C4","meeting":"C4-113","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-225027","title":"Reply LS on Slice list and priority information for cell reselection","source":"SA2","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":50290,"status":"noted","reservation_date":"2022-10-20 10:40:00","uploaded":"2022-10-20 12:46:26","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"},{"winame":" NR_slice-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"R2-2203807","lsto":"RAN2, RAN3, CT1, CT4","Cc":"","lsoriginalls":"S2-2203597","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_113_Toulouse\/Docs\/C4-225027.zip","group":"C4","meeting":"C4-113","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-225029","title":"Reply LS On PLMN ID used in Roaming Scenarios","source":"SA2","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Discussion","abstract":"SA2 thanks SA3 for the LS on PLMN ID used in Roaming Scenarios and the provided observations.\n\nSA2 discussed the observations in the LS and the two Editor\u2019s Notes in the attached CR and provides the following views: \n\n- The mandatory custom header \u201c3gpp-Sbi-Asserted-Plmn-Id\u201d defined in TS 29.500 can be always included by sending NF from Rel-17. The included PLMN ID represents the serving PLMN ID. In case the NF supports multiple PLMNs, the NF may consider the PLMN ID that the UE is registered to, unless something else is specified.\n- Other solutions may involve, e.g. the sending SEPP determines the PLMN ID by implementation mechanism and includes it if the sending NF (e.g. pre-Rel-17 NF) has not provided the serving PLMN ID related information in the custom header.\n- SA2 considers that CT4 is most suitable group to lead the discussion of this issue, with support from SA3 for security-related aspects (e.g. certificates).\n- Stage 2 requirement is expected to be documented in SA3 specifications. \n- GSMA should be kept in the loop","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":50310,"status":"noted","reservation_date":"2022-10-20 10:57:53","uploaded":"2022-10-20 12:46:26","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S3-221214","lsto":"SA3, CT4","Cc":"","lsoriginalls":"S2-2207391","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_113_Toulouse\/Docs\/C4-225029.zip","group":"C4","meeting":"C4-113","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-225031","title":"Reply LS on Inter-PLMN Handover of VoLTE calls and idle mode mobility of IMS sessions","source":"SA2","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Discussion","abstract":"As follow up to the issue raised in the LS S3i220244 from SA3LI and the cross WG CC held in July 7th, 2022, SA2 has made the following conclusions as a way forward:\n-Initially, changes will be limited to Rel-18 onwards to progress the work.\n-Use the basic solution as described in the attached document S2-2205903. The \u201cLI after inter-PLMN mobility\u201d use case is addressed in Rel-18 as part of the solution. Note that the draft CR is NOT approved in SA2. SA2 will continue to work on this as part of Rel-18.\n-Use S8HR\/TEI18 work item code(s) to make the updates, whether Cat F or C CRs to be discussed in future meetings.\n-Scope of the work in Rel-18 is limited to current GSMA requirements for IMS, which mandates RTP use and does not mention SRTP\/media encryption, thus solution will not consider media encryption.\n- VoLTE is the first priority. SA2 believe that subsequent work can re-use this solution concept for VoNR and handover between VoNR and VoLTE.\nAny further usecases\/requirements need to be addressed\/ discussed in future releases.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":50320,"status":"noted","reservation_date":"2022-10-20 11:43:29","uploaded":"2022-10-20 12:46:26","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA3LI, CT1, CT4, SA3","Cc":"","lsoriginalls":"S2-2207697","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_113_Toulouse\/Docs\/C4-225031.zip","group":"C4","meeting":"C4-113","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-225032","title":"Reply LS on 5G ProSe security open items","source":"SA2","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":50350,"status":"noted","reservation_date":"2022-10-20 11:45:30","uploaded":"2022-10-20 12:46:26","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"SP-220716","lsto":"SA, SA3","Cc":"CT, CT1, CT3, CT4, CT6","lsoriginalls":"S2-2207838","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_113_Toulouse\/Docs\/C4-225032.zip","group":"C4","meeting":"C4-113","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-225035","title":"Response LS on Identifier availability for Lawful Interception during Inter-PLMN handover","source":"SA2","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Discussion","abstract":"SA2 thanks SA3LI for their request regarding the transfer of MSISDN and IMEI at inter-PLMN handover in EPC and 5GC. \nSA2 has conducted a preliminary analysis of the situation but requests CT4 to do a more detailed examination of their stage 3 specifications.\nFrom the SA2 analysis (e.g., using the specification extracts in the annex below), SA2 believe that:\na)\tIn EPC and 5GC, the IMEI is already always sent from the source MME\/AMF to the target MME\/AMF (including inter-RAT cases) during idle mode mobility and handover, and this should include inter-PLMN situations.\nb)\tIn EPC the MSISDN is not sent at idle mode mobility or handover between MMEs, nor at inter-RAT idle mode mobility\/handover between AMF and MME. \ni)\tThis is probably not an LI problem for idle mode mobility because the UE cannot send\/receive data\/SMS with the new MME\/AMF until the registration process with the HPLMN has been completed and the HSS\/UDM has had the opportunity to download the MSISDN\/GPSI to the new MME\/AMF.\nii)\tFor handover, as long as SA3 do not see a problem, SA2 do not see an issue with adding it to their specifications especially as there are already some situations (SRVCC and PDN connections via SCEF) where the stage 3 specification (TS 29.274) already carries the MSISDN from source MME to target MME.\nc)\tIn 5GC, the GPSI is already sent from source AMF to target AMF at both idle mode mobility and handover.\nIf CT4 and SA3 do not see problems with the SA2 analysis and\/or the SA3-LI request, SA2 should be able to prepare CR(s) to add the MSISDN to the stage 2 TS 23.401 for inter-MME handover (and to include inter-RAT cases, possibly TS 23.502) in Release 18.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":50370,"status":"noted","reservation_date":"2022-10-20 11:53:39","uploaded":"2022-10-20 12:46:26","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT4, SA3, SA3-LI","Cc":"CT3","lsoriginalls":"S2-2209262","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_113_Toulouse\/Docs\/C4-225035.zip","group":"C4","meeting":"C4-113","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-225037","title":"Response LS on Clarifications for AF specific UE ID retrieval","source":"SA2","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":50450,"status":"noted","reservation_date":"2022-10-20 11:57:58","uploaded":"2022-10-20 12:46:26","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"EDGEAPP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S6-222555","lsto":"SA6","Cc":"CT3, CT4, SA3","lsoriginalls":"S2-2209270","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_113_Toulouse\/Docs\/C4-225037.zip","group":"C4","meeting":"C4-113","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-225043","title":"Progress and open issues for NPN enhancements in Rel-18","source":"SA2","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":50490,"status":"noted","reservation_date":"2022-10-20 12:13:20","uploaded":"2022-10-20 12:46:26","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"FS_eNPN_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA1, SA3, CT1","Cc":"CT3, CT4, RAN2, RAN3","lsoriginalls":"S2-2209860","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_113_Toulouse\/Docs\/C4-225043.zip","group":"C4","meeting":"C4-113","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-225045","title":"Response to \u201cLS to 3GPP SA2 on VoLTE Roaming GBR Handling\u201d","source":"SA2","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":50500,"status":"noted","reservation_date":"2022-10-20 12:21:28","uploaded":"2022-10-20 12:46:26","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"NRG 13_201r2","lsto":"GSMA-NRG","Cc":"CT4, SA4, CT3","lsoriginalls":"S2-2209969","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_113_Toulouse\/Docs\/C4-225045.zip","group":"C4","meeting":"C4-113","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-225049","title":"Identifier availability for Lawful Interception during Inter-PLMN handover","source":"SA3-LI","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"SA3LI would like to thank SA2 for their recent assistance and work on issues related to inter-PLMN handover. \nTo meet lawful interception requirements, it is necessary that the compelled PLMN deliver all traffic associated to the provided identifiers from time of tasking to the requesting law enforcement agency. This includes sessions which are transferred into a serving PLMN as a result of inter-PLMN handover. Both MSISDN and IMEI are used as target identifiers, and therefore need to be available at the point of inter-PLMN handover. As the association between the MSISDN, IMEI and other identifiers is not known to the visited network at the time of an inter-PLMN handover it will be unable to immediately apply lawful interception requirements.  SA3LI believe including MSISDN and IMEI in the MME UE context for all HPLMN to VPLMN, VPLMN to VPLMN and VPLMN to HPLMN scenarios would resolve this.\nIt is understood during an inter-PLMN handover, the PLMN receiving the handover will not be provided with the MSISDN or IMEI as part of the forward relocation requests MME UE context (TS 23.401 clause 5.5.1.2.2). SA3LI anticipate that this will create a delay in Lawful Interception leading to a loss of data when the MSISDN or IMEI is the targeted identifier.\nWhile SA3LI understands that the current focus of work is on S8HR, the same considerations will apply for GPSI and PEI in N9HR.\nTherefore, to meet lawful interception requirements, SA3LI kindly asks SA2 to review if MSISDN and IMEI can be included in the transferred MME UE context and that in the future if SA2 extends their work to include N9HR or non-voice service handover scenarios then SA3LI asks that SA2 make equivalent changes for those scenarios.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":50360,"status":"noted","reservation_date":"2022-10-20 12:32:25","uploaded":"2022-10-20 12:46:26","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"SA3, CT3, CT4","lsoriginalls":"s3i220485","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_113_Toulouse\/Docs\/C4-225049.zip","group":"C4","meeting":"C4-113","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-225050","title":"Reply LS to 3GPP SA2 on VoLTE Roaming GBR Handling","source":"SA4","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":50510,"status":"noted","reservation_date":"2022-10-20 12:34:23","uploaded":"2022-10-20 12:46:26","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"CT3, CT4, GSMA NRG","lsoriginalls":"S4-221192","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_113_Toulouse\/Docs\/C4-225050.zip","group":"C4","meeting":"C4-113","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-225051","title":"Reply LS on User Consent Updating","source":"SA5","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"SA5 thanks RAN 3 for the LS R3-224076\/S5-225021 on Reply LS on liaison on User Consent Updating and would like to inform RAN3 that SA5 has agreed to mention the NG messages UE CONTEXT MODIFICATION REQUEST and PATH SWITCH REQ ACK message among the other referenced messages capable of carrying the Management Based MDT PLMN (Modification) List IE, see also the attached CR.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":50520,"status":"noted","reservation_date":"2022-10-20 12:36:43","uploaded":"2022-10-20 12:46:26","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"NR_ENDC_SON_MDT_enh2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN3","Cc":"CT4, SA3","lsoriginalls":"S5-225321","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_113_Toulouse\/Docs\/C4-225051.zip","group":"C4","meeting":"C4-113","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-225053","title":"Forward on S6-222332, LS on Network federation interface for Telco edge consideration","source":"SA6","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"Background: GSMA OPG has developed PRD for Operator Platform Telco Edge Requirements which specifies architectural requirement and a corresponding reference architecture for Operator Platform. GSMA OPAG is developing the API specifications for interfaces or the Operator Platform. GSMA OPG, 3GPP and ETSI MEC ISG are coordinating to develop a single harmonized system architecture for edge computing.\n\nIn this context, SA6, SA2 and SA5 have received the attached LS from GSMA OPAG about East West Bound Interface (EWBI) APIs PRD for feedback. The EWBI APIs PRD may have impacts to the edge computing work for Rel.18 in SA and CT WGs and hence a coordinated response to GSMA OPAG is required. SA6 is currently reviewing the EWBI APIs PRD and may provide detailed technical response for December Plenary to enable a coordinated LS response by 3GPP SA to GSMA OPAG.\nSA6 asks SA2, SA3 and SA5 to review the EWBI PRD and provide any technical response to 3GPP SA by December Plenary for a coordinated LS response by 3GPP SA to GSMA OPAG. SA6 asks SA to create a coordinated response, if necessary, based upon the inputs to the December plenary from the SA WGs.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":50540,"status":"noted","reservation_date":"2022-10-20 12:41:54","uploaded":"2022-10-20 12:46:26","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA3, SA2, SA","Cc":"CT, CT1, CT3, CT4","lsoriginalls":"S6-222543","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_113_Toulouse\/Docs\/C4-225053.zip","group":"C4","meeting":"C4-113","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-225054","title":"Reply LS on user\u2019s consent for EDGEAPP","source":"SA6","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"SA6 thanks CT3 for the LS on EDGEAPP user\u2019s consent observations and related questions.\nQuestion 1 to SA6: For the Eees_UEIdentfier API, whether a trusted EES can directly utilize the relevant 3GPP 5GC services or can only utilize the relevant 3GPP 5GC services via the NEF?\nAnswer 1: Before replying to CT3, SA6 would like to check with SA2 for AF interaction with NFs. SA6 will further update CT3 after receiving feedback from SA2.\nQuestion to SA2: Since TS 23.502 clause 4.15.10 describes AF utilizing NEF service to obtain AF specific UE ID and clause 6.2.10 of TS 23.501 describes that a trusted AF can be allowed to directly interact with relevant NFs instead of using NEF, SA6 would like to ask SA2 whether a trusted AF can directly utilize UDM and BSF services to obtain AF specific UE ID in Rel-17. If so, what are the interaction details among those NFs without using NEF?\nQuestion 2 to SA3, SA6: Whether the External Identifier used as GPSI needs user\u2019s consent or not?\nAnswer 2: As mentioned in an editor\u2019s note in clause 8.6.5.2 of TS 23.558, SA6 believe this is falling into SA3 remit to answer the question.\nQuestion 3 to SA3, SA6: Whether the token is needed or not for the user\u2019s consent mechanism required in SA3 specification?\nAnswer 3: Regarding EDGE-3 Eees_UELocation API, the EAS may retrieve user consent before invoking EES service. Such a case is under study in TR 23.700-95 in Rel-18. Therefore, it is not supported in TS 23.558 in Rel-17 (see attached CR for clarification).","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":52930,"status":"noted","reservation_date":"2022-10-20 12:43:54","uploaded":"2022-10-20 12:46:26","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"EDGEAPP_EXT"},{"winame":" EDGEAPP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT3, SA2","Cc":"SA3, CT4","lsoriginalls":"S6-222555","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_113_Toulouse\/Docs\/C4-225054.zip","group":"C4","meeting":"C4-113","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-225293","title":"Response LS on Identifier availability for Lawful Interception during Inter-PLMN handover","source":"SA3-LI","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":52960,"status":"noted","reservation_date":"2022-11-04 07:37:46","uploaded":"2022-11-04 07:39:51","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2209262","lsto":"SA2","Cc":"CT3, CT4, SA3","lsoriginalls":"s3i220660","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_113_Toulouse\/Docs\/C4-225293.zip","group":"C4","meeting":"C4-113","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-225296","title":"Discussion on Security Vulnerabilities highlighted by GSMA LS C4-225023","source":"Samsung","contact":"Varini Gupta","contact-id":83459,"tdoctype":"discussion","for":"Discussion","abstract":"GSMA CVD PoE has sent LS C4-225023 to CT4 and SA3 highlighting potential security vulnerability within 5G Network functions encompassing OAuth2.0. This paper attempts to analyze the highlighted vulnerabilities and suggests next steps.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":50240,"status":"noted","reservation_date":"2022-11-04 08:55:31","uploaded":"2022-11-04 08:59:06","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_113_Toulouse\/Docs\/C4-225296.zip","group":"C4","meeting":"C4-113","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-225370","title":"Response LS on Identifier availability for Lawful Interception during Inter-PLMN handover","source":"VT4","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":537000,"status":"revised","reservation_date":"2022-11-14 09:33:48","uploaded":"2022-11-17 09:10:56","revisionof":"","revisedto":"C4-225542","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA3, SA3-LI","Cc":"CT3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_113_Toulouse\/Docs\/C4-225370.zip","group":"C4","meeting":"C4-113","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-225542","title":"Response LS on Identifier availability for Lawful Interception during Inter-PLMN handover","source":"CT4","contact":"Kimmo Kymalainen","contact-id":85426,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"approved","reservation_date":"2022-11-17 10:04:18","uploaded":"2022-11-17 10:31:11","revisionof":"C4-225370","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2, SA3-LI","Cc":"CT3, SA3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_113_Toulouse\/Docs\/C4-225542.zip","group":"C4","meeting":"C4-113","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]