[{"name":"S2-2002634","title":"LS from CT WG1: Reply LS on extended NAS timers for CE in 5GS","source":"CT WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 thanks RAN WG2 for the information provided on RAN delay for CE in 5GS. CT WG1 has decided, based on the feedback provided, to apply the same principles for NAS timer extension at CE as was done in EPS. The support of eDRX up to 10.24s in RRC_INACTIVE for WB-N1 UEs is in the understanding of CT WG1 comparable to the eDRX up to 10.24s supported in RRC_CONNECTED in EPS. As it was decided in EPS to not apply any additional NAS timer extension at the eDRX up to 10.24s supported in RRC_CONNECTED, the same decision is taken for eDRX in RRC_INACTIVE for WB-N1 in 5GS. Further it is the CT WG1 understanding that RAN delay for CE at RRC_INACTIVE in WB-N1 mode is covered by the general NAS timer extensions for CE, and no additional NAS timer extension is needed for this specific case.","secretary_remarks":"Noted","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13020,"status":"noted","reservation_date":"2020-03-26 10:57:37","uploaded":"2020-03-27 15:57:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"RAN WG3, SA WG2","lsoriginalls":"C1-200717","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002634.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002636","title":"LS from CT WG1: LS on service area restriction for CIoT 5GS optimization","source":"CT WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"Overall description: CT WG1 would like to seek guidance on the applicability of service area restriction for UEs that use CIoT 5GS optimizations. CT WG1 would like to ask the following question: Is the UE using CP CIoT or UP CIoT optimization allowed to send or receive data in a non-allowed area, including exception data? Action: CT WG1 respectfully requests SA WG2 to provide an answer to the question above.","secretary_remarks":"Responses drafted in S2-2002772 and S2-2002934. Postponed","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13030,"status":"postponed","reservation_date":"2020-03-26 10:57:37","uploaded":"2020-03-27 15:57:56","revisionof":"","revisedto":"S2-2003524","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C1-200839","lsreply":"S2-2003711","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002636.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002641","title":"LS from CT WG1: Reply LS on Rel-16 NB-IoT enhancements","source":"CT WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 thanks SA WG2 for their LS on 'Reply LS on Rel-16 NB-IoT enhancements'. CT WG1 has discussed the NAS impacts of both options provided by SA WG2 and would like to provide the following feedback: - Both options are feasible from the NAS protocol perspective. Additionally, CT WG1 would like to receive feedback on the following questions to decide the NAS part of the solution to pursue: - Question to RAN WG2: What values shall be supported for UE specific DRX for NB-IoT? - Question to RAN WG3: When the UE is accessing via NB-IoT, is the legacy MME is mandated to provide the stored UE specific DRX value, that was requested by the UE over NAS, in the S1 paging message to the eNB?. Action: CT WG1 kindly asks SA WG2 to take the information provided above into account.","secretary_remarks":"Noted","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13080,"status":"noted","reservation_date":"2020-03-26 10:57:37","uploaded":"2020-03-27 15:57:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3, SA WG2","Cc":"TSG CT, TSG RAN, TSG SA","lsoriginalls":"C1-201024","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002641.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002643","title":"LS from CT WG1: LS on suspend indication to the NAS","source":"CT WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"There seems to be an ambiguity associated with the suspend indication that the RRC provides to the NAS as follows: a) Section 5.3.8.7 of TS 36.331 (titled: UE actions upon entering RRC_INACTIVE) states: '1> indicate the suspension of the RRC connection to upper layers;' b) For a UE that is using user plane CIoT 5GS optimization, section 5.3.12 of TS 36.331 (titled: UE actions upon leaving RRC_CONNECTED or RRC_INACTIVE) states: '1> if leaving RRC_CONNECTED was triggered by suspension of the RRC: \u2026 [SKIP] \u2026 2> store the following information provided by E-UTRAN: 3> the resumeIdentity; \u2026 [SKIP] \u2026 2> indicate the suspension of the RRC connection to upper layers;' For the UE in WB-E-UTRA that is using user plane CIoT 5GS optimization, the NAS cannot know the trigger for the suspend indication from the lower layers i.e. RRC entering RRC inactive state or a suspension of the RRC connection for user plane CIoT 5GS optimization.","secretary_remarks":"Noted","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13090,"status":"noted","reservation_date":"2020-03-26 10:57:37","uploaded":"2020-03-27 15:57:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"SA WG2","lsoriginalls":"C1-201040","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002643.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002644","title":"LS from CT WG1: Reply LS on Mobile-terminated Early Data Transmission","source":"CT WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 thanks RAN WG2 for the information provided on MT-EDT. CT WG1 has agreed updates to 24.301 based on approved updates of 23.401 and the feedback given by RAN WG2. The CT WG1 updates of NAS protocol will introduce explicit support indicators from UE to network for control plane MT-EDT and user plane MT-EDT respectively. For further details, see the attached CT WG1 agreed CR. Action: CT WG1 asks. RAN WG2 and SA WG2 to take the information provided above into account and update their specifications accordingly, if needed.","secretary_remarks":"Noted","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13100,"status":"noted","reservation_date":"2020-03-26 10:57:37","uploaded":"2020-03-27 15:57:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, SA WG2","Cc":"CT WG4, RAN WG3, TSG RAN, TSG SA","lsoriginalls":"C1-201062","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002644.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002645","title":"LS from CT WG3: Reply LS on Service on I-NEF Event Exposure","source":"CT WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"CT WG3 thanks SA WG2 for the reply LS on Service on I-NEF Event Exposure. And would like to provide following feedback including some further questions. In stage 3, the NEF event exposure services are specified in two TSes, i.e. TS 29.122\/29.522 for NEF northbound APIs, and TS 29.591 for NEF southbound APIs. CT WG3 acknowledges SA WG2 that different formats of UE Id are used, i.e. external format (e.g. external group id) in northbound APIs and internal format (e.g. SUPI) in southbound APIs. SA WG2 S2-2001575 states: - NEF Event Exposure is designed for the consumer to subscribe to notifications. But via I-NEF Event Exposure, AMF or SMF is not subscribing to receive I-NEF notifications but configuring a routing address for sending its own notifications by means of subscription on behalf of third party NF (i.e. the NEF). This implies that the I-NEF processing for NEF Event Exposure differs from NEF processing of the same service operation. The above text implies that a subscription service is not used for subscription purpose but for configuration. The I-NEF will receive event notification from its NF service consumer (e.g. AMF, SMF) but not from other NF service provider. CT WG3 have the following questions:. Question 1: Why 'NF ID' is required for the Ninef_EventExposure_Subscribe request? Such NF ID is not included in Nnef_EventExposure_Subscribe operation, also not included in clause 4.15.1 of TS 23.502, is there any specific handling on I-NEF for the NF ID? Question 2: If Q1 is required, is the 'NF ID' an NF service consumer ID or producer ID? Question 3: Why '(Set of) Event ID(s)', 'Target of Event Reporting (SUPI or Internal Group Identifier)' and 'Event Reporting Information' in Ninef_EventExposure_Subscribe request are required for the Ninef_EventExposure_Subscribe operation and what's the I-NEF behaviour upon receipt of these information? Question 4: Is it possible that the target address of I-NEF is locally configured in NFs (e.g. AMF) or retrieved from NRF so that the NFs (e.g. AMF) sends Namf_EventExposure_Notify (or Nsmf_EventExposure_Notify) directly to the I-NEF to skip the Ninef_EventExposure_Subscribe? Question 5: Since the Ninef_EventExposure_Notify is removed in the SA WG2 CR in C3-201029\/S2-2001575, instead the Namf_EventExposure_Notify (or Nsmf_EventExposure_Notify) is sent by I-NEF to the NEF. Is I-NEF pretending to be the NF (e.g. AMF\/SMF)? What is the relationship between I-NEF and NF? Action: CT WG3 kindly asks SA WG2 to answer the above questions and update their specifications if necessary.","secretary_remarks":"Responses drafted in S2-2002758 and S2-2002988. Postponed","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13110,"status":"postponed","reservation_date":"2020-03-26 10:57:38","uploaded":"2020-03-27 15:57:56","revisionof":"","revisedto":"S2-2003528","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"C3-201494","lsreply":"S2-2004035","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002645.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002647","title":"LS from CT WG4: LS on MO exception data","source":"CT WG4","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 thanks SA WG2 for the LS on (S2-2001573 \/ C4-200386). The LS clarifies two issues related to MO exception data (Q4\/A4 and Q5\/A5). CT WG4 however has identified an additional issue. The stage 2 solution for rate control enforcement of normal and exception data relies on the AMF updating the SMF\/UPF and NEF upon changes of the RRC signalling connection establishment cause from 'normal data' to 'exception data' and vice-versa, and on the UPF applying the normal data rate or the normal data rate plus the additional data rate dependent on whether the RRC establishment has been established for 'normal' or 'exception' data. Currently, UE can send to the network 'MO exception data' and non 'MO exception data' indication only during RRC connection establishment, i.e. during transition from idle to connected mode, or during the connection resume. It is not clear what happens if UE is in a connected state and decides to change the UL data 'type'. That is, if UE sends one or more 'ordinary' data packet(s) and then decides to send one or more 'exceptional' data packet(s). In CT WG4 understanding, currently there is no way for the UE to inform the network about the change. This deficiency has a direct and negative implications on an UPF ability to accurately count UL MO data. For instance, if the UE sends exception data using a RRC signalling connection that had been setup for normal data, and the normal data rate limit is exceeded in UPF but the additional (exception) data rate limit won't, the UPF would drop the exception data that should normally have been delivered, according to the stage 2 solution defined for rate control enforcement by SA WG2. CT WG4 did not find an explicit requirements in stage 2 or a stage 3 specification (RAN WG2, CT WG1), which defines what shall the UE do in such use case to resolve the problem. Action: CT WG4 asks SA WG2 group to kindly clarify how the rate control enforcement solution specified in stage 2 works in the above scenario and inform CT WG4 about the developments.","secretary_remarks":"Response drafted in S2-2002888. Final response in S2-2003504","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13170,"status":"replied to","reservation_date":"2020-03-26 10:57:38","uploaded":"2020-03-27 15:57:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG2, CT WG1","lsoriginalls":"C4-201003","lsreply":"S2-2003504","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002647.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002677","title":"Add External Group Identifier","source":"CATT","contact":"Chenxi Bao","contact-id":84373,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add External Group Identifier in NIDD configuration procedure.","secretary_remarks":"Noted","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13250,"status":"noted","reservation_date":"2020-04-02 06:04:57","uploaded":"2020-04-10 06:20:02","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2172.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002677.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002696","title":"Corrections for Availability after DDN Failure event with UPF buffering","source":"Nokia, Nokia Shanghai-Bell","contact":"Thomas Belling","contact-id":68266,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Procedures for the case where PCC control is used as proposed as solution B in S2-2001809 are added. Step 0 is removed. Step 2 is split into two parts; Configuration and discarding packets.","secretary_remarks":"e-meeting r02 agreed. Revised to S2-2003458.","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13260,"status":"revised","reservation_date":"2020-04-07 10:02:25","uploaded":"2020-04-10 16:09:28","revisionof":"","revisedto":"S2-2003458","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2177.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002696.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002705","title":"PCC control for DDD status and availability after DDN failure events","source":"Nokia, Nokia Shanghai-Bell","contact":"Thomas Belling","contact-id":68266,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If PCC is used, the PCF is notified about the subscription to the Downlink data delivery status events and to DDN failure events at the SMF to allow the PCF to provide policies as described below. PCC rules are extended with IEs to request that buffering is applied when UE is not reachable and to request the SMF to send notifications about Downlink data delivery status events and to DDN failure events (similar to the existing Information on AF subscription to UP change events IE)..","secretary_remarks":"e-meeting r07 agreed. Revised to S2-2003459.","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13280,"status":"revised","reservation_date":"2020-04-07 16:14:14","uploaded":"2020-04-10 16:09:28","revisionof":"","revisedto":"S2-2003459","release":"Rel-16","crspec":23.503,"crspecversion":"16.4.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":431.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002705.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002737","title":"Specify the new service Nsmf_PDUSession_ MessageTransfer","source":"ZTE","contact":"Yingjie Hong","contact-id":76103,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Define the service Nsmf_PDUSession_ MessageTransfer","secretary_remarks":"e-meeting r02 agreed. Revised to S2-2003460.","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13300,"status":"revised","reservation_date":"2020-04-08 06:43:44","uploaded":"2020-04-10 00:50:17","revisionof":"","revisedto":"S2-2003460","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2184.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002737.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002756","title":"Correcting I-NEF procedure","source":"Ericsson, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clauses 4.2.2.2.2 and 4.9.1.3.3: Remove description related to Ninef_EventExposure_Subscribe\/Unsubscribe. Clause 4.15.3.2.3a: Replace Ninef_EventExposure_Notify with Nsmf_EventExposure_Notify and Namf_EventExposure_Notify. Remove description and steps of Ninef_EventExposure_Subscribe\/Unsubscribe. Clarify that AMF\/SMF conveys the NEF's notification endpoint info to the I-NEF, and how to do it is left to stage 3. Clause 5.2.6A: Remove the I-NEF Event Exposure service.","secretary_remarks":"Noted","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13130,"status":"noted","reservation_date":"2020-04-08 20:10:03","uploaded":"2020-04-10 19:30:54","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2187.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002756.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002757","title":"Correcting I-NEF service","source":"Ericsson, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove I-NEF Services","secretary_remarks":"Noted","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13140,"status":"noted","reservation_date":"2020-04-08 20:10:04","uploaded":"2020-04-10 19:30:54","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2239.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002757.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002758","title":"[DRAFT] Reply LS on 'Reply LS on Service on I-NEF Event Exposure'","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"This paper provides feedback to CT WG3 on the updated I-NEF procedure.","secretary_remarks":"Response to S2-2002645. Noted","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13120,"status":"noted","reservation_date":"2020-04-08 20:10:05","uploaded":"2020-04-10 19:30:54","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002758.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002772","title":"[DRAFT] Reply LS on service area restriction for CIoT 5GS optimization","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Response LS to CT WG1 LS on service area restriction for CIoT 5GS optimization","secretary_remarks":"Response to S2-2002636. Noted","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13040,"status":"noted","reservation_date":"2020-04-08 21:13:34","uploaded":"2020-04-10 19:30:55","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002772.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002773","title":"Service Area Restriction clarification","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1.Update clause 5.3.4.1.1 to clarify that using MM siganlling to obtain user service is not allowed in a Non-Allowed Area. 2.(Editorial)Move priority service description to the beginning of the clause for easy understanding.","secretary_remarks":"Noted. Revised at S2#139E in S2-2003712","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13050,"status":"revised","reservation_date":"2020-04-08 21:13:34","uploaded":"2020-04-10 19:30:55","revisionof":"","revisedto":"S2-2003712, S2-2004204","release":"Rel-16","crspec":23.501,"crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2243.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002773.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002818","title":"Support for Control Plane data back-off timer indication","source":"CATT","contact":"Qiang Deng","contact-id":74437,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct the indication for Control Plane data specific NAS level congestion control.","secretary_remarks":"Noted","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13320,"status":"noted","reservation_date":"2020-04-09 08:16:41","uploaded":"2020-04-09 08:44:16","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2256.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002818.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002819","title":"Reachable event report during idle mode mobility","source":"CATT","contact":"Qiang Deng","contact-id":74437,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the AMF informs SMF about UE reachability during idle mode mobility from 5GS to EPS.","secretary_remarks":"Noted","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13330,"status":"noted","reservation_date":"2020-04-09 08:16:42","uploaded":"2020-04-09 08:44:16","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2202.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002819.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002832","title":"Correction to handling of Service Gap timer for regulatory prioritized services","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is corrected that the MME shall not ignore the active flag and signalling active flag when TAU Request message has been received for establishing a PDN connection for emergency bearer service or when a PDN connection for emergency bearer service is already established.","secretary_remarks":"e-meeting r04 agreed. Revised to S2-2003461.","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13340,"status":"revised","reservation_date":"2020-04-09 12:14:51","uploaded":"2020-04-09 17:02:56","revisionof":"","revisedto":"S2-2003461","release":"Rel-16","crspec":23.401,"crspecversion":"16.6.0","workitem":[{"winame":"TEI16"}],"crnumber":3599.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002832.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002833","title":"Correction to handling of Service Gap timer for regulatory prioritized services","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that Access to the network for regulatory prioritized services includes also cases for Mobility Registration and Periodic Registration.","secretary_remarks":"Noted","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13360,"status":"noted","reservation_date":"2020-04-09 12:14:52","uploaded":"2020-04-09 17:02:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2259.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002833.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002834","title":"Correction to handling of Service Gap timer for regulatory prioritzed services","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Exceptions pertaining to regulatory prioritized services like Emergency services or exception reporting are corrected.","secretary_remarks":"Approved","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13370,"status":"agreed","reservation_date":"2020-04-09 12:14:53","uploaded":"2020-04-09 17:02:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2204.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200422","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002834.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002886","title":"Small data rate control enforcement of normal and exception data","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove signaling of whether the UE is accessing with the RRC establishment cause set to 'MO exception data' or not from SMF to UPF\/NEF for small data rate control purposes. Clarify that for UPF and NEF, the 'maximum allowed rate' is equal to the 'number of packets per time unit' plus the 'number of additional allowed exception report packets per time unit'.","secretary_remarks":"e-meeting r01 agreed. Revised to S2-2003457.","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13200,"status":"revised","reservation_date":"2020-04-09 18:48:15","uploaded":"2020-04-09 20:35:11","revisionof":"","revisedto":"S2-2003457","release":"Rel-16","crspec":23.501,"crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2277.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002886.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002887","title":"Small data rate control enforcement of normal and exception data","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove signaling of whether the UE is accessing with the RRC establishment cause set to 'MO exception data' or not from SMF to UPF\/NEF for small data rate control purposes.","secretary_remarks":"Approved","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13220,"status":"agreed","reservation_date":"2020-04-09 18:52:46","uploaded":"2020-04-09 20:35:11","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2216.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200422","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002887.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002888","title":"[DRAFT] Reply LS on MO exception data","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4","secretary_remarks":"Response to S2-2002647. Original version agreed, clean up needed. Revised to S2-2003504.","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13180,"status":"revised","reservation_date":"2020-04-09 18:56:46","uploaded":"2020-04-09 20:35:11","revisionof":"","revisedto":"S2-2003504","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002888.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002901","title":"Update PDU Session release when Control Plane Only indication is not applicable","source":"Intel","contact":"Meghashree D Kedalagudde","contact-id":49483,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the criteria for which AMF can request SMF to release Control Plane Only PDU Session for which Control Plane Only indication does not apply any longer in the PDU session release procedure.","secretary_remarks":"e-meeting r02 agreed. Revised, merging S2-2002910, to S2-2003462.","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13380,"status":"revised","reservation_date":"2020-04-09 22:14:05","uploaded":"2020-04-10 20:13:26","revisionof":"","revisedto":"S2-2003462","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2219.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002901.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002902","title":"Change of the restriction of enhanced coverage in UE Configuration Update procedure","source":"Intel","contact":"Meghashree D Kedalagudde","contact-id":49483,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that when a change regarding the use of coverage enhancement occurs (e.g. due to a change in subscription) and the UE is in CM-CONNECTED, the AMF shall trigger the UE Configuration Update procedure to the UE and indicate a need to perform a registration procedure.","secretary_remarks":"e-meeting r02 agreed. Revised to S2-2003464.","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13430,"status":"revised","reservation_date":"2020-04-09 22:17:06","uploaded":"2020-04-10 20:13:26","revisionof":"","revisedto":"S2-2003464","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2220.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002902.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002910","title":"Clariifcation on PDU Session release procedure","source":"OPPO","contact":"Jianhua Liu","contact-id":72698,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. clarify the AMF trigger PDU Session release in case Control Plane Only indication becomes not applicable. 2. change step1b of clause 4.3.4.3 to same description of step 1f of clause 4.3.4.3","secretary_remarks":"Merged into S2-2003462","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13400,"status":"merged","reservation_date":"2020-04-10 03:20:03","uploaded":"2020-04-10 12:50:15","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2222.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002910.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002916","title":"Service area restrictions for CIoT optimizations","source":"Samsung, InterDigital","contact":"Kisuk Kweon","contact-id":80126,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the service area restriction to take into account both CP and UP CIoT 5GS optimization. In general, the UE should not be allowed access to a service (CP or UP CIoT 5GS optimizations) except for: - sending MO exception data - response to MT control plane data (since an application layer ACK may be required). The restrictions are considerd for a UE in CM-IDLE, CM-IDLE with Suspend, and CM-CONNECTED states.","secretary_remarks":"Noted","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13070,"status":"noted","reservation_date":"2020-04-10 04:19:26","uploaded":"2020-04-10 14:32:48","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.4.0","workitem":[{"winame":"FS_CIoT_5G"},{"winame":"5G_CIoT"}],"crnumber":2286.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002916.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002934","title":"[DRAFT] Reply LS on service area restriction for CIoT 5GS optimization","source":"Samsung","contact":"Kisuk Kweon","contact-id":80126,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Response to S2-2002636. Noted","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13060,"status":"noted","reservation_date":"2020-04-10 05:36:57","uploaded":"2020-04-10 14:32:48","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"FS_CIoT_5G"},{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002934.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002984","title":"Correction of NEF-based NIDD procedures","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the NIDD parameters (e.g., maximum packet size) in the PDU Session Estalishment Procedure. Add NIDD parameters, RDS support and Rate Control related information in the SMF-NEF connection Establishment\/Release procedure. Parameters in related Nnef service operations updated.","secretary_remarks":"e-meeting r01 agreed. Revised to S2-2003467.","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13510,"status":"revised","reservation_date":"2020-04-10 08:39:56","uploaded":"2020-04-10 12:44:04","revisionof":"","revisedto":"S2-2003467","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2244.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002984.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002988","title":"[DRAFT] Reply LS on Service on I-NEF Event Exposure","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Reply to CT WG3 questions in their LS on I-NEF","secretary_remarks":"Response to S2-2002645. Noted","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13150,"status":"noted","reservation_date":"2020-04-10 08:40:00","uploaded":"2020-04-10 12:44:04","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002988.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002989","title":"Corrections on I-NEF event exposure","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: I-NEF call flow and service operation parameters are corrected: If I-NEF is needed, the SMF sends notifications to that I-NEF. In clause 4.15.3.2.3a steps 2-3, the I-NEF need not subscribe to notifications from the AMF or the SMF. Monitoring event notifications are conditional, subject to the notification event detection. Ninef_EventExposure_Subscribe operation parameters are corrected: Remove 'Target of Event Reporting (SUPI or Internal Group Identifier)' and 'Event Filter' and make 'Event Reporting Information' optional in the Ninef_EventExposure_Subscribe operation. Add notification of target address to receive notifications to be sent to the NEF in the output of Ninef_EventNotification_Subscribe. Move 'AMF ID (GUAMI)' to optional in Ninef and Namf EventExposure_Notify.","secretary_remarks":"Noted","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13160,"status":"noted","reservation_date":"2020-04-10 08:40:00","uploaded":"2020-04-10 12:44:04","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2245.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002989.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002990","title":"Corrections to restriction of use of Enhanced Coverage","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Clarified that only one indication, i.e. support for restriction of use of Enhanced Coverage, is sent from UE to the AMF via N1 interface. 2. Updated Enhanced Coverage Restricted information for NB-IoT.","secretary_remarks":"e-meeting r03 agreed. Revised to S2-2003465.","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13450,"status":"revised","reservation_date":"2020-04-10 08:40:02","uploaded":"2020-04-10 12:44:04","revisionof":"","revisedto":"S2-2003465","release":"Rel-16","crspec":23.501,"crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2302.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002990.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002991","title":"[DRAFT] LS on update of restriction of use of Enhanced Coverage","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"LS to inform other groups that SA WG2 has updated restriction of enhanced coverage for NB-IoT","secretary_remarks":"Noted","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13480,"status":"noted","reservation_date":"2020-04-10 08:40:03","uploaded":"2020-04-10 12:44:04","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, CT WG4, RAN WG3","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002991.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003163","title":"UE specific DRX for NB-IoT in 5GC","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":84607,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Include a separate indication for Accepted UE specific DRX paramters for NB-IoT in Registration procedure. Clarify that AMF needs to ensure the correct Paging DRX parameters for the RAT are included in N2 paging message. New value in UE context for AMF.","secretary_remarks":"e-meeting r02 agreed. Revised to S2-2003466.","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13490,"status":"revised","reservation_date":"2020-04-10 17:13:56","uploaded":"2020-04-10 18:34:15","revisionof":"","revisedto":"S2-2003466","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2300.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003163.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003164","title":"[DRAFT] LS on SA WG2 status of MT-EDT in Rel-16","source":"Qualcomm Technologies Int","contact":"Miguel Griot","contact-id":84607,"tdoctype":"LS out","for":"Approval","abstract":"Status in SA WG2 for support of MT-EDT, no agreement was reached for 5G system.","secretary_remarks":"Original version agreed, clean up needed. Revised to S2-2003505.","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13230,"status":"revised","reservation_date":"2020-04-10 17:21:00","uploaded":"2020-04-10 18:34:15","revisionof":"","revisedto":"S2-2003505","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG3, TSG RAN WG2, RAN WG3, CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003164.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003165","title":"PDU Session release when Control Plane Only indication is not available","source":"Interdigital Inc.","contact":"Xiaoyan Shi","contact-id":72162,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add description of step 1f of clause 4.3.4.2 of TS 23.502 will be used to this PDU session release case.","secretary_remarks":"e-meeting r01 agreed. Revised to S2-2003463.","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13410,"status":"revised","reservation_date":"2020-04-10 17:24:08","uploaded":"2020-04-10 18:10:34","revisionof":"","revisedto":"S2-2003463","release":"Rel-16","crspec":23.501,"crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2361.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003165.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003166","title":"PDU session modificaiton when Restriction of use of Enhanced Coverage changes","source":"Interdigital Inc.","contact":"Xiaoyan Shi","contact-id":72162,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add 'when the AMF determines that NAS-SM timer shall be updated due to the change of Enhanced Coverage Restriction' to step 1f in subclause 4.3.3.2.","secretary_remarks":"Approved","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13470,"status":"agreed","reservation_date":"2020-04-10 17:32:42","uploaded":"2020-04-10 18:10:34","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2301.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200422","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003166.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003457","title":"Small data rate control enforcement of normal and exception data","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove signaling of whether the UE is accessing with the RRC establishment cause set to 'MO exception data' or not from SMF to UPF\/NEF for small data rate control purposes. Clarify that for UPF and NEF, the 'maximum allowed rate' is equal to the 'number of packets per time unit' plus (if available) the 'number of additional allowed exception report packets per time unit'.","secretary_remarks":"Revision of S2-2002886. Approved","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13210,"status":"agreed","reservation_date":"2020-04-27 09:10:56","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2002886","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2277.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200422","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003457.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003458","title":"Corrections for Availability after DDN Failure event with UPF buffering","source":"Nokia, Nokia Shanghai-Bell","contact":"Thomas Belling","contact-id":68266,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Procedures for the case where PCC control is used as proposed as solution B in S2-2001809 are added. Step 0 is removed. Step 2 is split into two parts; configuration and discarding packets.","secretary_remarks":"Revision of S2-2002696. Approved","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13270,"status":"agreed","reservation_date":"2020-04-27 09:10:58","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2002696","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2177.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200422","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003458.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003459","title":"PCC control for DDD status and availability after DDN failure events","source":"Nokia, Nokia Shanghai-Bell","contact":"Thomas Belling","contact-id":68266,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If PCC is used, the PCF is notified about the subscription to the Downlink data delivery status events and to DDN failure events at the SMF to allow the PCF to provide policies as described below. PCC rules are extended with IEs to request the SMF to send notifications about Downlink data delivery status events and to DDN failure events (similar to the existing Information on AF subscription to UP change events IE)..","secretary_remarks":"Revision of S2-2002705. Approved","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13290,"status":"agreed","reservation_date":"2020-04-27 09:10:59","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2002705","revisedto":"","release":"Rel-16","crspec":23.503,"crspecversion":"16.4.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":431.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200422","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003459.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003460","title":"Specify the new service Nsmf_PDUSession_ MessageTransfer","source":"ZTE, Ericsson","contact":"Yingjie Hong","contact-id":76103,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update service operation name to Nsmf_PDUSession_TransferMOData in step 2 of figure 4.25.4-1 and add step 7. Update service operation name to Nsmf_PDUSession_TransferMTData in step 4, 11, 15 of figure 4.25.5-1 Add new service operations in SMF service table 5.2.8.1-1. Add description of new service operations in 5.2.8.2.1 Add new service operation description in 5.2.8.2.x(New) and 5.2.8.2.y(New)","secretary_remarks":"Revision of S2-2002737. Approved","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13310,"status":"agreed","reservation_date":"2020-04-27 09:11:01","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2002737","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2184.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200422","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003460.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003461","title":"Correction to handling of Service Gap timer for regulatory prioritized services","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is corrected that the MME shall not ignore the active flag and signalling active flag when TAU Request message has been received for establishing a PDN connection for emergency bearer service or when a PDN connection for emergency bearer service is already established.","secretary_remarks":"Revision of S2-2002832. Approved","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13350,"status":"agreed","reservation_date":"2020-04-27 09:11:02","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2002832","revisedto":"","release":"Rel-16","crspec":23.401,"crspecversion":"16.6.0","workitem":[{"winame":"TEI16"},{"winame":"CIoT"}],"crnumber":3599.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200552","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003461.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003462","title":"Update PDU Session release when Control Plane Only indication is not applicable","source":"Intel, OPPO","contact":"Meghashree D Kedalagudde","contact-id":49483,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Add the criteria for which AMF can request SMF to release Control Plane Only PDU Session for which Control Plane Only indication does not apply any longer in the PDU session release procedure. 2. change step1b of clause 4.3.4.3 to same description of step 1f of clause 4.3.4.2","secretary_remarks":"Revision of S2-2002901, merging S2-2002910. Approved","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13390,"status":"agreed","reservation_date":"2020-04-27 09:11:03","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2002901","revisedto":"SP-200527","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2219.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200422","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003462.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003463","title":"PDU Session release when Control Plane Only indication is not available","source":"Interdigital Inc.","contact":"Xiaoyan Shi","contact-id":72162,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add description of step 1f of clause 4.3.4.2 or step 1b of clause 4.3.4.3 of TS 23.502 will be used to this PDU session release case.","secretary_remarks":"Revision of S2-2003165. Approved","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13420,"status":"agreed","reservation_date":"2020-04-27 09:11:04","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2003165","revisedto":"SP-200528","release":"Rel-16","crspec":23.501,"crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2361.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200422","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003463.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003464","title":"Change of the restriction of enhanced coverage in UE Configuration Update procedure","source":"Intel","contact":"Meghashree D Kedalagudde","contact-id":49483,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that when a change regarding the use of coverage enhancement occurs (e.g. due to a change in subscription) and the UE is in CM-CONNECTED, the AMF shall trigger the UE Configuration Update procedure to the UE and indicate a need to perform a registration procedure.","secretary_remarks":"Revision of S2-2002902. Approved","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13440,"status":"agreed","reservation_date":"2020-04-27 09:11:06","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2002902","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2220.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200422","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003464.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003465","title":"Corrections to restriction of use of Enhanced Coverage","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Correct the requirement regarding a UE supporting Enhanced coverage shall support Enhanced coverage restriction. 2. Updated Enhanced Coverage Restricted information for NB-IoT.","secretary_remarks":"Revision of S2-2002990. Approved","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13460,"status":"agreed","reservation_date":"2020-04-27 09:11:07","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2002990","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2302.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200422","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003465.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003466","title":"UE specific DRX for NB-IoT in 5GC","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":84607,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Include a separate indication for Accepted UE specific DRX paramters for NB-IoT in Registration procedure. Clarify that AMF needs to ensure the correct Paging DRX parameters for the RAT are included in N2 paging message. New value in UE context for AMF.","secretary_remarks":"Revision of S2-2003163. Approved","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13500,"status":"agreed","reservation_date":"2020-04-27 09:11:08","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2003163","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2300.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200422","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003466.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003467","title":"Correction of NEF-based NIDD procedures","source":"Huawei, HiSilicon, Ericsson","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the NIDD parameters (e.g., maximum packet size) in the PDU Session Estalishment Procedure. Add NIDD parameters, RDS support and Rate Control related information in the SMF-NEF connection Establishment\/Release procedure. Parameters in related Nnef service operations updated.","secretary_remarks":"Revision of S2-2002984. Approved","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13520,"status":"agreed","reservation_date":"2020-04-27 09:11:09","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2002984","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2244.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200422","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003467.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003504","title":"Reply LS on MO exception data","source":"SA WG2","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC: RAN WG2, CT WG1. Attachments: TS 23.501 CR#2277 (S2-2003457), TS 23.502 CR#2216 (S2-2002887)","secretary_remarks":"Revision of S2-2002888. Approved","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13190,"status":"approved","reservation_date":"2020-04-27 09:11:47","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2002888","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2002647","lsto":"CT WG4","Cc":"RAN WG2, CT WG1","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003504.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003505","title":"LS on SA WG2 status of MT-EDT in Rel-16","source":"SA WG2","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: TSG SA, RAN WG2, RAN WG3, CT WG1, SA WG3","secretary_remarks":"Revision of S2-2003164. Approved","agenda_item_sort_order":27,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment \u2013 MT-EDT","tdoc_agenda_sort_order":13240,"status":"approved","reservation_date":"2020-04-27 09:11:47","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2003164","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, RAN WG2, RAN WG3, CT WG1, SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003505.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]