[{"name":"S2-2006782","title":"LS from SA WG3LI: LS on Location information for SMS over IMS","source":"SA WG3LI","contact":"Maurizio Iovieno","contact-id":23687,"tdoctype":"LS in","for":"Action","abstract":"LI requirements include the need for the operator to provide target's location information as part of intercepted signaling, when required by the LI warrant. With reference to SMS over IMS, SA WG3-LI would expect that, whenever an IMS user sends or receives a SMS over IMS, the CSCFs include the Network Provided Location Information (NPLI) in the PANI header (or equivalent functionalities), in addition to any possible user provided location information, for possible use by the LI functions in the operator network in case the user is a LI target. Location information is required to be the location when the SMS is sent\/received by the user. The requirement is applicable to both non-roaming and roaming scenarios. In order to ensure LI undetectability, this needs to be done for all users, no matter whether they are LI target. Looking at IMS Core Network specifications, it was however unclear to SA WG3-LI whether the needed capabilities, i.e. the inclusion of a NPLI in the PANI header when SMS over IMS are handled, are currently supported. Action: SA WG3-LI asks SA WG2 to provide feedback on the availability of location information at CSCFs when any IMS user sends or receives SMS over IMS and, if seen needed, to update their specifications in order to ensure that LI requirements on location information for LI of SMS over IMS are fulfilled.","secretary_remarks":"Revision of postponed S2-2004771 from S2#140E. Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10040,"status":"postponed","reservation_date":"2020-09-22 08:22:49","uploaded":"2020-09-22 09:22:30","revisionof":"S2-2004771","revisedto":"S2-2008329","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1, CT WG3, SA WG3","lsoriginalls":"S3i200161","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006782.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006786","title":"LS from 5G-ACIA (5G Alliance for Connected Industries and Automation): 5G capabilities exposure for factories of the future","source":"5G-ACIA","contact":"Andreas Mueller","contact-id":81087,"tdoctype":"LS in","for":"Information","abstract":"Over the last two years, 5G-ACIA has collected and analysed many industrial use cases. These use cases - as well as inferred communication service characteristics - have been documented by 3GPP in TS 22.104 and TS 22.261. 5G-ACIA has further refined and analysed operational use cases that are needed by factory operators to manage and maintain 5G-enabled devices and 5G Non-Public Networks (NPN) in a simple and efficient manner. 5G-ACIA believes the service exposure requirements derived from the aforementioned operational use cases are valuable input for upcoming contributions addressing ongoing work in 3GPP, such as the study items documented in TR 23.700 and TR 23.745. These requirements have been published in the 5G-ACIA white paper Exposure of 5G capabilities for connected industries and automation applications (www.5g-acia.org\/publications), which is also attached to this LS. This white paper focuses on operational use cases pertaining to device management, for example use cases that enable factory operators to manage the life cycle of devices, and e.g. to change and monitor the devices' connectivity. In order to execute these operational use cases efficiently, the industrial systems require a set of well standardised and published APIs that hide a great deal of 3GPP complexity and yet provide the needed flexibility to the factory operator. These capabilities are needed by factories of the future and expected from 5G NPN and 5G-enabled devices. 5G-ACIA would like to highlight the importance of these refined requirements for industrial operations and would appreciate it very much, if 3GPP considered the provided information to ongoing and upcoming specification work. 5G-ACIA would be eager to receive 3GPP's feedback on these new exposure interface requirements and related Stage-2 and Stage-3 work.","secretary_remarks":"Revision of postponed S2-2004788 from S2#140E. Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10030,"status":"noted","reservation_date":"2020-09-22 08:22:50","uploaded":"2020-09-22 09:22:30","revisionof":"S2-2004788","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG1, SA WG2, SA WG3, SA WG5, SA WG6, CT WG3, IEC TC 65, oneM2M TP, OPC Foundation, PI, IEEE TSN, TM Forum, ETG","lsoriginalls":"5G-ACIA_ LS_3GPP_Exposure_29062020","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006786.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006787","title":"LS from CT WG1: LS on mandate to provide any PLMN entry in the non-3GPP access node selection information","source":"CT WG1","contact":"John-Luc Bakker","contact-id":37326,"tdoctype":"LS in","for":"Action","abstract":"Some companies in CT WG1 have discussed the requirement that mandates the inclusion of the 'any PLMN' entry in the non-3GPP access node selection information (TS 23.501, clause 6.3.6). The equivalent of the 'any PLMN' entry in the ePDG selection information is optional (see TS 23.402). According to the N3IWF selection procedure described in clause 6.3.6 of TS 23.501, a mandatory inclusion of the 'any PLMN' entry in the N3AN selection information makes impossible some roaming scenarios involving HPLMN's non-3GPP access (e.g. the scenarios presented in Figures 4.2.8.2.2-2 and 4.2.8.2.3-3 of TS 23.501). An example of conditions where a roaming scenario involving HPLMN's non-3GPP access would be impossible: - N3AN node selection for IMS service is performed; - the UE is not located in its home country; - the UE registered to 5GC of a VPLMN X over 3GPP access; and - the N3AN node configuration information is provisioned; - an N3AN node selection information entry for the VPLMN X is absent in the N3AN node selection information of the N3AN node configuration information; - the DNS server function is able to resolve N3IWF FQDN or ePDG FQDN constructed according to the 'Any_PLMN' N3AN node selection information entry of the N3AN node configuration information. For such scenarios, unless selection of the N3IWF or ePDG in the visited country is required, using the HPLMN's non-3GPP access node should be enabled and controlled by the HPLMN's policy. The HPLMN's policy could be expressed by absence of the 'Any_PLMN' N3AN node selection information entry of the N3AN node configuration information. Action: CT WG1 asks SA WG2 group to clarify the purpose of the mandatory presence of the 'any PLMN' entry in the non-3GPP access node selection information.","secretary_remarks":"Revision of postponed S2-2004796 from S2#140E. Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10070,"status":"postponed","reservation_date":"2020-09-22 08:22:50","uploaded":"2020-09-22 09:22:30","revisionof":"S2-2004796","revisedto":"S2-2008331","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C1-204034","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006787.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006789","title":"LS from CT WG1: LS on maximum number of UP resources supported by NB-N1 mode UEs","source":"CT WG1","contact":"Mahmoud Watfa","contact-id":85785,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 would like to inform SA WG2 about the following agreements (see attachments) for UEs in NB-N1 mode: 1) Since the same lower layers are used as in NB-S1 mode, the UE indicates to the AMF whether it supports multiple UP resources (i.e. at most 2) in the 5GMM capability IE. 2) The UE and AMF enforce a maximum number of UP resources (i.e. 1 or 2) that can be active at any time based on the UE's capability as per the above. Action: CT WG1 respectfully asks SA WG2 to take the above information into account and update their specifications as needed.","secretary_remarks":"Revision of postponed S2-2004798 from S2#140E. Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10050,"status":"postponed","reservation_date":"2020-09-22 08:22:50","uploaded":"2020-09-22 09:22:30","revisionof":"S2-2004798","revisedto":"S2-2008332","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C1-204083","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006789.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006794","title":"LS from SA WG5: LS on SA5 Rel-17 work on SLA","source":"SA WG5","contact":"Xiaonan Shi","contact-id":83457,"tdoctype":"LS in","for":"Action","abstract":"SA WG5 has cooperated with GSMA 5GJA on implementing NG.116 (v2.0) GST SLA attributes as network slice ServiceProfile attributes in the 3GPP Network Resource Model (NRM) (TS 28.541 clauses 6.3.3, 6.4.1) in the Rel-16 work item Management Aspects of 5G Service-Level Agreement. This work item has been finalised in Rel 16, and a continuing Rel-17 work item Enhancement of Management Aspects of 5G Service-Level Agreement (SP-200190) has been approved. In Rel-17, SA WG5 will continue working on implementing updated GST SLA attributes, as GSMA 5GJA will continue working on NG.116. In addition, SA WG5 will work on breaking down SLA requirements to NetworkSliceSubnet to update the SliceProfile in the 3GPP NRM, which can provide clear requirements to CN, RAN and TN (TS 28.541 clauses 6.3.4, 6.4.1). Action: SA WG5 respectfully requests SA WG2 to take this information into account and provide feedback, if necessary.","secretary_remarks":"Revision of postponed S2-2004812 from S2#140E. Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10060,"status":"noted","reservation_date":"2020-09-22 08:22:50","uploaded":"2020-09-22 09:22:30","revisionof":"S2-2004812","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA 5GJA, SA WG2, RAN WG3, IETF TEAS WG","Cc":"TSG SA, SA WG1, SA WG6, RAN WG2, ETSI ISG ZSM","lsoriginalls":"S5-203370","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006794.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006798","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":"Revision of postponed S2-2005876 from S2#140E. Response drafted in S2-2006930. Final response in S2-2006930","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10110,"status":"replied to","reservation_date":"2020-09-22 08:22:50","uploaded":"2020-09-22 09:22:30","revisionof":"S2-2005876","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"S5-204443","lsreply":"S2-2006930","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006798.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006802","title":"LS on the stage 2 aspects of MINT","source":"CT WG1","contact":"Sang Min Park","contact-id":62105,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 has discussed a WID proposal for CT aspects of Minimization of Service Interruption (MINT-CT) in the CT WG August meetings, in order to support the service requirements specified for Rel-17. The WID on MINT-CT includes a study phase on both stage-2 and stage-3 aspects. CT WG1 is also planning to define end-to-end call flow regarding registration after selection of a disaster roaming PLMN in the stage-2 specification owned by CT WG1. CT WG1 would like to ask TSG SA if there is any concern on this approach. CT WG1 expects any feedback on this way forward until the next WG meeting so that both study phase and normative phase can progress within Rel-17 timeframe. Action: CT WG1 kindly asks TSG SA to take the information above into account and to provide feedback.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10300,"status":"noted","reservation_date":"2020-09-22 08:22:50","uploaded":"2020-09-22 15:39:21","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"CT WG4, CT WG3, SA WG3, SA WG2, TSG CT","lsoriginalls":"C1-205332","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006802.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006803","title":"LS on mandatory support of full rate user plane integrity protection for 5G","source":"CT WG1","contact":"Lena Chaponniere","contact-id":38080,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 thanks SA for their LS on mandatory support of full rate user plane integrity protection for 5G. CT WG1 would like to inform SA that CT WG1 fulfilled SA's request to mandate UE support of full rate user plane integrity protection for architecture option 2 in Release 16 via the agreement of the attached Release 16 CR. Regarding support of full rate user plane integrity protection for other architecture options in Release 17, CT WG1 expects SA WG3 to take the lead on specifying solutions for other architecture options and will update their specification after SA WG3 agrees normative requirements.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10310,"status":"noted","reservation_date":"2020-09-22 08:22:50","uploaded":"2020-09-22 15:39:21","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"TSG CT, TSG RAN, RAN WG3, RAN WG2, SA WG3, SA WG2","lsoriginalls":"C1-205392","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006803.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006804","title":"LS from CT WG1#125e: LS on Media Feature Tag for IMS Data Channel","source":"CT WG1","contact":"J\u00f6rgen Axell","contact-id":36534,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 thanks SA WG4 for the incoming LS in S4-200906\/C1-204650 on Media Feature Tag for IMS Data Channel. TS 24.229 is as SA WG4 points out service agnostic and specifies general support for IMS features. CT WG1 thus finds it appropriate that SA WG4 documents the values of the media feature tags they need. Since the procedures in TS 24.229 this far only referenced RFC 3840 related to the streaming media types, CT WG1 has clarified TS 24.229 in the attached agreed rel-17 CR. The new media feature tag is already supported in the annex A profile tables. The CR clarifies the procedures.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10320,"status":"noted","reservation_date":"2020-09-22 08:22:50","uploaded":"2020-09-22 15:39:21","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3, SA WG4","Cc":"SA WG2","lsoriginalls":"C1-205509","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006804.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006805","title":"LS from CT WG3#111e: LS Reply on Media Feature Tag for IMS Data Channel","source":"CT WG3","contact":"Nevenka Biondic","contact-id":41878,"tdoctype":"LS in","for":"Information","abstract":"CT WG3 would like to thank SA WG4 for sending the 'LS on Media Feature Tag for IMS Data Channel' in S4-200908 (\/C3-204021). CT WG3 has discussed the LS and would like to inform SA WG4 that CT WG3 has not identified any impact in CT WG3 specifications.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10330,"status":"noted","reservation_date":"2020-09-22 08:22:50","uploaded":"2020-09-22 15:39:21","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"CT WG1, SA WG2","lsoriginalls":"C3-204168","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006805.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006806","title":"LS from CT WG4: LS on AUSF\/UDM discovery based on SUCI information","source":"CT WG4","contact":"Yue Song","contact-id":57977,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 has analyzed the issue of insufficient length of Routing Indicator within SUCI, see attached discussion paper in C4-204078 for details. The current 4 digits of the Routing Indicator enables only 10 K ranges of subscriptions, which may not provide enough granularity and flexibility for moving subscriptions across UDRs not controlled by the same AUSF\/UDM, for operators with a large number of subscriptions (e.g. 100 K users per range for a PLMN with 1 billion subscriptions). CT WG4 agreed that the above limitation should be addressed. CT WG4 has also discussed the solution proposed in C4-204339 (attached) for solving this problem, enabling to use the Home Public Key ID as an additional parameter (that allows to encode e.g. a 5th digit, in addition to the key ID on 4 bits) for the discovery of the AUSF\/UDM. CT WG4 would be fine in principle to specify this solution in Rel-17, provided corresponding stage-2 requirements are agreed first. Action: CT WG4 kindly asks SA WG2 to consider specifying stage 2 enhancements for selection of AUSF\/UDM based on SUCI in Rel-17 to address the reported issue.","secretary_remarks":"Response drafted in S2-2006906. Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10130,"status":"postponed","reservation_date":"2020-09-22 08:22:50","uploaded":"2020-09-22 15:39:21","revisionof":"","revisedto":"S2-2008337","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"TSG CT, TSG SA, SA WG3","lsoriginalls":"C4-204337","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006806.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006810","title":"LS from RAN WG1: LS on Latency of NR Positioning Protocols","source":"RAN WG1","contact":"Alexey Khoryaev","contact-id":46112,"tdoctype":"LS in","for":"Information","abstract":"RAN WG1 evaluates physical layer latency and its potential reduction for NR Rel-17 positioning solutions. In order to evaluate End-To-End latency of NR positioning solutions the input from RAN WG2 is needed on latency components of NR\/NG-RAN\/5GC higher layer positioning protocols. RAN WG1 respectfully asks if RAN WG2 can provide a list of latency components with corresponding range of values for the existing and any potential enhanced NR positioning solutions, keeping in mind the End-To-End latency described as desired in the study item description (RP-200928)","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10340,"status":"noted","reservation_date":"2020-09-22 08:22:50","uploaded":"2020-09-22 15:39:21","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"RAN WG3, SA WG2","lsoriginalls":"R1-2007264","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006810.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006813","title":"LS from RAN WG2: Response LS to TSG SA on mandatory support of full rate user plane integrity protection for 5G","source":"RAN WG2","contact":"Axel Klatt","contact-id":20567,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 would like to thank TSG SA#88-e for their LS on 'mandatory support of full rate user plane integrity protection for 5G' [SP-200617] and the decision for which architecture options the requirement shall apply from Rel-16 onwards. RAN WG2 has discussed the request from SA#88-e and concluded that the requirement shall apply for NR connected to 5GC (aka Architecture Option 2) and further that it applies for NR-DC (handled in RAN terminology under the MR-DC framework), which has no explicit 'Option notation'. As RAN WG2 concluded based on company input that NR-DC would absolutely make sense considering the request from SA and the technical challenges are negligible once the UE implemented support for full rate UPIP for SA Option 2; based on this technical analysis RAN WG2 also decided to apply the mandatory full rate UPIP for NE-DC with MN terminated bearers as technically this is similar to NR-DC and covered in RAN WG2 already under the MR-DC framework. NE-DC with SN terminated bearers (i.e. in the eNB) should be subject to the further work in SA WG3 for Rel-17 and should consequently being covered in their new WI. RAN WG2 agreed during it's RAN WG2#111e meeting two CRs to reflect the UE requirements for Rel-16 in TS 38.300 [R2-2008513] and TS 37.340 [R2-2008639]. Regarding the addition of NE-DC with MN terminated bearers into the agreement, RAN WG2 would like to advise CT WG1 and SA WG2 to check their related changes to their specifications for any cross-WG inconsistency. To conclude corresponding work for other Architecture options in Rel-17, RAN WG2 will wait for the outcome of the discussions in SA WG3, looking forward receiving related requirements. Action: RAN WG2 asks TSG SA, CT WG1, SA WG2, SA WG3, TSG RAN and TSG CT to take the decisions above of RAN WG2 into account and note that the request by SA#88e has been accomplished for Rel-16. It should be especially noted that based on the discussions in RAN#111e NR-DC and NE-DC with MN terminated bearers are also already part of the agreement in RAN WG2. RAN WG2 asks TSG RAN to finally approve the related CRs as part of the normal approval process. RAN WG2 also would like to inform CT WG1 and SA WG2 about the agreed CRs and would like to advice CT WG1 and SA WG2 to check their related changes to their specifications for any cross-WG inconsistency.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10190,"status":"noted","reservation_date":"2020-09-22 08:22:50","uploaded":"2020-09-22 15:39:21","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, CT WG1, SA WG2, SA WG3, TSG CT, TSG RAN","Cc":"RAN WG3","lsoriginalls":"R2-2008643","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006813.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006814","title":"LS from RAN WG3: New service type of NR QoE","source":"RAN WG3","contact":"Dapeng Li","contact-id":79887,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 has discussed the support for various service types in Application Layer Measurement Collection and reporting for NR QOE and agreed to support the following service types: Streaming video in TS 26.247, VR in TS 26.118, MTSI in TS 26.114 and MBMS in TS 26.346. In addition, RAN WG3 agreed to consider the NR QoE management support for service type(s) related to URLLC in addition to VR. The exact URLLC service types supported in NR QoE management are FFS in RAN WG3.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10350,"status":"noted","reservation_date":"2020-09-22 08:22:50","uploaded":"2020-09-22 15:39:21","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"RAN WG2, SA WG5, SA WG2","lsoriginalls":"R3-205724","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006814.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006818","title":"LS from SA WG1: Reply LS on human-readable network name (HRNN)","source":"SA WG1","contact":"Adrian Buckley","contact-id":81014,"tdoctype":"LS in","for":"Action","abstract":"SA WG1 would like to thank CT on their LS (CP-201361\/S1-203197) and would like to provide the following answers. Question-1) Are there stage-1 requirements for a UE to obtain a human-readable network name for the manual NPN selection using means other than the system information broadcast? Answer from SA WG1: No. To clarify, there are currently no stage-1 requirements related to human-readable network name for the manual NPN selection. At this meeting, SA WG1 has agreed the attached CR (from Rel-16 onward) adding a new requirement on HRNN broadcasting, aligned with current stage2\/3 specs. Question-2) If the answer to Question-1 is yes, what is the precedence between the human-readable network name obtained via other means and the human-readable network name obtained from the system information broadcast? Answer from SA WG1: N\/A SA WG1 may consider further alignment gaps, or potential new requirements in a future release. Action: Please take into account the answers to the above 2 questions.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10220,"status":"noted","reservation_date":"2020-09-22 08:22:51","uploaded":"2020-09-22 15:39:21","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, TSG CT, CT WG1, RAN WG2","Cc":"CT WG4","lsoriginalls":"S1-203272","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006818.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006820","title":"LS from SA WG3: LS reply on AMF reallocation via RAN re-routing","source":"SA WG3","contact":"Juan Deng","contact-id":69910,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 thanks SA WG2 for the LS (S2-2001730) on AMF reallocation via RAN re-routing. SA WG3 has not been able to reach an agreement on the solutions proposed in SA WG2 and SA WG3 to solve the issues with the AMF reallocation via RAN re-routing. SA WG3 will continue discussing the issue and inform SA WG2 on agreed result. Action: SA WG3 kindly asks SA WG2 to take the above information into account.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10230,"status":"noted","reservation_date":"2020-09-22 08:22:51","uploaded":"2020-09-22 15:39:21","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"S3-201862","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006820.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006821","title":"LS from SA WG3: Reply LS on Reply PAP\/CHAP and other point-to-point protocols usage in 5GS","source":"SA WG3","contact":"Alf Zugenmaier","contact-id":52494,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 would like to thank SA WG2 for their LS Reply PAP\/CHAP and other point-to-point protocols usage in 5GS (S3-201509\/S2-2004481). SA WG3 would like to make the following observations: - EAP based secondary authentication in 5GS is a replacement for PAP\/CHAP in EPC. Therefore SA WG3 recommends use of secondary authentication instead of PAP\/CHAP using ePCO unless there are legacy applications requiring it. - PAP is outdated and should not be used any more (RFC 1334 (PAP) has been obsoleted by RFC 1994). Therefore, the warning should be in any 5G spec referring to PAP as well. - CHAP also comes with disadvantages, such as being amenable to brute force attacks if the password is guessable. - It is up to the external network operator to perform the risk assessment if PAP\/CHAP is used for authentication. Action: SA WG3 kindly asks SA WG2, CT WG1 and CT WG3 to take the above into consideration.","secretary_remarks":"Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10240,"status":"postponed","reservation_date":"2020-09-22 08:22:51","uploaded":"2020-09-22 15:39:21","revisionof":"","revisedto":"S2-2008339","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1, CT WG3","Cc":"CT WG4","lsoriginalls":"S3-202190","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006821.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006822","title":"LS from SA WG3: LS on Reference point interface names for AKMA","source":"SA WG3","contact":"Vlasios Tsiatsis","contact-id":76181,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 has defined the architecture and procedures of a new feature called Authentication and Key Management for Application using 3GPP Credentials (AKMA) in 3GPP TS 33.535. AKMA introduces a new a network function called the AKMA Anchor Function (AAnF) which interacts with an AKMA Application Function (AF in the architecture). As part of the architecture specification, reference point architecture and interfaces are introduced in the attached proposed CR S3-202038 in SA WG3#100-e. The architecture includes the following reference point interfaces with the tentatively proposed interface names: NA1: Reference point between the AKMA Anchor Function (AAnF) and the AUSF. NA2: Reference point between the AAnF and an internal AF. NA3: Reference point between the AAnF and the NEF. SA WG3 would like SA WG2 to confirm that the tentatively proposed interface names could be used in the TS 33.535 specification. Action: SA WG3 kindly requests SA WG2 to take the above into account and provide feedback.","secretary_remarks":"Response drafted in S2-2006932. Final response in S2-2008003","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10250,"status":"replied to","reservation_date":"2020-09-22 08:22:51","uploaded":"2020-09-22 15:39:21","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"S3-202250","lsreply":"S2-2008003","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006822.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006823","title":"LS from SA WG5: Reply LS on application registration in relation to mgmt aspects","source":"SA WG5","contact":"Deepanshu Gautam","contact-id":81664,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks SA WG6 for the LS on 'application registration in relation to mgmt aspects' and looking forward for further collaboration. SA WG5 is of opinion that similar information, with probable additions, present in EAS Profile will be made available to the management system at the time of initial provisioning\/deployment of EAS. However, whether such information is only provided by the management plane and not to be supplied during EAS registration is up to the SA WG6 architecture and the use cases. SA WG5 would like to inform SA WG6 that the work on FS_eEDGE_Mgt has started where SA WG5 would like to study this aspect further and will be sharing the details as appropriate.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10360,"status":"noted","reservation_date":"2020-09-22 08:22:51","uploaded":"2020-09-22 15:39:21","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"SA WG2","lsoriginalls":"S5-204117","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006823.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006824","title":"LS from : Reply LS to ETSI ISG ENI on mapping between ENI architecture and NWDAF\/MDAF","source":"SA WG5","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks ETSI ISG ENI for the liaison and would like to ask few further questions regarding ENI","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10370,"status":"noted","reservation_date":"2020-09-22 08:22:51","uploaded":"2020-09-22 15:39:21","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI ISG ENI","Cc":"SA WG2","lsoriginalls":"S5-204440","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006824.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006825","title":"LS from SA WG5: Reply LS from SA5 to GSMA on NG.116 support of different access types","source":"SA WG5","contact":"Kai Zhang","contact-id":66365,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to thank GSMA 5GJA for their LS on NG.116 support of different access types. To align with NG.116v2.0 in which the GST attribute 'supportedAccessTech' has been removed, SA WG5#132e has agreed a CR, awaiting SA#89 plenary approval in September, to delete the obsolete attribute 'supportedAccessTech' from 3GPP Network Resource Model (NRM) ServiceProfile in 3GPP TS 28.541. SA WG5 has also introduced NB-IoT support in the ServiceProfile to support the GST attribute 'NB-IoT Support' which describes whether NB-IoT is supported in the RAN in the network slice. If the future versions of NG.116 (the current version is NG.116v3.0) provide additional clarity on which attributes are only restricted to the 3GPP access networks, SA WG5 will be glad to be informed.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10380,"status":"noted","reservation_date":"2020-09-22 08:22:51","uploaded":"2020-09-22 15:39:21","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA 5GJA","Cc":"SA WG2","lsoriginalls":"S5-204476","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006825.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006826","title":"LS from TSG SA: Reply LS on the stage 2 aspects of MINT","source":"TSG SA","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"LS in","for":"Information","abstract":"TSG SA thanks CT WG1 for the LS [SP-200654 \/ C1-205332] on the stage 2 aspects of MINT. TSG SA has discussed the matter in their SA#89-e meeting and agreed that CT WG1 has a study item including a) How one PLMN failure does not lead to signalling overload in other PLMNs; and b) how to avoid 'returning UEs' overloading the PLMN that had earlier failed. When the study is completed, then CT WG1 should consult with SA and SA WG2 on how to proceed with normative work..","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10390,"status":"noted","reservation_date":"2020-09-22 08:22:51","uploaded":"2020-09-22 15:39:21","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"TSG CT, SA WG2, SA WG3, CT WG3, CT WG4","lsoriginalls":"SP-200880","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006826.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006827","title":"LS from TSG SA: LS on 5G GUTI re-allocation","source":"TSG SA","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS in","for":"Information","abstract":"TSG SA#89e endorsed the following Working Agreement (WA): - SA discussed and acknowledged the trade-off between user privacy protection and signalling optimisation for 5G CIoT. - Considering this trade off if the same 5G-GUTI is used multiple times for paging even for CIoT UEs, there exists a privacy risk (identification of the UE's presence in a particular location). Therefore, for a UE in 5GMM-IDLE mode with suspend indication, the network shall always allocate a new 5G-GUTI after paging and resume of a connection, even if a NAS message is not sent. Action: SA asks recipient WGs to take the above into account and update their specifications if needed and submit related CRs for approval to SA#90e and CT#90e.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10400,"status":"noted","reservation_date":"2020-09-22 08:22:51","uploaded":"2020-09-22 15:39:21","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3, CT WG1","Cc":"TSG CT","lsoriginalls":"SP-200883","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006827.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006829","title":"LS from TSG SA: LS on Rel-17 schedule","source":"TSG SA","contact":"Puneet Jain","contact-id":36283,"tdoctype":"LS in","for":"Action","abstract":"TSG SA acknowledges that the current Rel-17 Stage 2 freeze date (i.e. Dec 2020) is unrealistic and agrees that a shift in stage-2 freeze dates is required. The decision on new Rel-17 Stage-2 freeze dates will be taken at TSG SA#90-e as part of the discussion on the overall Rel-17 timeline, in coordination with TSG RAN and TSG CT. Action: Please take the above decision into account.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10290,"status":"noted","reservation_date":"2020-09-22 08:22:51","uploaded":"2020-09-22 15:39:21","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG2, SA WG3, SA WG4, SA WG5, SA WG6, TSG CT","Cc":"TSG RAN","lsoriginalls":"SP-200888","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006829.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006905","title":"Discussion on AUSF\/UDM discovery based on SUCI information.","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"discussion","for":"Discussion","abstract":"This contribution discusses the AUSF\/UDM discovery based on SUCI information.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10150,"status":"noted","reservation_date":"2020-09-29 12:17:10","uploaded":"2020-10-02 06:35:52","revisionof":"","revisedto":"","release":"Rel-17","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_141e_Electronic\/Docs\/S2-2006905.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006906","title":"[DRAFT] Reply LS on AUSF\/UDM discovery based on SUCI information","source":"Huawei, Hisilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"This contribution sends a Reply LS to CT WG4 on AUSF\/UDM discovery based on SUCI.","secretary_remarks":"Response to S2-2006806. Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10140,"status":"postponed","reservation_date":"2020-09-29 12:17:10","uploaded":"2020-10-02 06:35:52","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006906.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006930","title":"Reply LS on dynamic 5QIs","source":"SA WG2","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG5","secretary_remarks":"Response to S2-2006798. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10120,"status":"approved","reservation_date":"2020-09-29 14:15:31","uploaded":"2020-10-02 16:33:06","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2006798","lsto":"SA WG5","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006930.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006931","title":"Introduction of AKMA into the reference architecture","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adds the abbreviation, the NF and references points related to AKMA in 23.501 with suitable references to 33.535","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10280,"status":"noted","reservation_date":"2020-09-29 15:33:12","uploaded":"2020-10-02 17:37:13","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.6.0","workitem":[{"winame":"AKMA"}],"crnumber":2457.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006931.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006932","title":"[DRAFT] LS on LS on Reference point interface names for AKMA","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"Draft LS on LS on Reference point interface names for AKMA","secretary_remarks":"Response to S2-2006822. R01 agreed. Revised to S2-2008003","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10260,"status":"revised","reservation_date":"2020-09-29 15:33:17","uploaded":"2020-10-02 17:37:13","revisionof":"","revisedto":"S2-2008003","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"AKMA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2006932.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2007159","title":"AUSF\/UDM discovery based SUCI information","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Public Key ID is allowed to be used for AUSF\/UDM discovery.","secretary_remarks":"Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10160,"status":"postponed","reservation_date":"2020-10-01 02:39:49","uploaded":"2020-10-02 14:45:23","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"16.6.0","workitem":[{"winame":"TEI17"}],"crnumber":2478.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2007159.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2007160","title":"AUSF\/UDM discovery based SUCI information","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Public Key ID is allowed to be used for AUSF\/UDM discovery.","secretary_remarks":"Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10170,"status":"postponed","reservation_date":"2020-10-01 02:39:51","uploaded":"2020-10-02 14:45:23","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"16.6.0","workitem":[{"winame":"TEI17"}],"crnumber":2416.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2007160.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2007161","title":"[DRAFT] Reply LS on AUSF\/UDM discovery based on SUCI information","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to CT WG4 AUSF\/UDM discovery based on SUCI information","secretary_remarks":"Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10180,"status":"postponed","reservation_date":"2020-10-01 02:39:52","uploaded":"2020-10-02 14:45:23","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2007161.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2007178","title":"Alignment changes on user plane Integrity Protection according to the LS(S2-2006813)","source":"Vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Replace 'maximum supported data rate for integrity protection' to 'maximum supported data rate of the UE'. Remove the IE detail and leave it to stage3.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10200,"status":"noted","reservation_date":"2020-10-01 06:40:33","uploaded":"2020-10-02 18:07:37","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.6.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2480.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2007178.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2007179","title":"Alignment changes on user plane Integrity Protection according to the LS(S2-2006813)","source":"Vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Replace 'UE Integrity Protection Maximum Data Rate' to 'Maximum Supported Data Rate of the UE'.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10210,"status":"noted","reservation_date":"2020-10-01 06:40:34","uploaded":"2020-10-02 18:07:37","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.6.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2417.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2007179.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2007289","title":"Correcting preventing of home routing due to 'any PLMN' requirement","source":"BlackBerry UK Ltd., Rogers Communications Canada","contact":"John-Luc Bakker","contact-id":37326,"tdoctype":"CR","for":"Agreement","abstract":"Summary of change: Allow inclusion of the 'any PLMN' entry in the non-3GPP access node selection information to be optional.","secretary_remarks":"Revision of S2-2004947 from S2#140E. R01 Endorsed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10080,"status":"endorsed","reservation_date":"2020-10-01 18:52:01","uploaded":"2020-10-02 16:47:40","revisionof":"S2-2004947","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"16.6.0","workitem":[{"winame":"TEI17"}],"crnumber":2402.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2007289.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2007290","title":"[DRAFT] Response to LS on the mandate to provide 'any PLMN' entry in the non-3GPP access node selection information","source":"BlackBerry UK Ltd.","contact":"John-Luc Bakker","contact-id":37326,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Response to S2-2004948 (Noted to at S2#140E). R02 agreed. Revised to S2-2008009","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10090,"status":"revised","reservation_date":"2020-10-01 18:54:13","uploaded":"2020-10-02 16:47:40","revisionof":"S2-2004948","revisedto":"S2-2008009","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2007290.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2007795","title":"LS from GSMA 5GJA: LS from 5GJA to 3GPP CT4","source":"GSMA 5GJA (5GJA14_128r1)","contact":"Hiroshi Ishikawa","contact-id":72758,"tdoctype":"LS in","for":"Information","abstract":"Background: GSMA 5GJA has discussed whether recovery procedures are required in case there is mismatch of profiles stored in AMF and UDR for registered UEs, due to any unexpected corruption of profiles stored in UDR. 5GJA was not able to identify any dedi","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10410,"status":"noted","reservation_date":"2020-10-15 05:26:54","uploaded":"2020-10-15 05:27:19","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"SA WG2","lsoriginalls":"5GJA14_128r1","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2007795.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2008003","title":"LS on LS on Reference point interface names for AKMA","source":"SA WG2","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3","secretary_remarks":"Revision of S2-2006932R01 . Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10270,"status":"approved","reservation_date":"2020-10-19 05:20:07","uploaded":"2020-10-20 07:13:49","revisionof":"S2-2006932","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"AKMA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2006822","lsto":"SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2008003.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2008009","title":"Response to LS on the mandate to provide 'any PLMN' entry in the non-3GPP access node selection information","source":"SA WG2","contact":"John-Luc Bakker","contact-id":37326,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachment: TS 23.501 CR#2402","secretary_remarks":"Revision of S2-2007290. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10100,"status":"approved","reservation_date":"2020-10-19 05:20:12","uploaded":"2020-10-20 07:13:49","revisionof":"S2-2007290","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_141e_Electronic\/Docs\/S2-2008009.zip","group":"S2","meeting":"S2-141-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]