[{"name":"S2-2205400","title":"LS on Inter-PLMN Handover of VoLTE calls and idle mode mobility of IMS sessions","source":"SA WG3-LI","contact":"Koen Jaspers","contact-id":9291,"tdoctype":"LS in","for":"Action","abstract":"SA WG3-LI has identified that the handover between PLMNs using home routing for ongoing IMS-sessions (calls) creates issues for LI. With home routing roaming, HPLMN operators may be required to switch off the IMS confidentiality protection for all roamers in order to allow the lawful interception of roamers in the VPLMN without involvement of the HPLMN. The hitherto assumption SA WG3 LI had was that during the IMS registration, the IMS confidentiality protection would be turned off and as a consequence, a full capture of IMS session related signalling and media would be possible in the VPLMN for lawful interception purpose. If an IMS session moves from a serving PLMN for which confidentiality protection is allowed to a VPLMN where it is not allowed, then the IMS confidentiality protection would need to be switched off mid-session. Similarly, when the inter-PLMN handover happens with an established IMS session for a roamer, without having the complete IMS session related information, an effective lawful interception of such roamers is not possible in the VPLMN. In order to have a non-compromised lawful interception in the VPLMN, complete information of IMS sessions shall be made available in the VPLMN. While this LS focusses on the Home Routed VoLTE roaming for VoLTE\/EPC (S8HR) it is also applicable to VoNR\/5G Core (N9HR). The following list states the requirements related to inter PLMN handover and idle mode mobility of IMS-sessions: 1. For any ongoing call, following handover, it must be possible to intercept that S8HR call in the new PLMN. 2. In order to support the above, a mechanism shall exist to ensure that the HPLMN can turn off IMS confidentiality protection when any UE roams to a VPLMN. In addition, a mechanism may be required to support turning on the IMS confidentiality protection when the UE returns or roams back to the HPLMN. 3. The handover handling shall ensure that the VPLMN lawful interception system has access to the relevant identifiers to enable the lawful interception of IMS services of roamers. The relevant identifiers shall include at the minimum, the following: a) 3GPP access level identifiers (MSISDN, IMSI, IMEI). b) IMS level identifiers (IMPU, IMPIs) of local served party and IMPU of remote end point user. c) SDP information (codec, PT, etc.) for the media stream. 4. The HPLMN shall have a mechanism to detect that a user has roamed into and back from a different country. a) The HPLMN may be required to suspend the lawful interception for any targeted outbound roamer (including NTNs). Such suspension, if executed, may include the suspension of lawful interception for the content of communications or the suspension of lawful interception of content of communication and the signaling. b) When the HPLMN is required to suspend lawful interception for any targeted outbound roamer, the HPLMN shall have the mechanism to detect that the UE has moved back to the home country in order to start\/resume the lawful interception of that UE when required. 5. The lawful interception system in the VPLMN shall be able to detect whether the HPLMN has correctly configured the IMS session (e.g. confidentiality protection off). Any action resulting from such detection is a CSP policy issue. SA WG3-LI is looking forward to discuss the detailed list of information that needs to be provided at inter PLMN handover\/idle mode mobility and the most appropriate way to make the information available. For example: a) What changes are needed so the IMS can make the required information available? b) What is the preferred mechanism to get the IMS-information provided to the VPLMN (e.g. as part of the registration process)? c) Are changes needed for the HPLMN to be able to deactivate or activate the IMS confidentiality protection during inter-PLMN handover? d) Are changes needed for the VPLMN to detect if the correct configurations for roamers to allow lawful interception are in use at the VPLMN? Taking the regulatory process and techni","secretary_remarks":"Revision of postponed S2-2203662 from S2#151E. Response drafted in S2-2208090. CC#3: Final response in S2-2207697","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10060,"status":"replied to","reservation_date":"2022-06-17 13:06:18","uploaded":"2022-06-17 14:33:20","revisionof":"S2-2203662","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1","Cc":"SA WG3, CT WG4","lsoriginalls":"S3i220244","lsreply":"S2-2207697","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205400.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205401","title":"LS from SA WG4: Reply LS to CT WG3 on Data Reporting API","source":"SA WG4","contact":"Charles Lo","contact-id":50185,"tdoctype":"LS in","for":"Information","abstract":"SA WG4 wishes to thank CT WG3 for the LS on Data Reporting API in S4-220701 (C3-222485). SA WG4 wishes to inform CT WG3 that based on offline discussion among several delegates in SA WG4 and CT WG3, SA WG4 agrees with CT WG3 s suggestion to employ an HTTP custom operation in lieu of defining the Data Report resource of the Data Reporting API. That change is reflected in clause 7.2.1 of the attached TS 26.532 V1.3.0 as further described below. SA WG4 wishes to inform CT WG3 that TS 26.531 and TS 26.532 completion, as well as agreement on a CR regarding EVEX to the 5G Media Streaming stage 2 specification TS 26.501, were accomplished at SA WG4#119-e. At this point, and based on our understanding that EVEX-related modification of Rel-17 technical specifications in CT WG3 are well in progress and may reach completion at CT WG3#122-e, SA WG4 considers EVEX to be successfully finished and will seek SA Plenary approval of EVEX Work Item completion\/conclusion at SP#96 in June, 2022. Towards assisting development and approval of any remaining CRs in CT WG3 on technical specifications in support of EVEX, attached to this LS are the latest versions of draft TS 26.531 and TS 26.532, which we expect to be published in 3GPP as V17.0.0 of those specifications. Note that the in the latest TS 26.532 draft, the previously separate APIs in clauses 6.2 and 6.3 have been merged into a single API. Similarly, the previously separate APIs in clause 7.2 and 7.3 have been merged into a single API. Also, SA WG4 wishes to point CT WG3 to the EVEX-related CR to TS 26.501 agreed at SA WG4#119-e in S4-220834. SA WG4 hopes that the above information and the attached (and referenced) documents will be useful and timely for CT WG3 towards generation of updated CT WG3 specifications regarding EVEX functionality.","secretary_remarks":"Revision of postponed S2-2203666 from S2#151E. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10090,"status":"noted","reservation_date":"2022-06-17 13:06:18","uploaded":"2022-06-17 14:33:20","revisionof":"S2-2203666","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"SA WG2","lsoriginalls":"S4-220839","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205401.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205404","title":"LS from CT WG1: Reply LS on EPS fallback enhancements","source":"CT WG1","contact":"Lena Chaponniere","contact-id":38080,"tdoctype":"LS in","for":"Action","abstract":"To: SA WG2. CC: SA WG3","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":"2022-06-17 13:06:18","uploaded":"2022-06-20 10:59:52","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG3","lsoriginalls":"C1-223535","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205404.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205412","title":"LS from CT WG3: Reply LS on Data Reporting API","source":"CT WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"To: SA WG4. CC: SA WG2","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":"2022-06-17 13:06:19","uploaded":"2022-06-20 10:59:52","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"SA WG2","lsoriginalls":"C3-223571","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205412.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205418","title":"LS from TSG CT: LS on Priority given to Rel-17 LSs from CT","source":"TSG CT","contact":"Lionel Morand","contact-id":25150,"tdoctype":"LS in","for":"Action","abstract":"To: SA WG2, SA WG4. CC: TSG SA","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":"2022-06-17 13:06:19","uploaded":"2022-06-20 10:59:52","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG4","Cc":"TSG SA","lsoriginalls":"CP-221319","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205418.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205429","title":"LS from RAN WG3: Response LS on NAS PDU delivery during PDU Session modification procedure","source":"RAN WG3","contact":"Aijuan Liu","contact-id":43714,"tdoctype":"LS in","for":"Action","abstract":"To: SA WG2. Attachments: R3-223850","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":"2022-06-17 13:06:19","uploaded":"2022-06-20 10:59:53","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"R3-223929","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205429.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205430","title":"LS from RAN WG3: Reply LS on open issues for NB-IoT and eMTC support for NTN","source":"RAN WG3","contact":"Jiren Han","contact-id":75302,"tdoctype":"LS in","for":"Information","abstract":"To: RAN WG2","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":"2022-06-17 13:06:19","uploaded":"2022-06-20 10:59:53","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"","lsoriginalls":"R3-224007","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205430.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205436","title":"LS from SA WG3: Reply LS on EPS fallback enhancements","source":"SA WG3","contact":"Vlasios Tsiatsis","contact-id":76181,"tdoctype":"LS in","for":"Information","abstract":"To: RAN WG2. CC: SA WG2","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":"2022-06-17 13:06:19","uploaded":"2022-06-20 10:59:53","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"SA WG2","lsoriginalls":"S3-221162","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205436.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205439","title":"LS from SA WG3: LS on PLMN ID used in Roaming Scenarios","source":"SA WG3","contact":"Christine Jost","contact-id":49662,"tdoctype":"LS in","for":"Information","abstract":"To: CT WG4. Attachments: S3-221213","secretary_remarks":"Response drafted in S2-2205666. Final response in S2-2207391","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10160,"status":"replied to","reservation_date":"2022-06-17 13:06:19","uploaded":"2022-06-20 10:59:53","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"S3-221214","lsreply":"S2-2207391","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205439.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205442","title":"LS from SA WG3: LS reply on Reply LS on NTN specific User Consent and UE location in connected mode in NTN","source":"SA WG3","contact":"Vlasios Tsiatsis","contact-id":76181,"tdoctype":"LS in","for":"Information","abstract":"To: RAN WG2. CC: SA WG2, RAN WG3, CT WG1","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":"2022-06-17 13:06:19","uploaded":"2022-06-20 10:59:52","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"SA WG2, RAN WG3, CT WG1","lsoriginalls":"S3-221268","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205442.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205444","title":"LS from SA WG5: LS Reply on network slice LCM consumption and use case","source":"SA WG5","contact":"Jan Groenendijk","contact-id":49147,"tdoctype":"LS in","for":"Information","abstract":"To: SA WG6. CC: SA WG2","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":"2022-06-20 09:19:13","uploaded":"2022-06-20 10:59:52","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"SA WG2","lsoriginalls":"S5-223521","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205444.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205453","title":"LS from BBF: Response to SP-220347: Alignment concerning 5G-RG requirements and its remote management","source":"BBF","contact":"Lincoln Lavoie","contact-id":39231,"tdoctype":"LS in","for":"Information","abstract":"Dear colleagues, Thank you for your answer (SP-220347) to our previous liaison. We are pleased that TSG SA has acknowledged the responsibility of BBF for requirements for Residential Gateway related to Customer Premises Network and for remote management of the Residential Gateway. We appreciate the coordination and confirm we are happy to undertake work concerning the Residential Gateway in a cooperative relationship, as envisaged by TSG SA. We are processing TS 22.261 you have provided and will communicate further comments in a future liaison. We are attaching the latest version of our TR-124, Residential Gateway requirements specification, for your reference. We look forward to continuing our fruitful cooperation. Thanks, Lincoln Lavoie Broadband Forum Technical Committee Chair","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10030,"status":"noted","reservation_date":"2022-07-20 05:45:01","uploaded":"2022-07-20 06:40:19","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG2","Cc":"","lsoriginalls":"LIAISE-531","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205453.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205458","title":"LS from SA WG6: LS on FS_eEDGEAPP Solution for Support of NAT deployed within the edge data network","source":"SA WG6","contact":"shaowen zheng","contact-id":88792,"tdoctype":"LS in","for":"Action","abstract":"As part of SA WG6 s Rel-18 FS_eEDGEAPP study, SA WG6 has agreed a solution for KI#16 for support of NAT deployed within the edge data network. In Sol#23, UE provides either the CN network assigned IP address (i.e., the private IP address of the UE) or its MSISDN to the EES to obtain External UE ID from the EES. SA WG6 would like to check the following with SA WG2: - As mentioned in KI#16 about AF (e.g. EES) with a NATted UE IP address, can SA WG2 support taking NATted UE IP address as input and then exposing the UE External ID to EES? - In solution #23, EES (as AF) invokes Nnef_UEID API with UE private IP address allocated by 3GPP CN. In certain deployment when multiple UEs are allocated with the same private IP address, can SA WG2 support addressing IPv4 address overlap issue? SA WG6 would like to check with SA WG3: - whether there is security issue if the EEC share its private IP address with a trusted 3rd party EES. If yes, could SA WG3 address security issues related to this?. Action: SA WG6 asks SA WG2 to consider the above questions and invites SA WG2 to provide feedback.","secretary_remarks":"Responses drafted in S2-2206599, S2-2206796, S2-2206900. Final response in S2-2207394","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10330,"status":"replied to","reservation_date":"2022-07-20 05:45:01","uploaded":"2022-07-20 06:40:19","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3","Cc":"","lsoriginalls":"S6-221953","lsreply":"S2-2207394","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205458.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205459","title":"LS from GSMA NRG: LS to 3GPP Hosted SEPP","source":"GSMA NRG","contact":"Ralf Keller","contact-id":11142,"tdoctype":"LS in","for":"Information","abstract":"Background and new requirements: GSMA NRG 5GMRR has discussed the deployment of the 3GPP standardized SEPP. In particular, 5GMRR has discussed that the SEPP can also be outsourced and hosted by a provider outside the PLMN and has denoted this case as Hosted SEPP and the provider of the Hosted SEPP as Hosted SEPP provider, for example an IPX provider. 5GMRR has also discussed that a PLMN may use both local SEPPs (managed by PLMN) and Hosted SEPPs, i.e., the PLMN has local SEPPs each handling a set of roaming relations, while the Hosted SEPPs handle different set of roaming relations. Note that a hosted SEPP is not to be confused with a roaming hub as these are separate roles with different requirements. 5GMRR has agreed on the following requirements on Hosted SEPP: - NFs like AMF, NRF, SMF, UDM shall not be impacted by the decision to deploy a Hosted SEPP, i.e., o A NF in the VPLMN shall discover and interact with NF(s) in the HPLMN as standardized by 3GPP. o A NF in the HPLMN shall interact with NF(s) in the VPLMN as standardized by 3GPP. - All SBI messages shall be transmitted securely between the PLMN and the Hosted SEPP deployment. - Both the operator edge and the edge of the hosted SEPP deployment need to be protected. - A roaming partner SEPP shall interact with the Hosted SEPP as standardized by 3GPP. Section 4.19 of GSMA PRD IR.67 describes the use of DNS in Peer SEPP FQDN(s) discovery including the FQDN discovery for a non-MNO SEPP. Section 5.1.2 of GSMA PRD FS.34 describes the FQDN of the non-MNO SEPP. - The Hosted SEPP providers shall isolate the processing for each PLMN from the processing for other PLMNs. The hosted SEPP provider shall be able to use a different TLS certificate per serving PLMN for an incoming TLS connection, as the MNC and MCC of that PLMN are encoded in the certificate. This certificate shall be dedicated to the given PLMN (i.e., shall not contain MNC\/MCC combinations belonging to any other PLMN). It is assumed that the hosted SEPP is only able to obtain a certificate with an MCC\/MNC combination if the affected MNO has previously authorized this.","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":"2022-07-20 14:45:22","uploaded":"2022-07-20 14:45:39","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG2, CT WG4","lsoriginalls":"5GMRR#37 Doc 11","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205459.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205462","title":"LS from ITU-T SG13: LS on the consent of Recommendation ITU-T Y.3181 (ex-Y.ML-IMT2020-sandbox): 'Architectural framework for Machine Learning Sandbox in future networks including IMT-2020'","source":"ITU-T SG13","contact":"Marco Carugi","contact-id":31658,"tdoctype":"LS in","for":"Information","abstract":"This LS informs about the consent of Recommendation ITU-T Y.3181 (ex-Y.ML-IMT2020-sandbox) Architectural framework for Machine Learning Sandbox in future networks including IMT-2020 .","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":"2022-07-21 13:33:49","uploaded":"2022-07-21 13:51:28","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSAG, ITU-T SGs, 3GPP, GSMA, IEEE, ETSI, TMF, IETF, IRTF, ISO\/IEC, O-RAN Alliance, NGMN, \u2026.","Cc":"","lsoriginalls":"SG13-LS6","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205462.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205465","title":"LS from RAN WG3: Reply LS on PEI and UE Subgrouping","source":"RAN WG3","contact":"Chen Jie","contact-id":72417,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 thanks RAN WG2 for their LS on the PEI and UE Subgrouping. RAN WG3 would like to provide the following feedback for RAN WG2's questions. Question 1: Whether the mismatched understanding about the last used cell between UE and NW still exists in NR, if so, whether the LTE method (i.e. to introduce no last cell update indication in RRCRelease Message) can be reused? RAN WG3's answer: RAN WG3 thinks that the mismatched understanding about the last used cell between UE and NW also exists in NR. From RAN WG3 perspective, the mentioned LTE method can be reused for NR, however, the final decision is up to RAN WG2. Question 2: Whether this problematic scenario can be avoided or needs to be resolved through signaling? (In this scenario, assuming that the anchor gNB does not support CN assigned subgrouping). RAN WG3's answer: From RAN WG3 perspective, the problematic scenario can be avoided by implementation, e.g., CN-assigned subgrouping support is uniform in a certain area e.g., RNA or TAs. RAN WG3 has no solution other than to assume deployment coordination.","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":"2022-07-21 13:33:49","uploaded":"2022-07-25 10:36:31","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"SA WG2, CT WG1","lsoriginalls":"R3-224004","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205465.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205492","title":"Notes from Call on inter-PLMN VoLTE handover for interested delegates of SA WG3-LI, SA WG3, SA WG2, CT WG1 held on Thursday 7\/7\/22","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"discussion","for":"Information","abstract":"Notes from Call on inter-PLMN VoLTE handover for interested delegates of SA WG3-LI, SA WG3, SA WG2, CT WG1 held on Thursday 7\/7\/22","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10040,"status":"noted","reservation_date":"2022-07-29 15:15:55","uploaded":"2022-07-29 15:18:30","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205492.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205493","title":"Proposed Way Forward on VoLTE LI for inter-PLMN handover and idle mode mobility","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"discussion","for":"Approval","abstract":"Proposed Way Forward on VoLTE LI for inter-PLMN handover and idle mode mobility","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":"2022-07-29 15:19:20","uploaded":"2022-07-29 15:21:30","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205493.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205554","title":"Handling of HPLMN request for GBR greater than VPLMN value for IMS voice service in home routed roaming","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In home routed roaming scenarios for IMS voice service (i.e. the IMS APN defined by the GSMA), if the HPLMN requests a GBR greater than what the VPLMN is prepared to support, the MME will reject the request and the MME should inform the PLMN about the GBR data rate that it could accept on that type of MME and RAT.","secretary_remarks":"Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10240,"status":"postponed","reservation_date":"2022-08-06 09:56:24","uploaded":"2022-08-06 09:59:33","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.401","crspecversion":"17.5.0","workitem":[{"winame":"TEI17"}],"crnumber":3702.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205554.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205666","title":"[DRAFT] Reply LS on PLMN ID used in Roaming Scenarios","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS related to the PLMN ID handling in SEPP","secretary_remarks":"Response to S2-2205439. r06 agreed. Revised to S2-2207391.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10170,"status":"revised","reservation_date":"2022-08-08 23:30:47","uploaded":"2022-08-10 18:01:40","revisionof":"","revisedto":"S2-2207391","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205666.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205779","title":"[DRAFT] Reply LS on access to multiple IMS networks via a 5GC network slice","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"LS out","for":"Approval","abstract":"This LS replies to incoming LS S2-2200042 on access to multiple IMS networks via a 5GC network slice","secretary_remarks":"Response to S2-2200042 (Replied to at S2#149E). Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10250,"status":"noted","reservation_date":"2022-08-09 15:02:57","uploaded":"2022-08-10 13:23:42","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205779.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205903","title":"Cross border mobility related to IMS calls and LI for home routed IMS","source":"Ericsson, AT&T","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Endorsement","abstract":"Summary of change: Adding procedure for mobility between PLMNs for IMS Home routed roaming. Editorial updates","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10260,"status":"noted","reservation_date":"2022-08-09 23:02:15","uploaded":"2022-08-10 17:50:57","revisionof":"","revisedto":"S2-2209140","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205903.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205927","title":"Support for 5QI Priority Level in QoS constraints","source":"Peraton Labs, CISA ECD, AT&T, T-Mobile USA, Verizon","contact":"Robert Streijl","contact-id":92467,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 4.3.2.2.2, step 6, added to the QoS constraints the 5QI Priority Level that the VPLMN can accept.","secretary_remarks":"Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10270,"status":"postponed","reservation_date":"2022-08-10 00:16:40","uploaded":"2022-08-10 14:13:02","revisionof":"","revisedto":"S2-2209066","release":"Rel-17","crspec":"23.502","crspecversion":"17.5.0","workitem":[{"winame":"TEI17"}],"crnumber":3519.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205927.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2206379","title":"Clarification on NAS PDU delivery during PDU Session modification","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Rel-17 mirror CR: Summary of change: If the PDU Session modification is UE triggered and the N2 SM information indicates modification failure of whole PDU Session (i.e PDU Session Resource Failed to Modify Response Item), the SMF determines that the NAS PDU was not sent to UE and shall reject the PDU session modification by including a N1 SM container with a PDU Session Modification Reject message. Or else, SMF determines that the NAS PDU was sent to UE successfully and checks whether some QoS Flow modifications failed. If the (R)AN rejects QFI(s), the SMF shall trigger a separate NAS PDN Session Modification procedure after step 11 to align the SM context of this PDU Session in UE (i.e. delete the QoS rules and QoS Flow level QoS parameters of the failed QoS Flows).","secretary_remarks":"r03 agreed. Revised to S2-2207392.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10280,"status":"revised","reservation_date":"2022-08-10 10:00:13","uploaded":"2022-08-10 14:48:02","revisionof":"","revisedto":"S2-2207392","release":"Rel-17","crspec":"23.502","crspecversion":"17.5.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":3536.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2206379.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2206380","title":"Clarification on NAS PDU delivery during PDU Session modification","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If the PDU Session modification is UE triggered and the N2 SM information indicates modification failure of whole PDU Session (i.e PDU Session Resource Failed to Modify Response Item), the SMF determines that the NAS PDU was not sent to UE and shall reject the PDU session modification by including a N1 SM container with a PDU Session Modification Reject message. Or else, SMF determines that the NAS PDU was sent to UE successfully and checks whether some QoS Flow modifications failed. If the (R)AN rejects QFI(s), the SMF shall trigger a separate NAS PDN Session Modification procedure after step 11 to align the SM context of this PDU Session in UE (i.e. delete the QoS rules and QoS Flow level QoS parameters of the failed QoS Flows).","secretary_remarks":"r04 agreed. Revised to S2-2207393.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10300,"status":"revised","reservation_date":"2022-08-10 10:00:14","uploaded":"2022-08-10 14:48:02","revisionof":"","revisedto":"S2-2207393","release":"Rel-16","crspec":"23.502","crspecversion":"16.13.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":3537.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2206380.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2206389","title":"Handling of GBR for EPS fallback service in home routed roaming","source":"Vivo","contact":"vivian chong","contact-id":93021,"tdoctype":"discussion","for":"Approval","abstract":"This paper proposes to further discuss the EPS fallback scenario when HPLMN requested GBR value not compliant with roaming agreement.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10320,"status":"noted","reservation_date":"2022-08-10 10:03:59","uploaded":"2022-08-10 12:40:47","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2206389.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2206599","title":"[DRAFT] Reply LS on supporting of NAT deployed within the edge data network","source":"China Mobile","contact":"Yan Han","contact-id":93044,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on supporting of NAT deployed within the edge data network.","secretary_remarks":"Response to S2-2205458. Merged into S2-2207394","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10340,"status":"merged","reservation_date":"2022-08-10 12:13:52","uploaded":"2022-08-10 16:21:21","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2206599.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2206796","title":"[draft] LS on FS_eEDGEAPP Solution for Support of NAT deployed within the edge data network","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"[draft] LS on FS_eEDGEAPP Solution for Support of NAT deployed within the edge data network","secretary_remarks":"Response to S2-2205458. Merged into S2-2207394","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10350,"status":"merged","reservation_date":"2022-08-10 16:12:52","uploaded":"2022-08-10 17:04:46","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"FS_eEDGEAPP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2206796.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2206900","title":"[DRAFT] Reply LS on FS_eEDGEAPP Solution for Support of NAT deployed within the edge","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG6. CC: SA WG3","secretary_remarks":"r15 agreed. Revised to S2-2207394, merging S2-2206599 and S2-2206796.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10360,"status":"revised","reservation_date":"2022-08-10 19:22:41","uploaded":"2022-08-10 21:57:28","revisionof":"","revisedto":"S2-2207394","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"FS_eEDGEAPP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2206900.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2207391","title":"Reply LS On PLMN ID used in Roaming Scenarios","source":"SA WG2","contact":"Qian Chen","contact-id":94222,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3, CT WG4","secretary_remarks":"Revision of S2-2205666r06. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10180,"status":"approved","reservation_date":"2022-08-25 04:52:03","uploaded":"2022-08-30 09:43:26","revisionof":"S2-2205666","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2205439","lsto":"SA WG3, CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2207391.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2207392","title":"Clarification on NAS PDU delivery during PDU Session modification","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Rel-17 mirror CR: Summary of change: If the PDU Session modification is UE triggered and the N2 SM information indicates modification failure of whole PDU Session (i.e PDU Session Resource Failed to Modify Response Item), the SMF determines that the NAS PDU was not sent to UE and shall reject the PDU session modification by including a N1 SM container with a PDU Session Modification Reject message. Or else, SMF determines that the NAS PDU was sent to UE successfully and checks whether some QoS Flow modifications failed. If the (R)AN rejects QFI(s), the SMF shall trigger a separate NAS PDN Session Modification procedure after step 11 to align the SM context of this PDU Session in UE (i.e. delete the QoS rules and QoS Flow level QoS parameters of the failed QoS Flows).","secretary_remarks":"Revision of S2-2206379r03. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10290,"status":"agreed","reservation_date":"2022-08-25 04:52:03","uploaded":"2022-08-30 09:51:09","revisionof":"S2-2206379","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.5.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":3536.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"SP-220769","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2207392.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2207393","title":"Clarification on NAS PDU delivery during PDU Session modification","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If the PDU Session modification is UE triggered and the N2 SM information indicates modification failure of whole PDU Session (i.e PDU Session Resource Failed to Modify Response Item), the SMF determines that the NAS PDU was not sent to UE and shall reject the PDU session modification by including a N1 SM container with a PDU Session Modification Reject message. Or else, SMF determines that the NAS PDU was sent to UE successfully and checks whether some QoS Flow modifications failed. If the (R)AN rejects QFI(s), the SMF shall trigger a separate NAS PDN Session Modification procedure after step 11 to align the SM context of this PDU Session in UE (i.e. delete the QoS rules and QoS Flow level QoS parameters of the failed QoS Flows).","secretary_remarks":"Revision of S2-2206380r04. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10310,"status":"agreed","reservation_date":"2022-08-25 04:52:05","uploaded":"2022-08-30 09:51:09","revisionof":"S2-2206380","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.13.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":3537.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220769","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2207393.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2207394","title":"Reply LS on FS_eEDGEAPP Solution for Support of NAT deployed within the edge","source":"SA WG2","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG6 Cc: SA WG3","secretary_remarks":"Revision of S2-2206900r15, merging S2-2206599 and S2-2206796. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10370,"status":"approved","reservation_date":"2022-08-25 04:52:06","uploaded":"2022-08-30 09:43:26","revisionof":"S2-2206900","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"FS_eEDGEAPP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2205458","lsto":"SA WG6","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2207394.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2207697","title":"Reply LS on Inter-PLMN Handover of VoLTE calls and idle mode mobility of IMS sessions","source":"SA WG2","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3-LI, CT WG1, CT WG4, SA WG3 Attachments: S2-2205903","secretary_remarks":"CC#3: Revision of S2-2208090r01. This LS OUT was approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10080,"status":"approved","reservation_date":"2022-08-25 04:52:39","uploaded":"2022-08-30 09:43:26","revisionof":"S2-2208090","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2205400","lsto":"SA WG3-LI, CT WG1, CT WG4, SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2207697.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208090","title":"[DRAFT] Reply LS on Inter-PLMN Handover of VoLTE calls and idle mode mobility of IMS sessions","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3-LI, CT WG1, CT WG4. Attachments: S2-2205903","secretary_remarks":"Created at CC#2. Response to S2-2205400. CC#3: r01 agreed. Revised to S2-2207697.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10070,"status":"revised","reservation_date":"2022-08-22 15:38:23","uploaded":"2022-08-30 09:51:08","revisionof":"","revisedto":"S2-2207697","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3-LI, CT WG1","Cc":"SA WG3, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2208090.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]