[{"name":"S2-2102082","title":"LS from RAN WG3: LS to SA2 on Immediate Suspension","source":"RAN WG3","contact":"Zijiang Ma","contact-id":36270,"tdoctype":"LS in","for":"Action","abstract":"In Rel-16, immediate Suspension has been supported in NGAP. That means if the Suspend Request Indication IE is included in the UE CONTEXT RESUME REQUEST message, the AMF shall, if supported, consider that the NG-RAN node is requesting immediate transition to RRC IDLE with Suspend as specified in TS 23.502. If the Suspend Response Indication IE is included in the UE CONTEXT RESUME RESPONSE message, the NG-RAN node shall suspend the UE context, the UE-associated logical NG-connection and the related PDU session contexts and transitions the UE to RRC_IDLE. Thus, there is not additional UE Context Suspend procedure during immediate Suspension case. To support immediate Suspension procedure, RAN WG3 has agreed to introduce Information on Recommended Cells and RAN Nodes for Paging IE and Paging Assistance Data for CE Capable UE IE in NGAP: UE CONTEXT RESUME REQUEST message. Action: RAN WG3 respectfully asks SA WG2 to take the above information into account and update their related specification.","secretary_remarks":"Revision of postponed S2-2100014 from SA2#143E. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10170,"status":"noted","reservation_date":"2021-03-21 13:00:35","uploaded":"2021-03-21 15:42:58","revisionof":"S2-2100014","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"R3-207138","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102082.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102083","title":"LS from RAN WG3: Reply LS on NAS Non delivery for RRC_INACTIVE state","source":"RAN WG3","contact":"Jiancheng SUN","contact-id":62128,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 thanks SA WG2 for the LS on NAS Non delivery for RRC Inactive state. For the second answer, RAN WG3 further discussed how to inform AMF the non-delivery of the non-PDU session related NAS PDU received in the 'PDU Session Resource Setup' and 'Initial Context Setup'. For 'PDU Session Resource Setup', some companies in RAN WG3 still doubt if the scenario is valid, especially considering the following statement in TS 23.502 section 4.2.3.2: 'If the Service Request procedure is triggered by the Network (as described in clause 4.2.3.3) while the UE is in CM-CONNECTED state, only N2 SM information received from SMF is included in the N2 Request.' Question 1: For a UE in RRC_INACTIVE state, is there any use case for AMF to piggyback a non-PDU session related NAS PDU in PDU SESSION RESOURE SETUP REQUEST? For 'Initial Context Setup', the scenario is confirmed in RAN WG3, but we have not reached the consensus on how to inform AMF the non-delivery of the non-PDU session related NAS-PDU in the 'Initial Context Setup Request'. Here are two candidate solutions: - Solution 1: Use NAS NON DELIVERY INDICATION message to indicate the failure of the NAS delivery. - Solution 2: Use the 'Initial Context Setup failure' to implicitly indicate the failure of the NAS delivery. Question 2: Which solution is preferred to inform AMF the non-delivery of the non-PDU session related NAS-PDU in the 'Initial Context Setup Request'?. Action: RAN WG3 would like to further ask SA WG2 the following questions: Q1\/ For a UE in RRC_INACTIVE state, is there any use case for AMF to piggyback a non-PDU session related NAS PDU in PDU SESSION RESOURE SETUP REQUEST? Q2\/ Which solution is preferred to inform AMF the non-delivery of the non-PDU session related NAS-PDU in the 'Initial Context Setup Request'?","secretary_remarks":"Revision of postponed S2-2100015 from SA2#143E. Responses drafted in S2-2102172, S2-2102563 and S2-2102605. Final response in S2-2103216","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10350,"status":"replied to","reservation_date":"2021-03-21 13:00:35","uploaded":"2021-03-21 15:42:58","revisionof":"S2-2100015","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"R3-207170","lsreply":"S2-2103216","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102083.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102085","title":"LS from CT WG1: LS on interworking to 5GS with N26 due to UE\u2019s N1 mode capability disabling\/enabling","source":"CT WG1","contact":"Lin Shu","contact-id":43310,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 has defined disabling and re-enabling of UE's N1 mode capability for 3GPP access (see TS 24.501 subclause 4.9.2). After the UE has disabled its N1 mode capability for 3GPP access, the UE will move to 4G and indicate EPC that N1 mode not supported (i.e. the UE does not support 5GC NAS). With above, CT WG1 has discussed following sceanrio: (1) The UE operating in single-registration mode has disabled its N1 mode capability when registered in 5G and then moves to 4G of the current PLMN with N26 interface supported. (2) The UE initiates an EPS attach or TAU procedure in 4G during which the UE will indicate N1 mode is not supported. (3) Hereafter, the UE requests to establish a new PDN connection in 4G during which the UE will not generate the PDU session ID included in the (e)PCO IE to the network and the network will not include the mapped PDU session parameters (e.g. QoS flow descriptions, Session-AMBR, QoS rules) included in the (e)PCO IE to the UE. (4) The UE re-enables its N1 mode capability in 4G and then moves back to 5G. As in step (3), there is no mapped PDU session parameters included in the PDN connection, this PDN connection cannot be transferred to 5G in step (4). Session continuity for 5GS interworking was broken. CT WG1 would like to ask SA WG2: (1) If in above step (3), a combo PGW-C+SMF was selected for the PDN connection, whether and how to maintain the session continuity for this PDN connection when moving back to 5G? (2) If in above step (3), a standalone PGW was selected for the PDN connection, whether and how to maintain the session continuity for this PDN connection when moving back to 5G?. Action: CT WG1 kindly asks SA WG2 to answer above questions.","secretary_remarks":"Revision of postponed S2-2100037 from SA2#143E. Response drafted in S2-2102233 (withdrawn). Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10400,"status":"postponed","reservation_date":"2021-03-21 13:00:36","uploaded":"2021-03-21 15:42:58","revisionof":"S2-2100037","revisedto":"S2-2103717","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C1-207531","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102085.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102086","title":"LS on stage 3 aspects for Reliable Data Service Serialization Indication","source":"CT WG1","contact":"Vivek Gupta","contact-id":74448,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 has agreed the RDSSI WID in Rel-17 to implement the Reliable Data Service Serialization Indication feature in stage 3, whereas the corresponding stage 2 requirements are in Rel-16. Action: CT WG1 kindly asks TSG SA, TSG CT and SA WG2 to take above into account.","secretary_remarks":"Revision of postponed S2-2100039 from SA2#143E. Response drafted in S2-2102147. CC#1: Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10530,"status":"postponed","reservation_date":"2021-03-21 13:00:36","uploaded":"2021-03-21 15:42:58","revisionof":"S2-2100039","revisedto":"S2-2103718","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, TSG CT, TSG SA","Cc":"CT WG3","lsoriginalls":"C1-207769","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102086.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102087","title":"LS from SA WG4: LS Reply on New service type of NR QoE","source":"SA WG4","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"SA WG4 thanks RAN WG3 for their LS in (R3-205724\/ S4-201460). It is appreciated that RAN WG3 agreed to support Video Streaming, VR, MTSI and MBMS service types in the NR QoE study item, which covers media related services in SA WG4. Currently SA WG4 has only specified QMC functionality (for QoE configuration and reporting) for UMTS and LTE. When the RAN WG3 NR QoE work has concluded, SA WG4 will also expand the specified QMC support to include 5G NR accordingly. Due to the low-latency and high-reliability requirements, XR-related services may require URLLC support in some scenarios, especially for industrial or medical usage, but also for certain entertainment and business applications such as cloud gaming and split rendering. Currently, there are several ongoing XR-related Rel-17 activities in SA WG4, such as ITT4RT, FS_XRTraffic and FS_5GSTAR.","secretary_remarks":"Revision of postponed S2-2100046 from SA2#143E. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10030,"status":"noted","reservation_date":"2021-03-21 13:00:36","uploaded":"2021-03-21 15:42:58","revisionof":"S2-2100046","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"RAN WG2, SA WG5, SA WG2","lsoriginalls":"S4-201576","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102087.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102090","title":"LS from CT WG3: LS on NSI ID on N7 interface","source":"CT WG3","contact":"Abdessamad EL MOATAMID","contact-id":80517,"tdoctype":"LS in","for":"Action","abstract":"CT WG3 has observed that Stage 2 specified the network slice identifier (i.e. NSI ID) as an optional input parameter to be provided by the SMF to the PCF when requesting the creation of an SM Policy Association (i.e. within the Npcf_SMPolicyControl_Create service operation) in the frame of PDU session procedures, both in TS 23.502 (clauses 4.16.4 and 5.2.5.4.2), and TS 23.503 (clause 6.2.1.2). Cf. extract hereinafter from clause 4.16.4 of TS 23.502. '1. The SMF determines that the PCC authorization is required and requests to establish an SM Policy Association with the PCF by invoking Npcf_SMPolicyControl_Create operation (see clause 5.2.5.4.2). The SMF includes the following information: SUPI, PDU Session id, PDU Session Type, S-NSSAI, NSI ID (if available), DNN, DNN Selection Mode, GPSI (if available), Access Type, RAT Type, AMF instance identifier and if available, the IPv4 address and\/or IPv6 network prefix, PEI, User Location Information, UE Time Zone, Serving Network (PLMN ID, or PLMN ID and NID, see clause 5.34 of TS 23.501 [2]), Charging Characteristics, Session AMBR, default QoS information, Trace Requirements, Internal Group Identifier (see TS 23.501 [2], clause 5.9.7).' CT WG3 has not considered this parameter in TS 29.512 (within the Npcf_SMPolicyControl_Create service operation) so far, mainly because it is not specified how the SMF gets \/ is aware of NSI ID allocated for the PDU session and the use case(s) behind it. Therefore, CT WG3 would like to ask SA WG2 for clarification on this point, so as to resolve this remaining misalignment between Stage 2 and Stage 3 specifications: Q1: How does the SMF determine the NSI ID in this context? In this sense, please also clarify the meaning of the mention 'if available'. Q2: What is the foreseen use case behind it? In other words, how this parameter is expected to be used by the PCF in the frame of the Npcf_SMPolicyControl service?. Action: CT WG3 kindly asks SA WG2 to provide answers and clarifications on the above questions and update the related Stage 2 specifications accordingly, if necessary.","secretary_remarks":"Revision of postponed S2-2100056 from SA2#143E. Response drafted in S2-2102220. Final response in S2-2103217","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10580,"status":"replied to","reservation_date":"2021-03-21 13:00:36","uploaded":"2021-03-21 15:42:58","revisionof":"S2-2100056","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"C3-210310","lsreply":"S2-2103217","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102090.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102091","title":"LS from CT WG3: LS on Support of AF instance change","source":"CT WG3","contact":"Yali Yan","contact-id":66362,"tdoctype":"LS in","for":"Action","abstract":"CT WG3 is discussing the requirement on support of AF instance change as described in clause 4.3.6.3 of TS 23.502 Notification of user plane management event procedure. {. . .} CT WG3 has following questions need for further stage 2 clarification: Q1: If the AF needs to update the target AF instance information, does the AF need to trigger the Nnef_TrafficInfluence_Update service operation to the NEF, and the update of AF influence control on traffic routing is delivered to the SMF within the PCC rule via N7? Q2: If answer of Q1 is yes, what's the motivation to use Nnef_TrafficInfluence_AppRelocationInfo to include the target AF instance information? Q3: If answer of Q1 is no, how will the SMF consolidate the target AF information received by Nsmf_EventExposure_AppRelocationInfo with existing PCC rules if the information is not received via N7?","secretary_remarks":"Revision of postponed S2-2100058 from SA2#143E. Response drafted in S2-2102560 and S2-2102933. Final response in S2-2103220","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10880,"status":"replied to","reservation_date":"2021-03-21 13:00:36","uploaded":"2021-03-21 15:42:58","revisionof":"S2-2100058","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C3-210388","lsreply":"S2-2103220","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102091.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102092","title":"LS from CT WG3: LS on QoS monitoring control for Service Data Flows","source":"CT WG3","contact":"Xiaoyun Zhou","contact-id":77294,"tdoctype":"LS in","for":"Action","abstract":"As defined in clause 6.1.3.21 of TS 23.503, the PCF can generates the authorized QoS Monitoring policy for the service data flow based on the QoS Monitoring request if received from the AF and provide it within the PCC rule to SMF. As defined in clause 5.33.3.2 of TS 23.503, the SMF can derive the monitoring parameters based on the authorized QoS Monitoring policy received from the PCF and provide them to the PSA UPF and NG-RAN to activate the end to end UL\/DL packet delay measurement between UE and PSA UPF for a QoS flow. It is possible that the PCF generates more than one PCC rules including different QoS Monitoring policies based on the requests from the same or different AF(s). CT WG3 would like to ask SA WG2 following question: Q: If the QoS Monitoring policies are different, e.g. the delay thresholds for downlink packet are different among the PCC rules, but the SMF binds the PCC rules to the same QoS flow according to the QoS flow binding mechanism defined in clause 6.1.3.2.4 of TS 23.503, how does the SMF derive the monitoring parameters for the QoS flow?. Action: CT WG3 kindly asks SA WG2 to provide answers and update the related Stage 2 specifications accordingly, if necessary.","secretary_remarks":"Revision of postponed S2-2100059 from SA2#143E. Response drafted in S2-2102382. Final response in S2-2103224","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11020,"status":"replied to","reservation_date":"2021-03-21 13:00:36","uploaded":"2021-03-21 15:42:58","revisionof":"S2-2100059","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"C3-210409","lsreply":"S2-2103224","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102092.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102093","title":"LS from RAN WG3: E-RABs that cannot be handed over to 2G\/3G or 5G","source":"RAN WG3","contact":"Nianshan Shi","contact-id":45408,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 has discussed the below issue: when perform SRVCC from 4G to 3G, if the UE was earlier handed over from 5G and having the PS bearer (no voice) from 5G, eNB would perform SRVCC with two Iu connections (Iu-CS and Iu-PS) and informs the target RNC. But the Forward Relocation Request message may never be sent to the target node due to the QoS flow established in 5G does not contain Transaction Identifier (TI) and this TI is mandatory in the Forward Relocation Request message. This causes the SRVCC delay and in the worst case could even cause failure. The issue is general, with the introduction of NR, the PS bearers set up at 5G may not be able to handover to 2G\/3G or vice versa, e.g.: 5G without TI cannot be handed over to 2\/3G. Similarly, some E-RABs from 2G\/3G cannot be handed over to 5G. The mobility procedure may be delayed and in the worst case could fail. RAN WG3 would like to ask SA WG2 to investigate how we can solve the problem,. Action: RAN WG3 kindly asks feedback and guidance from SA WG2.","secretary_remarks":"Revision of postponed S2-2100108 from SA2#143E. Responses drafted in S2-2102278 and S2-2102751. Final response in S2-2103061","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10710,"status":"replied to","reservation_date":"2021-03-21 13:00:36","uploaded":"2021-03-21 15:42:58","revisionof":"S2-2100108","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1, CT WG4","lsoriginalls":"R3-211273","lsreply":"S2-2103061","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102093.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102098","title":"LS from SA WG5: LS Reply on QoS Monitoring for URLLC","source":"SA WG5","contact":"Yizhi Yao","contact-id":66963,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks RANs for the LS reply on QoS Monitoring for URLLC. In the LS, RAN WG3 answered that the measurements related to the RAN part of the packet delay, excluding the UL D1 packet delay, can be collected by the OAM by means of the following measurements defined in TS28.552: - D2 (DL delay on gNB-DU), referring to Average delay in RLC sublayer of gNB-DU in TS 28.552, \u00a7 5.1.3.3.3. - D3 (DL delay on F1-U), referring to Average delay on F1-U in TS 28.552, \u00a7 5.1.3.3.2. - D4 (DL delay in CU-UP), referring to Average delay DL in CU-UP in TS 28.552, \u00a7 5.1.3.3.1. SA WG5 would like to provide further clarification that the D2, D3 and D4 measurements defined by SA WG5 and referenced by RAN WG3 are the average delays, adding them up could get the average delay between NG-RAN and UE, however using these measurements cannot get the distribution of packet delays which are also defined in TS 28.552 and based on RAN part UL packet delay result excluding the UL D1 packet delay: - Distribution of UL packet delays between NG-RAN and UE, in clause 5.1.1.1.7 of TS 28.552. - Distribution of UL packet delays between PSA-UPF and UE, in clause 5.4.9.2.2 of TS 28.552.","secretary_remarks":"Revision of postponed S2-2100153 from SA2#143E. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10160,"status":"noted","reservation_date":"2021-03-21 13:00:36","uploaded":"2021-03-21 15:42:58","revisionof":"S2-2100153","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"SA WG2, RAN WG2","lsoriginalls":"S5-211350","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102098.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102102","title":"LS from SA WG4: LS on Server Domain Name Usage for Application Traffic Detection","source":"SA WG4","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"SA WG4 has specified the 5G Media Streaming (5GMS) architecure within Release 16, which enables usage of some Network Features using N5 or N33. For dynamic policy invocation, an ASP can configure one or more Policy Templates within the 5GMSd AF, which can then be individually invoked by a 5GMSd Client. The 5GMSd Client provides a Service Data Flow description (IP Packet Filter Set or server domain name(s)) when activating a dynamic policy to be applied by the 5GMSd AF. The 5GMSd AF then acts as AF towards the PCF or NEF. For using server domain names within a Service Data Flow description, SA WG4 understands that the 5GMSd AF first needs to provision a Packet Flow Description (PFD) containing a domain name using the PFD Management API, and then it selects the provisioned PFD (part of a PfdData object) using either the N5 Npcf_PolicyAuthorization API or else via the N33 AfSessionWithQos or ChargeableParty APIs. Note that a single 5GMSd AF might provision multiple PfdData objects, each containing one or more PFDs. Furthermore, SA WG4 understands that in the subsequent dynamic policy invocation procedures defined for the 5FMSd AF, previously provisioned PFDs can be referenced as an alternative traffic detection parameter to full flow descriptions. - When the Policy Template relates to QoS, the 5GMSd AF may use the Nnef_AFsessionWithQoS service as defined in TS 23.502 [3] clause 5.2.6.9. (The complete call flow is described in TS 23.502 clause 4.15.6.6); - When the Policy Template relates to a different charging scheme, the 5GMSd AF may use the Nnef_ChargeableParty service as defined in TS 23.502 [3] clause 5.2.6.8. Based on the above assumptions, SA WG4 would like to ask the following clarification questions to SA WG2 and CT WG3: 1: When invoking the Nnef_AFSessionWithQoS method, is it possible to use the application identifier (as a reference to a set of PFDs) instead of the flow description? 2: What is the relationship between the AF Identifer (SCS\/AS ID in 4G) and the AF application ID and\/or the application identifier? 3: When invoking a particular policy using Nnef_AFSessionWithQoS, is it possible to provide the DNN, the S-NSSAI, and\/or a reference to the server domain name for the purposes of traffic identification? NOTE: The same questions apply to Nnef_ChargeableThird Party API. Action: SA WG4 kindly asks SA WG2 to provide feedback for question 1 and question 3.","secretary_remarks":"Revision of postponed S2-2100262 from SA2#143E. Responses drafted in S2-2102174 and S2-2102219. Final response in S2-2103228","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11080,"status":"replied to","reservation_date":"2021-03-21 13:00:36","uploaded":"2021-03-21 15:42:58","revisionof":"S2-2100262","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG3","Cc":"","lsoriginalls":"S4-210311","lsreply":"S2-2103228","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102102.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102103","title":"LS from CT WG3: LS on Session Management Policy Data per PLMN","source":"CT WG3","contact":"Apostolos Papageorgiou","contact-id":81926,"tdoctype":"LS in","for":"Action","abstract":"In the procedure for SM Policy Association Establishment (TS 23.502 clause 4.16.4), SA WG2 has specified that in LBO, the V-PCF interacts with the UDR of the VPLMN but the retrieval of data using Nudr_DM_Query\/Subscribe from the UDR (or V-UDR) is specified per subscriber, as per the text highlighted below {. . .} In the LBO case, the Session Management Policy Data at the VPLMN cannot be stored per subscriber, since the subscribers of the HPLMN are not managed by the VPLMN, but the VPLMN can store Session Management Policy Data that are applicable to all the subscribers of a certain HPLMN. Although the above highlighted text could imply that the V-PCF can retrieve subscriber related data (which includes Session Management Policy Data) from the V-UDR, the key of Session Management Policy Data in the UDR is the SUPI. Based on the above, CT WG3 would like to ask the following clarification question to SA WG2: Q1. Can the UDR of the VPLMN store PDU Session policy control data per HPLMN? Q2. Is all the PDU Session policy control subscription information (specified in TS 23.503 Table 6.2-2) supported in the LBO scenario?. Action: CT WG3 kindly asks SA WG2 to provide feedback for questions Q1 and Q2 and update accordingly the specifications as necessary.","secretary_remarks":"Revision of postponed S2-2101800 from SA2#143E. Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10180,"status":"postponed","reservation_date":"2021-03-21 13:00:36","uploaded":"2021-03-21 15:42:58","revisionof":"S2-2101800","revisedto":"S2-2103722","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C3-211469","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102103.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102104","title":"LS from CT WG1#128e: LS on mandate to provide any PLMN entry in the non-3GPP access node selection information in Rel-16","source":"CT WG1","contact":"John-Luc Bakker","contact-id":37326,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 thanks SA WG2 for the response LS on the mandate to provide 'any PLMN' entry in the non-3GPP access node selection information (S2-2008009\/C1-207058), informing that the mandate of including the 'any PLMN' entry has been relaxed in Rel-17. CT WG1 would like to request that SA WG2 also relax this mandate in Rel-16 to simplify the 5GC non-3GPP access deployments and implementations that use Rel-16 as the baseline. Action: CT WG1 asks SA WG2 group to relax the mandate of including the 'any PLMN' entry in Rel-16","secretary_remarks":"Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10190,"status":"postponed","reservation_date":"2021-03-21 15:39:26","uploaded":"2021-03-21 15:42:58","revisionof":"","revisedto":"S2-2103723","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C1-211203","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102104.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102105","title":"LS from CT WG1: Reply LS on clarification on support of MAP messages at the UDM for SMS in 5GS","source":"CT WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 would like to thank SA WG3-LI for their question on MAP support in UDM for SMS service in 5GS. CT WG1 has updated TS 23.040 by adding some clarification regarding how the UDM supports the MAP and Diameter interfaces for SMS service in 5GS. Please find the updates in the attached CR (C1-211209).","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10040,"status":"noted","reservation_date":"2021-03-21 15:39:26","uploaded":"2021-03-21 15:42:58","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3LI","Cc":"SA WG2, CT WG4","lsoriginalls":"C1-211211","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102105.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102106","title":"Reply LS on User Plane Integrity Protection for eUTRA connected to EPC","source":"CT WG1","contact":"Lena Chaponniere","contact-id":38080,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 thanks SA WG3 for their LS on User Plane Integrity Protection for eUTRA connected to EPC. CT WG1 would like to provide the following answers to the questions addressed to CT WG1: - Question c) from SA WG3: (RAN 3 and CT 1) is a MME mandated to copy all the EEA\/EIA bits from NAS signalling into the S1-AP signalling? Response from CT WG1 to Question c): The S1-AP signalling is out of CT WG1's remit, so CT WG1 would like to defer to RAN WG3 for this question. - Question e) from SA WG3: (SA WG2 and CT WG1) SA WG3 decides UE to send an indication to the network that the UE support UP IP with eNB, one of options is to reuse EEA\/EIA bits in UE EPS Security Capability (e.g. reuse EIA7 to indicate UE support UP IP with eNB), so that both eNB and MME can use the UE EPS Security Capability to know UE support UP IP with eNB. Does there any issue on this? Response from CT WG1 to Question e): The EIA7 bit in the UE network capability IE is assigned to signal the support of 'EPS integrity algorithm EIA7'. There is no specified use in the NAS protocol for this bit and it is signalled for interpretation and use in other parts of the system. Thus, from a pure NAS protocol perspective it would be possible to change the meaning of this bit. CT WG1 cannot assess whether this leads to problems outside of NAS protocol. To re-define the EIA7 bit for this purpose will disable the use of the EEA7 bit for signaling the support of 'EPS encryption algorithm EEA7' as well.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10050,"status":"noted","reservation_date":"2021-03-21 15:39:26","uploaded":"2021-03-21 15:42:58","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG2, CT WG4, RAN WG3, RAN WG2","lsoriginalls":"C1-211461","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102106.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102107","title":"LS from CT WG4: LS on Group Subscriptions","source":"CT WG4","contact":"Bruno Landais","contact-id":68755,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 would like to get clarifications on the following aspects: Q1: Does a group subscription (with or without a maximum number of reports) created in UDM by NEF apply to group members that register to the network after the group subscription is created? Does a group subscription (with or without a maximum number of reports) created in AMF by UDM apply to group members that register or move to the AMF after the group subscription is created? Q2: If the answer of Q1 is yes, how can the NEF determine that the reporting for the group is complete? Q3: If the answer of Q1 is no, group members registered in the network and their serving AMFs are typically different when the group subscription is created and deleted. So is the requirement 'the UDM unsubscribes the monitoring event(s) to all AMF(s) serving the UEs belonging to that group' in clause 4.15.3.2.3 correct? Q4: During an inter-AMF mobility of a group member of a group subscription in S-AMF, does the group subscription that T-AMF creates, when there was no corresponding group subscription in T-AMF, only apply to the group member just moving from S-AMF, and not to other group members registered in T-AMF? Q5: During an inter-AMF mobility of a group member of a group subscription in S-AMF, should the group subscription be signalled to T-AMF only if the maximum number of reports for this UE was not already reached in S-AMF and the maximum duration did not already expire? Q6: If the group subscription expires in an AMF as specified in clause 4.15.1 of TS 23.502, any later group unsubscribe request from NEF\/UDM as specified in clause 4.15.3.2.3 will be rejected by the AMF since the group subscription should no longer exist. Is this the intended behaviour?. Action: CT WG4 kindly asks SA WG2 group to answer to the above questions.","secretary_remarks":"Responses drafted in S2-2102173, S2-2102404 and S2-2102845. Final response in S2-2103229","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11180,"status":"replied to","reservation_date":"2021-03-21 15:39:26","uploaded":"2021-03-21 15:42:58","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C4-211369","lsreply":"S2-2103229","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102107.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102108","title":"LS from CT WG4: Reply LS on Additional Clarifications on LI requirements applicable to SNPNs","source":"CT WG4","contact":"Waqar Zia","contact-id":86053,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 thanks SA WG2 for their reply LS on Additional Clarifications on LI requirements applicable to SNPNs. Correspondingly, CT WG4 has agreed to the attached CR implementing Visited Country FQDN for SNPN N3IWF Selection in 3GPP TS 23.003. CT WG4 has made the following additional observation: the Visited Country FQDN for SNPN N3IWF Selection may not be unique if locally assigned NIDs are used. This means that a visited country cannot enforce the selection of an N3IWF in this country for SNPNs that use a locally assigned NID. A visited country can however configure an FQDN that does not resolve to an IP address for such SNPNs . CT WG4 has added this observation in the attached agreed CR as a note, and would like to request SA WG2 to provide feedback if any. Action: CT WG4 kindly asks SA WG2 to note the above indicated additional observation and to provide feedback if any. Additionally, CT WG4 requests SA WG2 to incorporate it in corresponding stage-2 as needed.","secretary_remarks":"CC#1: Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11230,"status":"postponed","reservation_date":"2021-03-21 15:39:26","uploaded":"2021-03-21 15:42:58","revisionof":"","revisedto":"S2-2103724","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG3LI, CT WG1","lsoriginalls":"C4-211519","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102108.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102109","title":"LS from CT WG4: LS on N3IWF FQDN for emergency service","source":"CT WG4","contact":"Xingyue Zhou","contact-id":42680,"tdoctype":"LS in","for":"Action","abstract":"There is a remaining editor's note in TS 23.003: 'Editor's note: It is FFS whether N3IWF FQDN for emergency service is supported', C4-211031 which is postponed proposes to remove this editor note directly since there is no additional requirement for an N3IWF to support emergency services comparing with an N3IWF for normal services. However, it is found that the statements on selection of N3IWF for emergency services as quoted below in clause 6.3.6.4 of TS 23.501 are not clear: { . . .} CT WG4 would like to ask SA WG2: Question 1): Which one does the highlighted 'Operator Identifier Emergency FQDN' and 'Visited Country Emergency FQDN' refer to? a) emergency ePDG FQDN b) either emergency ePDG FQDN or emergency N3IWF FQDN Question 2): If the answer to Q1) is 'b', why does emergency N3IWF FQDN need to be defined?. Action: CT WG4 kindly asks SA WG2 to answer the questions above and consider to provide corresponding clarifications in clause 6.3.6.4 of TS 23.501.","secretary_remarks":"Responses drafted in S2-2102156, S2-2102911 and S2-2102925. CC#1: Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11240,"status":"postponed","reservation_date":"2021-03-21 15:39:26","uploaded":"2021-03-21 15:42:58","revisionof":"","revisedto":"S2-2103725","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1","lsoriginalls":"C4-211521","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102109.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102110","title":"LS from CT WG4: LS on the support of L2TP with CUPS","source":"CT WG4","contact":"yong yang","contact-id":59744,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 has studied the Sx\/N4 extensions to support L2TP tunnelling over SGi\/N6 interface with Control Plane and User Plane Separation (CUPS) as part of WI BEPoP (BEst Practice of PFCP) and CT WG4 has agreed the following conclusions (as documented in the attachment): - the PFCP protocol extensions to support L2TP tunneling over N6\/SGi for 5GC\/EPS is to be standardized based on the solution#8 as described in 6.8 in Rel-17. - The normative requirements related to transfer L2TP Tunnel Information and L2TP Session Information from the CP function to the UP function together with a general description of L2TP function is to be specified in 3GPP TS 29.244 [3] based the clauses 6.8.1, 6.8.2 and 6.8.3. Action: CT WG4 kindly requests SA WG2 to review the solution and provide feedback if any and update their specification if necessary.","secretary_remarks":"Response drafted in S2-2102139. Final response in S2-2103232","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11350,"status":"replied to","reservation_date":"2021-03-21 15:39:26","uploaded":"2021-03-21 15:42:58","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG3","Cc":"SA WG3","lsoriginalls":"C4-211624","lsreply":"S2-2103232","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102110.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102111","title":"LS from CT WG4: LS on update a Binding Indication for multiple contexts","source":"CT WG4","contact":"yong yang","contact-id":59744,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 has agreed to introduce enhancements to the binding procedures to support updating a binding indication for a group of resources\/contexts by sending one single notification request towards a given peer NF service instance. This may be used e.g. in scenarios during which a group of resources needs to be taken over by a different NF within an NF set, to reduce signaling, latency, improve load rebalancing among alternative NFs, avoid the need for redirections when multiple consumers (e.g. AMF and PCF) would reselect different alternative NFs at the same time, and avoid potential overload in the database storing all the shared contexts. Action: CT WG4 kindly requests SA WG2 to review the solution and provide feedback if any and update their specification if necessary.","secretary_remarks":"Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10200,"status":"postponed","reservation_date":"2021-03-21 15:39:26","uploaded":"2021-03-21 15:42:58","revisionof":"","revisedto":"S2-2103726","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C4-211709","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102111.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102112","title":"LS from CT WG4: LS Response on Clarification on support of MAP messages at the UDM for SMS in 5GS","source":"CT WG4","contact":"Qingfen Liu","contact-id":79904,"tdoctype":"LS in","for":"Information","abstract":"CT WG4 thanks SA WG3-LI for the LS asking clarification on support of MAP messages at the UDM for the SMS in 5GS in stage 3. CT WG4 agreed the attached CR to TS 29.002 (MAP) to indicate that the UDM may support the MAP interface to the SMS-GMSC\/SMS-Router. In deployments where the UDM supports a MAP interface towards the SMS-GMSC\/SMS-Router, the UDM should be understood to have an integrated\/collocated HLR component that handles the MAP signalling. SMS-GMSCs and SMS-Router are not aware and do not need to be aware whether they are talking to a standalone HLR or to an HLR that is integrated\/collocated with an UDM.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10060,"status":"noted","reservation_date":"2021-03-21 15:39:26","uploaded":"2021-03-21 15:42:59","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3LI","Cc":"SA WG2, CT WG1","lsoriginalls":"C4-211721","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102112.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102113","title":"LS from CT WG4: LS on Information on the port number allocation solutions","source":"CT WG4","contact":"Giorgi Gulbani","contact-id":82292,"tdoctype":"LS in","for":"Information","abstract":"CT WG4 was tasked by TSG CT (see CP-201316) to specify alternative solutions for port allocation for new 3GPP interfaces from Rel-17 onwards. CT WG4 work on FS_PortAl SID (Unique identifier: 890002) has reached the first milestone. CT WG4 will send TR 29.835 v0.4.0 for information to CT plenary meeting #91e. TR 29.835 will be used as an input for another TR 29.941, which will provide guidelines for selecting solutions. CT WG4 would like to ask RAN WG2, RAN WG3, SA WG4, CT WG3 and SA WG5 WGs to kindly review TR 29.835 v0.4.0 and share their views with CT WG4. Feedback from RAN WGs will be taken into account when finalizing TR 29.835. Preferred solutions will also be documented in TR 29.941, which will be maintained.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10070,"status":"noted","reservation_date":"2021-03-21 15:39:26","uploaded":"2021-03-21 15:42:59","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3, SA WG4, CT WG3, SA WG5","Cc":"TSG SA, TSG CT, TSG RAN, SA WG2","lsoriginalls":"C4-211806","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102113.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102114","title":"LS from CT WG4: LS on Requirement on Support of VxLAN Tunnelling","source":"CT WG4","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 is now working on the work item 'BEPoP', aiming to improve the interoperability between SMF and UPF especially on the key features which are required for the vertical scenarios. During the study, CT WG4 has identified one issue on support of Ethernet type communication as following: In numbers of vertical environments, e.g. factories, mines and so on, there are lots of devices working on Layer 2 and which may do not have the TCP\/IP protocol stack, where the Ethernet PDU session is used. However, operators have reported the issues that the chipsets and modules are not mature enough to support the Ethernet PDU session access yet and the market foreground is not optimistic. And in order to meet the existing requirements from industrial field, there exist a temporary solution which is normally used in some pilot industrial 5G project (see attachment in C4-211817). This temporary solution requires a pair of additional equipment to be deployed between the terminal and application server which makes the network more complex. It's hard for customer to accept it as a commercial solution. One possible 5GC solution is to set up a VxLAN tunnel between the UE(CPE) and the UPF. (see attachment in C4-211817). Potential stage-2 impacts are foreseen regarding this solution. Since the vertical scenarios are major parts of 5G services, and there are existing requirements from the field, from operator point of view it is desirable to complete the work within Rel-17 timeframe. It is also recognized that SA WG2 has a really tight schedule for Rel-17, so if SA WG2 agrees CT WG4 to study on this topic within BEPoP work item including the potential stage-2 impacts and informs SA WG2 about the outcome of the discussion for ratification. Action: CT WG4 kindly asks SA WG2 to take the information above into account, and provide feedback on: 1) Whether SA WG2 is able to arrange the work on this issue as soon as possible; and if not 2) Whether SA WG2 will grant CT WG4 to study this issue within BEPoP work item including the potential stage-2 impacts.","secretary_remarks":"Responses drafted in S2-2102601, S2-2102824, S2-2102868 and S2-2102929. Final response in S2-2103236","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11500,"status":"replied to","reservation_date":"2021-03-21 15:39:26","uploaded":"2021-03-21 15:42:59","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG5","lsoriginalls":"C4-211827","lsreply":"S2-2103236","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102114.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102117","title":"LS from SA WG1: Reply LS on extraterritorial use of MCC for satellite access","source":"SA WG1","contact":"Francesco Pica","contact-id":57089,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 thanks CT WG1 for their LS and provides some answers below. SA WG1 would like to note that the responsibility for the international identification plan for public networks and subscriptions (including allocation and usage of MCC+MNC) is within the ITU-T. Question 1: Is the PLMN X allowed to use the MCC corresponding to Country A as the MCC of its PLMN ID in the system info broadcast to offer service to UEs located in Country B or Country C, or must the PLMN X use an MCC in the range of 9xx? SA WG1 Answer 1: SA WG1 believes that the above question should be addressed by ITU-T. Question 2: Could SA WG1 outline if there are any use cases where in such a scenario it is allowed that the PLMN X is using a country specific MCC rather then an MCC in the range of 9xx?' SA WG1 Answer 2: None of the requirements in TS 22.261 cover, or preclude, the scenario described in this liaison from CT WG1, and no use case in TR 22.822 addresses the use of country specific MCC in such a scenario. SA WG1 specification TS 22.261 specifies satellite access networks (e.g. satellite NG-RAN). Per clause 6.3.2.3 of TS 22.261, a satellite NG-RAN can be combined with other terrestrial radio access networks under a common core network (see also SA WG1 LS on PLMN-RAT selection, in S1-204379). Clause 6.21.2 of TS 22.261 also includes a requirement that a 5G satellite access network shall support NG-RAN sharing. Question 3: Is this ITU-T E212 Annex E applicable for NTN network deployments? If yes is it recommended as general solution for extra-territorial NTN, or just under certain conditions? SA WG1 Answer 3: SA WG1 believes that the above question should be addressed by ITU-T.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10080,"status":"noted","reservation_date":"2021-03-21 15:39:26","uploaded":"2021-03-21 15:42:58","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG2, RAN WG2, SA WG3","lsoriginalls":"S1-210358","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102117.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102118","title":"LS from SA WG1: Reply LS on clarification on problematic UAV","source":"SA WG1","contact":"Francesco Pica","contact-id":57089,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 would like to respond to SA WG6 with the following answers: Question 1: From a general perspective, any UAV\/UAV controller deviating from its expected operations is a problematic UAV. What is the definition of a 'problematic UAV\/UAV Controller' in a 3GPP context? Answer 1: SA WG1 has agreed to clarify the current requirement, see corresponding CR to 22.125 attached. Question 2: Are there specific use cases or examples of data needed to be exchanged between the UTM and the 3GPP system for this requirement? Answer 2: Per SA WG1 understanding, the 3GPP system may be able to monitor and expose UAV related information towards the UTM, which may help the UTM to detect UAV abnormalities. Please see clause 6.2 of TS 22.125.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10090,"status":"noted","reservation_date":"2021-03-21 15:39:26","uploaded":"2021-03-21 15:42:58","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"SA WG2, ACJA","lsoriginalls":"S1-210359","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102118.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102120","title":"Reply LS on 5MBS progress and issues to address","source":"SA WG3","contact":"Longhua Guo","contact-id":80179,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 thanks RAN WG2 for their LS (R2-2102480) on 5MBS progress. SA WG3 is working on the study item (TR 33.850) on the security aspects of 5MBS. Hopefully, the study will be finalized no later than SA WG3#104 meeting in August.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10100,"status":"noted","reservation_date":"2021-03-21 15:39:26","uploaded":"2021-03-21 15:42:58","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"RAN WG3, SA WG4, SA WG2","lsoriginalls":"S3-211313","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102120.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102121","title":"Reply LS on selecting a PLMN not allowed in the country where a UE is physically located","source":"SA WG3LI","contact":"Mark Canterbury","contact-id":70749,"tdoctype":"LS in","for":"Information","abstract":"SA WG3LI thanks CT WG1 for seeking resolution on the following questions (taken from C1-210437): Question 1: Can a UE using satellite access select a PLMN not allowed in the country where the UE is physically located? Question 2: If the answer to Question 1 is yes, what are the services that a UE can obtain by a PLMN not allowed in the country where the UE is physically located? SA WG3LI would like to clarify the following assumptions as part of their answer: - The land mobile UE is within the borders of a territory (not e.g. maritime access from international waters or aeronautical access) such that it can be considered subject to the laws and regulations of that territory - That those laws and regulations forbid the PLMN from serving the UE in question (this appears to be implied by Question 1, but SA WG3LI wishes to clarify it) SA WG3LI notes that questions on when or why access to a PLMN may be forbidden in a particular country are, in general, outside the scope of SA WG3LI, and may be better referred to other groups e.g. ITU. However, under these assumptions, SA WG3LI believes that the guiding principle should be that the UE is subject to the laws and regulations of the territory in which it is located. The fact that a UE technically can use satellite access should not provide a way of circumventing those laws and regulations. If the UE is capable of determining whether the PLMN is allowed in the territory, then SA WG3LI believes the answers are as follows: Question 1: No Question 2: None (with the possible exception of emergency calling - this should be referred to SA WG1) If, as SA WG3LI believes is more likely, the UE requires some interaction with the PLMN for them to collectively determine whether the PLMN is allowed to serve the UE, then the answers are as follows: Question 1: Yes, but only to the extent required for the PLMN to determine whether the UE is permitted to be served by it according to the laws and regulations of the territory in which the UE is located. The PLMN is responsible for denying access if the UE is not permitted to be served by it. Satellite access for a PLMN does not create additional exceptions to the national roaming regulation or to PLMN selection when a UE is roaming. Question 2: None (with the possible exception of emergency calling - this should be referred to SA WG1) SA WG3LI recognises that there are likely to be practical difficulties in implementing this restriction, including: - Difficulties in determining UE location sufficiently accurately - UEs in regions where borders are disputed However, such difficulties do not remove the requirement for 3GPP networks to ensure that UE's usage and access conditions comply with the laws and regulations applicable to the UE. LI requirements may be a factor in the PLMN's determination of whether it can serve the UE but under no circumstances shall the PLMN reveal to the UE any information about the LI capabilities of the PLMN. If the UE is permitted access to the PLMN, SA WG3LI wishes to highlight that the PLMN is then subject to the same LI requirements as terrestrial accesses e.g.. that the PLMN can be required to perform LI in the country in which the UE is located.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10110,"status":"noted","reservation_date":"2021-03-21 15:39:26","uploaded":"2021-03-21 15:42:58","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG1, SA WG2","lsoriginalls":"S3i210129","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102121.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102122","title":"LS from SA WG5: LS reply from 3GPP SA5 to GSMA on 5G Operator Platform Telco Edge proposal","source":"SA WG5","contact":"Joey Chou","contact-id":45463,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to thank GSMA for the LS 'New Whitepaper: 'Operator Platform Telco Edge proposal''. SA WG5 is working on the edge computing management and orchestration to support relevant edge computing works in SA WG2 and SA WG6 WGs. Rel. 17 TR 28.814 'Management and orchestration; Study on enhancements of edge computing management' at https:\/\/www.3gpp.org\/DynaReport\/28814.htm, defines the management solutions to enable ASP (Application Service Provider) to deploy the EAS (Edge Application Server) that implements the server function of an edge application in the edge data networks. TR 28.814 also defines performance assurance solutions to allow ASP to monitor the EAS performance. The requirements, as described in GSMA's white paper, may be considered in the study. SA WG5 would keep GSMA updated about the progress of the study. SA WG5 likes to collaborate with GSMA to address the requirements related to the deployment and management of edge computing.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10120,"status":"noted","reservation_date":"2021-03-21 15:39:26","uploaded":"2021-03-21 15:42:58","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA","Cc":"SA WG2, SA WG6","lsoriginalls":"S5-212319","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102122.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102124","title":"LS from SA WG6: LS on slicing management aspects in relation to SEAL","source":"SA WG6","contact":"Omar Elloumi","contact-id":82490,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 has endorsed a study item (as per S6-210708) pertaining Network Slice Capability Exposure for Application Layer Enablement. SA WG2 has defined the northbound APIs of NEF which already include some slice related exposure abilities at UE\/session level. SA WG5 has already defined support of the exposure capability of MnS related to slices. Besides these existing initiatives, there exists gaps between management of network slices and their utilization by the vertical applications. Specifically to support end-to-end network services, application layer and network layer needs to coordinate (e.g. related modification of resource or policies) Through this LS we would like to seek the views of SA WG5 as regards the exposure of slicing management aspects to SEAL (Service Enabler Architecture Layer for Verticals - TS 23.434) as a means to address requirements from third party applications. We would also like to request SA WG5 views about interactions with ongoing work in SA WG5, in particular: . - TS 28.857 which describes how an operator, as NPN service (built on network slice as a service) provider, expose management capability (through APIs) to a 3rd party NPN customers based on business objectives of the customer - FS_MNSAC which investigates how 3GPP management system control the access\/exposure of management capability to internal or external consumers. Some SA WG6 members highlighted the need to coordinate with SA WG5 to avoid overlapping specifications and ensure complementary approaches.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10130,"status":"noted","reservation_date":"2021-03-21 15:39:26","uploaded":"2021-03-21 15:42:58","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"SA WG2","lsoriginalls":"S6-210709","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102124.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102128","title":"LS from 5G-ACIA: 5G capabilities exposure for factories of the future - revised","source":"5G-ACIA","contact":"Andreas Mueller","contact-id":81087,"tdoctype":"LS in","for":"Action","abstract":"5G-ACIA published a white paper in June 2020 on the exposed 5G capabilities that are needed by factory operators to manage and maintain industrial 5G devices and 5G Non-Public Networks (NPN) in a simple and efficient manner. That white paper has now been enhanced to include additional capabilities and some clarification to the capabilities and functions from the previous version of the white paper. In particular, device-centric requirements have been clarified and a few new ones added in accordance with SA WG1 requirements of Release 17. Concerning net-work-centric requirements, network monitoring have been detailed in the Annex of the white paper. Also, the Annex now lists parameters for QoS monitoring. Since 5G-ACIA believes that these service exposure requirements are valuable to be considered in ongoing work in 3GPP, we would like to make this new white paper availa-ble to you: - White paper title: Exposure of 5G capabilities for connected industries and automa-tion applications - Link www.5g-acia.org\/publications - PDF copy: attached to this liaison statement 5G-ACIA would be eager to receive 3GPP's feedback on these new exposure interface requirements and related Stage-2 and Stage-3 work. Action: 5G-ACIA would like to respectfully request SA WG1, WG2, WG3 and WG6 to consider the identified requirements as captured in the updated whitepaper and to pro-vide feedback to 5G-ACIA concerning of how the identified new requirements can be ad-dressed in Rel-17 or future releases.","secretary_remarks":"Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10210,"status":"postponed","reservation_date":"2021-03-31 14:12:25","uploaded":"2021-03-31 14:39:29","revisionof":"","revisedto":"S2-2103727","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG2, SA WG3, SA WG6","Cc":"TSG SA, SA WG5, CT WG3, ...","lsoriginalls":"5G-ACIA_LS_3GPP_Exposure_18032021","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102128.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102129","title":"LS from GSMA Operator Platform Group on edge computing definition and integration","source":"GSMA OPG","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"Introduction: The GSMA, one of the Market Representation Partners of 3GPP and participant of ETSI ISG MEC, has launched a project, Operator Platform, to define a platform to expose and monetize network and services capabilities such as edge computing, network slicing or IP COMs. The first focus set for this activity is to define architectural requirements and concept for Telco Edge Cloud. After having issued a white paper to outline a common concept agreed among operators, Operator Platform Group has been created to define architectural capabilities required to achieve the agreed objective and identify the actions to be taken by the industry to ensure a full standardisation and development of the operator platform. Discussion: The whitepaper's [3] intention is aiming all the Industry, including operators, vendors, OEMs and service providers, to define a common solution for network and services capability exposure. As a first phase, GSMA is drafting a PRD (Permanent Reference Document) that will provide an end-to-end (E2E) definition of the Operator Platform for edge computing support allowing the GSMA to ensure delivery of this E2E vision across the Industry and the different SDOs. {. . .} The main objective of the GSMA is to ensure a full detailed definition of these interfaces within the industry in order to meet the operator platform expectation. {. . .} Actions: Based on the above mapping the GSMA wishes to start a multi-party discussion with ETSI ISG and 3GPP in order to: - 3GPP and ETSI ISG to confirm which specific working group will interface with GSMA OPG. - Ensure standard development of the defined interfaces and avoid duplication of works or divergences between SDOs. - Ensure that there is only one reference definition per interfaces in the industry. - Build the governance and collaboration model between GSMA, 3GPP, ETSI ISG to guarantee E2E delivery of the Operator Platform standardisation. The 3GPP\/ETSI groups are then invited to confirm their interest in ensuring their alignment in developing the Operator Platform concept in their respective SDOs. In case of positive answer, GSMA is willing to organise a workshop in order to close the collaboration model and define next steps.","secretary_remarks":"Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10140,"status":"postponed","reservation_date":"2021-03-31 14:12:31","uploaded":"2021-03-31 14:39:29","revisionof":"","revisedto":"S2-2103728","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI ISG MEC, TSG SA, SA WG2, SA WG5, SA WG6CC","Cc":"ETSI ISG NFV","lsoriginalls":"OPG_52_Doc_03","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102129.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102130","title":"LS from WBA 5G Work Group: Liaison Statement on 5G & Wi-Fi RAN Convergence","source":"WBA 5G Work Group","contact":"Nigel Bird","contact-id":27137,"tdoctype":"LS in","for":"Information","abstract":"Dear TSG SA Chair Georg Mayer, and SA WG2 Chair Puneet Jain, WBA thanks TSG SA for ongoing work regarding WLAN integration into 3GPP 5G systems in the Release 16 and Release 17. The WBA 5G Work Group has been looking into 5G and Wi-Fi RAN convergence topic for over 2 years. WBA published phase 1 analysis on this topic jointly with the NGMN as part of a RAN Convergence Paper published in September 2019. During 2020, WBA Members approved the creation of a phase 2 project to conduct further in-depth analysis on 5G & Wi-Fi RAN Convergence (https:\/\/wballiance.com\/5g-wi-fi-ran-convergence-global-architecture-policy). The WBA 5G Work Group has now concluded the phase 2 of the project in the form of a whitepaper titled '5G and Wi-Fi RAN Convergence - Aligning the Industry on Opportunities and Challenges', identifying potential challenges and gaps related to providing end-to-end 5G services using both 5G and Wi-Fi accesses. Reason for contact: The WBA 5G Work Group has highlighted potential challenges and gaps in the following key areas related to the 5G and Wi-Fi convergence: - 5G and Wi-Fi convergence architecture (for Trusted and Untrusted WLAN access); - ATSSS multi-access functionality; - End-to-end QoS; - Policy Interworking and enhancements across 5G and Wi-Fi; - Support for Wi-Fi only devices. Potential challenges and gaps identified in these key areas are captured in Section 3 of the paper. Section 4 provides recommendations for the industry to address them and Section 5 lists specific items to be addressed by relevant standard bodies. {. . .} We believe that further actions are needed by the industry and standards bodies to address key challenges and gaps highlighted in the WBA 5G and Wi-Fi RAN Convergence paper, for realizing new business opportunities presented by the convergence between 5G and Wi-Fi. We look forward to working together with your organization to address the issues highlighted above. Please let us know if we could collaborate on any items that might be of interest to your organization. Looking forward to continued cooperation between our organizations. Thank you very much in advance and for any additional information please contact WBA PMO (pmo@wballiance.com). Best Regards, WBA PMO (pmo@wballiance.com","secretary_remarks":"Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10150,"status":"postponed","reservation_date":"2021-03-31 14:12:31","uploaded":"2021-03-31 14:39:29","revisionof":"","revisedto":"S2-2103729","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG2","Cc":"","lsoriginalls":"WBA LS on 5G Wi-Fi RAN Convergence","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102130.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102136","title":"Support for L2TP based on CT WG4's LS and TR.","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Approval","abstract":"This contribution discusses support for L2TP and impacts to SA WG2 specifications based on the solution concluded in CT WG4.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11360,"status":"noted","reservation_date":"2021-03-31 19:50:14","uploaded":"2021-04-06 18:49:18","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"BEPoP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102136.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102137","title":"Support for L2TP on N6","source":"Ericsson, Nokia, Nokia Shanghai Bell, ZTE, China Mobile, China Telecom","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add support for ptoviding L2TP information in5GS","secretary_remarks":"S2-2102137r02 agreed. Revised to S2-2103230","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11370,"status":"revised","reservation_date":"2021-03-31 19:50:14","uploaded":"2021-04-06 18:49:18","revisionof":"","revisedto":"S2-2103230","release":"Rel-17","crspec":23.501,"crspecversion":"17.0.0","workitem":[{"winame":"BEPoP"},{"winame":" TEI17"}],"crnumber":2691.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102137.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102138","title":"Support for L2TP on SGi","source":"Ericsson, ZTE, China Mobile, China Telecom","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add support for providing L2TP information from PGW-C to PGW-U. Clarify that PGW-U may provide UE IP address to PGW-C.","secretary_remarks":"S2-2102138r03 agreed. Revised to S2-2103231","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11390,"status":"revised","reservation_date":"2021-03-31 19:50:14","uploaded":"2021-04-06 18:49:18","revisionof":"","revisedto":"S2-2103231","release":"Rel-17","crspec":23.214,"crspecversion":"16.2.0","workitem":[{"winame":"BEPoP"},{"winame":" TEI17"}],"crnumber":76.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102138.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102139","title":"[DRAFT] Reply LS on the support of L2TP with CUPS","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"The paper proposes a reply to the CT WG4 LS on L2TP support (C4-211624\/S2-2102110)","secretary_remarks":"Response to S2-2102110. Revised to S2-2103232.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11410,"status":"revised","reservation_date":"2021-03-31 19:50:15","uploaded":"2021-04-06 18:49:18","revisionof":"","revisedto":"S2-2103232","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"BEPoP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG3","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102139.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102147","title":"[DRAFT] LS on Reliable Data Service Serialization Indications in Rel-16","source":"Convida Wireless LLC","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"LS out","for":"Approval","abstract":"SA WG2 would like to indicate that, in Rel-16, the Reliable Data Service Serialization Indication feature has been removed from TS 23.682, TS 23.501, and TS 23.502. The associated CRs are attached.","secretary_remarks":"Response to S2-2102086. CC#1: Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10570,"status":"postponed","reservation_date":"2021-03-31 21:07:52","uploaded":"2021-04-06 18:56:31","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"RDSSI"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"TSG SA, TSG CT, CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102147.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102148","title":"Removal of Reliable Data Service Serialization Indications","source":"Convida Wireless LLC","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removed the reliable data service serialization indications.","secretary_remarks":"CC#1: Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10540,"status":"postponed","reservation_date":"2021-03-31 21:10:35","uploaded":"2021-04-06 18:56:31","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.682,"crspecversion":"16.9.0","workitem":[{"winame":"RDSSI"}],"crnumber":476.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102148.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102149","title":"Removal of Reliable Data Service Serialization Indications","source":"Convida Wireless LLC","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removed the reliable data service serialization indications.","secretary_remarks":"CC#1: Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10550,"status":"postponed","reservation_date":"2021-03-31 21:13:49","uploaded":"2021-04-06 18:56:31","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.8.0","workitem":[{"winame":"RDSSI"}],"crnumber":2695.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102149.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102150","title":"Removal of Reliable Data Service Serialization Indications","source":"Convida Wireless LLC","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removed the reliable data service serialization indications.","secretary_remarks":"CC#1: Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10560,"status":"postponed","reservation_date":"2021-03-31 21:16:23","uploaded":"2021-04-06 18:56:31","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.8.0","workitem":[{"winame":"RDSSI"}],"crnumber":2601.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102150.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102153","title":"DNN and S-NSSAI for NEF API ChargebleParty and AF Session with QoS","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce DNN and S-NSSAI for Chargeble Party at AF session setup, in clause 4.15.6.4\/5 Introduce DNN and S-NSSAI for AF session with QoS procedures, in clause 4.15.6.6\/6a Introduce DNN and S-NSSAI in ChargeableParty service operations Introduce DNN and S-NSSAI in AFSessionWithQoS service operations","secretary_remarks":"Revision of S2-2100295. S2-2102153r01 agreed. Revised to S2-2103227","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11140,"status":"revised","reservation_date":"2021-04-01 14:12:56","uploaded":"2021-04-06 18:49:19","revisionof":"S2-2100295","revisedto":"S2-2103227","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"5GMS3"},{"winame":" TEI17"}],"crnumber":2491.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102153.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102154","title":"Support for L2TP on N6","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add support for L2TP in 5GS","secretary_remarks":"S2-2102154r02 agreed. Revised to S2-2103233","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11430,"status":"revised","reservation_date":"2021-04-01 14:40:32","uploaded":"2021-04-06 17:52:59","revisionof":"","revisedto":"S2-2103233","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"TEI17"},{"winame":" BEPoP"}],"crnumber":2602.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102154.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102156","title":"[DRAFT] LS on N3IWF FQDN for emergency service","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"[draft] LS on N3IWF FQDN for emergency service","secretary_remarks":"Response to S2-2102109. CC#1: Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11250,"status":"postponed","reservation_date":"2021-04-01 14:40:34","uploaded":"2021-04-06 17:52:59","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102156.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102157","title":"Correction to N3IWF (PLMN) selection for emergency service","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This LS highlights a mistake in \u00a7 6.3.6.4 'PLMN Selection for emergency services'","secretary_remarks":"CC#1: Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11260,"status":"postponed","reservation_date":"2021-04-01 14:40:34","uploaded":"2021-04-06 17:52:59","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.8.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":2698.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102157.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102158","title":"Correction to N3IWF (PLMN) selection for emergency service","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Rel-17 mirror CR: Summary of change: This LS highlights a mistake in \u00a7 6.3.6.4 'PLMN Selection for emergency services'","secretary_remarks":"CC#1: Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11270,"status":"postponed","reservation_date":"2021-04-01 14:40:35","uploaded":"2021-04-06 17:52:59","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.0.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":2699.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102158.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102163","title":"[DRAFT] LS on interworking to 5GS with N26 due to UE's N1 mode capability disabling\/enabling","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"Draft LS on interworking to 5GS with N26 due to UE's N1 mode capability disabling\/enabling","secretary_remarks":"Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10430,"status":"postponed","reservation_date":"2021-04-01 14:40:35","uploaded":"2021-04-06 18:31:36","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5GProtoc17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102163.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102164","title":"Solving interworking to 5GS with N26 issue due to UE's N1 mode capability disabling\/enabling","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: At EPS to 5GS mobility R16 UE consider as released the PDN connections that were established over EPS and for which the UE has not received mapped 5GS QoS parameters from the network, The MME does not transfer to 5GS a PDN connection that was established over EPC on a stand-alone PGW. (the UE has released it per item 1 above) The MME tries to transfer to 5GS a PDN connection that was established over EPC on a SMF+ PGW-c. What happens next is discussed below. At EPS to 5GS HO The initial AMF invokes (step 4 of figure 4.11.1.2.2.2-1) the Nsmf_PDUSession_CreateSMContext service operation (UE EPS PDN Connection, initial AMF ID, data Forwarding information, Target ID) on the SMF identified by the SMF+PGW-C address and indicates HO Preparation Indication. \u2026. The SMF finds the corresponding PDU Session based on EPS Bearer Context(s). IF the PDU Session Id retrieved by the SMF does not belong to the range of UE allocated PDU Session ID(s), the SMF rejects the AMF request and the PDN connection is not further handed-over (assumed to be released by the UE per item 1 above). When the SMF allocates a PDU Session ID for the PDU Session this is within a specific range The unique PDU Session ID can be created based on the EPS Bearer IDs assigned by the MME for the PDN Connections associated with the UE and not be in the range of PDU Session ID values that can be created by a 5GC NAS capable UE.","secretary_remarks":"Revision of S2-2100101. S2-2102164r02 technically endorsed. Revised to S2-2103058.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10440,"status":"revised","reservation_date":"2021-04-01 14:40:35","uploaded":"2021-04-06 18:31:36","revisionof":"S2-2100101","revisedto":"S2-2103058","release":"Rel-16","crspec":23.502,"crspecversion":"16.8.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":2465.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102164.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102165","title":"Solving interworking to 5GS with N26 issue due to UE's N1 mode capability disabling\/enabling","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: At EPS to 5GS mobility UE consider as released the PDN connections that were established over EPS while the UE did not receive 5GS parameters from the network as answer to the PDN connection request. This covers the case where the UE did not provide a PDU Session ID to the network when establishing a PDN connection while the N1 mode is diasabled The MME does not transfer to 5GS a PDN connection that was established over EPC on a stand-alone PGW. (the UE has released it per item 1 above) The MME tries to transfer to 5GS a PDN connection that was established over EPC on a SMF+ PGW-c. what happens next is discussed below. At EPS to 5GS HO, the initial AMF invokes (step 4 of figure 4.11.1.2.2.2-1) the Nsmf_PDUSession_CreateSMContext service operation (UE EPS PDN Connection, initial AMF ID, data Forwarding information, Target ID) on the SMF identified by the SMF+PGW-C address and indicates HO Preparation Indication (to avoid switching the UP path). \u2026. The SMF finds the corresponding PDU Session based on EPS Bearer Context(s). IF the PDU Session Id retrieved by the SMF does not belong to the range of UE allocated PDU session Id(s); the SMF rejects the AMF request and the PDN connection is not further handed-over (assumed to be released by the UE per item 1 above). When the SMF allocates a PDU Session Id for the PDU Session this is within a specific range The unique PDU Session ID can be created based on the EPS Bearer IDs assigned by the MME for the PDN Connections associated with the UE and not be in the range of PDU Session ID values that can be created by a 5GC NAS capable UE. In summary, the R17 behavior is the same than in R16 except that R17 specifications supports the UE option where the UE sends a PDU Session ID to the network when establishing a PDN connection while N1 mode is Disabled","secretary_remarks":"S2-2102165r01 technically endorsed. Revised, merging S2-2102774, to S2-2103059.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10460,"status":"revised","reservation_date":"2021-04-01 14:40:36","uploaded":"2021-04-06 18:33:08","revisionof":"","revisedto":"S2-2103059","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":2603.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102165.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102172","title":"[DRAFT] Reply LS on NAS Non delivery for RRC Inactive state","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"LS to RAN WG3 to inform the SA WG2 view on the NAS non delivery for RRC inactive state","secretary_remarks":"Response to S2-2102083. S2-2102172r09 agreed. Revised to S2-2103216, merging S2-2102605, S2-2102563","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10360,"status":"revised","reservation_date":"2021-04-01 21:27:08","uploaded":"2021-04-06 18:50:54","revisionof":"","revisedto":"S2-2103216","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102172.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102173","title":"[DRAFT] Reply LS on Group Subscription","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"LS to CT WG4 answering questions from CT WG4 related to event subcription handling for group of UE","secretary_remarks":"Response to S2-2102107. Merged into S2-2103229","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11190,"status":"merged","reservation_date":"2021-04-01 21:27:08","uploaded":"2021-04-06 18:50:54","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102173.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102174","title":"[DRAFT] Reply LS on Server Domain Name Usage for Application Traffic Detection","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"LS to SA WG4 provider SA WG2 conclusions on NEF related service API","secretary_remarks":"Response to S2-2102102. Merged into S2-2103228","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11090,"status":"merged","reservation_date":"2021-04-01 21:27:08","uploaded":"2021-04-06 18:50:54","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5GMS3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102174.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102175","title":"Application Identifier for SCEF API ChargebleParty and AS Session with QoS","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce Application Identifier for AS session with required QoS case in clause 5.11 Introduce Application Identifier for chargeable party case in clause 5.12","secretary_remarks":"Revision of S2-2100293. S2-2102175r01 agreed. Revised to S2-2103225","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11100,"status":"revised","reservation_date":"2021-04-01 21:27:08","uploaded":"2021-04-06 18:50:54","revisionof":"S2-2100293","revisedto":"S2-2103225","release":"Rel-17","crspec":23.682,"crspecversion":"16.9.0","workitem":[{"winame":"TEI17"},{"winame":" 5GMS3"}],"crnumber":475.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102175.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102176","title":"Application Identifier for NEF API ChargebleParty and AF Session with QoS","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce Application Identifier in AF requests to influence traffic routing flow, in clause 4.3.6.2. Introduce Application Identifier for Chargeble Party at AF session setup, in clause 4.15.6.4\/5. Introduce Application ID for AF session with QoS procedures, in clause 4.15.6.6\/6a. Introduce Application Identifier in ChargeableParty service operations in clause 5.2.6.8. Introduce Application Identifier in AFSessionWithQoS service operations in clause 5.2.6.9.","secretary_remarks":"Revision of S2-2100294. S2-2102176r01 agreed. Revised to S2-2103226","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11120,"status":"revised","reservation_date":"2021-04-01 21:27:09","uploaded":"2021-04-06 18:50:54","revisionof":"S2-2100294","revisedto":"S2-2103226","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"TEI17"},{"winame":" 5GMS3"}],"crnumber":2490.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102176.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102219","title":"[DRAFT] LS Reply on Server Domain Name Usage for Application Traffic Detection","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Reply to the LS on Server Domain Name Usage for Application Traffic Detection","secretary_remarks":"Response to S2-2102102. S2-2102219r05 agreed. Revised to S2-2103228, merging S2-2102174","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11160,"status":"revised","reservation_date":"2021-04-02 07:05:05","uploaded":"2021-04-06 09:13:05","revisionof":"","revisedto":"S2-2103228","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5GMS3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102219.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102220","title":"[DRAFT] LS Reply on NSI ID on N7 interface","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"To answer the LS on NSI ID on N7 interface from CT WG3","secretary_remarks":"Response to S2-2102090. S2-2102220r01 agreed. Revised to S2-2103217","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10590,"status":"revised","reservation_date":"2021-04-02 07:05:05","uploaded":"2021-04-06 09:13:05","revisionof":"","revisedto":"S2-2103217","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"},{"winame":" 5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102220.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102221","title":"Delete NSI ID via N7 interface","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Delete NSI ID in N7 interface.","secretary_remarks":"Confirm CR Number - CR states 2615! S2-2102221r02 agreed. Revised to S2-2103218","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10610,"status":"revised","reservation_date":"2021-04-02 07:05:05","uploaded":"2021-04-06 09:13:05","revisionof":"","revisedto":"S2-2103218","release":"Rel-15","crspec":23.502,"crspecversion":"15.13.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2616.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102221.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102222","title":"Delete NSI ID via N7 interface","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Delete NSI ID in N7 interface.","secretary_remarks":"Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10630,"status":"agreed","reservation_date":"2021-04-02 07:05:06","uploaded":"2021-04-06 09:13:05","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.8.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2617.0,"crrevision":"","crcategory":"A","tsg_crp":"SP-210324","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102222.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102223","title":"Delete NSI ID via N7 interface","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Rel-17 mirror CR: Summary of change: Delete NSI ID in N7 interface.","secretary_remarks":"Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10640,"status":"agreed","reservation_date":"2021-04-02 07:05:08","uploaded":"2021-04-06 09:13:05","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2618.0,"crrevision":"","crcategory":"A","tsg_crp":"SP-210324","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102223.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102224","title":"Delete NSI ID via N7 interface","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Delete NSI ID in N7 interface.","secretary_remarks":"Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10650,"status":"agreed","reservation_date":"2021-04-02 07:05:09","uploaded":"2021-04-06 09:13:04","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.9.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":548.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-210324","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102224.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102225","title":"Delete NSI ID via N7 interface","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Delete NSI ID in N7 interface.","secretary_remarks":"Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10660,"status":"agreed","reservation_date":"2021-04-02 07:05:10","uploaded":"2021-04-06 09:13:04","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.503,"crspecversion":"16.8.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":549.0,"crrevision":"","crcategory":"A","tsg_crp":"SP-210324","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102225.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102226","title":"Delete NSI ID via N7 interface","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Rel-17 mirror CR: Summary of change: Delete NSI ID in N7 interface.","secretary_remarks":"Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10670,"status":"agreed","reservation_date":"2021-04-02 07:05:11","uploaded":"2021-04-06 09:13:04","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.503,"crspecversion":"17.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":550.0,"crrevision":"","crcategory":"A","tsg_crp":"SP-210324","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102226.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102227","title":"Delete NSI ID via N7 interface","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Delete NSI ID in N7 interface. Clarify NSI ID is only applicable when the consumer is NSSF but not PCF.","secretary_remarks":"Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10680,"status":"agreed","reservation_date":"2021-04-02 07:05:12","uploaded":"2021-04-06 09:13:04","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.288,"crspecversion":"16.7.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":264.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-210330","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102227.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102228","title":"Delete NSI ID via N7 interface","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Rel-17 mirror CR: Summary of change: Delete NSI ID in N7 interface. Clarify NSI ID is only applicable when the consumer is NSSF but not PCF.","secretary_remarks":"S2-2102228r07 agreed. Revised to S2-2103219","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10690,"status":"revised","reservation_date":"2021-04-02 07:05:13","uploaded":"2021-04-06 09:13:04","revisionof":"","revisedto":"S2-2103219","release":"Rel-17","crspec":23.288,"crspecversion":"17.0.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":265.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102228.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102229","title":"Update PCF services table and NEF services table","source":"China Telecom","contact":"Jiayifan Liu","contact-id":87717,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding Npcf_AMPolicyAuthorization services into the services provided by PCF table. Adding Nnef_AMPolicyAuthorization services and Nnef_AMInfluence services into the services provided by NEF table.","secretary_remarks":"WI Code should be 'TEI17_DCAMP'. Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10270,"status":"not treated","reservation_date":"2021-04-02 08:12:27","uploaded":"2021-04-02 09:15:14","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"TEI17_DCAMP"}],"crnumber":2619.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102229.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102233","title":"[DRAFT] Reply LS on interworking to 5GS with N26 due to UE's N1 mode capability disabling\/enabling","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"WITHDRAWN: Reply LS on interworking to 5GS with N26 due to UE's N1 mode capability disabling\/enabling","secretary_remarks":"Revision of S2-2100130. Response to S2-2102085. WITHDRAWN","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10410,"status":"withdrawn","reservation_date":"2021-04-02 14:32:07","uploaded":"2021-04-06 12:37:53","revisionof":"S2-2100130","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102233.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102234","title":"UE request bearer resource modification due to N1 capability change","source":"Huawei, HiSilicon, MediaTek Inc.","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Enhance the UE request bearer resource modification procedure to support the CN providing the mapped 5GS QoS parameters to the UE. ============ #144 =============== Add descripition in geneal part. Enhance Npcf_SMPolicyControl_Update service.","secretary_remarks":"Revision of S2-2100131. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10420,"status":"noted","reservation_date":"2021-04-02 14:32:07","uploaded":"2021-04-06 12:37:53","revisionof":"S2-2100131","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"TEI16"},{"winame":" 5GS_Ph1"}],"crnumber":2469.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102234.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102278","title":"[DRAFT] Reply LS on E-RABs that cannot be handed over to 2G\/3G or 5G","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"This LSout replies with solutions to resolve the issue brought up in the Lsin.","secretary_remarks":"Response to S2-2102093. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10720,"status":"noted","reservation_date":"2021-04-05 12:31:17","uploaded":"2021-04-06 18:52:28","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"TEI15"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"CT WG1, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102278.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102279","title":"SRVCC when 5GS interworking is supported","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: MME proceeds with PS HO even if MME knows that the PS HO is deemed to fail, e.g. when UE was previously in 5GS. Clarify that MME constructs in Forward Relocaton Request message (to SGSN) the Transaction Identifier IE if it is not available.","secretary_remarks":"Revision of S2-2100328. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10770,"status":"noted","reservation_date":"2021-04-05 12:31:17","uploaded":"2021-04-06 18:52:28","revisionof":"S2-2100328","revisedto":"","release":"Rel-16","crspec":23.216,"crspecversion":"16.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":368.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102279.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102280","title":"PS HO from EUTRAN to GERAN\/UTRAN or to NG-RAN","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: During E-RAB setup (e.g. in Initial Attach, Service Request, Handover), if the MME determines that handover to GERAN\/UTRAN is not possible based on e.g. when 5GS interworking is supported for certain PDN connection(s), UE was previously in 5GS, or If the MME determines that handover to NG-RAN is not possible for certain PDN connection(s) based on e.g. 5GS interworking is not supported, or UE was previously in 2G\/3G, the MME indicates such decisions to the eNB for each E-RAB over S1AP. The MME needs to initiate PDN connection towards the SMF+PGW-C if MME knows the PDN connection cannot be transferred to 2G\/3G or cannot be moved to 5GS.","secretary_remarks":"Revision of S2-2100329. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10780,"status":"noted","reservation_date":"2021-04-05 12:31:18","uploaded":"2021-04-06 18:53:52","revisionof":"S2-2100329","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.8.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":2494.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102280.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102281","title":"PS HO from EUTRAN to GERAN\/UTRAN or to NG-RAN","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Rel-17 mirror CR: Summary of change: During E-RAB setup (e.g. in Initial Attach, Service Request, Handover), if the MME determines that handover to GERAN\/UTRAN is not possible based on e.g. when 5GS interworking is supported for certain PDN connection(s), UE was previously in 5GS, or If the MME determines that handover to NG-RAN is not possible for certain PDN connection(s) based on e.g. 5GS interworking is not supported, or UE was previously in 2G\/3G, the MME indicates such decisions to the eNB for each E-RAB over S1AP. The MME needs to initiate PDN connection towards the SMF+PGW-C if MME knows the PDN connection cannot be transferred to 2G\/3G or cannot be moved to 5GS.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10790,"status":"noted","reservation_date":"2021-04-05 12:31:19","uploaded":"2021-04-06 18:53:52","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":2627.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102281.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102311","title":"E-RABs that cannot be handed over to 2G\/3G or 5G.","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"This paper discusses solutions to address issues that E-RABs that cannot be handed over to 2G\/3G or 5G and propose way forward.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10760,"status":"noted","reservation_date":"2021-04-05 17:15:15","uploaded":"2021-04-06 18:53:52","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102311.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102312","title":"Correction to the N3IWF selection procedure","source":"Lenovo, Motorola Mobility, BlackBerry UK Ltd.","contact":"Apostolis Salkintzis","contact-id":22112,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that if the UE is registered via 3GPP access to a PLMN, then the UE shall select an N3IWF in this PLMN, only when this PLMN is explicitly included in the Non-3GPP access node selection information. With the changes in this CR it is clarified that if: the UE is registered via 3GPP access to a VPLMN; and this VPLMN is not included in the N3AN node selection information; and the visited country does not mandate N3IWF selection in this country; and the N3AN node selection information does not contain other VPLMNs in the visited country, or the N3AN node selection information contains other VPLMNs in the visited country but the UE fails to connect to an N3IWF in any of these VPLMNs; then the UE shall select an N3IWF in the HPLMN.","secretary_remarks":"Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11300,"status":"agreed","reservation_date":"2021-04-05 17:47:49","uploaded":"2021-04-06 17:57:07","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.8.0","workitem":[{"winame":"TEI16"},{"winame":" 5GS_Ph1"}],"crnumber":2722.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-210330","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102312.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102313","title":"Correction to the N3IWF selection procedure","source":"Lenovo, Motorola Mobility, BlackBerry UK Ltd.","contact":"Apostolis Salkintzis","contact-id":22112,"tdoctype":"CR","for":"Approval","abstract":"Rel-17 mirror CR: Summary of change: It is clarified that if the UE is registered via 3GPP access to a PLMN, then the UE shall select an N3IWF in this PLMN, only when this PLMN is explicitly included in the Non-3GPP access node selection information. With the changes in this CR it is clarified that if: the UE is registered via 3GPP access to a VPLMN; and this VPLMN is not included in the N3AN node selection information; and the visited country does not mandate N3IWF selection in this country; and the N3AN node selection information does not contain other VPLMNs in the visited country, or the N3AN node selection information contains other VPLMNs in the visited country but the UE fails to connect to an N3IWF in any of these VPLMNs; then the UE shall select an N3IWF in the HPLMN.","secretary_remarks":"Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11310,"status":"agreed","reservation_date":"2021-04-05 17:50:49","uploaded":"2021-04-06 17:57:07","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.0.0","workitem":[{"winame":"TEI16"},{"winame":" 5GS_Ph1"}],"crnumber":2723.0,"crrevision":"","crcategory":"A","tsg_crp":"SP-210330","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102313.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102347","title":"[DRAFT] LS on voice centric UE impact due to S1 mode disable","source":"China Telecommunications","contact":"Heng Nie","contact-id":40431,"tdoctype":"LS out","for":"Approval","abstract":"SA WG2 would kindly ask CT WG1 to provide possible improvement for the voice centric UE, once the UE disables its S1 mode, in order to minimize the duration that the UE stays in the unfavorable domain, or prevent the UE from staying in the unfavorable dom","secretary_remarks":"Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10260,"status":"not treated","reservation_date":"2021-04-06 03:48:40","uploaded":"2021-04-06 03:53:35","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102347.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102382","title":"[DRAFT] Reply LS on QoS Monitoring Control for Service Data Flows","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"LS Reply on QoS Monitoring Control for Service Data Flows","secretary_remarks":"Revision of S2-2100852. Response to S2-2102092. Revised to S2-2103224.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11030,"status":"revised","reservation_date":"2021-04-06 06:40:11","uploaded":"2021-04-06 13:59:20","revisionof":"S2-2100852","revisedto":"S2-2103224","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102382.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102383","title":"Updates to support QoS Monitoring control for service data flows","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: PCC rule with QoS Monitoring policy is bound to separate QoS Flow.","secretary_remarks":"Revision of S2-2100853. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11050,"status":"agreed","reservation_date":"2021-04-06 06:40:11","uploaded":"2021-04-06 13:59:20","revisionof":"S2-2100853","revisedto":"","release":"Rel-16","crspec":23.503,"crspecversion":"16.8.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":537.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-210329","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102383.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102384","title":"Updates on PCC rule triggered GTP-U path monitoring","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In case the PCC rule with QoS Monitoring Policy triggers the GTP-U path monitoring, the SMF ignores the QoS Monitoring Policy when performing QoS Flow Binding.","secretary_remarks":"S2-2102384r03 agreed. Revised to S2-2103223","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11060,"status":"revised","reservation_date":"2021-04-06 06:40:12","uploaded":"2021-04-06 13:59:20","revisionof":"","revisedto":"S2-2103223","release":"Rel-16","crspec":23.501,"crspecversion":"16.8.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":2745.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102384.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102396","title":"Support of AF change","source":"CATT","contact":"Yuan Tao","contact-id":82804,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Addtion of Information on AF change (including indication of AF change, target AF ID and notification target address of the target AF) for AF influence on traffic routing.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10980,"status":"noted","reservation_date":"2021-04-06 07:15:29","uploaded":"2021-04-06 08:06:58","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.8.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":2747.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102396.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102397","title":"Support of AF change","source":"CATT","contact":"Yuan Tao","contact-id":82804,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Addtion of Information on AF change (including indication of AF change, target AF ID and notification target address of the target AF) for AF influence on traffic routing. Removal of the parameters within Nnef_TrafficInfluence_AppRelocationInfo and Nsmf_EventExposure_AppRelocationInfo for supporting AF change.","secretary_remarks":"S2-2102397r07 agreed. Revised to S2-2103222, merging S2-2102561, S2-2102935","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11000,"status":"revised","reservation_date":"2021-04-06 07:15:30","uploaded":"2021-04-06 08:06:58","revisionof":"","revisedto":"S2-2103222","release":"Rel-16","crspec":23.502,"crspecversion":"16.8.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":2643.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102397.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102404","title":"[DRAFT] Reply LS on Group Subscriptions","source":"Huawei,HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on Group Subscriptions","secretary_remarks":"Response to S2-2102107. Merged into S2-2103229","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11200,"status":"merged","reservation_date":"2021-04-06 07:25:09","uploaded":"2021-04-06 11:21:43","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102404.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102543","title":"Correct the N6 definition and related NOTE","source":"China Mobile","contact":"Dan Wang","contact-id":87155,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct the N6 definition and related NOTE","secretary_remarks":"Not Handled. Revised at S2-145E in S2-2104433","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10280,"status":"revised","reservation_date":"2021-04-06 09:31:11","uploaded":"2021-04-06 11:58:22","revisionof":"","revisedto":"S2-2104433","release":"Rel-15","crspec":23.501,"crspecversion":"15.12.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI15"}],"crnumber":2779.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102543.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102551","title":"(Mirror)Correct the N6 definition and related NOTE","source":"China Mobile","contact":"Dan Wang","contact-id":87155,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct the N6 definition and related NOTE","secretary_remarks":"Not Handled. Revised at S2-145E in S2-2104444","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10290,"status":"revised","reservation_date":"2021-04-06 09:36:26","uploaded":"2021-04-06 11:58:22","revisionof":"","revisedto":"S2-2104444","release":"Rel-16","crspec":23.501,"crspecversion":"16.8.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":2782.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102551.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102552","title":"(Mirror)Correct the N6 definition and related NOTE","source":"China Mobile","contact":"Dan Wang","contact-id":87155,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct the N6 definition and related NOTE","secretary_remarks":"Not Handled. Revised at S2-145E in S2-2104454","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10300,"status":"revised","reservation_date":"2021-04-06 09:39:26","uploaded":"2021-04-06 11:58:22","revisionof":"","revisedto":"S2-2104454","release":"Rel-17","crspec":23.501,"crspecversion":"17.0.0","workitem":[{"winame":"TEI17"}],"crnumber":2783.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102552.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102559","title":"UP change event update during AF relocation.","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"discussion","for":"Agreement","abstract":"This contribution discusses UP change event update during AF relocation.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10900,"status":"noted","reservation_date":"2021-04-06 10:23:58","uploaded":"2021-04-06 15:46:54","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102559.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102560","title":"[DRAFT] LS response on support of AF influence change","source":"Huawei,HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"LS response on support of AF influence change","secretary_remarks":"Response to S2-2102091. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10890,"status":"noted","reservation_date":"2021-04-06 10:23:58","uploaded":"2021-04-06 15:46:54","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102560.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102561","title":"Correction of the notification of UP path management Events","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove the unnecesary optional input parameters in Nnef_TrafficInfluence_AppRelocationInfo service operation. Clarify that the new AF create a new UP path management event subscription after the AF relocation.","secretary_remarks":"Merged into S2-2103222","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10910,"status":"merged","reservation_date":"2021-04-06 10:23:58","uploaded":"2021-04-06 15:46:54","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.8.0","workitem":[{"winame":"TEI17"},{"winame":" 5G_URLLC"}],"crnumber":2666.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102561.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102562","title":"Correction of the notification of UP path management Events","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Rel-17 mirror CR: Summary of change: Remove the unnecesary optional input parameters in Nnef_TrafficInfluence_AppRelocationInfo service operation. Clarify that the new AF create a new UP path management event subscription after the AF relocation.","secretary_remarks":"S2-2102562r02 agreed. S2-2102562r02 agreed. Revised to S2-2103221, merging S2-2102939","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10920,"status":"revised","reservation_date":"2021-04-06 10:23:59","uploaded":"2021-04-06 15:46:54","revisionof":"","revisedto":"S2-2103221","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"TEI17"},{"winame":" 5G_URLLC"}],"crnumber":2667.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102562.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102563","title":"[DRAFT] Reply LS on NAS Non delivery for RRC inactivated state","source":"Huawei,HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Draft response LS related to the NAS-non-delivery from RAN WG3.","secretary_remarks":"Response to S2-2102083. Merged into S2-2103216","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10380,"status":"merged","reservation_date":"2021-04-06 10:24:00","uploaded":"2021-04-06 15:46:54","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102563.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102600","title":"Discussion on Support of VxLAN Tunnelling.","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"discussion","for":"Endorsement","abstract":"This discussion paper discusses the requirement and alternative solutions for support of VxLAN Tunnelling.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11520,"status":"noted","reservation_date":"2021-04-06 10:34:40","uploaded":"2021-04-06 14:43:51","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"","workitem":[{"winame":"TEI17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102600.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102601","title":"[DRAFT] Reply LS on Requirement on Support of VxLAN Tunnelling","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to incoming LS (C4-211827) on Requirement on Support of VxLAN Tunnelling","secretary_remarks":"Response to S2-2102114. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11510,"status":"noted","reservation_date":"2021-04-06 10:34:40","uploaded":"2021-04-06 14:43:51","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"SA WG5","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102601.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102605","title":"[DRAFT] Reply LS on NAS Non delivery for RRC_INACTIVE state","source":"CATT","contact":"Yunjing Hou","contact-id":46707,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on NAS Non delivery for RRC Inactive state (S2-2009100\/ R3-207170)","secretary_remarks":"Response to S2-2102083. Merged into S2-2103216","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10390,"status":"merged","reservation_date":"2021-04-06 10:46:20","uploaded":"2021-04-06 11:35:14","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102605.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102751","title":"[DRAFT] LS on E-RABs that cannot be handed over to 2G\/3G or 5G","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"Draft LS on E-RABs that cannot be handed over to 2G\/3G or 5G (relates to LS on E-RABs that cannot be handed over to 2G\/3G or 5G (R3-211273 \/ S2-2102093))","secretary_remarks":"S2-2102751r06 agreed. Revised to S2-2103061.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10730,"status":"revised","reservation_date":"2021-04-06 13:09:08","uploaded":"2021-04-06 19:45:44","revisionof":"","revisedto":"S2-2103061","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102751.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102762","title":"SRVCC procedure in case of PDN connections without TI","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Rel-17 mirror CR: Summary of change: For 5G SRVCC to 3G it is described in 23.501 \u00a7 5.17.2.4 'Mobility between 5GS and GERAN\/UTRAN' that 'After the 5G SRVCC to UTRAN, all the PDU sessions of the UE are released'; The same behaviour may take place at the indirect mobility 5G ( 4G ( (SRVCC) 3G Thus at SRVCC from EPC to 3G the MME issues a Forward Relocation Request message to the SGSN but this Forward Relocation Request does not transfer to the SGSN PDN connections for which no TI has been negotiated with the UE (PDN connections corresponding to PDU Sessions established over 5GS). No impact is thus expected to the ENB. It has to be Noted that 23.060 \u00a7 6.9.2.2.2 Combined Hard Handover and SRNS Relocation Procedure already foresees that at SRNS relocation: 'The list of RABs requested by the new SGSN may differ from list of RABs established in the Source RNC contained in the Source-RNC to target RNC transparent container'. the final list of RAB(s) Established on the becomes empty (based on MME pruning out PDN connections without a TI) does not create a mobility \/ hand-Over from ENB while the ENB was not handling User Plane","secretary_remarks":"Revised to S2-2102930. (Wrong CR Number used)","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10800,"status":"revised","reservation_date":"2021-04-06 13:22:59","uploaded":"2021-04-06 19:45:44","revisionof":"","revisedto":"S2-2102930","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":2697.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102762.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102763","title":"SRVCC procedure in case of PDN connections without TI","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: For 5G SRVCC to 3G it is described in 23.501 \u00a7 5.17.2.4 'Mobility between 5GS and GERAN\/UTRAN' that 'After the 5G SRVCC to UTRAN, all the PDU sessions of the UE are released'; The same behaviour may take place at the indirect mobility 5G ( 4G ( (SRVCC) 3G Thus at SRVCC from EPC to 3G the MME issues a Forward Relocation Request message to the SGSN but this Forward Relocation Request does not transfer to the SGSN PDN connections for which no TI has been negotiated with the UE (PDN connections corresponding to PDU Sessions established over 5GS). No impact is thus expected to the ENB. It has to be Noted that 23.060 \u00a7 6.9.2.2.2 Combined Hard Handover and SRNS Relocation Procedure already foresees that at SRNS relocation: 'The list of RABs requested by the new SGSN may differ from list of RABs established in the Source RNC contained in the Source-RNC to target RNC transparent container'.","secretary_remarks":"Revision of S2-2100228. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10820,"status":"noted","reservation_date":"2021-04-06 13:23:00","uploaded":"2021-04-06 19:49:02","revisionof":"S2-2100228","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.8.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":2477.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102763.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102771","title":"EPC interworking with N26 due to UE's N1 mode capability disabling\/enabling","source":"Samsung","contact":"Jungshin Park","contact-id":65750,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A UE that disables 5G NAS allocates and sends a PDU Session ID to the network during the PDN connection establishment. A UE stores 5G parameters for PDU sessions that are handed over to EPS irrespective of its 5G NAS enabling\/disabling status.","secretary_remarks":"Merged into S2-2103060","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10490,"status":"merged","reservation_date":"2021-04-06 14:00:36","uploaded":"2021-04-06 14:29:42","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2812.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102771.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102774","title":"EPC interworking with N26 due to UE's N1 mode capability disabling\/enabling","source":"Samsung","contact":"Jungshin Park","contact-id":65750,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A UE that disables 5G NAS allocates and sends a PDU Session ID to the network during the PDN connection establishment. A UE stores 5G parameters for PDU sessions that are handed over to EPS irrespective of its 5G NAS enabling\/disabling status.","secretary_remarks":"Merged into S2-2103059","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10500,"status":"merged","reservation_date":"2021-04-06 14:06:49","uploaded":"2021-04-06 14:29:42","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2700.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102774.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102775","title":"Discussion and Proposal on the SRVCC issue from RAN WG3 LS.","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"discussion","for":"Discussion","abstract":"This paper discusses the SRVCC issue from RAN WG3 LS, and gives the proposal way forward.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10750,"status":"noted","reservation_date":"2021-04-06 14:07:08","uploaded":"2021-04-06 14:39:14","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102775.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102776","title":"Clarificaton on the eNB behavoir for SRVCC","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To avoid the SRVCC faliure, the eNB either may be configued to initiate the SRVCC CS HO only, or only hand the E-RAB over to UTRAN\/GERAN according to MME indication specified in the 23.502.","secretary_remarks":"S2-2102776r04 agreed. Revised to S2-2103062.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10830,"status":"revised","reservation_date":"2021-04-06 14:07:08","uploaded":"2021-04-06 14:39:14","revisionof":"","revisedto":"S2-2103062","release":"Rel-16","crspec":23.216,"crspecversion":"16.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":369.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102776.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102777","title":"Clarification on EPS beaer can be handed over from EUTRAN to GERAN\/UTRAN","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding new clause, During E-RAB setup related procedure, the MME may send the indication in S1AP whether the bearer can be handed over to GERAN\/UTRAN.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10850,"status":"noted","reservation_date":"2021-04-06 14:07:09","uploaded":"2021-04-06 14:39:14","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.8.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":2701.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102777.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102778","title":"Clarification on EPS beaer can be handed over from EUTRAN to GERAN\/UTRAN","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Rel-17 mirror CR: Summary of change: Adding new clause, During E-RAB setup related procedure, the MME may send the indication in S1AP whether the bearer can be handed over to GERAN\/UTRAN.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10860,"status":"noted","reservation_date":"2021-04-06 14:07:10","uploaded":"2021-04-06 14:39:14","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":2702.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102778.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102779","title":"The impact of UE N1 mode change in EPS","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If the UE supports 5GC NAS, at PDN connection establishment in EPC, the UE allocates a PDU Session ID and sends it to the SMF+PGW-C via PCO, regardless of whether N1 mode is enabled or disabled. The SMF+PGW-C always send the mapped Qos parameter to UE if it receives the PDU session ID","secretary_remarks":"S2-2102779r03 technically endorsed. Revised, merging S2-2102771, to S2-2103060.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10510,"status":"revised","reservation_date":"2021-04-06 14:07:11","uploaded":"2021-04-06 14:39:14","revisionof":"","revisedto":"S2-2103060","release":"Rel-17","crspec":23.501,"crspecversion":"17.0.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":2814.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102779.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102819","title":"Update of LCS exposure via NEF","source":"Huawei","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to clarify it is the NEF to derive the LCS client type, when the request is from an AF.","secretary_remarks":"S2-2102819r01 agreed. Revised to S2-2103234","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11470,"status":"revised","reservation_date":"2021-04-06 15:14:54","uploaded":"2021-04-06 16:07:19","revisionof":"","revisedto":"S2-2103234","release":"Rel-16","crspec":23.273,"crspecversion":"16.6.0","workitem":[{"winame":"5G_eLCS"}],"crnumber":168.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102819.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102820","title":"[DRAFT] LS Response on the input parameters of the LCS subscription request from an AF via NEF","source":"Huawei","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC: CT WG4. Attachments: S2-210xxxx (CR)","secretary_remarks":"Response to S2-2100020 (Replied to at S2#143-e in S2-2101595). Revised to S2-2103235.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11450,"status":"revised","reservation_date":"2021-04-06 15:14:55","uploaded":"2021-04-06 16:07:19","revisionof":"","revisedto":"S2-2103235","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102820.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102823","title":"Update of Annex B in TS 23.271","source":"Huawei","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the texts in TS 23.271 annex B, by removing the LCS client type.","secretary_remarks":"Confirm Specification Number - CR states 23.271!. (If 23.271, a new CR number is needed). Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11490,"status":"noted","reservation_date":"2021-04-06 15:14:57","uploaded":"2021-04-06 16:07:19","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.273,"crspecversion":"16.6.0","workitem":[{"winame":"5G_eLCS"}],"crnumber":171.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102823.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102824","title":"[DRAFT] LS response on Requirement on Support of VxLAN Tunnelling","source":"Huawei","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4","secretary_remarks":"Response to S2-2102114. Merged into S2-2103236","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11530,"status":"merged","reservation_date":"2021-04-06 15:14:58","uploaded":"2021-04-06 16:07:19","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102824.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102845","title":"[DRAFT] Reply LS on group subscriptions","source":"Nokia Japan","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to CT WG4 questions on Group Subscriptions.","secretary_remarks":"Response to S2-2102107. S2-2102845r05 agreed. Revised to S2-2103229, merging S2-2102173, S2-2102629, S2-2102404","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11210,"status":"revised","reservation_date":"2021-04-06 15:40:32","uploaded":"2021-04-06 16:02:45","revisionof":"","revisedto":"S2-2103229","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102845.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102868","title":"[DRAFT] Draft LS on Requirement on Support of VxLAN Tunnelling","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"Draft LS on Requirement on Support of VxLAN Tunnelling","secretary_remarks":"Response to S2-21021144. S2-2102868r05 agreed. Revised to S2-2103236, merging S2-2102824, S2-2102929","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11540,"status":"revised","reservation_date":"2021-04-06 16:46:04","uploaded":"2021-04-06 18:07:39","revisionof":"","revisedto":"S2-2103236","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"BEPoP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"SA WG5","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102868.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102906","title":"New service operation of Namf_Communication_CancelRelocateUEContext","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add new service operation of Namf_Communication_CancelRelocateUEContext","secretary_remarks":"Confirm Spec version used - CR states g.8.0! S2-2102906r02 agreed. Revised to S2-2103214","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10310,"status":"revised","reservation_date":"2021-04-06 18:07:14","uploaded":"2021-04-06 18:28:03","revisionof":"","revisedto":"S2-2103214","release":"Rel-16","crspec":23.502,"crspecversion":"16.8.0","workitem":[{"winame":"eNS"}],"crnumber":2721.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102906.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102907","title":"New service operation of Namf_Communication_CancelRelocateUEContext","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","for":"Approval","abstract":"Rel-17 mirror CR: Summary of change: Add new service operation of Namf_Communication_CancelRelocateUEContext","secretary_remarks":"Confirm Spec version used - CR states g.8.0! Revised to S2-2103215.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10330,"status":"revised","reservation_date":"2021-04-06 18:07:15","uploaded":"2021-04-06 18:28:03","revisionof":"","revisedto":"S2-2103215","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"eNS"}],"crnumber":2722.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102907.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102911","title":"[DRAFT] LS Response on N3IWF FQDN for emergency service","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"LS out","for":"Approval","abstract":"LS on N3IWF FQDN for emergency service","secretary_remarks":"Response to S2-2102109. CC#1: Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11280,"status":"postponed","reservation_date":"2021-04-06 18:07:18","uploaded":"2021-04-06 18:28:03","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102911.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102912","title":"Correction on N3IWF selection for Emergency service","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Visited Country non-3GPP Emergency FQDN is used to determine which PLMNs in the visited country support emergency services in non-3GPP access. After PLMN selection for emergency service, if UE determines to select N3IWF, it shall use the Operator Identifier N3IWF FQDN or Tracking Area Identity N3IWF FQDN to select the address of an N3IWF in selected PLMN. Other small updates","secretary_remarks":"Confirm Spec version used - CR states h.0.0! CC#1: Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11290,"status":"postponed","reservation_date":"2021-04-06 18:07:18","uploaded":"2021-04-06 18:28:03","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.0.0","workitem":[{"winame":"TEI17"},{"winame":" 5GS_Ph1"}],"crnumber":2844.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102912.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102924","title":"FQDNs for N3IWF selection for emergency services","source":"Qualcomm","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce FQDNs for N3IWF selection for emergency services Add existing configured Emergency ePDG FQDN Separate the existing combined PLMN selection for emergency services via non-3GPP access into a procedure for stand-alone N3IWF selection and a combined N3IWF\/ePDG selection procedure for emergency services to enhance readability.","secretary_remarks":"CC#1: Postponed. Revised at S2-145E in S2-2104548","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11330,"status":"revised","reservation_date":"2021-04-06 19:23:32","uploaded":"2021-04-06 19:41:50","revisionof":"","revisedto":"S2-2104548","release":"Rel-17","crspec":23.501,"crspecversion":"17.0.0","workitem":[{"winame":"TEI17"}],"crnumber":2848.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102924.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102925","title":"[DRAFT] Reply LS on N3IWF FQDN for emergency service","source":"Qualcomm","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4, CT WG1. Attachments: S2-2102924 (TS 23.501 CR#2848)","secretary_remarks":"Response to S2-2102109. CC#1: Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11320,"status":"postponed","reservation_date":"2021-04-06 19:29:17","uploaded":"2021-04-06 19:41:50","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4, CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102925.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102927","title":"Clarification for Visited Country FQDN DNS query for SNPNs with locally assigned NIDs","source":"Qualcomm Incorprorated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the following Note to clause 6.3.6.2a: 'NOTE X: Locally assigned NIDs are not supported, since a DNS cannot be properly configured for multiple SNPNs using the same locally assigned NID. If the visited country mandates the selection of an N3IWF in this country, the NAPTR record(s) associated to the Visited Country FQDN of SNPNs that use a locally assigned NID can be provisioned with the replacement field containing an FQDN that cannot be resolved to an IP address.'","secretary_remarks":"CC#1: Postponed. Revised at S2-145E in S2-2103750","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11340,"status":"revised","reservation_date":"2021-04-06 19:35:16","uploaded":"2021-04-06 19:41:50","revisionof":"","revisedto":"S2-2103750","release":"Rel-16","crspec":23.501,"crspecversion":"16.8.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":2849.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102927.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102929","title":"[DRAFT] Reply LS on Requirement on Support of VxLAN Tunnelling","source":"Qualcomm","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC: SA WG5","secretary_remarks":"Response to S2-2102114. Merged into S2-2103236","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11560,"status":"merged","reservation_date":"2021-04-06 19:37:56","uploaded":"2021-04-06 19:41:50","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"BEPoP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"SA WG5","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102929.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102930","title":"SRVCC procedure in case of PDN connections without TI","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Rel-17 mirror CR: Summary of change: For 5G SRVCC to 3G it is described in 23.501 \u00a7 5.17.2.4 'Mobility between 5GS and GERAN\/UTRAN' that 'After the 5G SRVCC to UTRAN, all the PDU sessions of the UE are released'; The same behaviour may take place at the indirect mobility 5G ( 4G ( (SRVCC) 3G Thus at SRVCC from EPC to 3G the MME issues a Forward Relocation Request message to the SGSN but this Forward Relocation Request does not transfer to the SGSN PDN connections for which no TI has been negotiated with the UE (PDN connections corresponding to PDU Sessions established over 5GS). No impact is thus expected to the ENB. It has to be Noted that 23.060 \u00a7 6.9.2.2.2 Combined Hard Handover and SRNS Relocation Procedure already foresees that at SRNS relocation: 'The list of RABs requested by the new SGSN may differ from list of RABs established in the Source RNC contained in the Source-RNC to target RNC transparent container'.","secretary_remarks":"Revision of S2-2102762. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10810,"status":"noted","reservation_date":"2021-04-06 19:55:26","uploaded":"2021-04-07 05:21:14","revisionof":"S2-2102762","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":2697.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102930.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102933","title":"[DRAFT] Reply LS on Support of AF instance change","source":"Nokia, Nokia Shanghai Bell","contact":"Shubhranshu Singh","contact-id":86758,"tdoctype":"LS out","for":"Approval","abstract":"Response LS on support of AF influence change","secretary_remarks":"Response to S2-2102091. S2-2102933r02 agreed. Revised to S2-2103220","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10940,"status":"revised","reservation_date":"2021-04-06 20:08:29","uploaded":"2021-04-06 21:20:05","revisionof":"","revisedto":"S2-2103220","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102933.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102935","title":"Correction to Notification of user plane management event","source":"Nokia, Nokia Shanghai Bell","contact":"Shubhranshu Singh","contact-id":86758,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updates to the Notification of user plane management event procedures","secretary_remarks":"Merged into S2-2103222","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10960,"status":"merged","reservation_date":"2021-04-06 20:49:05","uploaded":"2021-04-06 21:05:52","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.8.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":2727.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102935.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102939","title":"Correction to Notification of user plane management event","source":"Nokia, Nokia Shanghai Bell","contact":"Shubhranshu Singh","contact-id":86758,"tdoctype":"CR","for":"Approval","abstract":"Rel-17 mirror CR: Summary of change: Updates to the Notification of user plane management event procedures","secretary_remarks":"Merged into S2-2103221","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10970,"status":"merged","reservation_date":"2021-04-06 20:57:38","uploaded":"2021-04-06 21:11:13","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":2728.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102939.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102952","title":"SRVCC PS HO without Trasaction Identifier","source":"Cisco","contact":"Irfan Ali","contact-id":74090,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: MME proceeds with PS HO for SRVCC even if Transaction ID and other 3G\/2G QoS parameters are not prosent for EPS Bearers. For these bearers, the MME does not include the PDP Context parmeters. Only SRB is setup on the target side for the PS connection.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10870,"status":"noted","reservation_date":"2021-04-06 23:50:08","uploaded":"2021-04-06 23:53:36","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.216,"crspecversion":"16.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":370.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102952.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102954","title":"LS from GSMA FSAG: Prevention of attacks on sliced core network","source":"GSMA FSAG (FSAG Doc 91_005)","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"Background: GSMA has been made aware by AdaptiveMobile Security through its Coordinated Vulnerability Disclosure Programme on three attack vectors to a sliced 5G core network. Action: GSMA politely requests CT WG4, SA WG2 and SA WG3 to consider the above information and validate their current specifications in light of the attack scenarios above and evaluate whether the current specifications sufficiently mitigate those threats, or whether further clarifications and mitigation measures are required in short or long-term.","secretary_remarks":"Response drafted in S2-2102958. Final response in S2-2103213","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10220,"status":"replied to","reservation_date":"2021-04-07 12:32:38","uploaded":"2021-04-07 12:33:17","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4, SA WG3, SA WG2","Cc":"","lsoriginalls":"FSAG Doc 91_005","lsreply":"S2-2103213","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102954.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102955","title":"LS from ITU-T SG11: LS\/r on draft Recommendation ITU-T Q.Sig_Req_ETS_IMS_roaming 'Signalling requirements for emergency telecommunication service in IMS roaming environment' (S2-210310)","source":"ITU-T SG11 (SG11-LS178)","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"This liaison statement aims to reply the LS from 3GPP TSG SA WG2 and inform 3GPP TSG SA WG2, ITU-T Study Group 2, 3GPP TSG SA, 3GPP TSG CT, and 3GPP TSG SA WG6 on the latest progress on the draft ITU-T Q.Sig_Req_ETS_IMS_roaming.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10250,"status":"noted","reservation_date":"2021-04-12 10:18:42","uploaded":"2021-04-12 10:19:50","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, ITU-T SG2","Cc":"TSG SA, SA WG6, TSG CT","lsoriginalls":"SG11-LS178","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102955.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102956","title":"Support of AF change","source":"CATT","contact":"Yuan Tao","contact-id":82804,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Addtion of Information on AF change (including indication of AF change, target AF ID and notification target address of the target AF) for AF influence on traffic routing.","secretary_remarks":"Mirror CR to S2-2102396. Created at CC#1. Mirror CR should not be TEI17. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10990,"status":"noted","reservation_date":"2021-04-12 13:43:15","uploaded":"2021-04-13 07:58:52","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.0.0","workitem":[{"winame":"5G_URLLC"},{"winame":" TEI17"}],"crnumber":2855.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102956.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102958","title":"[DRAFT] Reply LS to Prevention of attacks on sliced core network","source":"SA WG2","contact":"Alessio Casati","contact-id":82456,"tdoctype":"LS out","for":"Approval","abstract":"To: . CC: . Attachments: .","secretary_remarks":"Created at CC#1. Response to S2-2102954. S2-2102958r03 agreed. Revised to S2-2103213","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10230,"status":"revised","reservation_date":"2021-04-12 17:16:27","uploaded":"2021-04-12 17:17:06","revisionof":"","revisedto":"S2-2103213","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA FSAG, CT WG4, SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2102958.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103058","title":"Solving interworking to 5GS with N26 issue due to UE's N1 mode capability disabling\/enabling","source":"Nokia, Nokia Shanghai Bell, Ericsson","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: At EPS to 5GS mobility 1. R16 UE consider as released the PDN connections that were established over EPS and for which the UE has not received mapped 5GS QoS parameters from the network, 2. The MME does not transfer to 5GS a PDN connection that is not possible to be transferred to 5GS, e.g. PDN connection was established over EPC on a stand-alone PGW. (the UE has released it per item 1 above) 3. If the MME tries to transfer to 5GS a PDN connection that was established over EPC on a SMF+ PGW-C, what happens next is discussed below. At EPS to 5GS HO, the initial AMF invokes (step 4 of figure 4.11.1.2.2.2-1) the Nsmf_PDUSession_CreateSMContext service operation (UE EPS PDN Connection, initial AMF ID, data Forwarding information, Target ID) on the SMF identified by the SMF+PGW-C address and indicates HO Preparation Indication. \u2026. The SMF finds the corresponding PDU Session based on EPS Bearer Context(s). If the PDU Session Id was not received from the UE, , the SMF rejects the AMF request and the PDN connection is not further transferred to 5GS (assumed to be released by the UE per item 1 above).","secretary_remarks":"Revision of S2-2102164r02. Technically Endorsed. Revised at S2-145E in S2-2103993, S2-2104223","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10450,"status":"revised","reservation_date":"2021-04-19 13:17:15","uploaded":"2021-04-20 14:31:19","revisionof":"S2-2102164","revisedto":"S2-2103993, S2-2104223","release":"Rel-16","crspec":23.502,"crspecversion":"16.8.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":2465.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2103058.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103059","title":"Solving interworking to 5GS with N26 issue due to UE's N1 mode capability disabling\/enabling","source":"Nokia, Nokia Shanghai Bell, Ericsson","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: At EPS to 5GS mobility UE consider as released the PDN connections that were established over EPS while the UE did not receive 5GS parameters from the network as answer to the PDN connection request. This covers the case where the UE did not provide a PDU Session ID to the network when establishing a PDN connection while the N1 mode is diasabled The MME does not transfer to 5GS a PDN connection that is not possible to be transferred to 5GS, e.g. PDN connection was established over EPC on a stand-alone PGW. (the UE has released it per item 1 above) The MME tries to transfer to 5GS a PDN connection that was established over EPC on a SMF+ PGW-c. what happens next is discussed below. At EPS to 5GS HO, the initial AMF invokes (step 4 of figure 4.11.1.2.2.2-1) the Nsmf_PDUSession_CreateSMContext service operation (UE EPS PDN Connection, initial AMF ID, data Forwarding information, Target ID) on the SMF identified by the SMF+PGW-C address and indicates HO Preparation Indication (to avoid switching the UP path). \u2026. The SMF finds the corresponding PDU Session based on EPS Bearer Context(s). IF the PDU Session Id was not received from the UE; the SMF rejects the AMF request and the PDN connection is not further transferred to 5GS (assumed to be released by the UE per item 1 above). In summary, the R17 behavior is the same than in R16 except that R17 specifications supports the UE option where the UE sends a PDU Session ID to the network when establishing a PDN connection while N1 mode is Disabled R17 specificiation supports MME initiating PDN disconnection with reactivation required when N1 mode is (re-)enabled if MME has selected standalone PGW.","secretary_remarks":"Revision of S2-2102165r01, merging S2-2102774. Technically Endorsed. Revised at S2-145E in S2-2103994, S2-2104004","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10470,"status":"revised","reservation_date":"2021-04-19 13:17:16","uploaded":"2021-04-20 14:31:19","revisionof":"S2-2102165","revisedto":"S2-2103994, S2-2104004","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":2603.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2103059.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103060","title":"The impact of UE N1 mode change in EPS","source":"ZTE, Nokia, NokiaShanghai Bell, Ericsson, Samsung","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If the UE supports 5GC NAS, at PDN connection establishment in EPC, the UE allocates a PDU Session ID and sends it to the SMF+PGW-C via PCO, regardless of whether N1 mode is enabled or disabled. The SMF+PGW-C always send the mapped Qos parameter to UE if it receives the PDU session ID and mobility from EPS to 5GS is allowed by the operator","secretary_remarks":"Revision of S2-2102779r03, merging S2-2102771. Technically Endorsed. Revised at S2-145E in S2-2104446","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10520,"status":"revised","reservation_date":"2021-04-19 13:17:17","uploaded":"2021-04-20 14:31:19","revisionof":"S2-2102779","revisedto":"S2-2104446","release":"Rel-17","crspec":23.501,"crspecversion":"17.0.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":2814.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2103060.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103061","title":"LS on E-RABs that cannot be handed over to 2G\/3G or 5G","source":"SA WG2","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3. CC: CT WG4. Attachments: 23.216 CR0369 (S2-2103062)","secretary_remarks":"Revision of S2-2102751r06. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10740,"status":"approved","reservation_date":"2021-04-19 13:17:18","uploaded":"2021-04-20 14:31:21","revisionof":"S2-2102751","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2102093","lsto":"RAN WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2103061.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103062","title":"Clarificaton on the eNB behavoir for SRVCC","source":"ZTE, Nokia, Nokia Shanghai Bell","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To avoid the SRVCC faliure, the eNB may be configued to initiate the SRVCC CS HO only.","secretary_remarks":"Revision of S2-2102776r04. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10840,"status":"agreed","reservation_date":"2021-04-19 13:17:18","uploaded":"2021-04-20 14:31:21","revisionof":"S2-2102776","revisedto":"","release":"Rel-16","crspec":23.216,"crspecversion":"16.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":369.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-210330","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2103062.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103213","title":"Reply LS on Prevention of attacks on sliced core network","source":"SA WG2","contact":"Alessio Casati","contact-id":82456,"tdoctype":"LS out","for":"Approval","abstract":"To: GSMA FSAG. CC: CT WG4, SA WG3","secretary_remarks":"Revision of S2-2102958r03. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10240,"status":"approved","reservation_date":"2021-04-19 13:17:36","uploaded":"2021-04-20 14:31:23","revisionof":"S2-2102958","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2102954","lsto":"GSMA FSAG","Cc":"CT WG4, SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2103213.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103214","title":"New service operation of Namf_Communication_CancelRelocateUEContext","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add new service operation of Namf_Communication_CancelRelocateUEContext","secretary_remarks":"Revision of S2-2102906r02. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10320,"status":"agreed","reservation_date":"2021-04-19 13:17:36","uploaded":"2021-04-20 14:31:23","revisionof":"S2-2102906","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.8.0","workitem":[{"winame":"eNS"}],"crnumber":2721.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-210334","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2103214.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103215","title":"New service operation of Namf_Communication_CancelRelocateUEContext","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","for":"Approval","abstract":"Rel-17 mirror CR: Summary of change: Add new service operation of Namf_Communication_CancelRelocateUEContext","secretary_remarks":"Revision of S2-2102907. Approved. Revised at S2-145E in S2-2104455","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10340,"status":"revised","reservation_date":"2021-04-19 13:17:37","uploaded":"2021-04-20 14:31:23","revisionof":"S2-2102907","revisedto":"S2-2104455","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"eNS"}],"crnumber":2722.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2103215.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103216","title":"Reply LS on Reply LS on NAS Non delivery for RRC Inactive state","source":"SA WG2","contact":"Qian Chen","contact-id":83135,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3. CC: CT WG4","secretary_remarks":"Revision of S2-2102172r09 merging S2-2102605, S2-2102563. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10370,"status":"approved","reservation_date":"2021-04-19 13:17:38","uploaded":"2021-04-20 14:31:23","revisionof":"S2-2102172","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2102083","lsto":"RAN WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2103216.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103217","title":"LS Reply on NSI ID on N7 interface","source":"SA WG2","contact":"Haiyang Sun","contact-id":79579,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC: CT WG4. Attachments: TS 23.502 CR2616, TS 23.502 CR2617, TS 23.502 CR2618, TS 23.503 CR0548, TS 23.503 CR0549, TS 23.503 CR0550, TS 23.288 CR 0264, TS 23.288 CR0265","secretary_remarks":"Revision of S2-2102220r01. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10600,"status":"approved","reservation_date":"2021-04-19 13:17:38","uploaded":"2021-04-20 14:31:23","revisionof":"S2-2102220","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"},{"winame":" 5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2102090","lsto":"CT WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2103217.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103218","title":"Delete NSI ID via N7 interface","source":"Huawei, HiSilicon, Ericsson","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Delete NSI ID in N7 interface.","secretary_remarks":"Revision of S2-2102221r02. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10620,"status":"agreed","reservation_date":"2021-04-19 13:17:38","uploaded":"2021-04-20 14:31:23","revisionof":"S2-2102221","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.13.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2616.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-210324","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2103218.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103219","title":"Delete NSI ID via N7 interface","source":"Huawei, HiSilicon, Ericsson","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Rel-17 mirror CR: Summary of change: Delete NSI ID in N7 interface. Clarify NSI ID is only applicable when the consumer is NSSF but not PCF.","secretary_remarks":"Revision of S2-2102228r07. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10700,"status":"agreed","reservation_date":"2021-04-19 13:17:39","uploaded":"2021-04-20 14:31:23","revisionof":"S2-2102228","revisedto":"","release":"Rel-17","crspec":23.288,"crspecversion":"17.0.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":265.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"SP-210330","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2103219.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103220","title":"LS response on Support of AF instance change","source":"SA WG2","contact":"Shubhranshu Singh","contact-id":86758,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. Attachments: TS 23.502 CR2643 (S2-2103222), CR2667 (S2-2103221)","secretary_remarks":"Revision of S2-2102933r02. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10950,"status":"approved","reservation_date":"2021-04-19 13:17:41","uploaded":"2021-04-20 14:31:23","revisionof":"S2-2102933","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2102091","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2103220.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103221","title":"Support of AF change","source":"Huawei, HiSilicon, CATT, Nokia, Nokia Shanghai Bell,Ericsson","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Rel-17 mirror CR: Summary of change: Updates to the Notification of user plane management event procedures, ensuring that information received directly by SMF via _AppRelocationInfo, if any, are aligned with those received within the PCC rules via N7.","secretary_remarks":"Revision of S2-2102562r02, merging S2-2102939. Approved. Revised at S2-145E in S2-2104724","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10930,"status":"revised","reservation_date":"2021-04-19 13:17:41","uploaded":"2021-04-20 14:31:23","revisionof":"S2-2102562","revisedto":"S2-2104724","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"5G_URLLC"},{"winame":" TEI17"}],"crnumber":2667.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2103221.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103222","title":"Support of AF change","source":"CATT, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Ericsson","contact":"Yuan Tao","contact-id":82804,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updates to the Notification of user plane management event procedures, ensuring that information received directly by SMF via _AppRelocationInfo, if any, are aligned with those received within the PCC rules via N7.","secretary_remarks":"Revision of S2-2102397r07, merging S2-2102561, S2-2102935. Approved. Revised at S2-145E in S2-2104714","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11010,"status":"revised","reservation_date":"2021-04-19 13:17:42","uploaded":"2021-04-20 14:31:23","revisionof":"S2-2102397","revisedto":"S2-2104714","release":"Rel-16","crspec":23.502,"crspecversion":"16.8.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":2643.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2103222.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103223","title":"Updates on PCC rule triggered GTP-U path monitoring","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In case the PCC rule with QoS Monitoring Policy triggers the GTP-U path monitoring, the SMF ignores the QoS Monitoring Policy when performing QoS Flow Binding.","secretary_remarks":"Revision of S2-2102384r03. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11070,"status":"agreed","reservation_date":"2021-04-19 13:17:43","uploaded":"2021-04-20 14:31:23","revisionof":"S2-2102384","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.8.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":2745.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-210329","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2103223.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103224","title":"Reply LS on QoS monitoring control for Service Data Flows","source":"SA WG2","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC: CT WG4. Attachments: S2-2102383 (CR 0537), S2-2103223 (CR 2745)","secretary_remarks":"Revision of S2-2102382. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11040,"status":"approved","reservation_date":"2021-04-19 13:17:44","uploaded":"2021-04-20 14:31:23","revisionof":"S2-2102382","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2102092","lsto":"CT WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2103224.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103225","title":"Application Identifier for SCEF API ChargebleParty and AS Session with QoS","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce Application Identifier for AS session with required QoS case in clause 5.11 Introduce Application Identifier for chargeable party case in clause 5.12","secretary_remarks":"Revision of S2-2102175r01. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11110,"status":"agreed","reservation_date":"2021-04-19 13:17:44","uploaded":"2021-04-20 14:31:23","revisionof":"S2-2102175","revisedto":"","release":"Rel-17","crspec":23.682,"crspecversion":"16.9.0","workitem":[{"winame":"5GMS3"},{"winame":" TEI17"}],"crnumber":475.0,"crrevision":2.0,"crcategory":"C","tsg_crp":"SP-210341","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2103225.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103226","title":"Application Identifier for NEF API ChargebleParty and AF Session with QoS","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce Application Identifier for Chargeble Party at AF session setup, in clause 4.15.6.4. Introduce Application ID for AF session with QoS procedures, in clause 4.15.6.6. Introduce Application Identifier in ChargeableParty service operations in clause 5.2.6.8. Introduce Application Identifier in AFSessionWithQoS service operations in clause 5.2.6.9.","secretary_remarks":"Revision of S2-2102176r01. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11130,"status":"agreed","reservation_date":"2021-04-19 13:17:45","uploaded":"2021-04-20 14:31:23","revisionof":"S2-2102176","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"5GMS3"},{"winame":" TEI17"}],"crnumber":2490.0,"crrevision":2.0,"crcategory":"C","tsg_crp":"SP-210341","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2103226.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103227","title":"DNN and S-NSSAI for NEF API ChargebleParty and AF Session with QoS","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce DNN and S-NSSAI for Chargeble Party at AF session setup, in clause 4.15.6.4 Introduce DNN and S-NSSAI for AF session with QoS procedures, in clause 4.15.6.6 Introduce DNN and S-NSSAI in ChargeableParty service operations Introduce DNN and S-NSSAI in AFSessionWithQoS service operations","secretary_remarks":"Revision of S2-2102153r01. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11150,"status":"agreed","reservation_date":"2021-04-19 13:17:47","uploaded":"2021-04-20 14:31:23","revisionof":"S2-2102153","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"5GMS3"},{"winame":" TEI17"}],"crnumber":2491.0,"crrevision":2.0,"crcategory":"C","tsg_crp":"SP-210341","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2103227.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103228","title":"LS Reply on Server Domain Name Usage for Application Traffic Detection","source":"SA WG2","contact":"Haiyang Sun","contact-id":79579,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG4.CC: CT WG3. Attachments: 23.502 CR 2490\/2491, 23.682 CR 0475","secretary_remarks":"Revision of S2-2102219r05, merging S2-2102174. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11170,"status":"approved","reservation_date":"2021-04-19 13:18:06","uploaded":"2021-04-20 14:31:23","revisionof":"S2-2102219","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5GMS3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2102102","lsto":"SA WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2103228.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103229","title":"Reply LS on Group Subscriptions","source":"SA WG2","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. Attachments: S2-2101579","secretary_remarks":"Revision of S2-2102845r05, merging S2-2102261, S2-2102173, S2-2102404. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11220,"status":"approved","reservation_date":"2021-04-19 13:18:06","uploaded":"2021-04-20 14:31:23","revisionof":"S2-2102845","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2102107","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2103229.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103230","title":"Support for L2TP on N6","source":"Ericsson, Nokia, Nokia Shanghai Bell, ZTE, China Mobile, China Telecom","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add support for providing L2TP information in 5GS","secretary_remarks":"Revision of S2-2102137r02. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11380,"status":"agreed","reservation_date":"2021-04-19 13:18:06","uploaded":"2021-04-20 14:31:23","revisionof":"S2-2102137","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.0.0","workitem":[{"winame":"BEPoP"},{"winame":" TEI17"}],"crnumber":2691.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"SP-210346","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2103230.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103231","title":"Support for L2TP on SGi","source":"Ericsson, ZTE, China Mobile, China Telecom, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add support for providing L2TP information from PGW-C to PGW-U. Clarify that PGW-U may provide UE IP address to PGW-C.","secretary_remarks":"Revision of S2-2102138r03. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11400,"status":"agreed","reservation_date":"2021-04-19 13:18:19","uploaded":"2021-04-20 14:31:23","revisionof":"S2-2102138","revisedto":"","release":"Rel-17","crspec":23.214,"crspecversion":"16.2.0","workitem":[{"winame":"BEPoP"},{"winame":" TEI17"}],"crnumber":76.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"SP-210346","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2103231.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103232","title":"Reply LS on the support of L2TP with CUPS","source":"SA WG2","contact":"Stefan Rommer","contact-id":25950,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4, CT WG3, SA WG3. Attachment: TS 23.501 CR2691, TS 23.502 CR2602, TS 23.214 CR0076","secretary_remarks":"Revision of S2-2102139. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11420,"status":"approved","reservation_date":"2021-04-19 13:18:20","uploaded":"2021-04-20 14:31:23","revisionof":"S2-2102139","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"BEPoP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2102110","lsto":"CT WG4, CT WG3, SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2103232.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103233","title":"Support for L2TP on N6","source":"Nokia, Nokia Shanghai Bell, Ericsson","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add support for L2TP in 5GS.","secretary_remarks":"Revision of S2-2102154r02. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11440,"status":"agreed","reservation_date":"2021-04-19 13:18:20","uploaded":"2021-04-20 14:31:23","revisionof":"S2-2102154","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"BEPoP"},{"winame":" TEI17"}],"crnumber":2602.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"SP-210346","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2103233.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103234","title":"Update of LCS exposure via NEF","source":"Huawei","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to clarify it is the NEF to derive the LCS client type, when the request is from an AF.","secretary_remarks":"Revision of S2-2102819r01. Approved. Covered by S2-2104833 at S2-145E","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11480,"status":"noted","reservation_date":"2021-04-19 13:18:21","uploaded":"2021-04-20 14:31:23","revisionof":"S2-2102819","revisedto":"","release":"Rel-16","crspec":23.273,"crspecversion":"16.6.0","workitem":[{"winame":"5G_eLCS"}],"crnumber":168.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2103234.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103235","title":"LS Response on the input parameters of the LCS subscription request from an AF via NEF","source":"SA WG2","contact":"Runze Zhou","contact-id":60945,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC: CT WG4. Attachments: S2-2103234","secretary_remarks":"Revision of S2-2102820. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11460,"status":"approved","reservation_date":"2021-04-19 13:18:22","uploaded":"2021-04-20 14:31:23","revisionof":"S2-2102820","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_eLCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2100020","lsto":"CT WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2103235.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103236","title":"LS on Requirement on Support of VxLAN Tunnelling","source":"SA WG2","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC: SA WG5","secretary_remarks":"Revision of S2-2102868r05, merging S2-2102824, S2-2102929. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":11550,"status":"approved","reservation_date":"2021-04-19 13:18:22","uploaded":"2021-04-20 14:31:23","revisionof":"S2-2102868","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"BEPoP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2102114","lsto":"CT WG4","Cc":"SA WG5","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_144E_Electronic\/Docs\/S2-2103236.zip","group":"S2","meeting":"S2-144-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]