[{"name":"S2-2108251","title":"LS from SA WG6: Reply LS on IP address to GPSI translation","source":"SA WG6","contact":"Nishant Gupta","contact-id":62473,"tdoctype":"LS in","for":"Action","abstract":"SA WG6 thanks SA WG2 for the reply LS on IP address to GPSI translation. SA WG6 would like to express the following view for GPSI: On SA WG2's question #1: In SA WG6's understanding, although GPSI is a public identifier, a user may not be willing to share the GPSI with AFs in the form of MSISDN, due to its potential misuse (e.g. SMS spam). SA WG3 recognized this concern in their LS to SA WG6 and SA WG2 in S6-210012\/ S2-2100044. On SA WG2's question #2 and #3: If GPSI is designed to be in the form of an External Identifier per AF and is also temporary (based on e.g. temporal validity or invalidated on a request by the subscriber), it will help in preventing the tracking of user's behaviour across AFs. Action: SA WG6 kindly requests SA WG2 and SA WG3 to consider the above information when designing the required features.","secretary_remarks":"Revision of S2-2106990 from S2#147E. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10030,"status":"noted","reservation_date":"2021-10-29 06:35:07","uploaded":"2021-10-29 06:36:41","revisionof":"S2-2106990","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG3","lsoriginalls":"S6-211082","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108251.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108256","title":"Reply LS on IP address to GPSI translation","source":"SA WG3","contact":"Longhua Guo","contact-id":80179,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 would like to thank SA WG2 for the LS reply on IP address to GPSI translation (S3-211392 \/ S2-2101307). SA WG2 asked in their LS that A GPSI can be either an MSISDN or an External Identifier. The GPSI in either form is used for the same purposes in the 5G System. SA WG2 would like to understand whether there would be different privacy considerations on sending external identifier to an AF possibly depending on if the GPSI takes the form of an MSISDN or an External Identifier. SA WG2 would also like to understand the following: 1. Are there privacy concerns (and do you see any difference) with exposing to an AF that may be external the GPSI in the form of MSISDN or the GPSI in the form of External Identifier? SA WG3 would like to inform SA WG2 and SA WG6 that SA WG3 sees some privacy issues with the usage of GPSI in the form of MSISDN. SA WG2 also asked the following follow-up questions: If the GPSI in either form does not meet the privacy requirements: 2. Should a new exposed subscription identifier be permanent or temporary? If such new exposed subscription identifier is temporary, what is its temporal validity? SA WG2 assumes that it is then up to the 5GC operator (e.g. NEF) to define this validity. SA WG3 has not yet concluded that the use of a temporary identifiers justifies the gain. SA WG2 is recommended to proceed with the use of permanent identifiers only at this stage for this feature. SA WG3 will inform SA WG2 if SA WG3 later concludes on the use of temporary identifiers and the desired properties of such temporary identifiers. 3. Should such new exposed subscription identifier be 'global' or per AF? SA WG3 agrees on that a mechanism to support 'GPSI per AF' helps to prevent possible tracking of users among AFs. SA WG3 would like to also inform SA WG2 and SA WG6 that SA WG3 considers that this LS reply also covers the issues raised in the Reply LSes (S3-211391 \/ S2-2009339) and (S3-211424 \/ S6-211082). Action: SA WG3 kindly asks SA WG2 and SA WG6 to take the above into account.","secretary_remarks":"Revision of S2-2107003 from S2#147E. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10040,"status":"noted","reservation_date":"2021-10-29 06:35:07","uploaded":"2021-10-29 06:36:41","revisionof":"S2-2107003","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6, SA WG2","Cc":"SA WG1","lsoriginalls":"S3-212355","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108256.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108257","title":"LS from GSMA 5GJA: LS on Traffic Categories in URSP","source":"GSMA 5GJA","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"LS in","for":"Action","abstract":"GSMA NG 5GJA has profiled the use of URSP in GSMA PRD NG.114 and NG.113 based on the currently supported URSP functionality in 3GPP TS 23.503 and in 3GPP TS 24.526. GSMA NG 5GJA has discussed the need to support standardized and MNO-specific traffic categories in the traffic descriptor in URSP. Examples of traffic categories to be standardized are: - Enterprise: traffic from one or more applications related to Enterprise service - Gaming: traffic from one or more applications related to Gaming service, e.g., with low latency requirement - Video Streaming: traffic from one or more applications related to Video Streaming, e.g., HD video streaming, 4K video streaming Standardized traffic categories could be defined by 3GPP or by GSMA. MNO-specific traffic categories should be represented by a number of octets (flexible format to allow any string). A given traffic category can be used by more than one application simultaneously, and one application can simultaneously use more than one traffic category. Action: GSMA NG 5GJA kindly requests SA WG2 to consider the above requirements and to provide feedback to GSMA on how to support traffic categories.","secretary_remarks":"Revision of S2-2107006 from S2#147E. Response drafted in S2-2108979. Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10050,"status":"postponed","reservation_date":"2021-10-29 06:35:07","uploaded":"2021-10-29 06:36:41","revisionof":"S2-2107006","revisedto":"S2-2200005","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"5GJA17_104","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108257.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108267","title":"LS from CT WG3: LS on PDU Session ID assignment for the Interworking scenario","source":"CT WG3","contact":"Xiaoyun Zhou","contact-id":77294,"tdoctype":"LS in","for":"Action","abstract":"CT WG3 is studying an issue of PDU Session ID assignment in the following scenario: 1) UE firstly establishes a PDN connection via MME and MME assigns a Default EPS bearer ID1 to the PDN connection. The SMF+PGW-C will calculate a PDU Session ID1 with the value of 64 + Default EPS bearer ID1 according to Table 5.4.2-1 of TS 29.571, e.g. if Default EPS bearer ID is 5, then the calculated PDU Session ID1 is 69. And then the SMF+PGW-C sends the PDU Session ID1 to the PCF as a parameter to identify the PDU session for the SUPI, DNN and S-NSSAI. 2) UE handovers to the ePDG and the ePDG assigns a new Default EPS bearer ID2. The Default EPS bearer ID2 may be the same as the Default EPS bearer ID1 or different from the Default EPS bearer ID1. CT WG3 understands the SMF+PGW-C doesn't calculate a new PDU session ID, since there is no explicit requirement to do so. 3) UE may establish an additional PDU connection to the same DNN and S-NSSAI via MME while the UE keeps the PDN connection via ePDG. As the MME may assign the same value of Default EPS bearer ID3 as the Default EPS bearer ID1, the SMF+PGW-C would allocate the same PDU session ID3 as the PDU session ID1 (i.e. the Default EPS bearer ID3 is 5, and the PDU Session ID3 will be 69). When the SMF+PGW-C sends the PDU Session ID3 to the PCF, PCF can't identify this is a different PDU Session than PDU Session ID1 and may reject the request from the SMF+PGW-C incorrectly. CT WG3 would like to ask the following questions to SA WG2: Question 1: Is it correct understanding that SMF+PGW-C doesn't calculate a new PDU session ID at UE handover from MME to ePDG, and vice-versa? Question 2: If answer to Q1 is yes, how to resolve the issue raised in bullet 3)? Question 3: If answer to Q1 is no, can the SMF+PGW-C update the PDU session ID to the PCF with new calculated value?. Action: CT WG3 kindly asks SA WG2 to answer the questions above and amend the SA WG2 specifications accordingly, where appropriate.","secretary_remarks":"Revision of S2-2107031 from S2#147E. Responses drafted in S2-2108589 and S2-2108853. Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10240,"status":"postponed","reservation_date":"2021-10-29 06:35:07","uploaded":"2021-10-29 06:36:42","revisionof":"S2-2107031","revisedto":"S2-2200008","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"C3-214527","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108267.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108268","title":"LS from CT WG4: LS on creating a new stage 2 TS for SMS-SBI","source":"CT WG4","contact":"Liu Liu","contact-id":76788,"tdoctype":"LS in","for":"Action","abstract":"According to LS (SP-191362 and CP-193301), CT WGs take responsibility for the study on service-based support for SMS in 5GC. CT WG4 has discussed the way for SBI-based SMS since CT WG4#99e, and has reached a consensus basically. But after discussion, CT WG4 believes that a new stage 2 TS for SMS-SBI should be created, where all SMS-SBI services and procedures are described in detail. CT WG4 would be glad to take the responsibility of this TS, based on the former studies on SMS-SBI. CT WG4 kindly ask SA WG2\/CT WG1 to confirm the creation of a new stage 2 TS for SMS-SBI, and also CT WG4's responsibility of this TS. Action: CT WG4 kindly ask SA WG2\/CT WG1 to confirm the creation of a new stage 2 TS for SMS-SBI, and also CT WG4's responsibility of this TS.","secretary_remarks":"Revision of S2-2107033 from S2#147E. Final response in S2-2109340","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10070,"status":"replied to","reservation_date":"2021-10-29 06:35:07","uploaded":"2021-10-29 06:36:41","revisionof":"S2-2107033","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1","Cc":"","lsoriginalls":"C4-214540","lsreply":"S2-2109340","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108268.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108272","title":"LS from RAN WG3: Reply LS on RACS capability detection with S1 and NG handover","source":"RAN WG3","contact":"Alexander Vesely","contact-id":10078,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 thanks SA WG2 for their LS on RACS capability detection with S1 and NG handover. RAN WG3 has discussed the topic and will continue discussing solutions for Rel-17 to generalise the communication between target and source RAN node at handover via CN nodes regarding protocol support at the target RAN node. Action: RAN WG3 asks SA WG2 to take the above reply into account","secretary_remarks":"Revision of S2-2107052 from S2#147E. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10090,"status":"noted","reservation_date":"2021-10-29 06:35:07","uploaded":"2021-10-29 06:36:41","revisionof":"S2-2107052","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"R3-214373","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108272.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108275","title":"Reply LS on creating a new stage 2 TS for SMS-SBI","source":"CT WG1","contact":"Mikael Wass","contact-id":42217,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 thanks CT WG4 for the LS on creating a new stage 2 TS for SMS-SBI informing CT WG1 and SA WG2 of the CT WG4 preference to create a new stage 2 TS for SMS-SBI, where all SMS-SBI services and procedures are described in detail: CT WG4 kindly ask SA WG2\/CT WG1 to confirm the creation of a new stage 2 TS for SMS-SBI, and also CT WG4's responsibility of this TS. CT WG1 discussed the CT WG4 proposal and agrees that a new stage 2 TS for SMS-SBI under CT WG4 responsibility should be created. Furthermore, CT WG1 expects that updates in 3GPP TS 23.040 for linkage between existing SMS stage 2 functionalities and the new TS for SMS-SBI will be needed and this will be done in the CT WG1 scope of SMS_SBI WI.","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":"2021-10-29 06:41:19","uploaded":"2021-10-29 07:49:49","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"SA WG2","lsoriginalls":"C1-216043","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108275.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108289","title":"LS from ETSI TC LI: Reply LS on PSCELL ID availability in SGW CDR","source":"ETSI TC LI","contact":"Carmine Rizzo","contact-id":52778,"tdoctype":"LS in","for":"Information","abstract":"ETSI TC LI would like to thank SA WG5 for the LS (S5-214069) on PSCELL ID availability in SGW CDR replying to ETSI TC LI request in providing the same capability in allowing the CSPs to comply with the Retained Data Regulations. ETSI TC LI gladly confirms that the above added functionality fulfils the Retained Data related requirements by allowing the CSPs to have access to the PSCELL ID information at a later time.","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":"2021-10-29 06:41:20","uploaded":"2021-10-29 07:49:49","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"TSG SA, SA WG2, RAN WG3, SA WG3-LI","lsoriginalls":"LI(21)P58049r1","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108289.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108291","title":"LS from APT Wireless Group: APT REPORT ON EMERGING CRITICAL APPLICATIONS & USE CASES OF IMT FOR INDUSTRIAL, SOCIETAL AND ENTERPRISE USERS","source":"APT Wireless Group","contact":"BHARAT BHATIA","contact-id":46829,"tdoctype":"LS in","for":"Information","abstract":"The AWG is developing a working document towards an APT Report on 'EMERGING CRITICAL APPLICATIONS & USE CASES OF IMT FOR INDUSTRIAL, SOCIETAL AND ENTERPRISE USERS' The scope of the report is on new\/emerging critical applications and use cases of IMT-Advanced and IMT-2020 for industrial, societal and enterprise users, both 4G LTE and NR. Current draft working document being developed in the AWG is enclosed for reference. As SA WG6 (SA WG6) is the application enablement and critical communication applications group for critical applications of IMT, AWG would kindly invite the 3GPP to provide relevant materials, use cases and any other related material that would facilitate in completion of this Report. AWG would appreciate 3GPP to provide any feedback before the next 29th APT Wireless Group (AWG-29) meeting, scheduled in March\/April 2022, if any. For technical queries please contact: Mr. Bharat Bhatia ITU-APT Foundation of India +91 9810173737 Email: Bharat.bhatia@itu-apt.org AWG will keep 3GPP informed of the progress and outcomes of relevant studies in future AWG meetings.","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":"2021-10-29 06:41:20","uploaded":"2021-10-29 07:49:49","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG6","Cc":"SA WG2","lsoriginalls":"AWG28_OUT03 (Rev.1)","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108291.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108293","title":"LS from SA WG5: Reply LS to GSMA on new whitepaper E2E Network Slicing Architecture","source":"SA WG5","contact":"Kai Zhang","contact-id":66365,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to thank GSMA NG for their LS on New Whitepaper: 'E2E Network Slicing Architecture'. SA WG5 supports the intention of the whitepaper to show guidance of the entire industry ecosystem, for operators, vendors and service providers to be able to consider common solutions of network slicing. SA WG5 provides the following feedback on the whitepaper: - Regarding 2.4 SLA\/SLS attributes for Network Slicing o Besides the alignment work of attributes between Service Profile in 3GPP TS 28.541 and GST NG.116 is proceeding at the present time, Service Profile can be translated to corresponding requirements for dedicated domains. For example, 5GC SliceProfile is used to carry 5GC domain requirements, NG-RAN SliceProfile is used to carry NG-RAN domain requirements, and TN requirements are translated and provided to TN domain. Please see 3GPP TS 28.541 for further information on the relation between GSMA GST, ServiceProfile and SliceProfile. - Regarding the figure of High level diagram of O&M domain in 5.4 O&M o Why is there TMF638 Inventory Mgmt illustrated in RAN Mgmt domain and CN Mgmt Domain? SA WG5 thinks the intent of TMF638 Inventory Mgmt API is to provide a consistent\/standardized mechanism to query and manipulate the Service inventory in E2E Network & Service Mgmt Domain, not for a dedicated domain like RAN Mgmt domain or CN Mgmt domain. - Regarding the figure of 3GPP NRM for 5G network in 5.4.1 SA WG5 o JSON is listed as one kind of Solution Sets in the figure. However, in SA WG5 Rel-17 work, JSON has been replaced by YAML. 3GPP NRM Stage 3 Solution Sets are YAML and YANG.","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":"2021-10-29 06:41:20","uploaded":"2021-10-29 07:49:49","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA NG","Cc":"TSG SA, SA WG2, TSG RAN","lsoriginalls":"S5-215083","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108293.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108295","title":"LS from SA WG6: LS on network slice management service consumption","source":"SA WG6","contact":"shaowen zheng","contact-id":88792,"tdoctype":"LS in","for":"Information","abstract":"The ongoing Rel-18 study in FS_NSCALE (TR 23.700-99) is investigating the services and functions of SA WG6 enablement layer to ensure the efficient network slice capability exposure. That needs SA WG6 enablement layer act as trusted 3rd party or consumer to invoke control and management plane capabilities from SA WG2 and SA WG5 pertaining to network slicing. SA WG6 would like to get clarification about the following related to the network slice management service: - Is SA WG5 planning to provide an interface to an AF for slice management by a trusted third-party?","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":"2021-10-29 06:41:20","uploaded":"2021-10-29 07:49:49","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"SA WG2","lsoriginalls":"S6-212460","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108295.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108296","title":"LS from GSMA NRG: LS from NRG to 3GPP on Emergency Communication Improvement","source":"GSMA NRG","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"Legal authorities are requesting Mobile operators to provide access to emergency services through emergency communication also to roamers regardless of the used service (Voice, SMS , video,\u2026). European Commission is mandated to adopt a Delegated Act to ensure effective access to emergency services through emergency communications, defining major improvements regarding emergency communication. The Delegated Act should be adopted by 21 December 2022. A consultation activity will be held between October and December 2021. The objective of the initiative is to ensure that regardless of the means of emergency communications - calls, SMS, application, real time text, video - end-users benefit from effective access to emergency services, everywhere in EU, especially in roaming conditions. Major improvements regarding emergency communication are listed below: 1. Access to emergency services through emergency communications to the most appropriate PSAP should be ensured. The scope of emergency communications could be broadened from voice to SMS, video and other types of interpersonal communication services. Emergency communications should be free of charge for end-users. More effective emergency communications would allow reliable and efficient access to the most appropriate PSAP, shorter call processing times and enable shorter 'on scene' arrival times of emergency services. 2. Ensure equivalent access to emergency services for end-users with disabilities throughout the EU (including roaming cases), coherent implementation of accurate and reliable caller location and adaptation of routing protocols to an all-IP environment. 3. The caller location is the single most essential contextual data; the more accurate the localisation, the swifter the emergency intervention can be. New technologies or mixes of technologies allow more accurate and reliable caller location that should be available both in domestic and cross border (roaming) context. Delivery of both network-based and handset-derived caller location should be delivered without delay to the most appropriate PSAP. More information could be read using the following link: https:\/\/ec.europa.eu\/info\/law\/better-regulation\/have-your-say\/initiatives\/13183-Emergency-communications-improving-access-through-the-single-European-emergency-number-'112'_en. Proposed axis of improvement Based on EU request (and other local authorities), GSMA NG\/NRG believes that emergency services could be improved on the following aspects: - Service extension: Emergency should be accessible regardless of the service used (voice, SMS, video, ,\u2026). - Roaming extension: All emergency services shall be provided and supported in roaming conditions, and routed to the appropriate PSAP directly by the visited network (tromboning via the home network should be avoided). - Location improvement: Caller location should be improved, using in a standard way the terminal and network location. Requests: GSMA NG\/NRG requests 3GPP to study the following questions related to the 3 axis (service, coverage, location) : - Service extension: Emergency service should be enhanced to SMS (specially for end-users with disabilities). Is it possible to define a standard emergency SMS service using IMS for example? - Roaming extension: Emergency service should be available in roaming condition. Is it possible to use data LBO for all standard emergency services (voice, SMS, video,), in order to connect to the visited PSAP ? - Location improvement: Caller location should be provided whatever the service (voice, SMS, video), whatever the coverage (domestic, roaming), using in a standard way the terminal and network location. Is it possible to standardise more in detail terminal location provided to PSAP, typically like AML (Advanced Mobile Location) solutions ? GSMA NG\/NRG requests 3GPP to study the 2 following service evolutions: - Emergency service should be enhanced to SMS (in R18), - AML should be integrated in 3GPP spec in further releases.","secretary_remarks":"Response drafted in S2-2108981. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10340,"status":"noted","reservation_date":"2021-10-29 06:41:20","uploaded":"2021-11-04 06:08:49","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"SA WG2, ETSI TC EMTEL","lsoriginalls":"NRG_012_200","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108296.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108312","title":"Discussion of Open-Source-Defined Multi-Access Edge Computing","source":"Xidian University","contact":"Liqiang Zhao","contact-id":93700,"tdoctype":"discussion","for":"Discussion","abstract":"Discusses the architecture and the principles of open-source-defined multi-access edge computing, include the network decoupling and reconfiguration of the network functions and resources.","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":"2021-11-05 02:46:22","uploaded":"2021-11-14 14:15:44","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_148E_Electronic_2021-11\/Docs\/S2-2108312.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108384","title":"Documentation Handling on NF profile.","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"This paper proposes to capture the parameters of NF profile in 23.502 and provide a reference to 23.502 in clause 6.2.6.2 of 23.501.","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":"2021-11-07 01:33:18","uploaded":"2021-11-08 19:33:53","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108384.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108385","title":"Documentation handling for description of NF profile","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add a note that additional parameters in the NF profile, refer to clause 5.2.7.2.2 of TS 23.502","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":"2021-11-07 01:33:18","uploaded":"2021-11-08 19:33:53","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":3369.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108385.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108386","title":"SMF+PGW-C assigned PDU Session ID","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: View-1 is assumed: Add a note the scenario of SMF+PGW-C assigning same PDU Sessions for muultiple PDN connection is not seen in real deployment. .","secretary_remarks":"Revision of (Postponed) S2-2107164 from S2#147E. Source to WG incorrect. CC#2: Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10190,"status":"noted","reservation_date":"2021-11-07 01:33:19","uploaded":"2021-11-08 19:33:53","revisionof":"S2-2107164","revisedto":"S2-2200112, S2-2200310","release":"Rel-17","crspec":23.502,"crspecversion":"17.2.1","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":3135.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108386.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108412","title":"Support of the mapping from IP addressing information provided to an AF to the user identity","source":"[Nokia, Nokia Shanghai Bell], Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In this case the 5GC first needs to retrieve the Permanent identifier of the UE before trying to fulfil the AF request. The 5GC may need to determine the Permanent identifier of the UE based on: the UE address as provided by the AF, the corresponding DNN and\/or S-NSSAI information: this may have been provided by the AF or determined by the NEF using the identity of the AF;","secretary_remarks":"Revision of (Postponed) S2-2107653 from S2#147E. r05 agreed. Revised to S2-2109140, merging S2-2108923","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10200,"status":"revised","reservation_date":"2021-11-07 01:47:00","uploaded":"2021-11-08 19:26:08","revisionof":"S2-2107653","revisedto":"S2-2109140","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"EDGEAPP"}],"crnumber":2385.0,"crrevision":6.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108412.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108413","title":"AF specific UE ID retrieval","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A new procedure is added for the AF to retrieve the AF specific GPSI (in the form of external id as defined in TS 23.003). The Event Exposure and Parameter Provisioning (targetting an individual) UE are updated to support requests with UE addressing information.","secretary_remarks":"Revision of (Postponed) S2-2107248 from S2#147E. r06 agreed. Revised to S2-2109141, merging S2-2108924","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10220,"status":"revised","reservation_date":"2021-11-07 01:47:02","uploaded":"2021-11-08 19:26:08","revisionof":"S2-2107248","revisedto":"S2-2109141","release":"Rel-17","crspec":23.502,"crspecversion":"17.2.1","workitem":[{"winame":"EDGEAPP"}],"crnumber":2926.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108413.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108486","title":"PDU Session ID assignment for non N1-NAS UEs","source":"Cisco Systems, Nokia, Nokia Shanghai Bell, ZTE","contact":"Irfan Ali","contact-id":74090,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The UDM assigns PDU Session ID for UEs that do not support N1 NAS and are anchored on SMF+PGW-C","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10270,"status":"noted","reservation_date":"2021-11-08 04:40:15","uploaded":"2021-11-08 14:09:00","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.2.1","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":3249.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108486.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108497","title":"Discussion and proposal on PDU session ID issue in CT WG3 LS.","source":"ZTE, Nokia, Nokia Shanghai Bell, Cisco Systems","contact":"Zhendong Li","contact-id":38521,"tdoctype":"discussion","for":"Discussion","abstract":"This discussion paper discusses the issue raised by CT WG3 LS, analyses the potential solution, and give the proposal","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10280,"status":"noted","reservation_date":"2021-11-08 06:37:52","uploaded":"2021-11-08 14:17:27","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_148E_Electronic_2021-11\/Docs\/S2-2108497.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108589","title":"[DRAFT] Reply LS on PDU Session ID assignment for the Interworking scenario","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on PDU Session ID assignment for the Interworking scenario to CT WG3.","secretary_remarks":"Revision of (Postponed) S2-2107485 from S2#147E. Response to S2-2108267. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10250,"status":"noted","reservation_date":"2021-11-08 09:13:33","uploaded":"2021-11-08 14:58:42","revisionof":"S2-2107485","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"TEI16"},{"winame":" 5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108589.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108590","title":"Discussion on PDU Session ID assignment for interworking scenario.","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"discussion","for":"Agreement","abstract":"This discussion paper aims at comparing solutions for resolving PDU Session ID conflict in interworking scenario and proposing way forward.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10290,"status":"noted","reservation_date":"2021-11-08 09:13:33","uploaded":"2021-11-08 15:00:57","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_148E_Electronic_2021-11\/Docs\/S2-2108590.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108591","title":"Correction on PDU Session ID assignment by SMF+PGW-C","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: SMF+PGW-C updates the allocated PDU Session ID for the UE that does not support 5GC NAS when the PDN connection handovers between 3GPP access and Non-3GPP access.","secretary_remarks":"Revision of (Postponed) S2-2107486 from S2#147E. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10300,"status":"noted","reservation_date":"2021-11-08 09:13:33","uploaded":"2021-11-08 15:00:57","revisionof":"S2-2107486","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.10.0","workitem":[{"winame":"TEI16"},{"winame":" 5GS_Ph1"}],"crnumber":3190.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108591.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108592","title":"Correction on PDU Session ID assignment by SMF+PGW-C","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Rel-17 mirror CR: Summary of change: SMF+PGW-C updates the allocated PDU Session ID for UE that does not support 5GC NAS when the PDN connection handovers between 3GPP access and Non-3GPP access.","secretary_remarks":"Revision of (Postponed) S2-2107487 from S2#147E. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10310,"status":"noted","reservation_date":"2021-11-08 09:13:34","uploaded":"2021-11-08 15:00:57","revisionof":"S2-2107487","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.2.0","workitem":[{"winame":"TEI16"},{"winame":" 5GS_Ph1"}],"crnumber":3191.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108592.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108853","title":"[DRAFT] LS on PDU Session ID assignment for the Interworking scenario","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"[draft] LS on PDU Session ID assignment for the Interworking scenario","secretary_remarks":"Response to S2-2108267. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10260,"status":"noted","reservation_date":"2021-11-08 14:02:56","uploaded":"2021-11-08 18:10:25","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"},{"winame":" 5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"CT WG4, SA WG5","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108853.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108923","title":"Support of the mapping from IP addressing information provided to an AF to the user identity","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In this case the 5GC first needs to retrieve the Permanent identifier of the UE before trying to fulfil the AF request. The 5GC may need to determine the Permanent identifier of the UE based on: the UE address as provided by the AF, the corresponding DNN and\/or S-NSSAI information: this may have been provided by the AF or determined by the NEF using the identity of the AF;","secretary_remarks":"Revision of (Postponed) S2-2107653 from S2#147E. Merged into S2-2109140","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10320,"status":"merged","reservation_date":"2021-11-08 16:38:24","uploaded":"2021-11-08 20:13:25","revisionof":"S2-2107653","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"EDGEAPP"}],"crnumber":2385.0,"crrevision":7.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108923.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108924","title":"Support of the mapping from IP addressing information provided to an AF to the user identity","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: An AF may request (via the NEF) information exposure or parameter provisioning targetting an individual UE, identifying the target UE by providing UE addressing information. In this case the 5GC (NEF) first needs to retrieve a Permanent Identifier of the UE Then the NEF Event exposure or the parameter provisioning may apply as defined in R16. Nnef_EventExposure_Subscribe, Nnef_Location_LocationUpdateNotify and Nnef_ParameterProvision operations are modified accordingly. The NEF may deliver back to the AF an UE external Identifier for an Application. This UE external Identifier for an Application may later on be used by the AF to issue further requests about the same UE.","secretary_remarks":"Revision of (Postponed) S2-2107654 from S2#147E. Merged into S2-2109141","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10330,"status":"merged","reservation_date":"2021-11-08 16:38:36","uploaded":"2021-11-08 20:13:25","revisionof":"S2-2107654","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.2.1","workitem":[{"winame":"EDGEAPP"}],"crnumber":2329.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108924.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108979","title":"[DRAFT] Reply LS to GSMA NG 5GJA on Traffic Categories in URSP","source":"Apple","contact":"Krisztian Kiss","contact-id":57762,"tdoctype":"LS out","for":"Approval","abstract":"To: GSMA NG 5GJA. CC:","secretary_remarks":"Response to S2-2108257. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10060,"status":"noted","reservation_date":"2021-11-08 22:18:57","uploaded":"2021-11-08 22:21:56","revisionof":"","revisedto":"S2-2201191","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"FS_eUEPO"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA NG 5GJA","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108979.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108980","title":"New WID on Study on Emergency Short Message Service .","source":"Orange","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"SID new","for":"Approval","abstract":"Per request from GSMA (S2-2108296), study the architectural evolutions of the 3GPP System to support Emergency SMS, based on the requirements specified in TS 22.101 during SA WG1#96-e.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10360,"status":"noted","reservation_date":"2021-11-08 22:52:46","uploaded":"2021-11-08 23:23:33","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108980.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108981","title":"[DRAFT] Reply LS on Emergency Communication Improvement","source":"Orange","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"LS out","for":"Approval","abstract":"Reply to GSMA NRG on Emergency Communication Improvement","secretary_remarks":"Response to S2-2108296. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10350,"status":"noted","reservation_date":"2021-11-08 22:52:46","uploaded":"2021-11-08 23:23:33","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA NRG","Cc":"SA WG1, ETSI TC EMTEL","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108981.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108986","title":"NRF Profile documentation","source":"Nokia, Nokia Shanghai-Bell","contact":"Thomas Belling","contact-id":68266,"tdoctype":"discussion","for":"Discussion","abstract":"NRF Profile documentation","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":"2021-11-08 23:29:53","uploaded":"2021-11-08 23:34:11","revisionof":"","revisedto":"","release":"","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_148E_Electronic_2021-11\/Docs\/S2-2108986.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109006","title":"LS from RAN WG3: LS On Source IP address clarifications","source":"RAN WG3","contact":"Angelo Centonza","contact-id":45800,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 is carrying out work to support ACL in NG-RAN. A definition of the ACL functionality can be found in TS36.413 and it is reported below for convenience: ACL functionality: A functionality controlling the access to network nodes. In case of Access Control Lists (ACL) functionality is applied in a network node the network node may only accept connections from other peer network nodes once the source addresses of the sending network node is already known in the target node. As part of the work on ACL, RAN WG3 needs to specify how to signal the source IP address(es) used for DL forwarding traffic within one GTP-U tunnel. In order for RAN WG3 to progress, RAN WG3 would like to ask CT WG4 whether DL forwarding traffic contained within a GTP-U DL forwarding tunnel can be transmitted by more than one source IP address.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10370,"status":"noted","reservation_date":"2021-11-15 12:14:31","uploaded":"2021-11-15 12:15:37","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"SA WG2","lsoriginalls":"R3-216139","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109006.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109007","title":"LS from RAN WG3: Reply to Reply LS On ACL support for Indirect Data Forwarding","source":"RAN WG3","contact":"Angelo Centonza","contact-id":45800,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 thanks SA WG2 for the reply LS on ACL support Indirect Data Forwarding. SA WG2 asked RAN WG3 to provide their view on whether the source address for a normal Iu-U\/N3 tunnel (for example, during Service request procedure from CM_IDLE to CM_CONNECTED) needs to be provided to RAN for ACL support or it can be made aware to RAN by other means. RAN WG3 discussed this use case and agreed that the source address for a normal Iu-U\/N3 tunnel may be configured at the RAN. Hence this use case is considered of lower priority and a solution for it is not needed. RAN WG3 would like to point out that the case of indirect data forwarding is different because the UP GW responsible for data forwarding may be different from the UP GW serving the Iu-U\/N3 tunnel. RAN WG3 would like to ask SA WG2 to confirm whether this understanding is correct and whether the UP GW selection for data forwarding is subject to any limitations. Action: RAN WG3 kindly asks SA WG2 to take the above into account.","secretary_remarks":"Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10380,"status":"postponed","reservation_date":"2021-11-15 12:14:31","uploaded":"2021-11-15 12:15:37","revisionof":"","revisedto":"S2-2200023","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1, CT WG4","lsoriginalls":"R3-216140","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109007.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109010","title":"LS from RAN WG3: Reply LS on Guidelines on Port Allocation for New 3GPP Interfaces","source":"RAN WG3","contact":"Gino Masini","contact-id":23120,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 thanks CT WG4 for the latest information and status report on the port number allocation solutions. Solutions #1-4, 8 all have varying impacts on implementations and\/or deployments, and have dependencies on the operator's infrastructure, including transport infrastructure. In general, they are not considered feasible. Solutions #3, 5 which affect the transport network layer, including SCTP, are also unfeasible. RAN WG3 prefers not to impact transport layer implementations, given that SCTP is today the basis for all RAN WG3-defined interfaces. We acknowledge the possible drawback of Solution #6, as described in Sec. 4.4.3 of TR 29.941. RAN WG3 understands that implementations are responsible for resolving any collisions. We would ask CT WG4 to keep us informed of any updates on this. RAN WG3 confirms that static port number allocation by 3GPP (Solution #6 in TR 29.941) and port allocation via OAM (Solution #7 in TR 29.941) shall be the way forward.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10390,"status":"noted","reservation_date":"2021-11-15 12:14:47","uploaded":"2021-11-15 12:15:37","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"RAN WG2, SA WG4, CT WG3, SA WG5, SA WG2, TSG SA, TSG CT, TSG RAN","lsoriginalls":"R3-216233","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109010.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109140","title":"Support of the mapping from IP addressing information provided to an AF to the user identity","source":"Nokia, Nokia Shanghai Bell, Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In this case the 5GC first needs to retrieve the Permanent identifier of the UE before trying to fulfil the AF request. The 5GC may need to determine the Permanent identifier of the UE based on: the UE address as provided by the AF, the corresponding DNN and\/or S-NSSAI information: this may have been provided by the AF or determined by the NEF using the identity of the AF;","secretary_remarks":"Revision of S2-2108412r05, merging S2-2108923. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10210,"status":"agreed","reservation_date":"2021-11-22 09:37:11","uploaded":"2021-11-23 15:21:14","revisionof":"S2-2108412","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"EDGEAPP"}],"crnumber":2385.0,"crrevision":8.0,"crcategory":"C","tsg_crp":"SP-211289","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109140.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109141","title":"AF specific UE ID retrieval","source":"Ericsson, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A new procedure is added for the AF to retrieve the AF specific GPSI (in the form of external id as defined in TS 23.003). The Event Exposure and Parameter Provisioning (targetting an individual) UE are updated to support requests with UE addressing information.","secretary_remarks":"Revision of S2-2108413r06, merging S2-2108924. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10230,"status":"agreed","reservation_date":"2021-11-22 09:37:13","uploaded":"2021-11-23 15:21:14","revisionof":"S2-2108413","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.2.1","workitem":[{"winame":"EDGEAPP"}],"crnumber":2926.0,"crrevision":4.0,"crcategory":"B","tsg_crp":"SP-211289","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109141.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109340","title":"Reply LS on creating a new stage 2 TS for SMS-SBI","source":"SA WG2","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC: CT WG1","secretary_remarks":"Created at CC#2. Response to S2-2108268. This LS 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":"2021-11-22 09:40:16","uploaded":"2021-11-23 15:31:13","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2108268","lsto":"CT WG4","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109340.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]