[{"name":"S2-2004767","title":"LS from SA WG5: LS on analysis of GSMA GST attributes","source":"SA WG5","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"There is an ongoing 3GPP Rel-16 WID which is related to management support for network slicing: - Management Aspects of 5G Service-Level Agreement (SP-190789) SA WG5 thinks that SLA requirements can be fulfilled from management aspect and system aspect in a coordinated way. SA WG5 has started analysing the attributes from GSMA PRD NG.116 v1.0 and has approved S5-197621 in which the 3GPP network slicing ServiceProfile NRM is updated to implement some GST SLA attributes. SA WG5 is working on the translation from GST attributes to 3GPP ServiceProfile NRM and the translation from 3GPP ServiceProfile NRM to 3GPP SliceProfile NRM, and will provide the configurable attributes to 3GPP 5GC domain (e.g. AMF, SMF, UPF etc.) and NG-RAN domain (e.g. NG-RAN node) based on 3GPP SliceProfile NRM, and will provide TN requirements to non-3GPP TN domain management systems, see below figure. Action: SA WG5 respectfully requests SA WG2 to take this information into account and provide feedback, if necessary.","secretary_remarks":"Revision of postponed S2-2003518 from S2#139E. 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-08-04 05:43:45","uploaded":"2020-08-04 06:30:30","revisionof":"S2-2003518","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG3, IETF","Cc":"TSG SA, SA WG1, SA WG6, RAN WG2, GSMA 5GJA, ETSI ISG ZSM","lsoriginalls":"S5-197853","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004767.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-2004768","title":"LS from CT WG4: LS on End Marker Indication","source":"CT WG4","contact":"Caixia Qi","contact-id":56676,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 has discussed the support of stage2 requirement on End Marker Indication over N16\/N16a interface, and agreed that there is no need to define the new End Marker Indication, as the (H-)SMF\/UPF can send an End Marker packet every time there is a change of N9 tunnel information. It was also pointed out during the discussion that the new End Marker Indication over N16 would cause backward compatibility problem, as Rel-15 V-SMF changing the V-UPF would never send the End Marker Indication to the Rel-16 H-SMF, while the Rel-16 H-SMF would wait for this indication to send the End Marker packet. It is also desirable to keep the SMF behaviour aligned with H-SMF, i.e. sending an End Marker packet on the old I-UPF\/V-UPF tunnel when switching to a new N3\/N9 tunnel. Action: CT WG4 kindly asks SA WG2 group to take the above information into account and to consider aligning TS 23.502 accordingly.","secretary_remarks":"Revision of postponed S2-2003529 from S2#139E. Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10680,"status":"noted","reservation_date":"2020-08-04 05:43:45","uploaded":"2020-08-04 06:30:30","revisionof":"S2-2003529","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C4-201165","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004768.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-2004769","title":"LS from SA WG5: Reply LS on analytics support for energy saving","source":"SA WG5","contact":"Jean Michel Cornily","contact-id":7599,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks TSG SA for their Liaison Statement on 'analytics support for energy saving'. SA WG5 would like to inform SA and SA WG2 that our Rel-16 work item 'Energy efficiency of 5G' is about to be completed. The EE KPI and related performance measurements have been defined for NG-RAN as well as energy saving management use cases, requirements and information model. SA WG5 understands that the questions from SA WG2 are related to energy saving in a virtualized 5G core network. SA WG5 thinks that the relevance of virtualized 5GC energy saving use cases and solutions can be assessed when the means exist to measure the corresponding energy efficiency KPI before and after the energy saving functionality has been activated. As the 3GPP management system has the overall network view, the coordination between 5GC energy saving and NG-RAN energy saving needs to be considered from the OA&M aspect. SA WG5 is discussing the objectives of a Release 17 work item on use cases, requirements and solutions, as enhancement of Rel-16 energy efficiency and energy saving in 5G networks. The work includes the following aspects: a) 5GC network functions and b) the case of virtualized network functions. The potential usage of analytics and NWDAF is to be considered, in conjunction with OA&M (incl. MDAS - Management Data Analytics Service) in Rel-17 work. SA WG5 encourages SA WG2 to elaborate further on the description of potential energy saving use cases and solutions for 5GC, involving NWDAF or not, and in relationship with OA&M, and keep SA WG5 updated. To SA WG2: Please consider the information included above in SA WG2 work.","secretary_remarks":"Revision of postponed S2-2003532 from S2#139E. Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10090,"status":"noted","reservation_date":"2020-08-04 05:43:45","uploaded":"2020-08-04 06:30:30","revisionof":"S2-2003532","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG2, SA WG3, SA WG3LI, RAN WG3","lsoriginalls":"S5-201472","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004769.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-2004770","title":"LS from GSMA 5GJA: LS reply to SA WG2 on PLMN Selection","source":"GSMA 5GJA","contact":"Mari Melander","contact-id":37233,"tdoctype":"LS in","for":"Action","abstract":"GSMA 5GJA thanks SA WG2 for their LS 'LS on GSMA NG.116 Attribute Area of service and impact on PLMN selection'. At this time, GSMA 5GJA thinks the existing mechanisms are sufficient while GSMA continues to study 5GS roaming scenarios (including the Network Slicing aspects) for the identification of any additional impacts. Actions: GSMA 5GJA kindly asks SA WG2, SA WG1, and CT WG1 to take this information into account.","secretary_remarks":"Revision of postponed S2-2003533 from S2#139E. 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-08-04 05:43:45","uploaded":"2020-08-04 06:30:30","revisionof":"S2-2003533","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1, SA WG1","Cc":"","lsoriginalls":"5GJA12_115r3","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004770.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-2004771","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-2003551 from S2#139E. Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10230,"status":"postponed","reservation_date":"2020-08-04 05:43:45","uploaded":"2020-08-04 06:30:30","revisionof":"S2-2003551","revisedto":"","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":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004771.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-2004772","title":"LS from RAN WG3: LS on AS rekeying handling","source":"RAN WG3","contact":"Aijuan Liu","contact-id":43714,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 discussed the behaviour of NG-RAN node if it receives one NGAP UE CONTEXT MODIFICATION REQUEST message that includes both the Security Key IE and the Emergency Fallback Indicator IE. From RAN WG3 point of view, if the NG-RAN node performs the AS rekeying procedure as the highest priority, the emergency fallback will be delayed. Therefore it should be beneficial for the NG-RAN node to ignore the Security Key IE and only perform emergency fallback in this case. From NGAP protocol, the IEs mentioned above are all optional and could be present in one message. However, RAN WG3 is not sure whether such case is possible to happen, considering the AMF is possible to halt the trigger for AS rekeying (i.e. to decide not to include the Security Key IE) when it requests the NG-RAN node to perform emergency fallback. Besides, RAN WG3 understands that AS re-keying procedure could be initiated by AMF via either UE CONTEXT MODIFICATION REQUEST message or PATH SWITCH REQUEST ACKNOWLEDGE message. One issue discussed in RAN WG3 is whether it should be supported for the NG-RAN node to inform the AMF of the re-keying failure in either of the two cases. Action: RAN WG3 respectfully asks SA WG2 to feedback whether the case that both the Security Key IE and the Emergency Fallback Indicator IE are included within one NGAP UE CONTEXT MODIFICATION REQUEST message is abnormal or not","secretary_remarks":"Revision of postponed S2-2003557 from S2#139E. Responses drafted in S2-2005233 and S2-2005406. CC#2: Final response in S2-2005909","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10350,"status":"replied to","reservation_date":"2020-08-04 05:43:45","uploaded":"2020-08-04 06:30:30","revisionof":"S2-2003557","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3","Cc":"","lsoriginalls":"R3-202833","lsreply":"S2-2005909","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004772.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-2004774","title":"LS from RAN WG2: LS on SIB indication for UE specific DRX","source":"RAN WG2","contact":"Mungal Singh Dhanda","contact-id":84552,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 like to inform SA WG2 of the following agreement: - The SIB indication to enable\/disable the use of UE specific DRX for 5GS is cell specific indication. Action: RAN WG2 respectfully asks SA WG2 to take into consideration the above agreement.","secretary_remarks":"Revision of postponed S2-2003561 from S2#139E. Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10240,"status":"noted","reservation_date":"2020-08-04 05:43:45","uploaded":"2020-08-04 06:30:51","revisionof":"S2-2003561","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"R2-2004057","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004774.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-2004776","title":"LS from SA WG3: LS on Updated User Plane Integrity Protection advice","source":"SA WG3","contact":"Tim Evans","contact-id":49202,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 has reviewed the information provided by the GSMA regarding user plane integrity protection (UPIP) related attacks on 3GPP 4G and 5G networks. Whilst these attacks are very difficult, require very skilled attackers to exploit and are currently localised attacks based on false base stations, SA WG3 is conscious that once such attacks are known, refinements and the development of tools for less skilled attacks usually follow. SA WG3 advises that it has agreed the following 2 CR's: 1. S3-201442 (attached) - CR to 33.501 (5G security) - Adds an informative annex describing how to secure DNS and ICMP traffic 2. S3-201443 (attached) - CR to TS 33.401 (LTE security) - Adds an informative reference to the informative annex added into TS 33.501 describing how to secure DNS and ICMP traffic Additionally, SA WG3 discussed S3-201457 (attached), but several delegates raised concerns about the impacts of this solution on SA WG2 specifications. SA WG2 are invited to comment as to whether S3-201296 has any adverse impacts. Actions: 1. SA WG3 kindly asks CT WG1 and SA WG2 to review this information and update their specifications from release 16 accordingly. 2. SA WG3 kindly asks SA WG2 to review and comment as to whether S3-201457 has any adverse impacts on their specifications.","secretary_remarks":"Revision of postponed S2-2004308 from S2#139E. Response drafted in S2-2005688. Final response in S2-2006180","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10430,"status":"replied to","reservation_date":"2020-08-04 05:43:45","uploaded":"2020-08-04 06:30:51","revisionof":"S2-2004308","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, SA WG2","Cc":"TSG SA, TSG RAN","lsoriginalls":"S3-201487","lsreply":"S2-2006180","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004776.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-2004777","title":"LS from SA WG1: Reply LS on CMAS\/ETWS and emergency services for SNPNs","source":"SA WG1","contact":"Betsy Covell","contact-id":82463,"tdoctype":"LS in","for":"Action","abstract":"SA WG1 thanks RAN WG2 for the LS on CMAS\/ETWS and emergency services for SNPNs. In response to the questions from RAN WG2, SA WG1 provides the following: - There are no SA WG1 service requirements related to the support of PWS by SNPNs in Rel-16. - SA WG1 plans to further discuss adding service requirements for the support of PWS by SNPNs from Rel-17 onward. Action: SA WG1 asks RAN WG2 and SA WG2 groups to take the above information into account.","secretary_remarks":"Revision of postponed S2-2004315 from S2#139E. Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10250,"status":"noted","reservation_date":"2020-08-04 05:43:45","uploaded":"2020-08-04 06:30:51","revisionof":"S2-2004315","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, SA WG2","Cc":"CT WG1","lsoriginalls":"S1-202220","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004777.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-2004778","title":"LS from SA WG1: LS on 5GC assisted cell selection for accessing network slice","source":"SA WG1","contact":"Xu Lingjun","contact-id":56324,"tdoctype":"LS in","for":"Action","abstract":"SA WG1 thanks SA WG2 for their LS on 5GC assisted cell selection for accessing network slice (S1-202026\/S2-2001728). SA WG2 asks SA WG1 for feedback on the use case provided in S2-2001467. SA WG1 considers it to be a valid use case, but has not analysed the technical potential solutions illustrating the SA WG2 use-case\/key issue or other potential solutions. SA WG1 would like to direct SA WG2 to a related requirement in TS 22.261 clause 6.1, SA WG1 has defined that Network Slices can be further customised for operators to provide the optimal functionality of a complete network. Hence, an operator is always allowed to define specific capabilities and deployment configuration in network slices, this includes dedicated specific radio frequency to specific network slices. SA WG1 welcome further information of the progress of the study items in SA WG2 and RAN WG3. Action: SA WG1 asks SA WG2 to take this information into account in their work.","secretary_remarks":"Revision of postponed S2-2004316 from S2#139E. Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10260,"status":"noted","reservation_date":"2020-08-04 05:43:45","uploaded":"2020-08-04 06:30:51","revisionof":"S2-2004316","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG2, RAN WG3","lsoriginalls":"S1-202264","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004778.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-2004780","title":"LS from SA WG1: Reply to LS on Clarification of the definition of a UAS","source":"SA WG1","contact":"Atle Monrad","contact-id":79349,"tdoctype":"LS in","for":"Action","abstract":"SA WG1 has considered the incoming LS from SA WG6 requesting clarification on stage 1 requirements, as copied below. The text in the definition of a UAS and other normative text in TS 22.125 is not aligned with the informative Annex A. Further, it can be noted that there is text in the informative Annex A that is normative. SA WG1 has discussed the definition of a UAS and come to the conclusion that an update of TS 22.125 is needed, see the attached agreed CR. Action: SA WG1 requests SA WG2 and SA WG6 to take the above into account in their work and update their specifications as necessary.","secretary_remarks":"Revision of postponed S2-2004319 from S2#139E. Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10270,"status":"noted","reservation_date":"2020-08-04 05:43:45","uploaded":"2020-08-04 06:30:51","revisionof":"S2-2004319","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG6","Cc":"","lsoriginalls":"S1-202267","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004780.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-2004781","title":"LS from SA WG1: reply LS on GSMA NG.116 Attribute Area of service and impact on PLMN","source":"SA WG1","contact":"Betsy Covell","contact-id":82463,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 thanks SA WG2 for the LS noted in the header. In the LS, SA WG2 made the following request to SA WG1: SA WG2 kindly requests to provide their view as to whether the understanding of SA WG2 is correct and any other feedback. SA WG2's understanding is correct. There are no related SA WG1 requirements in R17. However, for information SA WG1 has agreed to the attached SID to study use cases and generate potential requirements for Rel-18 that may lead to Rel-18 enhancements.","secretary_remarks":"Revision of postponed S2-2004323 from S2#139E. Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10100,"status":"noted","reservation_date":"2020-08-04 05:43:45","uploaded":"2020-08-04 06:30:51","revisionof":"S2-2004323","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1, RAN WG2, RAN WG3, GSMA 5GJA, GSMA WAS","Cc":"","lsoriginalls":"S1-202294","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004781.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-2004785","title":"LS from SA WG5: LS on network data analysis energy saving","source":"SA WG5","contact":"Jean Michel Cornily","contact-id":7599,"tdoctype":"LS in","for":"Action","abstract":"In S5-201169 \/ S2-1912770 (LS on analytics support for energy saving), SA WG2 describes the following use case related to energy saving in the 5GC: ' In particular, the network data analysis may indicate that all the UEs served by some UPF instances are low priority UEs. Based on this information, the SMF can intentionally re-allocate the low priority UEs among fewer dedicated UPF instances which are used only for serving the low priority UEs at night and running on fewer dedicated servers. As a result, there can be more UPF instances having no UE allocated to them and can be removed by the NFV orchestrator. Consequently, there can be more physical resources, such as servers, to be shut down at night and less energy to be consumed. '. As part of its Rel-17 study item 'Study on new aspects of EE for 5G networks' (FS_EE5G), SA WG5 has studied this use case. From SA WG5 point of view, some points are to be clarified, including: 1. It is not clear: a. how UEs are characterized as low or high priority and on which criteria (e.g. user profile, etc.), b. where NWDAF gets this information from, c. whether UE priority is relative to within a given network slice (i.e. priority amongst UEs of a given network slice) or across network slices (i.e. priority amongst UEs of different network slices); 2. It is not clear if the main criteria for reallocating traffic from some UPF instances to fewer UPF instances is the UE priority or the time of the day (the above text mentions 'at night') or service level parameters. In other words, can't the reallocation of traffic from some UPF instances to fewer UPF instances be decided only based on the traffic load at some time of the day \/ night? 3. Since UEs can be attached to up to eight network slices simultaneously and UPF instances either belong to a single network slice (in such a case, traffic reallocation can be done only between UPF instances of the same network slice) or are shared amongst two or more network slices (in such a case, traffic reallocation can be done between UPF instances of different network slices serving the low priority UEs), the re-allocation of the traffic from some UPF instances to some other UPF instances must take this into consideration, implying that the NWDAF must have this knowledge prior to taking any decision; 4. Is it necessary that NWDAF have the information about which UPF instances are susceptible to receive traffic from other UPF instances? If yes, how does it obtain this information? 5. Migrating the traffic from some UPF instances to other UPF instances so as to switch off some servers requires interacting with NFV MANO functions (e.g. for VNF instance migration \/ termination). How NWDAF interacts with NFV MANO function(s) and via which reference point(s) is not specified. The reference point Os-Ma-Nfvo is for interactions between NFV Orchestrator and OSS\/BSS and, consequently, can't be used by NWDAF; 6. Reallocating traffic from some UPF instances to other UPF instances may have to take into consideration additional information such as e.g.: a. When ordering a network slice to his Network Slice Provider (NSP), a Network Slice Customer (NSC) may express isolation requirements such as e.g. 'I want my UPF instances be physically isolated from any other UPF instances allocated to other NSCs'. NWDAF has no knowledge of this, only OSS can have such information; b. All concerned UPF instances may not be on the same site \/ data centre, which potentially are not powered by the same source of energy. The network operator may be willing to privilege green sources of energy. In addition, the cost of energy may highly differ between sites \/ data centres. NWDAF has no knowledge of this, only OSS can have such information; c. All these UPF instances may be hosted on different types of servers, where some types of servers can be more energy efficient than others, so that the network operator may be willing to privilege these energy efficient servers. NWDAF has no knowledge","secretary_remarks":"Revision of postponed S2-2004631 from S2#139E. Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10280,"status":"postponed","reservation_date":"2020-08-04 05:43:45","uploaded":"2020-08-04 06:30:51","revisionof":"S2-2004631","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"TSG SA","lsoriginalls":"S5-203360","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004785.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-2004787","title":"LS from IETF DRIP: Scope and goals of the Drone Remote ID Protocol Working Group (DRIP) of the Internet Engineering Task Force (IETF)","source":"IETF DRIP","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"Dear Sir, This email intents to share with 3GPP the scope and goals of the Drone Remote ID Protocol Working Group (DRIP) of the Internet Engineering Task Force (IETF). The remaining of this email contains a brief description of the DRIP Working Group as well as the IETF. If you have any questions or concerns, feel free to contact us, we would be more than happy to take them into account. The DRIP co-chairs: Mohammed Boucadair and Daniel Migault The Internet Area Director: Eric Vyncke","secretary_remarks":"Revision of postponed S2-2004636 from S2#139E. 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-08-04 05:43:45","uploaded":"2020-08-04 06:30:51","revisionof":"S2-2004636","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"LSs_from_IETF_9June2020","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004787.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-2004788","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":"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-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":"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":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004788.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-2004789","title":"LS from GSMA 5GJA: LS on NG.116 support of different access types","source":"GSMA 5GJA","contact":"Alessio Casati","contact-id":82456,"tdoctype":"LS in","for":"Information","abstract":"GSMA 5GJA would like to inform SA WG2 and SA WG5 that there is an ongoing effort to clarify which NG.116 attributes apply to a specific access type. GSMA 5GJA understands the 5GS is access agnostic. GSMA 5GJA agrees that NG.116 is not restricted to only apply to 3GPP access type and expects that future versions of NG.116 (the current version is NG.116v3.0) will provide additional clarity on which attributes are only restricted to the 3GPP access networks. Action: GSMA 5GJA kindly asks SA WG2, SA WG5 to take this information into account.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10110,"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 WG5","Cc":"","lsoriginalls":"5GJA13_117r4","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004789.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-2004790","title":"LS from ETSI ISG ENI: Proposed Liaison to 3GPP SA2\/SA5 on mapping between ENI architecture and NWDAF\/MDAF","source":"ETSI ISG ENI","contact":"Raymond Forbes","contact-id":80208,"tdoctype":"LS in","for":"Information","abstract":"ETSI ENI would like to inform a WI called 'Mapping between ENI architecture and operational systems', GS ENI 011, was approved in ETSI ENI#12 meeting (December 2019) and is under specification now. It specifies how to map ENI system to operational system, which is the physical and virtual system that is used by operators to maintain and manage the network and resources. How to map ENI with NWDAF\/MDAF is one of studied topics in this WI. In addition, ETSI ENI noted SA WG2 discussed the functional architecture of NWDAF which has some linkage with GS ENI 011. Action: ETSI ENI would like to share above information and look forward to keeping additional collaboration with SA WG2 and SA WG5.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10120,"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 WG5","Cc":"","lsoriginalls":"ENI(20)014_022r1","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004790.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-2004791","title":"LS from ETSI ISG ETI: Announcement of ISG ETI","source":"ETSI ISG ETI","contact":"Tony Rutkowski","contact-id":73114,"tdoctype":"LS in","for":"Information","abstract":"ETSI is pleased to announce that they have formed Industry Specification Group (ISG) Encrypted Traffic Integration (ETI) to scope and identify means to ensure that the increasing preponderance of encrypted traffic can successfully integrate to the requirements of network management and optimisation. The group has agreed to start work on 5 work items to allow the scoping of the problem and in due course to lead to future standards and solutions across networks. Details of the work programme can be found at https:\/\/portal.etsi.org\/ETI. GR-ETI-001 Problem Statement GR-ETI-002 Requirements analysis GS-ETI-003 Integration strategies and techniques GR-ETI-004 Ontology MI-ETI-006 Ecosystem Officers of ETI, appointed in the Kick-off Meeting, are: Chairman: Tony Rutkowski, CIS Vice-chair: Scott Cadzow, C3L","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10130,"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, oneM2M, ETSI ISGs","Cc":"CCDB, ISO\/IEC, ENISA, ITU-T SGs, OASIS CTI, CACAO, OpenC2","lsoriginalls":"ETI(20)000009r1","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004791.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-2004796","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":"Response drafted in S2-2004948. Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10520,"status":"postponed","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":"","lsoriginalls":"C1-204034","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004796.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-2004798","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":"Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10300,"status":"postponed","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":"","lsoriginalls":"C1-204083","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004798.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-2004799","title":"LS from CT WG3: Reply LS on PAP\/CHAP and other point-to-point protocols usage in 5GS","source":"CT WG3","contact":"Waqar Zia","contact-id":86053,"tdoctype":"LS in","for":"Information","abstract":"CT WG3 thanks CT WG1 for the LS on PAP\/CHAP and other point-to-point protocols usage in 5GS. CT WG1's question: The following point-to-point protocols are defined in TS 24.008 as (e)PCO parameters which can be exchanged between the UE and the network during GPRS and EPS session management procedure: - C021 Link Control Protocol (LCP) - C023 Password Authentication Protocol (PAP) - 8021 IP Control Protocol (IPCP) - C223 Challenge Handshake Authentication Protocol (CHAP) Are above point-to-point protocols supported in 5GS (i.e. Rel-15 and\/or Rel-16) as (e)PCO parameters or to be supported in the near future (i.e. Rel-17)? CT WG3's Answer: CT WG3 has reviewed its current specifications related to the question above and the summary of the current status is in the following: TS 23.401 cl.4.4.3.3 describes PPP support for P-GW: 'The network does not support PPP bearer type in this version of the specification. Pre-Release 8 PPP functionality of a GGSN may be implemented in the PDN GW.' Since PPP bearer type was deprecated in Rel-8, there is no support in TS 29.061 and 29.561 describing the interworking with external DN using PPP in 5G. For the authentication, if PCO includes PAP\/CHAP, SMF doesn't currently support using RADIUS\/Diameter protocol including the corresponding PAP\/CHAP information elements directly for interaction with external DN-AAA server, in the current release 15 and 16, but a combo-SMF+PGW node can support Radius\/Diameter interface through its PGW component.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10140,"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":"CT WG1","Cc":"SA WG2, SA WG3, CT WG4","lsoriginalls":"C3-203609","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004799.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-2004801","title":"LS from CT WG4: LS on Clarifications on UE Reachability event","source":"CT WG4","contact":"Lu Yunjie","contact-id":74423,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 would like to inform SA WG2 that CT WG4 has agreed TS 29.518 CR #370 (attached) from Rel-15 onwards, to support the UE Reachability event on AMF Event Exposure service, as specified in TS 23.502 v15.9.0. According to stage 2, the UE reachability event is used for different subscription requests for both internal exposure (e.g. by SMF) and external exposure (e.g. by UDM\/NEF) services. The CR thus introduces a new indication in service request to allow the consumer NF to indicate whether the subscription is for 'changes of UE reachability state' report (internal) or for 'UE reachable for DL traffic' report (external). NOTE: Stage 2 only explicitly specified event for 'UE reachable for DL traffic' (see 'UE Reachability' event in table 4.15.3.1-1 of 3GPP TS 23.502). However, CT WG4 further discovered certain aspects that are not clearly specified in Stage 2 {...} Action: CT WG2 kindly asks SA WG2 to take the above observations into consideration and provide further clarifications on the mentioned concerns in stage 2.","secretary_remarks":"Response drafted in S2-2004899. Final response in S2-2006183","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10560,"status":"replied to","reservation_date":"2020-08-04 05:43:46","uploaded":"2020-08-04 08:11:14","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C4-203425","lsreply":"S2-2006183","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004801.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-2004805","title":"LS from RAN WG3: LS reply on RACS multiple radio capability formats","source":"RAN WG3","contact":"Feng Han","contact-id":73581,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 thanks SA WG2 for the LS on 'RACS multiple radio capability formats'. RAN WG3 has agreed to introduce the support for multiple coding formats from the RAN node to the CN node over S1 and NG interfaces (as indicated by the SA WG2 LS). The agreed TPs are attached for reference. Action: RAN WG3 respectfully asks SA WG2 to take the above into account.","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-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":"RAN WG2, CT WG4, CT WG3","lsoriginalls":"R3-204147","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004805.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-2004810","title":"LS from SA WG3LI: Additional Clarifications on LI requirements applicable to SNPNs","source":"SA WG3LI","contact":"Alexander Markman","contact-id":35093,"tdoctype":"LS in","for":"Action","abstract":"SA WG3-LI would like to thank SA WG2 for their response LS and an opportunity to further clarify the LI requirements for SNPNs. {...} Action: SA WG3-LI kindly requests SA WG2 to take the above clarifications and answers into consideration when designing the solution for SNPN N3IWF selection. SA WG3-LI would also like SA WG2 to answer the question in the last paragraph above.","secretary_remarks":"Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10320,"status":"postponed","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":"","lsoriginalls":"S3i200409","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004810.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-2004811","title":"LS from SA WG5: Reply LS to Reply LS on support for eCall over NR","source":"SA WG5","contact":"Maryse Gardella","contact-id":68914,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks SA for the LS on support for eCall over NR. SA WG5 can confirm that the IMS charging enhancements, introduced from Rel-15 to cover IMS on top of 5GCore, include IMS emergency sessions, with no restriction on the 3GPP radio access type (E-UTRA or NR). Therefore, the support eCall in IMS over NR with 5G Core is already covered from charging's perspective from Rel-15.","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-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":"TSG SA","Cc":"SA WG2, RAN WG2, CT WG1, RAN WG5, SA WG1, SA WG4, TSG RAN, TSG CT","lsoriginalls":"S5-203369","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004811.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-2004812","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":"Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10330,"status":"postponed","reservation_date":"2020-08-04 05:43:46","uploaded":"2020-08-04 08:11:14","revisionof":"","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":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004812.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-2004813","title":"LS from TSG SA: LS on mandatory support of full rate user plane integrity protection for 5G","source":"TSG SA","contact":"Johannes Achter","contact-id":5595,"tdoctype":"LS in","for":"Action","abstract":"TSG SA#88-e has discussed the request from GSMA Board (SP-200533) and GSMA CVD (SP 200304) which informs 3GPP about a new security threat published in February 2020 exploiting a lack of integrity protection of the user plane in LTE and NR. GSMA CVD has discussed the matter and concluded that the security vulnerability is also imposed by the current specification for NR which mandate user plane integrity protection for UE only for 64 kbps (see TS38.300). As the topic has been already discussed since August 2019 between RAN WG2 and SA WG3, TSG SA decided to close this security gap as soon as possible. It has been decided to mitigate the security threat caused by the lack of user plane integrity protection for all UEs supporting connection to the 5GC by including mandatory full-rate UPIP for Architecture option 2 from Release16 onwards and extending it to other Architecture options from Release 17 onwards. The attached Release 16 CR to TS 33.501 was approved by TSG SA#88. The addressed working groups are requested to agree on necessary Release 16 CRs for all their relevant specifications during their Q3\/2020 meetings in order to approve the respective CRs in the TSG Plenaries in September 2020 for Rel-16. TSG SA also encourages working groups to conclude corresponding work for other Architecture options in Rel-17. Action: TSG SA asks SA WG2, SA WG3, RAN WG2, RAN WG3 and CT WG1 to update their respective Rel-16 specifications to mitigate the security threat caused by the lack of user plane integrity protection for 5GC-capable UEs (supporting Architecture option 2) and submit the Rel-16 CRs to TSG#89. TSG SA encourages SA WG2, SA WG3, RAN WG2, RAN WG3 and CT WG1 to conclude corresponding work for other Architecture options in Rel-17.","secretary_remarks":"Response drafted in S2-2004945. Final response in S2-2006181","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10460,"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":"CT WG1, SA WG2, SA WG3, RAN WG2, RAN WG3","Cc":"TSG RAN, TSG CT","lsoriginalls":"SP-200617","lsreply":"S2-2006181","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004813.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-2004814","title":"LS from TSG SA: LS on HO to congested cells","source":"TSG SA","contact":"Dario Serafino Tonesi","contact-id":43468,"tdoctype":"LS in","for":"Information","abstract":"During the conclusion of Alternative QoS Profile feature, some companies raised concerns that handover to a congested site potentially causing the GBR flows to be released could be a potential issue. It was concluded that such potential issue can be further investigated and may be resolved, if not mitigated via existing mechanism. Action: SA respectfully asks RAN 3 to look into this potential issue and inform SA WG2 about the outcome.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10180,"status":"noted","reservation_date":"2020-08-04 05:43:46","uploaded":"2020-08-04 08:11:14","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"SA WG2, TSG RAN","lsoriginalls":"SP-200631","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004814.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-2004844","title":"Remove un-necessary End Marker Indication in invocations of Nsmf_PDUSession_Update Request (missing part)","source":"Nokia, Nokia Shanghai Bell, Ericsson","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Align to CT WG4 LS and request: Remove un-necessary End Marker Indication in invocations of Nsmf_PDUSession_Update Request related with UE mobility","secretary_remarks":"r01 agreed. Revised, merging S2-2005196, to S2-2006188","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10690,"status":"revised","reservation_date":"2020-08-08 16:19:26","uploaded":"2020-08-13 08:04:47","revisionof":"","revisedto":"S2-2006188","release":"Rel-16","crspec":"23.502","crspecversion":"16.5.1","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":2330.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-2004844.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-2004899","title":"[DRAFT] Reply LS on 'LS on Clarifications on UE Reachability event'","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Provide feedback that SMF subscribes to UE reachability after Namf_Communication_N1N2MessageTransfer error due to UE unreachable.","secretary_remarks":"Response to S2-2004801. r04 agreed. Revised to S2-2006183","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10570,"status":"revised","reservation_date":"2020-08-10 20:10:07","uploaded":"2020-08-13 19:24:46","revisionof":"","revisedto":"S2-2006183","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004899.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-2004900","title":"SMF aware of UE Reachability after N1N2MessageTransfer error due to UE unreachable","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When the SMF refrains from sending further Namf_Communication_N1N2MessageTransfer message for DL data to the AMF while the UE is unreachable, the SMF subscribes to the AMF event exposure for UE reachability.","secretary_remarks":"Agreed. Revised to S2-2006184.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10590,"status":"revised","reservation_date":"2020-08-10 20:10:07","uploaded":"2020-08-13 19:26:41","revisionof":"","revisedto":"S2-2006184","release":"Rel-15","crspec":"23.502","crspecversion":"15.10.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2335.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-2004900.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-2004901","title":"SMF aware of UE Reachability after N1N2MessageTransfer error due to UE unreachable","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: When the SMF refrains from sending further Namf_Communication_N1N2MessageTransfer message for DL data to the AMF while the UE is unreachable, the SMF subscribes to the AMF event exposure for UE reachability.","secretary_remarks":"Agreed. Revised to S2-2006185.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10610,"status":"revised","reservation_date":"2020-08-10 20:10:08","uploaded":"2020-08-13 19:26:41","revisionof":"","revisedto":"S2-2006185","release":"Rel-16","crspec":"23.502","crspecversion":"16.5.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2336.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004901.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-2004943","title":"UE user plane integrity protection mandatory at full rate","source":"Qualcomm Incorporated, MediaTek, Ericsson, Deutsche Telekom, Orange","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Aligns TS 23.501 with CR SP-200628 to TS 33.501 that defines that UE shall support integrity protection of user data at any data rate, up to and including, the highest data rate supported by the UE. Clarifies in TS 23.501 how the PDU se","secretary_remarks":"r07 agreed. Revised to S2-2006182","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10490,"status":"revised","reservation_date":"2020-08-11 13:27:49","uploaded":"2020-08-13 19:33:47","revisionof":"","revisedto":"S2-2006182","release":"Rel-16","crspec":"23.501","crspecversion":"16.5.1","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":2400.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004943.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-2004944","title":"UE user plane integrity protection mandatory at full rate","source":"Qualcomm Incorporated, MediaTek, Ericsson, Deutsche Telekom, Orange","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Aligns TS 23.502 with CR SP-200628 to TS 33.501 that defines that UE shall support integrity protection of user data at any data rate, up to and including, the highest data rate supported by the UE","secretary_remarks":"Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10510,"status":"agreed","reservation_date":"2020-08-11 13:30:44","uploaded":"2020-08-13 19:33:47","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.5.1","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":2341.0,"crrevision":"","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-2004944.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-2004945","title":"[DRAFT] LS on mandatory support of full rate user plane integrity protection for 5G","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"Reply to SA LS on mandatory support of full rate user plane integrity protection for 5G","secretary_remarks":"Response to S2-2004813. Agreed. Revised to S2-2006181.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10470,"status":"revised","reservation_date":"2020-08-11 13:53:53","uploaded":"2020-08-13 19:33:47","revisionof":"","revisedto":"S2-2006181","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"TEI16"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"CT WG1, SA WG3, RAN WG2, RAN WG3, TSG RAN, TSG CT","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004945.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-2004946","title":"Correcting preventing of home routing due to 'any PLMN' requirement","source":"BlackBerry UK Ltd.","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":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10530,"status":"noted","reservation_date":"2020-08-11 19:24:17","uploaded":"2020-08-13 04:01:02","revisionof":"","revisedto":"","release":"Rel-15","crspec":"23.501","crspecversion":"15.10.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2401.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-2004946.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-2004947","title":"Correcting preventing of home routing due to 'any PLMN' requirement","source":"BlackBerry UK Ltd.","contact":"John-Luc Bakker","contact-id":37326,"tdoctype":"CR","for":"Agreement","abstract":"Rel-16 mirror CR: Summary of change: Allow inclusion of the 'any PLMN' entry in the non-3GPP access node selection information to be optional.","secretary_remarks":"Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10540,"status":"noted","reservation_date":"2020-08-11 19:26:09","uploaded":"2020-08-13 04:01:02","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.5.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2402.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004947.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-2004948","title":"[DRAFT] Response to LS on the mandate to provide 'any PLMN' entry in the non-3GPP access node selection information","source":"BlackBerry UK Limited","contact":"John-Luc Bakker","contact-id":37326,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"Response to S2-2004796. Noted","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10550,"status":"noted","reservation_date":"2020-08-11 19:29:52","uploaded":"2020-08-13 04:01:02","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004948.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-2005050","title":"LS from TSG CT: Reply LS on S1\/NG DAPS handover","source":"TSG CT","contact":"Lena Chaponniere","contact-id":38080,"tdoctype":"LS in","for":"Action","abstract":"TSG CT thanks SA WG2 for their LS on S1\/NG DAPS handover. TSG CT has agreed that CT WG4 should work on completing the stage 3 changes required to enable S1\/NG DAPS handover in Rel-16 at CT WG4#99-e. Consequently TSG CT sees no issue with approving the CRs agreed by SA WG2 in S2-2004472 and S2-2004473 at SA#88. Action: TSG CT asks SA WG2, SA and RAN WG3 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":10740,"status":"noted","reservation_date":"2020-08-12 12:43:09","uploaded":"2020-08-12 13:15:59","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, TSG SA, RAN WG3, CT WG4","Cc":"TSG RAN","lsoriginalls":"CP-201312","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005050.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-2005087","title":"LS from CT WG1: Reply LS on support of eCall over NR","source":"CT WG1","contact":"Lena Chaponniere","contact-id":38080,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 thanks TSG SA for their LS on support of eCall over NR. CT WG1 would like to inform SA that CT WG1 has completed the work required to support eCall in IMS over NR (with 5G Core) as requested by TSG SA, via the agreement of the attached CR.","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-08-12 14:40:30","uploaded":"2020-08-12 15:06:39","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG2, SA WG5, RAN WG2, RAN WG5, SA WG1, SA WG4, TSG RAN, TSG CT, CT WG6","lsoriginalls":"C1-203221","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005087.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-2005088","title":"LS from CT WG1: Reply LS on Updated User Plane Integrity Protection advice","source":"CT WG1","contact":"Kundan Tiwari","contact-id":81849,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 thanks SA WG3 for sending the LS and the agreed CRs S3-201442 and S3-201443 in the LS. CT WG1 has discussed SA WG3 requirement mentioned in the attached CRs S3-201442\/43 of the LS and captured the requirements in the CR C1-204119, C1-204120 and C1-204121. The CRs are attached with the LS.","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-08-12 14:40:50","uploaded":"2020-08-12 15:06:39","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"TSG SA, TSG RAN, SA WG2","lsoriginalls":"C1-204194","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005088.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-2005196","title":"Remove End Marker Indication in N16\/N16a","source":"China Mobile","contact":"Dan Wang","contact-id":87155,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Alignment with CT WG4 LS and remove un-necessary End Marker Indication in invocations of Nsmf_PDUSession_Update Request related with UE mobility","secretary_remarks":"Merged into S2-2006188","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10710,"status":"merged","reservation_date":"2020-08-13 02:23:24","uploaded":"2020-08-13 04:43:59","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.5.1","workitem":[{"winame":"ETSUN"}],"crnumber":2353.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-2005196.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-2005231","title":"Removal of sending AS key","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Removing the security context from the request to trigger emergency fallback towards NG-RAN. 2. Adding a NOTE to clarify that the NG RAN node can ignore the security context if it is included in the the request to trigger emergency f","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-08-13 03:17:30","uploaded":"2020-08-13 09:30:01","revisionof":"","revisedto":"","release":"Rel-15","crspec":"23.502","crspecversion":"15.10.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2354.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-2005231.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-2005232","title":"Removal of sending security key","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: 1. Removing the security context from the request to trigger emergency fallback towards NG-RAN. 2. Adding a NOTE to clarify that the NG RAN node can ignore the security context if it is included in the the request to t","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-08-13 03:17:32","uploaded":"2020-08-13 09:30:01","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.5.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2355.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005232.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-2005233","title":"[DRAFT] LS Reply on AS rekeying handling","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"LS out","for":"Approval","abstract":"This contribution proposes to reply LS from RAN WG3","secretary_remarks":"Response to S2-2004772. 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-08-13 03:17:32","uploaded":"2020-08-13 09:30:01","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005233.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-2005381","title":"UE Reachability event clarification","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the step that the UE Reachiability notification can be requested by other NF. Add description on the notification part for internal exposure notification.","secretary_remarks":"Merged into S2-2006186","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10630,"status":"merged","reservation_date":"2020-08-13 07:16:17","uploaded":"2020-08-13 16:07:32","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.5.1","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":2359.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-2005381.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-2005385","title":"Clarification on End marker","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The UPF does not send DN to SMF when it receives end marker packets and no forwarding tunnel established. The UPF drops end marker packets. Delete leftover end marker indications.","secretary_remarks":"r04 agreed. Revised to S2-2006189","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10720,"status":"revised","reservation_date":"2020-08-13 07:16:20","uploaded":"2020-08-13 16:07:32","revisionof":"","revisedto":"S2-2006189","release":"Rel-16","crspec":"23.502","crspecversion":"16.5.1","workitem":[{"winame":"ETSUN"},{"winame":"5GS_Ph1"}],"crnumber":2361.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-2005385.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-2005406","title":"[DRAFT] Reply LS on AS rekeying handling","source":"Huawei","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to RAN WG3 on AS rekeying issue.","secretary_remarks":"Response to S2-2004772. CC#2: S2 200540r01 was agreed. Revised in S2-2005909.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10390,"status":"revised","reservation_date":"2020-08-13 07:30:52","uploaded":"2020-08-13 15:07:19","revisionof":"","revisedto":"S2-2005909","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"},{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005406.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-2005407","title":"Clarification on concurrency of AS rekeying handling and Emergency Fallback procedure for R15","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1.When the AS re-keying procedure and the Emergency Fallback procedure collides, the AMF gives up the AS re-keying procedure and only initiates the emergency fallback procedure. 2.If AMF includes both the Security Key IE and the Emergen","secretary_remarks":"Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10410,"status":"agreed","reservation_date":"2020-08-13 07:30:52","uploaded":"2020-08-13 15:07:19","revisionof":"","revisedto":"","release":"Rel-15","crspec":"23.501","crspecversion":"15.10.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"NR_newRAT-Core"}],"crnumber":2419.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200671","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005407.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-2005408","title":"Clarification on concurrency of AS rekeying handling and Emergency Fallback procedure for R16","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: 1.When the AS re-keying procedure and the Emergency Fallback procedure collides, the AMF gives up the AS re-keying procedure and only initiates the emergency fallback procedure. 2.If AMF includes both the Security Key","secretary_remarks":"Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10420,"status":"agreed","reservation_date":"2020-08-13 07:30:53","uploaded":"2020-08-13 15:07:19","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.5.1","workitem":[{"winame":"5GS_Ph1"},{"winame":"NR_newRAT-Core"}],"crnumber":2420.0,"crrevision":"","crcategory":"A","tsg_crp":"SP-200671","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005408.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-2005480","title":"Corrections on DAPS HO Procedure","source":"Samsung","contact":"Sang-Jun Moon","contact-id":30993,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Step 6 descriptions are corrected. - Step reference numbers are corrected.","secretary_remarks":"Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10750,"status":"agreed","reservation_date":"2020-08-13 10:11:09","uploaded":"2020-08-13 11:04:40","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.5.1","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":2367.0,"crrevision":"","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-2005480.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-2005492","title":"Correction on Deregistration procedures for SMS over NAS","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Different network requirements following UE requested deregistration of SMS service and network-initiated UE deregistration are identified. During UE initiated deregistration for SMS Service, the AMF deactivates SMS Service using Nsmsf","secretary_remarks":"r04 agreed. Revised to S2-2006178","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10030,"status":"revised","reservation_date":"2020-08-13 10:22:12","uploaded":"2020-08-13 19:39:10","revisionof":"","revisedto":"S2-2006178","release":"Rel-15","crspec":"23.502","crspecversion":"15.10.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2278.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005492.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-2005493","title":"Correction on Deregistration procedures for SMS over NAS","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Removal of ambiguous UE registration condition in the AMF. Formal introduction of Access Type specific use of Nsmsf_SMService_Deactivate is added in the service operation definition. Update the description of Nsmsf_S","secretary_remarks":"r01 agreed. Revised to S2-2006179","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10050,"status":"revised","reservation_date":"2020-08-13 10:22:14","uploaded":"2020-08-13 19:39:10","revisionof":"","revisedto":"S2-2006179","release":"Rel-16","crspec":"23.502","crspecversion":"16.5.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2368.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005493.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-2005544","title":"Stage 3 alignment on UE reachability event","source":"NTT DOCOMO","contact":"Atsushi Minokuchi","contact-id":26474,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To clarify description on UE reachability event","secretary_remarks":"r09 agreed. Revised, merging S2-2005381, to S2-2006186","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10640,"status":"revised","reservation_date":"2020-08-13 10:53:55","uploaded":"2020-08-13 11:22:21","revisionof":"","revisedto":"S2-2006186","release":"Rel-15","crspec":"23.502","crspecversion":"15.10.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2378.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-2005544.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-2005547","title":"Stage 3 alignment on UE reachability event","source":"NTT DOCOMO","contact":"Atsushi Minokuchi","contact-id":26474,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: To clarify description on UE reachability event","secretary_remarks":"r01 agreed. Revised to S2-2006187","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10660,"status":"revised","reservation_date":"2020-08-13 10:59:15","uploaded":"2020-08-13 11:22:21","revisionof":"","revisedto":"S2-2006187","release":"Rel-16","crspec":"23.502","crspecversion":"16.5.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2380.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005547.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-2005616","title":"Work analytics on 5G capabilities for factories of the future requested by 5G-ACIA.","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"discussion","for":"Discussion","abstract":"This discussion paper aims at providing analysis on the gaps and maps for the 5G-ACIA LS: 5G capabilities for factories of the future and proposes a way forward to address the gaps.","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-08-13 12:32:13","uploaded":"2020-08-13 14:19:25","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"FS_eNPN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005616.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-2005688","title":"[DRAFT] Reply LS on Updated User Plane Integrity Protection advice","source":"Samsung R&D Institute India","contact":"Lalith Kumar","contact-id":80547,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"Response to S2-2004776. Revised to S2-2006180.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10440,"status":"revised","reservation_date":"2020-08-13 13:47:25","uploaded":"2020-08-13 14:05:45","revisionof":"","revisedto":"S2-2006180","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"TEI16"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005688.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-2005702","title":"Support for DTLS","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Makes text in TS 23.501 normative to align with TS 24.501 Gives reference to TS 24.501","secretary_remarks":"Confirm Spec version used - CR states 16.7.0! r03 agreed. Revised to S2-2006190.","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10760,"status":"revised","reservation_date":"2020-08-13 14:11:53","uploaded":"2020-08-13 19:33:47","revisionof":"","revisedto":"S2-2006190","release":"Rel-16","crspec":"23.501","crspecversion":"16.5.1","workitem":[{"winame":"TEI16"},{"winame":"UPIP_SEC"}],"crnumber":2442.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-2005702.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-2005746","title":"Fixing Redirection for EPS Fallback indication","source":"Nokia, Nokia Shanghai Bell, Verizon, Samsung","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Align the procedures to state that the AMF sends this indication whenever EPS Fallback is supported in the PLMN. It is then up to RAN to determine when to perform HO or RRC redirection (considering also N26 support but also other factor","secretary_remarks":"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-08-13 15:10:33","uploaded":"2020-08-13 21:54:11","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.5.1","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":2391.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-2005746.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-2005822","title":"Corrections to MME Emergency Configuration Data for enable the selection of diffrent emergency gateways based on UE capabilities","source":"Nokia, Nokia Shanghai-Bell","contact":"Thomas Belling","contact-id":68266,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To enable a diffrentiation of the emergency gateway based on UE\u00b4s support of 5GC NAS, the Emergency Configuration Data in the MME defined in 3GPP\u00a0TS\u00a023.401are extended with the following IEs: Emergency Access Point Name (em APN) for 5GS","secretary_remarks":"Postponed","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10080,"status":"postponed","reservation_date":"2020-08-13 19:03:30","uploaded":"2020-08-13 19:54:35","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.5.1","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":2400.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-2005822.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-2005875","title":"LS from RAN WG3: Reply LS on mandatory support of full rate user plane integrity protection for 5G","source":"RAN WG3","contact":"Luis Lopes","contact-id":84588,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 would like to thank TSG SA for the LS on mandatory support of full rate user plane integrity protection for 5G. RAN WG3 has analysed the agreed CR to TS 33.501 in SP-200628 and thinks that this does not impact RAN WG3 specifications. Regarding release 17, RAN WG3 intends to wait for SA WG3 to analyse the impact on security requirements and architecture. RAN WG3 will follow up based on SA WG3's conclusions. Action: RAN WG3 kindly asks TSG SA, TSG RAN, TSG CT, SA WG2, SA WG3, RAN WG2, and CT WG1 to take the above information into account, and inform RAN WG3 of further progress on this topic.","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-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":"TSG SA, TSG RAN, TSG CT, CT WG1, SA WG2, SA WG3, RAN WG2","Cc":"","lsoriginalls":"R3-205653","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005875.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-2005909","title":"Reply LS on AS rekeying handling","source":"SA WG2","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3. CC: SA WG3. Attachments: TS 23.501, CR 2419, CR 2420","secretary_remarks":"Revision r01 of S2-2005406. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10400,"status":"approved","reservation_date":"2020-08-31 14:28:36","uploaded":"2020-08-31 14:29:39","revisionof":"S2-2005406","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"},{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2004772","lsto":"RAN WG3","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005909.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-2006178","title":"Correction on Deregistration procedures for SMS over NAS","source":"Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Hisilicon","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Different network requirements following UE requested deregistration of SMS service and network-initiated UE deregistration are identified. During UE initiated deregistration for SMS Service, the AMF deactivates SMS Service using Nsmsf","secretary_remarks":"Revision r04 of S2-2005492. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10040,"status":"agreed","reservation_date":"2020-09-03 04:31:38","uploaded":"2020-09-03 15:01:14","revisionof":"S2-2005492","revisedto":"","release":"Rel-15","crspec":"23.502","crspecversion":"15.10.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2278.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-200671","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2006178.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-2006179","title":"Correction on Deregistration procedures for SMS over NAS","source":"Nokia, Nokia Shanghai Bell, Ericsson","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Removal of ambiguous UE registration condition in the AMF. Formal introduction of Access Type specific use of Nsmsf_SMService_Deactivate is added in the service operation definition. Update the description of Nsmsf_S","secretary_remarks":"Revision r01 of S2-2005493. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10060,"status":"agreed","reservation_date":"2020-09-03 04:31:39","uploaded":"2020-09-03 15:01:14","revisionof":"S2-2005493","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.5.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2368.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"SP-200671","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2006179.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-2006180","title":"Reply LS on Updated User Plane Integrity Protection advice","source":"SA WG2","contact":"Lalith Kumar","contact-id":80547,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3. CC: CT WG1","secretary_remarks":"Revision of S2-2005688. CC#2: Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10450,"status":"approved","reservation_date":"2020-08-31 14:28:37","uploaded":"2020-08-31 14:29:39","revisionof":"S2-2005688","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"TEI16"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2004776","lsto":"SA WG3","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2006180.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-2006181","title":"LS on mandatory support of full rate user plane integrity protection for 5G","source":"SA WG2","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"To: TSG SA. CC: CT WG1, SA WG3, RAN WG2, RAN WG3, TSG RAN, TSG CT. Attachments: TS 23.501 CR 2400, TS 23.502 CR 2341","secretary_remarks":"Revision of S2-2004945. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10480,"status":"approved","reservation_date":"2020-08-31 14:28:37","uploaded":"2020-08-31 14:29:39","revisionof":"S2-2004945","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"TEI16"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2004813","lsto":"TSG SA","Cc":"CT WG1, SA WG3, RAN WG2, RAN WG3, TSG RAN, TSG CT","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2006181.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-2006182","title":"UE user plane integrity protection mandatory at full rate","source":"Qualcomm Incorporated, MediaTek, Ericsson, Deutsche Telekom, Orange, OPPO, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Aligns TS 23.501 with CR SP-200628 to TS 33.501 that defines that UE shall support integrity protection of user data at any data rate, up to and including, the highest data rate supported by the UE. Clarifies in TS 23.501 how the PDU se","secretary_remarks":"Revision r07 of S2-2004943. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10500,"status":"agreed","reservation_date":"2020-09-03 04:31:40","uploaded":"2020-09-03 15:01:14","revisionof":"S2-2004943","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.5.1","workitem":[{"winame":"TEI16"},{"winame":"UPIP_SEC"}],"crnumber":2400.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"SP-200686","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2006182.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-2006183","title":"Reply LS on 'LS on Clarifications on UE Reachability event'","source":"SA WG2","contact":"Chen Qian","contact-id":65948,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. Attachments: 23.502 CR2335 (Rel-15) and CR2336 (Rel-16)","secretary_remarks":"Revision r04 of S2-2004899. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10580,"status":"approved","reservation_date":"2020-08-31 14:28:37","uploaded":"2020-08-31 14:29:39","revisionof":"S2-2004899","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2004801","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2006183.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-2006184","title":"SMF aware of UE Reachability after N1N2MessageTransfer error due to UE unreachable","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When the SMF refrains from sending further Namf_Communication_N1N2MessageTransfer message for DL data to the AMF while the UE is unreachable, the SMF subscribes to the AMF event exposure for UE reachability.","secretary_remarks":"Revision of S2-2004900. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10600,"status":"agreed","reservation_date":"2020-09-03 04:31:42","uploaded":"2020-09-03 15:01:14","revisionof":"S2-2004900","revisedto":"","release":"Rel-15","crspec":"23.502","crspecversion":"15.10.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2335.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200671","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2006184.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-2006185","title":"SMF aware of UE Reachability after N1N2MessageTransfer error due to UE unreachable","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: When the SMF refrains from sending further Namf_Communication_N1N2MessageTransfer message for DL data to the AMF while the UE is unreachable, the SMF subscribes to the AMF event exposure for UE reachability.","secretary_remarks":"Revision of S2-2004901. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10620,"status":"agreed","reservation_date":"2020-09-03 04:31:43","uploaded":"2020-09-03 15:01:14","revisionof":"S2-2004901","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.5.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2336.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"SP-200671","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2006185.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-2006186","title":"Stage 3 alignment on UE reachability event","source":"NTT DOCOMO, Nokia, Nokia Shanghai Bell, Ericsson, Huawei","contact":"Atsushi Minokuchi","contact-id":26474,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To clarify description on UE reachability event","secretary_remarks":"Revision r09 of S2-2005544, merging S2-2005381. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10650,"status":"agreed","reservation_date":"2020-09-03 04:31:44","uploaded":"2020-09-03 15:01:14","revisionof":"S2-2005544","revisedto":"","release":"Rel-15","crspec":"23.502","crspecversion":"15.10.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2378.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200671","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2006186.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-2006187","title":"Stage 3 alignment on UE reachability event","source":"NTT DOCOMO, Nokia, Nokia Shanghai Bell, Ericsson, Huawei","contact":"Atsushi Minokuchi","contact-id":26474,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: To clarify description on UE reachability event","secretary_remarks":"Revision r01 of S2-2005547 (mirror to S2-2006186). Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10670,"status":"agreed","reservation_date":"2020-09-03 04:31:45","uploaded":"2020-09-03 15:01:14","revisionof":"S2-2005547","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.5.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2380.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"SP-200671","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2006187.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-2006188","title":"Remove un-necessary End Marker Indication in invocations of Nsmf_PDUSession_Update Request (missing part)","source":"Nokia, Nokia Shanghai Bell, Ericsson, China Mobile, Huawei, HiSilicon","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Align to CT WG4 LS and request: Remove un-necessary End Marker Indication in invocations of Nsmf_PDUSession_Update Request related with UE mobility","secretary_remarks":"Revision r01 of S2-2004844, merging S2-2005196. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10700,"status":"agreed","reservation_date":"2020-09-03 04:31:46","uploaded":"2020-09-03 15:01:14","revisionof":"S2-2004844","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.5.1","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":2330.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-2006188.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-2006189","title":"Clarification on End marker","source":"Huawei, HiSilicon, Nokia, Nokia Shanghai Bell","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To avoid unnecessary Data Notification message, it is proposed that the UPF does not send Data Notification to SMF if the received downlink packet is end marker packets and there is no F-TEID where to send these packets. Instead, the I-","secretary_remarks":"Revision r04 of S2-2005385. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10730,"status":"agreed","reservation_date":"2020-09-03 04:31:47","uploaded":"2020-09-03 15:01:14","revisionof":"S2-2005385","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.5.1","workitem":[{"winame":"ETSUN"},{"winame":"5GS_Ph1"}],"crnumber":2361.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200681","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2006189.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-2006190","title":"Support for DTLS","source":"Qualcomm Incorporated, Nokia, Nokia Shanghai Bell","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Makes text in TS 23.501 normative to align with TS 24.501 Gives reference to TS 24.501","secretary_remarks":"Revision r03 of S2-2005702. Approved","agenda_item_sort_order":5,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10770,"status":"agreed","reservation_date":"2020-09-03 04:31:48","uploaded":"2020-09-03 15:01:14","revisionof":"S2-2005702","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.5.1","workitem":[{"winame":"TEI16"},{"winame":"UPIP_SEC"}],"crnumber":2442.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-2006190.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}]