[{"name":"S2-2004784","title":"LS from SA WG6: LS on IP address to GPSI translation","source":"SA WG6","contact":"Nishant Gupta","contact-id":62473,"tdoctype":"LS in","for":"Action","abstract":"In the SA WG6 architecture for enabling Edge Applications, the Edge Enabler Server (EES) and the Edge Configuration Server (ECS) utilize 3GPP core network capabilities. The EES also facilitates use of 3GPP core network capability exposure by the Edge Application Servers (EAS). For this purpose, the EES, acting as trusted or untrusted application function, requires the ability to translate a UE's IP address to its GPSI. If the UE's IP address is provided by the EAS, it could be its private (i.e. non-NAT'd) IP address or public (i.e. NAT'd) IP address, in case NAT systems are employed by the 3GPP network. To SA WG2: 1. Is there a core network supported method to provide a UE's GPSI to an EAS directly? 2. Does the core network provide an API to translate a UE's IP address (private and public) to its GPSI, and if not, would it be feasible to provide such functionality in Rel-17 in order to address the SA WG6 requirement for UE IP address translation? 3. While providing the functionality requested in bullet 1, is it feasible to provide application-specific GPSIs, to ensure that a single GPSI can not be used to track an end user's activity across applications (EASs), to protect end user privacy? To SA WG3: Since the GPSI may be used by EASs to obtain sensitive information about a UE, such as its location, SA WG6 kindly asks SA WG3 to ensure that user consent is secured before providing the GPSI or any other sensitive information about the UE to an EAS. Action: SA WG6 requests SA WG2 to kindly consider the above questions and provide feedback accordingly.","secretary_remarks":"Revision of postponed S2-2004338 from S2#139E. Responses drafted in S2-2004845 and S2-2005255. Final response in S2-2005923","agenda_item_sort_order":52,"ainumber":"4.2","ainame":"Miscellaneous items","tdoc_agenda_sort_order":10810,"status":"replied to","reservation_date":"2020-08-04 05:43:45","uploaded":"2020-08-04 06:30:51","revisionof":"S2-2004338","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3","Cc":"","lsoriginalls":"S6-200947","lsreply":"S2-2005923","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004784.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004792","title":"LS from BBF: Uniqueness of FN-RG PEI for Lawful Interception purposes","source":"BBF","contact":"Lincoln Lavoie","contact-id":39231,"tdoctype":"LS in","for":"Information","abstract":"Dear colleagues, We have received the reply from SA WG2 to your LS on uniqueness of PEI in certain FN-RG configurations (S2-2003521\/ S3i200069) and would like to provide additional clarifications to the SA WG2 statements, on which we are in full agreement. We would like to highlight the reasons why, as explained by SA WG2, in the wireline context, the most appropriate parameter to identify the target of interception is the Global Line Identifier (GLI). The GLI is a unique identifier of the subscription associated with the line where the FN-BRG is connecting. The attributes forming the GLI are inserted by the W-5GAN, specifically the wireline OLT or DSLAM serving as Access Nodes, which are trusted elements in the provider's network. The inserted attributes are required to be network-wide unique per existing BBF standards, meaning each subscriber can be uniquely and unambiguously identified. BBF acknowledges that, within the context of wireline-wireless convergence, PEI has been specified in 3GPP TS 23.316 as containing the FN-BRG MAC address. This, in most cases, corresponds to the permanent MAC address configured on the RG by the manufacturer. Nevertheless, the FN-BRG MAC address should not be considered a trustable attribute for LI, as Government regulations in most countries have strict requirements on ensuring that intercept is only performed for the targeted subscriber and not mistakenly on any other subscriber that is not targeted. The FN-BRG MAC address is not assured to be unique, due to either manufacturing error, end-user spoofing, etc., and above all not in control of W-5GAN. Moreover, it should be taken onto account that, in accordance with several national regulations, the subscriber has the liberty to change its FN-BRG equipment: therefore, it cannot exist a one-to-one association between the subscriber and the MAC address he uses to connect. Finally, in view of deployments with Layer-2 FN-BRGs (a use case of interest but not yet covered by the specifications), multiple sessions may result for the same household, each with a unique MAC address. For administrative convenience and accuracy, using the GLI as the intercept identifier ensures all sessions from the same FN-BRG will be subject to LI. Having said that, we strongly recommend basing the lawful interception of a wireline target on its GLI and not on the PEI indicated in the Registration. We look forward to continuing our fruitful relationship. Thanks, Lincoln Lavoie Broadband Forum Technical Committee Chair","secretary_remarks":"Missing from Chairmans Notes. CC#4: This LS was noted.","agenda_item_sort_order":52,"ainumber":"4.2","ainame":"Miscellaneous items","tdoc_agenda_sort_order":10950,"status":"noted","reservation_date":"2020-08-04 05:43:46","uploaded":"2020-08-04 08:11:14","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3, SA WG3-LI","Cc":"CableLabs","lsoriginalls":"LIAISE-407-02","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004792.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004795","title":"LS from CT WG1: Reply LS on the applicability of 5G NAS protocol for 5G-RG and FN-RG (LIAISE-397)","source":"CT WG1","contact":"Christian Herrero-Veron","contact-id":45210,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 thanks Broadband Forum for their LS on the applicability of 5G NAS protocol for 5G-RG and FN-RG (LIAISE-397). CT WG1 is also of the opinion that wireline specific aspects should be summarized in TS 24.501. Hence, CT WG1 has updated the clause 4.7 in the Rel-16 version of the specification to include wireline aspects. In addition to this, the new clause '4.13 on Support of NAS signalling using wireline access network' aims at helping readers of the specification to understand the wireline specific aspects. CT WG1 is committed to continue enhancing clauses 4.7 and 4.13 in future versions of the specification to help readers and implementers.","secretary_remarks":"Missing from Chairmans Notes. CC#4: This LS was noted.","agenda_item_sort_order":52,"ainumber":"4.2","ainame":"Miscellaneous items","tdoc_agenda_sort_order":10960,"status":"noted","reservation_date":"2020-08-04 05:43:46","uploaded":"2020-08-04 08:11:14","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"Broadband Forum","Cc":"SA WG2","lsoriginalls":"C1-203949","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004795.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004803","title":"LS from CT WG4: LS on Bulk operation of LCS-service","source":"CT WG4","contact":"Qingfen Liu","contact-id":79904,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 has analysed the procedure of Bulk Operation of LCS Service Request targeting Multiple UEs, as specified in clause 6.8 of TS 23.273, and identified some confusions. CT WG4 would like to ask SA WG2 to clarify the following questions: 1. When using Service Based Interface (SBI), which node is expected to be the aggregation point of Bulk Operation of LCS Service, i.e. the node who resolves the group identifier to member UEs and aggregate the location requests and responses for each UE in the group, NEF or GMLC or both? 2. If the GMLC is expected to be the aggregation point of Bulk Operation of LCS Service, what should the GMLC respond for a request of bulk operation, especially for 5GC_MT_LR procedure? NOTE: CT WG4 observed that if NEF sends a 5GC-MT-LR request towards GMLC for group of UEs, there is no way for GMLC to relay the multiple responses (one per UE) to the NEF, using current service operations specified in TS 23.273 (Only one service response is allowed per service request in SBI and location for one UE is allowed in Ngmlc_Location_ProvideLocation response). 3. If used as aggregation point, when does the GMLC \/ NEF acknowledge the request for Bulk Operation, i.e. does it respond the LCS client \/ AF after it received all positioning responses from network side for all UEs in the group or respond without AMF checking? 4. If GMLC \/ NEF responds the LCS client \/ AF immediately, based on what criterion does the GMLC \/ NEF decide to respond success or failure or partial success? And How should GMLC \/ NEF to notify the LCS Client \/ AF if the requests for positioning for some UEs fail because of some different reasons (e.g. The UE is not online) after GMLC \/ NEF responded success to LCS client \/ AF?. Action: CT WG4 kindly requests SA WG2 to clarify above questions.","secretary_remarks":"Responses drafted in S2-2004897, S2-2005039 and S2-2005676. Final response in S2-2005921","agenda_item_sort_order":52,"ainumber":"4.2","ainame":"Miscellaneous items","tdoc_agenda_sort_order":10890,"status":"replied to","reservation_date":"2020-08-04 05:43:46","uploaded":"2020-08-04 08:11:14","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG3","lsoriginalls":"C4-203629","lsreply":"S2-2005921","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004803.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004841","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 only be able to identify an UE target of an AF request for data provisioning or for Event exposure (information retrieval about a UE) by providing IP addressing information (IP address and port information) about this UE. In t","secretary_remarks":"Postponed","agenda_item_sort_order":52,"ainumber":"4.2","ainame":"Miscellaneous items","tdoc_agenda_sort_order":10840,"status":"postponed","reservation_date":"2020-08-08 16:19:21","uploaded":"2020-08-13 08:04:47","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"16.5.1","workitem":[{"winame":"EDGEAPP"}],"crnumber":2385.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004841.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004842","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 IP addressing information (IP address and port) of the UE. In this case the 5GC first nee","secretary_remarks":"Noted","agenda_item_sort_order":52,"ainumber":"4.2","ainame":"Miscellaneous items","tdoc_agenda_sort_order":10850,"status":"noted","reservation_date":"2020-08-08 16:19:24","uploaded":"2020-08-13 08:04:47","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"16.5.1","workitem":[{"winame":"EDGEAPP"}],"crnumber":2329.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004842.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004845","title":"[DRAFT] LS on IP address to GPSI translation","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"LS on IP address to GPSI translation","secretary_remarks":"Response to S2-2004784. r09 agreed. Revised, merging S2-2005255, to S2-2005923.","agenda_item_sort_order":52,"ainumber":"4.2","ainame":"Miscellaneous items","tdoc_agenda_sort_order":10820,"status":"revised","reservation_date":"2020-08-08 16:19:27","uploaded":"2020-08-13 08:04:47","revisionof":"","revisedto":"S2-2005923","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"EDGEAPP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6, SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004845.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004897","title":"[DRAFT] LS Response on Bulk operation of LCS-service","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Response to LS from CT WG4 on Bulk operation of LCS-service","secretary_remarks":"Response to S2-2004803. CC#3: S2 2004897R04 was reviewed and agreed. This was revised to clean up, merging S2-2005039 and S2-2005676, in S2-2005921","agenda_item_sort_order":52,"ainumber":"4.2","ainame":"Miscellaneous items","tdoc_agenda_sort_order":10920,"status":"revised","reservation_date":"2020-08-10 20:07:14","uploaded":"2020-08-13 19:24:46","revisionof":"","revisedto":"S2-2005921","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004897.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2005039","title":"[DRAFT] LS Reply on Bulk operation of LCS-service","source":"Nokia, Nokia Shanghai Bell","contact":"Pallab Gupta","contact-id":87959,"tdoctype":"LS out","for":"Approval","abstract":"LS Reply on Bulk operation of LCS-service","secretary_remarks":"Response to S2-2004803. Merged into S2-2005921","agenda_item_sort_order":52,"ainumber":"4.2","ainame":"Miscellaneous items","tdoc_agenda_sort_order":10900,"status":"merged","reservation_date":"2020-08-12 10:51:53","uploaded":"2020-08-13 15:46:21","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005039.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2005255","title":"[DRAFT] Reply LS on IP address to GPSI translation","source":"China Mobile","contact":"Dan Wang","contact-id":87155,"tdoctype":"LS out","for":"Approval","abstract":"[Draft] Reply LS on IP address to GPSI translation","secretary_remarks":"Response to S2-2004784 Merged into S2-2005923","agenda_item_sort_order":52,"ainumber":"4.2","ainame":"Miscellaneous items","tdoc_agenda_sort_order":10860,"status":"merged","reservation_date":"2020-08-13 03:40:29","uploaded":"2020-08-13 12:58:27","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005255.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2005499","title":"Further corrections to SGC handling","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) UE with running SGC timer is not to set the active flag\/signalling active flag at TAU except in case of regulatory prioritized services. 2) UE not to start SGC timer after TAU in case of regulatory prioritized services","secretary_remarks":"r01 agreed. Revised to S2-2005924.","agenda_item_sort_order":52,"ainumber":"4.2","ainame":"Miscellaneous items","tdoc_agenda_sort_order":10870,"status":"revised","reservation_date":"2020-08-13 10:24:08","uploaded":"2020-08-13 13:35:30","revisionof":"","revisedto":"S2-2005924","release":"Rel-16","crspec":"23.401","crspecversion":"16.7.0","workitem":[{"winame":"TEI16"}],"crnumber":3611.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005499.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2005676","title":"[DRAFT] LS on Bulk operation of LCS-service","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"The LS provides feedback to CT WG4 questions","secretary_remarks":"Response to S2-2004803. Merged into S2-2005921","agenda_item_sort_order":52,"ainumber":"4.2","ainame":"Miscellaneous items","tdoc_agenda_sort_order":10910,"status":"merged","reservation_date":"2020-08-13 13:34:42","uploaded":"2020-08-13 14:50:40","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005676.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2005876","title":"LS from SA WG5: LS on dynamic 5QIs","source":"SA WG5","contact":"Yizhi Yao","contact-id":66963,"tdoctype":"LS in","for":"Action","abstract":"SA WG5 has been defining performance measurements (in TS 28.552) and KPIs (in TS 28.554) with subcounters for monitoring the 5G network performance for each 5QI, and each subcounter is identified by the corresponding 5QI value. In order to evaluate the network performance pertinent to a 5QI, OAM needs to know the QoS characteristic of the 5QI. The characteristics of standardized 5QIs and preconfigured 5QIs are already known by OAM, and SA WG5 is working on the solutions enabling OAM to get the QoS characteristic of dynamic 5QIs. SA WG5 has the following questions with regards to the dynamic 5QIs. Q1: whether the same 'dynamic 5QI' value may be used to represent different 5QI characteristics for different UEs in the same Network Function? Q2: whether the same 'dynamic 5QI' value may be used to represent different 5QI characteristics over time. I.e. what is the scope of persistency for the 'dynamic 5QI' value?. Action: SA WG5 respectfully requests SA WG2 to answer the questions mentioned above.","secretary_remarks":"CC#3: Response drafted in S2-2005920. Postponed","agenda_item_sort_order":52,"ainumber":"4.2","ainame":"Miscellaneous items","tdoc_agenda_sort_order":10790,"status":"postponed","reservation_date":"2020-08-25 04:45:52","uploaded":"2020-08-25 04:46:42","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"S5-204443","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005876.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2005917","title":"LS on 5G RG that support MA PDU Session","source":"SA WG2","contact":"Laurent Thiebaut","contact-id":72921,"tdoctype":"LS out","for":"Approval","abstract":"To: BBF","secretary_remarks":"Generated during CC#3. Approved","agenda_item_sort_order":52,"ainumber":"4.2","ainame":"Miscellaneous items","tdoc_agenda_sort_order":10940,"status":"approved","reservation_date":"2020-08-31 14:28:37","uploaded":"2020-08-31 14:29:39","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"BBF","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005917.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2005920","title":"Reply LS on dynamic 5QIs","source":"Intel","contact":"Saso Stojanovski","contact-id":56758,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG5","secretary_remarks":"Generated during CC#3. Response to S2-2005876. Postponed","agenda_item_sort_order":52,"ainumber":"4.2","ainame":"Miscellaneous items","tdoc_agenda_sort_order":10800,"status":"postponed","reservation_date":"2020-09-03 04:31:20","uploaded":"2020-09-03 14:51:12","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005920.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2005921","title":"LS Response on Bulk operation of LCS-service","source":"SA WG2","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC: CT WG3","secretary_remarks":"Revision R04 of S2-2004897, merging S2-2005039 and S2-2005676. Approved","agenda_item_sort_order":52,"ainumber":"4.2","ainame":"Miscellaneous items","tdoc_agenda_sort_order":10930,"status":"approved","reservation_date":"2020-08-31 14:28:37","uploaded":"2020-08-31 14:29:39","revisionof":"S2-2004897","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2004803","lsto":"CT WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005921.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2005923","title":"LS on IP address to GPSI translation","source":"SA WG2","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG6. CC: SA WG3","secretary_remarks":"Revision r09 of S2-2004845., merging S2-2005255. Approved","agenda_item_sort_order":52,"ainumber":"4.2","ainame":"Miscellaneous items","tdoc_agenda_sort_order":10830,"status":"approved","reservation_date":"2020-09-03 04:31:21","uploaded":"2020-09-03 14:51:12","revisionof":"S2-2004845","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"EDGEAPP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2004784","lsto":"SA WG6, SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005923.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2005924","title":"Further corrections to SGC handling","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) UE with running SGC timer is not to set the active flag\/signalling active flag at TAU except in case of regulatory prioritized services. 2) UE not to start SGC timer after TAU in case of regulatory prioritized services","secretary_remarks":"Revision r01 of S2-2005499. Approved","agenda_item_sort_order":52,"ainumber":"4.2","ainame":"Miscellaneous items","tdoc_agenda_sort_order":10880,"status":"agreed","reservation_date":"2020-09-03 04:31:21","uploaded":"2020-09-03 14:51:12","revisionof":"S2-2005499","revisedto":"","release":"Rel-16","crspec":"23.401","crspecversion":"16.7.0","workitem":[{"winame":"TEI16"}],"crnumber":3611.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200686","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005924.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006778","title":"LS from RAN WG2: Reply LS on early UE capability retrieval for eMTC","source":"RAN WG2","contact":"Veera Prasada Kadiri","contact-id":72325,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 thanks SA WG2 for their reply LS confirming that SA WG2 has not identified any technical issues to support early UE capability retrieval for eMTC UEs for EPS from system architecture perspective. RAN WG2 discussed the concerns raised by SA WG2 for 5GS and would like to provide the responses as follows: SA WG2 LS indicated: - Concerns to enable use of truncated 5G-S-TMSI for all UEs accessing ng-eNBs connected to 5GC as this would reduce the available AMF Set ID number space, AMF Pointer number space and TMSI number space (due to truncation) for all UEs. RAN WG2 response: RAN WG2 has a potential solution to identify in Msg3 to include InitialUE-Identity-5GC which enables ng-eNB to differentiate between BL UEs and non-BL UEs in CE mode. Such solution would allow AMF to allocate 40-bit truncated 5G-S-TMSI only for BL UEs. SA WG2 LS indicated: - Concerns about truncated 5G-S-TMSIs being used, with no additional checks, to retrieve the UE capabilities for all UEs and the high levels of coordination required between operators in RAN sharing cases for eMTC UEs using CP optimisations. - Concerns about introducing to EPS capabilities that are not supported by 5GS, or no clear path exists for its addition to 5GS. RAN WG2 thinks the above two concerns are out of RAN WG2 scope and up to SA WG2 to address. Action: RAN WG2 respectfully asks SA WG2 to take above response into consideration.","secretary_remarks":"Postponed","agenda_item_sort_order":52,"ainumber":"4.2","ainame":"Miscellaneous items","tdoc_agenda_sort_order":10780,"status":"postponed","reservation_date":"2020-08-26 19:22:45","uploaded":"2020-08-26 19:24:27","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG3, CT WG1","lsoriginalls":"R2-2008238","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2006778.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006779","title":"LS from SA WG5: LS on New function for Network Slice PA and Management Charging","source":"SA WG5","contact":"SHAN CHEN","contact-id":47584,"tdoctype":"LS in","for":"Action","abstract":"SA WG5 would like to inform SA WG2 that a new function, CEF (Charging Enablement Function), has been specified to the Charging Architecture in Rel-16. The CEF (Charging Enablement Function) is specified to consume NWDAF and MnS services for the purpose of Network Slice Performance and Analytics Charging and to consume MnS services for the purpose of Network Slice Management charging as follow: - Network Data Analytics service (Nnwdaf) exposed by the Network Data Analytics Function (NWDAF), as described in TS 23.288 are subscribed to by CEF for performance and analytics information. - Network Slice Management service (MnS) exposed by the Management Service (MnS), as described in TS 28.532 are subscribed to by CEF for network slice configuration, performance and analytics information. Action: SA WG5 kindly asks SA WG2 to take into account the CEF as the consumer of NWDAF.","secretary_remarks":"CC#4: This LS was missing from Chairman's notes and was postponed.","agenda_item_sort_order":52,"ainumber":"4.2","ainame":"Miscellaneous items","tdoc_agenda_sort_order":10970,"status":"postponed","reservation_date":"2020-08-28 14:49:27","uploaded":"2020-08-28 14:49:49","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"S5-204593","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2006779.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]