[{"name":"S2-2000007","title":"LS from SA WG1: Reply LS on authentication of group of IoT devices","source":"SA WG1","contact":"Chao Liu","contact-id":72318,"tdoctype":"LS in","for":"Action","abstract":"SA WG1 thanks SA WG2 for S2-1908632 and SA WG3 for S3-191601 on authentication of group of IoT devices. It is clear from these questions and previous LS from SA WG3 (S3-183717) that downstream groups cannot complete work to support bulk IoT operations including bulk authentication in Rel16. SA WG1 will remove the confusing requirements. Please see attached CR. For Rel17, please see the clarifications below. SA WG1 understands SA WG3 will not address bulk authentication. 1) SA WG2 is kindly seeking clarification on the actual bulk operations and related use cases that SA WG1 is assuming, e.g., does 'manage (e.g., provide service parameters, activate, deactivate) multiple UEs in bulk' refers to subscription and service management? Answer: The use cases for bulk operation of IoT devices include scenarios in which several to many devices associated to the same user are operated simultaneously. Such scenarios may be, for example, sensors embedded in a newly constructed building or bridge, reusable public safety sensors dispersed around a geographic area such as a wildfire or crime scene, weather sensors on a ship, or smart meter sensors in a parking garage. SA WG1 already captured the requirements for bulk operation in clause 6.4.2.2 and 8.3, TS 22.261, quoted as below: o The 5G network shall optimize the resource use of the control plane and\/or user plane to support bulk operation for high connection density (e.g., 1 million connections per square kilometre) of multiple UEs. o The 5G network shall optimize the resource use of the control plane and\/or user plane to manage (e.g., provide service parameters, activate, deactivate) multiple of UEs in bulk. o The 5G system shall support a timely, efficient, and\/or reliable mechanism to transmit the same information to multiple UEs. o The 5G network shall support a resource efficient mechanism for authenticating multiple IoT devices in bulk. According to the above requirements, the actual bulk operations refer to not only managing (e.g., provide service parameters, activate, deactivate) multiple UEs in bulk, but also operating UEs in bulk for control plane and\/or user plane resource optimization. 2) SA WG2 would also like to ask for additional details on the common criteria that SA WG1 is assuming. Answer: The common criteria means the IoT devices\/UEs have something in common from service point of view, e.g., they can be associated with same enterprise user or same vendor, or they can share common job duties like all the smoking detection devices in a building. Detail definition of the common criteria and whether and how it refers to common context in the network would be in solution space thus will be out of SA WG1 discussion. SA WG1 encourages SA WG2 and SA WG3 to find proper solutions to address this issues. Action: SA WG1 asks SA WG2 and SA WG3 to take the replies above into consideration.","secretary_remarks":"Postponed S2-1910864 from SA2#136. Noted in parallel session","agenda_item_sort_order":28,"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":15850,"status":"noted","reservation_date":"2019-12-18 15:23:43","uploaded":"2020-01-06 08:48:38","revisionof":"S2-1910864","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3","Cc":"","lsoriginalls":"S1-192816","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000007.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000009","title":"LS from CT WG4: LS on Enhanced coverage restriction","source":"CT WG4","contact":"liu qifeng","contact-id":63651,"tdoctype":"LS in","for":"Action","abstract":"Retrieval UE subscription data and provision UE subscription data have different view. From the subscription data retrieval view (see 23.502 clause 4.27.1 step 3 and 7), subset of UE's Enhanced coverage restriction data(per user per PLMN) is enough on demand, but from the parameters provision view, the overall picture of UE's Enhanced coverage restriction data can be retrieved and configured, hence different resources are suggested to use for higher efficiency. And next, AMF and AF belong to two different network domain, separate services are suggested to use for data isolation, and UDM have already defined separated services for them, SDM service is provided to retrieve UE subscription data, PP service is provided for provision of UE subscription data. Conclusion CT WG4 would suggest PP service is used for provision of Enhanced coverage restriction by AF via from data provision view, and SDM service is used for retrieval of Enhanced coverage restriction by AMF on demand. Action: CT WG4 kindly asks SA WG2 to take note of the above decision and let CT WG4 know if SA WG2 sees any issue with this approach.","secretary_remarks":"Postponed S2-1910873 from SA2#136. Response drafted in S2-2000272. Final response in S2-2001251","agenda_item_sort_order":28,"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":15190,"status":"replied to","reservation_date":"2019-12-18 15:23:43","uploaded":"2020-01-06 08:48:38","revisionof":"S2-1910873","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG3","lsoriginalls":"C4-194530","lsreply":"S2-2001251","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000009.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000011","title":"LS from CT WG3: LS on Service on I-NEF Event Exposure","source":"CT WG3","contact":"Yali Yan","contact-id":66362,"tdoctype":"LS in","for":"Action","abstract":"CT WG3 has started the work on 5G_CIoT and is specifying the I-NEF Event Exposure (i.e. Ninef_EventExposure) service as defined in TS 23.502. CT WG3 is also specifying the NEF Event Exposure (i.e. Nnef_EventExposure) service which is used by the NF service consumer(s) (e.g. NWDAF) to (un)subscribe to notification of observed events in the NEF. From CT WG3 point of view, the NEF acts as I-NEF in roaming scenario, the Nnef_EventExposure service works well in both non-roaming and roaming scenarios for different NF service consumers. It's unnecessary to define a dedicated service for the I-NEF Event Exposure functionality. CT WG3 has already decided to implement the functionality of I-NEF Event Exposure by the Nnef_EventExposure service. Action: CT WG3 kindly asks SA WG2 to take above CT WG3 decision into account and clarify their specifications in the related respect.","secretary_remarks":"Postponed S2-1910880 from SA2#136. Responses drafted in S2-2000396 and S2-2000723. Final response in S2-2001575","agenda_item_sort_order":28,"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":15620,"status":"replied to","reservation_date":"2019-12-18 15:23:43","uploaded":"2020-01-06 08:48:38","revisionof":"S2-1910880","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"C3-194445","lsreply":"S2-2001330","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000011.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000015","title":"LS from CT WG4: Reply LS on Small Data Rate Control and APN Rate Control","source":"CT WG4","contact":"Bruno Landais","contact-id":68755,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 thanks SA WG2 for their Reply LS on Small Data Rate Control and APN Rate Control. CT WG4 is specifying the corresponding stage 3 changes. CT WG4 would like to point out the following remaining issues in stage 2: {...} CT WG4 assumption has been that UPF does not know what is an exception data and simply counts any packets exceeding the normal small data rate control rate as 'exception data'. Why is an 'MO Exception Data Counter' sent to UPF? What is the UPF expected to do with this counter? If the stage 2 CR intends to signal to the UPF whether an RRC signalling connection is established for normal data or exception data, to let the UPF differentiate 'normal data' from 'exception data', what does happen if the control plane signalling from AMF to (V-)SMF (to H-SMF) to UPF takes more time than user plane packets (exception data)? The Exception data may get assimilated to 'normal data' in this case and get dropped by the UPF even when the data rate for exception data is not exceeded. Action: CT WG4 kindly asks SA WG2 group to clarify the above issues.","secretary_remarks":"Postponed S2-1911943 from SA2#136. Response drafted in S2-2000392. Final response in S2-2001573","agenda_item_sort_order":28,"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":15470,"status":"replied to","reservation_date":"2019-12-18 15:23:43","uploaded":"2020-01-06 08:48:38","revisionof":"S2-1911943","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C4-195471","lsreply":"S2-2001327","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000015.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000036","title":"LS from RAN WG2: Reply LS on Mobile-terminated Early Data Transmission","source":"RAN WG2","contact":"Umesh Phuyal","contact-id":71775,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 thanks SA WG2 for their reply LS on Mobile-terminated Early Data Transmission feature which is being introduced for eMTC and NB-IoT in Rel-16. SA WG2 indicated in the LS: - SA WG2 has concluded that the UE indicates the capability of supporting MT-EDT via NAS layer. MME can decide whether a PDN connectivity is applied for MT-EDT according to UE capability; SA WG2 kindly ask RAN WG2 whether there is concern about this. RAN WG2 response: - From RAN WG2 point of view, there is no concern to indicate the capability of supporting MT-EDT via NAS layer, and for MME to decide whether a PDN connectivity is applied for MT-EDT according to UE capability. - It should be possible for the UE to indicate separate capability for CP MT-EDT and UP MT-EDT at NAS level. - If NAS indicates MT-EDT capability and CN initiates MT-EDT according to the UE capability, there is no need of separate AS capability indication for MT-EDT. Therefore, RAN WG2 will specify that: - CP and\/or UP MT-EDT are optional features for UE without AS capability signalling. - If the UE supports MT-EDT for the CP solution, it shall also support MO-EDT for the CP solution. - If the UE supports MT-EDT for the UP solution, it shall also support MO-EDT for the UP solution. SA WG2 also indicated: - SA WG2 has assumption that MT-EDT is implemented on top of MO-EDT (i.e. UE will trigger MO-EDT procedure in response to Paging Request with MT-EDT indication). RAN WG2 response: - RAN WG2 is aiming to specify MT-EDT with minimal changes on top of Rel-15 MO-EDT as follows: ? For CP case: RAN WG2 will support ability to include dedicatedInfoNAS in RRCConnectionSetup in response to RRCEarlyDataRequest (i.e. during CP EDT fallback to full RRC connection). ? For UP case: in response to paging request with MT-EDT indication, in some cases the UE may transmit non-EDT msg1 and receive non-EDT msg2; however, same procedure as in MO-EDT for AS security reactivation and transmission of msg3 is performed for MT-EDT. Action: RAN WG2 respectfully asks SA WG2 and CT WG1 to take the above into account and provide feedback\/update on MT-EDT, if any.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":28,"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":15020,"status":"noted","reservation_date":"2019-12-18 15:23:44","uploaded":"2020-01-06 08:48:38","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1","Cc":"RAN WG3, TSG RAN, TSG SA","lsoriginalls":"R2-1916368","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000036.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000046","title":"LS from SA WG1: Reply LS on UAC for NB-IOT","source":"SA WG1","contact":"Francesco Pica","contact-id":57089,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 thanks RAN WG2 for their LS on UAC for NB-IOT. SA WG1 has discussed and agreed to introduce support of UAC for NB-IOT starting from Rel-16, including a new access catogory for MO-exception data, as per enclosed agreed CRs. It should be noted that, based on SA WG1 consensus, the new access catogory for MO-exception data does not differentiate PLMN types (i.e., conditions 'a, b & c', as defined for UAC category 1).","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":28,"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":15860,"status":"noted","reservation_date":"2019-12-18 15:23:44","uploaded":"2020-01-06 08:48:38","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"CT WG1, SA WG2, RAN WG3","lsoriginalls":"S1-193592","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000046.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000053","title":"LS from SA WG3: Reply LS to SA2 on 5G-S-TMSI Truncation Procedure","source":"SA WG3","contact":"Wu Rong","contact-id":49499,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 thank SA WG2 for the LS on 5G-S-TMSI Truncation Procedure. For the UE using CP CIoT 5GS Optimisation, since AS security is not activated, n and m are not protected. In that case, SA WG3 recommend to send the n and the m in a protected message. Action: SA WG3 kindly asks SA WG2 to take the above information into account.","secretary_remarks":"Response drafted in S2-2000089. Final response in S2-2001248","agenda_item_sort_order":28,"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":15060,"status":"replied to","reservation_date":"2019-12-18 15:23:45","uploaded":"2020-01-06 08:48:38","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG2, CT WG4, CT WG1, RAN WG3","lsoriginalls":"S3-194482","lsreply":"S2-2001248","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000053.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000087","title":"Clarifications for truncated 5G-S-TMSI","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify in clause 5.31.4.3 that the AMF configures the UE with the sizes of the components of the Truncated 5G-S-TMSI.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":28,"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":15210,"status":"noted","reservation_date":"2019-12-20 20:38:26","uploaded":"2020-01-06 22:17:21","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2008.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000087.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000089","title":"[DRAFT] Reply LS on truncated 5G-S-TMSI","source":"Qualcomm Incoporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3, RAN WG2, CT WG4, CT WG1. CC: RAN WG3","secretary_remarks":"Response to S2-2000053. Revised in parallel session to S2-2001248.","agenda_item_sort_order":28,"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":15130,"status":"revised","reservation_date":"2019-12-20 20:45:05","uploaded":"2020-01-06 22:17:21","revisionof":"","revisedto":"S2-2001248","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, RAN WG2, CT WG4, CT WG1","Cc":"RAN WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000089.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000104","title":"Alignment with TS 23.502 and clarification on Extended Buffering","source":"ORANGE","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) Replacement of 'Extended Buffering Status Change' by 'Downlink Data Delivery Status'. 2) Removal of the editor's note in 5.31.9 about the support of the monitoring events via SMF.","secretary_remarks":"Revision of unhandled S2-1911080 from S2#136. Revised in parallel session, merging S2-2000728, to S2-2001252.","agenda_item_sort_order":28,"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":15380,"status":"revised","reservation_date":"2019-12-24 15:59:31","uploaded":"2020-01-07 16:05:55","revisionof":"S2-1911080","revisedto":"S2-2001252","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1691.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000104.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000105","title":"Corrections on Extended Buffering","source":"Orange","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) SMF is added in the list of NFs able to report directly to the NEF about monitoring events 2) The UPF reports data notification only if configured and if this is the first downlink packet to be buffered 3) Removal of the possibility for the SMF to indicate to the UPF to stop data notification 4) Removal of the condition that extended buffering is not configured in UPF for header compression and encapsulation of the downlink data. 5) Clarify that the buffering mentioned in the last paragraph of step 2h is in SMF. 6) Editorial fixes.","secretary_remarks":"Revision of unhandled S2-1911081 from S2#136. Revised in parallel session to S2-2001254.","agenda_item_sort_order":28,"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":15400,"status":"revised","reservation_date":"2019-12-24 16:05:58","uploaded":"2020-01-07 16:15:54","revisionof":"S2-1911081","revisedto":"S2-2001254","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1667.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000105.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000257","title":"Correction of WB-E-UTRA and WB-E-UTRAN terminology","source":"Orange","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - a definition for 'WB-E-UTRA' is added. - all occurences of 'WB-E-UTRAN' are replaced by 'WB-E-UTRA'; in one occurence this change is accompanied by the removal of 'connected to 5GC', which is not needed.","secretary_remarks":"Revised in parallel session to S2-2001280.","agenda_item_sort_order":28,"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":16030,"status":"revised","reservation_date":"2020-01-03 16:21:56","uploaded":"2020-01-07 17:01:40","revisionof":"","revisedto":"S2-2001280","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2034.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000257.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000262","title":"MT EDT support for 5GC.","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":84607,"tdoctype":"discussion","for":"Approval","abstract":"Proposes MT EDT support for 5GC.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":28,"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":15030,"status":"noted","reservation_date":"2020-01-03 18:22:23","uploaded":"2020-01-07 00:12:02","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000262.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000263","title":"MT-EDT introduction","source":"Qualcomm Incorporated, OPPO, Intel, NEC","contact":"Miguel Griot","contact-id":84607,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - add MT-EDT may be initiated by AMF for CP Optimization in clause 5.31.4.1. - add MT-EDT may be initiated by AMF for UP Optimization in clause 5.31.18. - Remove repeated MO EDT text in 5.31.18.","secretary_remarks":"Revision of noted S2-1911723 from S2#136. Noted in parallel session. Revised at S2#137E in S2-2002016 (noted)","agenda_item_sort_order":28,"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":15180,"status":"revised","reservation_date":"2020-01-03 18:26:34","uploaded":"2020-01-07 00:12:02","revisionof":"S2-1911723","revisedto":"S2-2002016","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1894.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000263.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000264","title":"MT-EDT introduction","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":84607,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - UE sends MT-EDT support to AMF during registration procedure. - During PDU session establishment, AMF indicates to SMF the PDU session is for MT-EDT. - add MT-EDT procedure for UP optimization. - add MT-EDT procedure for CP optimization. Rev 4\u00a0: - adds the 5G-GUTI allocation mechanism in both clause 4.8.2.y and 4.24.x. Rev 5\u00a0: Includes clarification of old\/new 5G-GUTI handling for paging.","secretary_remarks":"Revision of noted S2-1912487 from S2#136. Noted in parallel session. Revised at S2#137E in S2-2002017 (postponed)","agenda_item_sort_order":28,"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":15190,"status":"revised","reservation_date":"2020-01-03 18:29:23","uploaded":"2020-01-07 00:12:02","revisionof":"S2-1912487","revisedto":"S2-2002017","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1848.0,"crrevision":6.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000264.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000271","title":"Correction to Enhanced Coverage Restriction Control via NEF","source":"Intel, Convida Wireless","contact":"Meghashree D Kedalagudde","contact-id":49483,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarification that separate services are used to retrieve UE subscritpion data i.e., SDM service and to provision UE subscription data i.e., PP service.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":28,"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":15350,"status":"noted","reservation_date":"2020-01-03 21:43:48","uploaded":"2020-01-06 23:49:26","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1975.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000271.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000272","title":"[DRAFT] Reply LS on Enhanced coverage restriction","source":"Intel","contact":"Meghashree D Kedalagudde","contact-id":49483,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC: CT WG3","secretary_remarks":"Response to S2-2000009. Revised in parallel session to S2-2001251.","agenda_item_sort_order":28,"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":15220,"status":"revised","reservation_date":"2020-01-03 21:48:13","uploaded":"2020-01-06 23:49:26","revisionof":"","revisedto":"S2-2001251","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000272.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000291","title":"Availability after DDN Failure in 5GC","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"This paper discusses the implication of the existing solution and proposes an AMF centric solution","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":28,"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":15310,"status":"noted","reservation_date":"2020-01-03 22:09:11","uploaded":"2020-01-07 04:54:42","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000291.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000292","title":"Availability after DDN Failure in 5GC","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: UDM subscribes Availability after DDN Failure event only to AMF with DNN, S-NSSAI and Traffic Descriptor if available. AMF sends the Traffic Descriptor in Nsmf_PDUSession_CreateSMContext or Nsmf_PDUSession_UpdateSMContext\/ to the SMF, requesting SMF to report DDN Failure if packet from an AF (represented by the Traffic Descriptor) are dropped. SMF reports DDN Failure to AMF using Nsmf_PDUSession_SMContextStatusNotify service operation. Remove Availability after DDN Failure event from Nsmf_EventExposure Service operation.","secretary_remarks":"Revised in parallel session to S2-2001256.","agenda_item_sort_order":28,"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":15460,"status":"revised","reservation_date":"2020-01-03 22:09:11","uploaded":"2020-01-07 04:54:42","revisionof":"","revisedto":"S2-2001256","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1983.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000292.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000293","title":"Availability after DDN Failure event with UPF buffering","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: #1 SMF provisions the Traffic Descriptor (if received) in PDR and the UPF reports what traffic has been dropped. #2 Replace the non-existing clause 4.15.3.2a with clause 4.15.3.2.7. #3 Correct the heading of 4.15.3.3 Information flow for availability after DDN Failure event with UPF buffering.","secretary_remarks":"Agreed in parallel session. This was removed from block approval. This was left for e-mail approval. e-mail revision 1 approved. Revised to S2-2001678.","agenda_item_sort_order":28,"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":15480,"status":"revised","reservation_date":"2020-01-03 22:09:12","uploaded":"2020-01-07 04:54:42","revisionof":"","revisedto":"S2-2001678","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1984.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000293.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000294","title":"Idle mode mobility with data fowarding","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) A flow for 5GS to EPS idle mobility with data forwarding is added. 2) A flow for EPS to 5GS idle mobility with data forwarding is added 3) Clause 4.11.1.3.2 is updated to remove the data forwarding text","secretary_remarks":"Revision of withdrawn S2-1912422 from S2#136. Revised in parallel session to S2-2001253.","agenda_item_sort_order":28,"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":15430,"status":"revised","reservation_date":"2020-01-03 22:12:37","uploaded":"2020-01-07 14:25:04","revisionof":"S2-1911108","revisedto":"S2-2001253","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1590.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000294.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000299","title":"Service Gap Control handling at UE side during IWK","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Descriptions are added for timer handling at UE side during IWK.","secretary_remarks":"Agreed in parallel session. Block approved","agenda_item_sort_order":28,"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":15560,"status":"agreed","reservation_date":"2020-01-03 22:16:53","uploaded":"2020-01-07 14:25:04","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2035.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200062","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000299.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000300","title":"NEF service update for NIDD","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Service operation name in 4.25.4 is updated New service operation is included in 5.2.6.1 and defined in 5.2.6.15.x to synch with stage 3.","secretary_remarks":"Revised in parallel session, merging S2-2000620, to S2-2001258.","agenda_item_sort_order":28,"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":15570,"status":"revised","reservation_date":"2020-01-03 22:16:54","uploaded":"2020-01-07 14:25:04","revisionof":"","revisedto":"S2-2001258","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1985.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000300.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000301","title":"[DRAFT] Reply LS on NIDD service modelling on N29","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"LS response to CT WG4 LS","secretary_remarks":"Response to S2-1910855 (noted at S2#136). Revised in parallel session to S2-2001270.","agenda_item_sort_order":28,"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":15440,"status":"revised","reservation_date":"2020-01-03 22:16:55","uploaded":"2020-01-07 14:25:04","revisionof":"","revisedto":"S2-2001270","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_136AH_Incheon\/Docs\/S2-2000301.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000391","title":"Small Data Rate Control enforcement corrections","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Incorrect requirement to include a non-existing parameter is removed in clause 4.3.4.3. The 'maximum allowed rate' applies when it has been configured by H-SMF and the 'MO Exception Data' is detected by the network based on RRC Establishment cause. End marker ('normal data indication') for MO Exception Data is added more clearly by re-naming the parameter to 'MO Exception Data parameter' that can take values 'MO Exception Data' and 'normal data'. The criteria for considering MT data as exception data after 'MO Exception Data' is received is added. The SMF holds back the Exception Data until the 'MO Exception Data' indication has reached the anchor UPFs and NEFs. H-SMF informing the V-SMF on whether rate control is applied on a PDU session and V-SMF obtaining the SM Context including the Small Data Rate Control Status is added in the 5GS to EPS Handover using N26 interface for the roaming case.","secretary_remarks":"Confirm CR Number - CR states '' !. Revised in parallel session to S2-2001282.","agenda_item_sort_order":28,"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":15660,"status":"revised","reservation_date":"2020-01-06 11:07:00","uploaded":"2020-01-07 14:40:05","revisionof":"","revisedto":"S2-2001282","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2001.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000391.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000392","title":"[DRAFT] Reply on Small Data RAte Control and APN Rate Control","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC:","secretary_remarks":"Response to S2-2000015. Revised in parallel session to S2-2001271.","agenda_item_sort_order":28,"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":15520,"status":"revised","reservation_date":"2020-01-06 11:10:46","uploaded":"2020-01-07 14:40:05","revisionof":"","revisedto":"S2-2001271","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_136AH_Incheon\/Docs\/S2-2000392.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000393","title":"Exception data rate control.","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"discussion","for":"Discussion","abstract":"Addressing issues brought up by CT WG4 in SA WG2 CIoT specifications","secretary_remarks":"Not Handled","agenda_item_sort_order":28,"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":15480,"status":"not treated","reservation_date":"2020-01-06 11:13:27","uploaded":"2020-01-07 14:40:05","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000393.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000394","title":"Corrections on I-NEF call flow","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: I-NEF call flow and service operation parameters are corrected: - AMF\/SMF does not subscribe to I-NEF notifications but configures NEF routing address to I-NEF - For a given monitoring event, either AMF or SMF configures the I-NEF, but not both (depending on which one of the two is monitoring that event) - If I-NEF is needed, the AMF\/SMF configures I-NEF with routing path to NEF and sends notifications to that I-NEF. - In clause 4.15.3.2.3a step 2-3, the I-NEF need not subscribe to notifications from the AMF or SMF, as the I-NEF routing configuration causes the SMF\/AMF to update the corresponding monitoring configuration. - Since SMF and AMF notifications are re-used, I-NEF notification service operation is not needed. - Monitoring event notifications are conditional, subject to the notification event detection. - Event Filter and Chargeable Party Identifier are removed from the I-NEF configuration. - user is identified by SUPI or Internal Group Identifier between SMF\/AMF and I-NEF. - the old SMF removes its I-NEF association after SMF change. Various editorial mistakes are also corrected.","secretary_remarks":"Confirm CR Number - CR states '' ! Revised in parallel session, merging S2-2000724, to S2-2001275.","agenda_item_sort_order":28,"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":15800,"status":"revised","reservation_date":"2020-01-06 11:15:29","uploaded":"2020-01-07 14:40:05","revisionof":"","revisedto":"S2-2001275","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2002.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000394.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000395","title":"Corrections on I-NEF service operation","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"WITHDRAWN: Summary of change: The naming of the service operation set is corrected to align with the more substantial change in TS 23.502","secretary_remarks":"Confirm CR Number - CR states '' !. Withdrawn","agenda_item_sort_order":28,"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":15790,"status":"withdrawn","reservation_date":"2020-01-06 11:17:51","uploaded":"2020-01-07 14:40:05","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2041.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000395.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000396","title":"[DRAFT] Reply LS on Service on I-NEF event exposure","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC: CT WG4","secretary_remarks":"Not Handled","agenda_item_sort_order":28,"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":15680,"status":"not treated","reservation_date":"2020-01-06 11:20:48","uploaded":"2020-01-07 14:40:05","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_136AH_Incheon\/Docs\/S2-2000396.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000397","title":"Addition of eDRX parameter to subscription data types","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Subscribed eDRX parameter is added to Subscription Data Types.","secretary_remarks":"Confirm CR Number - CR states '' !. Revised in parallel session to S2-2001276.","agenda_item_sort_order":28,"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":15910,"status":"revised","reservation_date":"2020-01-06 11:23:06","uploaded":"2020-01-07 14:40:05","revisionof":"","revisedto":"S2-2001276","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2003.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000397.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000398","title":"Correction of Nsmf_SendMOData parameter list","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Superfluous data container parameter is removed.","secretary_remarks":"Confirm CR Number - CR states '' !. Revised in parallel session to S2-2001277.","agenda_item_sort_order":28,"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":15930,"status":"revised","reservation_date":"2020-01-06 11:25:41","uploaded":"2020-01-07 14:40:05","revisionof":"","revisedto":"S2-2001277","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2004.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000398.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000454","title":"Extended Buffering Control in the SMF","source":"Tencent","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In case of Control Plane CIoT 5GS Optimisation is enabled for the PDU session with LBO, the NEF is not used as the anchor of this PDU Session. If the DL data buffering in the SMF applies, store the DL Data for an Extended Buffering time. If the Extended Buffering timer expires, the SMF discards the buffered downlink data. Delete the 2 duplicate sentences in the Step 6 of clause 4.2.3.3. The Nnef_NIDD_Delivery Response is sent to the AF with a cause value indicating that no acknowledgement was received in step 17 of clause 4.25.5.","secretary_remarks":"Agreed in parallel session. Block approved","agenda_item_sort_order":28,"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":15420,"status":"agreed","reservation_date":"2020-01-06 15:44:59","uploaded":"2020-01-07 14:56:23","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2013.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200063","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000454.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000477","title":"Clarifications for truncated 5G-S-TMSI","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify in clause 4.2.2.2.2 that the AMF configures the UE with the sizes of the components of the Truncated 5G-S-TMSI.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":28,"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":15220,"status":"noted","reservation_date":"2020-01-06 16:40:11","uploaded":"2020-01-06 22:17:21","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2020.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000477.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000504","title":"Assistance indication for WUS grouping","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":84607,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce WUS assistance information in 5GC.","secretary_remarks":"Confirm Spec version used - CR states 16.2.0!. Revised in parallel session to S2-2001249.","agenda_item_sort_order":28,"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":15290,"status":"revised","reservation_date":"2020-01-06 18:03:48","uploaded":"2020-01-07 00:12:02","revisionof":"","revisedto":"S2-2001249","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"TEI16"},{"winame":"5G_CIoT"}],"crnumber":2053.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000504.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000516","title":"WUS assistance information procedures","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":84607,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce WUS assistance between in 5GC in the following procedures\u00a0: Registration procedure (UE-AMF) Network triggered service request procedure (AMF to ng-eNB). UPF anchored MT Data Transport in Control Plane CIoT 5GS Optimisation (AMF to ng-eNB). UE Context Transfer","secretary_remarks":"Revised in parallel session to S2-2001250.","agenda_item_sort_order":28,"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":15310,"status":"revised","reservation_date":"2020-01-06 18:07:17","uploaded":"2020-01-07 00:12:02","revisionof":"","revisedto":"S2-2001250","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"TEI16"},{"winame":"5G_CIoT"}],"crnumber":2025.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000516.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000619","title":"Update to Nnef_SMContext_Create service operation","source":"ETRI, UANGEL","contact":"Seungik Lee","contact-id":48790,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In the clause 4.25.2 and 5.2.6.15.2, add SMF ID as an input parameter of Nnef_SMContext_Create Request.","secretary_remarks":"Agreed in parallel session. Block approved","agenda_item_sort_order":28,"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":15890,"status":"agreed","reservation_date":"2020-01-07 06:08:33","uploaded":"2020-01-07 09:30:28","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2035.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200063","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000619.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000620","title":"Update to Nnef_NIDD_Delivery service operation","source":"ETRI, UANGEL","contact":"Seungik Lee","contact-id":48790,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In the clause 4.25.4 and 5.2.6.14.2, add PDU Session ID as an input parameter of Nnef_NIDD_Delivery Request.","secretary_remarks":"Merged into S2-2001258","agenda_item_sort_order":28,"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":15620,"status":"merged","reservation_date":"2020-01-07 06:10:11","uploaded":"2020-01-07 09:30:28","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2036.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000620.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000660","title":"Small Data Rate Control enforcement corrections","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The 'maximum allowed rate' applies when it has been configured by H-SMF and the 'MO Exception Data' is detected by the network based on RRC Establishment cause. End marker ('normal data indication') for MO Exception Data and the criteria for considering MT data as exception data after 'MO Exception Data' is received is added.","secretary_remarks":"Confirm CR Number - CR states ' ' ! Confirm CR Revision - CR states 2082! Merged into S2-2001272","agenda_item_sort_order":28,"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":15650,"status":"merged","reservation_date":"2020-01-07 07:17:41","uploaded":"2020-01-07 14:40:05","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2082.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000660.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000716","title":"NAS signalling of CP Relocation Indication Truncated 5G-S-TMSI Parameters","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The AMF assigns the n and m values for the Truncated 5G-S-TMSI, replacing RAN assignment,","secretary_remarks":"Confirm CR Number - CR states 2048!. Revised in parallel session to S2-2001246.","agenda_item_sort_order":28,"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":15230,"status":"revised","reservation_date":"2020-01-07 08:59:59","uploaded":"2020-01-07 13:12:50","revisionof":"","revisedto":"S2-2001246","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2088.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000716.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000717","title":"NAS signalling of CP Relocation Indication Truncated 5G-S-TMSI Parameters Procedures","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Whenever a 5G-GUTI is assigned to the UE, the AMF can also assign the configuration to allow it to create the Truncated 5G-S-TMSI.","secretary_remarks":"Revised in parallel session to S2-2001247.","agenda_item_sort_order":28,"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":15250,"status":"revised","reservation_date":"2020-01-07 09:00:00","uploaded":"2020-01-07 13:12:50","revisionof":"","revisedto":"S2-2001247","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2049.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000717.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000718","title":"Clarification to MICO mode and Periodic Registration Timer Control","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In the timer control clause 5.31.7.5: Clarify that MICO mode and peridoic registration timer control are decided by the AMF at the same time according to Expected UE Behaviour. Clarify that a 'large periodic registration timer value' can be determined based on Network Configuration parameters. Remove the word 'just'. It is up to the AMF's implementation to decide how much earlier than the scheduled DL communication time. Add 'value' after the 'periodic registration timer' as it is the value not the timer that is included in the registration accept message. In the general MICO clause 5.4.1.3: Clarify that the AMF can get the Expected UE Behaviour parameters and Network Configuration parameters from the UDM.","secretary_remarks":"Revision of unhandled S2-1911646 from S2#136. Revised in parallel session to S2-2001278.","agenda_item_sort_order":28,"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":15950,"status":"revised","reservation_date":"2020-01-07 09:00:00","uploaded":"2020-01-07 13:12:50","revisionof":"S2-1911646","revisedto":"S2-2001278","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1668.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000718.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000719","title":"Correction for MO Exception Data Rate and its inclusion CDRs","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct UPF to SMF for which NF includes the MO Exception Data Indication in the CDRs. Clarify that the exception rate is added to the normal rate when MO Exception Data is indicated.","secretary_remarks":"Revised in parallel session, merging S2-2000660, to S2-2001272.","agenda_item_sort_order":28,"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":15720,"status":"revised","reservation_date":"2020-01-07 09:00:02","uploaded":"2020-01-07 13:12:50","revisionof":"","revisedto":"S2-2001272","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2089.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000719.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000720","title":"Correction for non MO-Exception Data cause signalling","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removal of the way to signal non MO-Exception data RRC establisment cause and redundant text that could cause confusion and clarify that NFs are also informed about non MO-Exception Data RRC establishment causes. Spellings corrected.","secretary_remarks":"Revised in parallel session to S2-2001279.","agenda_item_sort_order":28,"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":15970,"status":"revised","reservation_date":"2020-01-07 09:00:03","uploaded":"2020-01-07 13:14:02","revisionof":"","revisedto":"S2-2001279","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2050.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000720.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000721","title":"Correction to UE context in AMF for Power Saving Function","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The eDRX parameters ,Active Time and Strictly Periodic Registration Timer Indication are added in the UE context in the AMF.","secretary_remarks":"Revision of unhandled S2-1911658 from S2#136. Agreed in parallel session. Block approved","agenda_item_sort_order":28,"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":16000,"status":"agreed","reservation_date":"2020-01-07 09:00:04","uploaded":"2020-01-07 13:14:02","revisionof":"S2-1911658","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1776.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-200063","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000721.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000722","title":"DDD status event with UPF buffering procedure","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Specify how to subcribe to data delivery status notifications if buffering in the UPF is used. Some mirror correction to the Information flow for downlink data delivery status with SMF buffering.","secretary_remarks":"Revision of unhandled S2-1911660 from S2#136. Revised in parallel session to S2-2001257.","agenda_item_sort_order":28,"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":15500,"status":"revised","reservation_date":"2020-01-07 09:00:06","uploaded":"2020-01-07 13:14:02","revisionof":"S2-1911660","revisedto":"S2-2001257","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1930.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000722.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000723","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 LS to S2-2000011\/C3-194445 on Service on I-NEF Event Exposure","secretary_remarks":"Revision of postponed S2-1911648 from S2#136. Response to S2-2000011. Revised in parallel session to S2-2001274.","agenda_item_sort_order":28,"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":15690,"status":"revised","reservation_date":"2020-01-07 09:00:09","uploaded":"2020-01-07 13:14:02","revisionof":"S2-1911648","revisedto":"S2-2001274","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_136AH_Incheon\/Docs\/S2-2000723.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000724","title":"Clarification on implementation of Ninef_EventExposure","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that Ninef_EventExposure service can be merged into Nnef_EventExposure service with a NOTE. Change the Target of Event Reporting of Ninef_EventExposure service from external UE ID to internal UE ID.","secretary_remarks":"Merged into S2-2001275","agenda_item_sort_order":28,"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":15830,"status":"merged","reservation_date":"2020-01-07 09:00:09","uploaded":"2020-01-07 13:14:02","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2051.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000724.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000725","title":"Notification Endpoint allocation during the AMF relocation","source":"Huawei, HiSilicon,","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: During the AMF relocation, if the 'Availability after DDN Failure' is subscribed, the new AMF allocates a new AMF notification endpoint and notify the NF consumer of the new AMF notification endpoint associated with the change of AMF notification endpoint event","secretary_remarks":"Revision of unhandled S2-1911650 from S2#136. Noted in parallel session","agenda_item_sort_order":28,"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":15550,"status":"noted","reservation_date":"2020-01-07 09:00:10","uploaded":"2020-01-07 13:14:02","revisionof":"S2-1911650","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1926.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000725.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000727","title":"Add Serving PLMN rate control in the PDU Session Establishment","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add Serving PLMN rate control in the PDU Session Establishment Procedure.","secretary_remarks":"Revised in parallel session to S2-2001273.","agenda_item_sort_order":28,"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":15760,"status":"revised","reservation_date":"2020-01-07 09:00:12","uploaded":"2020-01-07 13:14:02","revisionof":"","revisedto":"S2-2001273","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2052.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000727.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000728","title":"Remove Editor's note for monitoring event via SMF","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove Editor's note for monitoring event via SMF","secretary_remarks":"Merged into S2-2001252","agenda_item_sort_order":28,"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":15900,"status":"merged","reservation_date":"2020-01-07 09:00:12","uploaded":"2020-01-07 13:14:02","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2090.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000728.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000729","title":"N4 session level reporting for supporting Availability after DDN failure","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the traffic information of DL data reporting in N4 Session Level Reporting procedure.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":28,"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":15540,"status":"noted","reservation_date":"2020-01-07 09:00:13","uploaded":"2020-01-07 13:14:02","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2053.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000729.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000730","title":"Clarification on Enhanced Coverage Restriction","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that Parameter Provision service is used for provision of Enhanced Coverage Restriction.","secretary_remarks":"Agreed in parallel session. Block approved","agenda_item_sort_order":28,"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":15340,"status":"agreed","reservation_date":"2020-01-07 09:00:14","uploaded":"2020-01-07 13:14:02","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2054.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200063","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000730.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000885","title":"Update to AMF exposure of mobility events for extended buffering in NEF","source":"ETRI, UANGEL","contact":"Seungik Lee","contact-id":48790,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In the clause 4.15.4.2, add the case that NEF performs Extended Buffering for a PDU session using Control Plane CIoT 5GS Optimisation.","secretary_remarks":"Revised in parallel session to S2-2001255.","agenda_item_sort_order":28,"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":16060,"status":"revised","reservation_date":"2020-01-07 13:40:33","uploaded":"2020-01-07 13:46:24","revisionof":"","revisedto":"S2-2001255","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2072.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000885.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001246","title":"NAS signalling of CP Relocation Indication Truncated 5G-S-TMSI Parameters","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The AMF assigns the n and m values for the Truncated 5G-S-TMSI, replacing RAN assignment, in the Registration procedure.","secretary_remarks":"Revision of S2-2000716. Agreed in parallel session. Block approved","agenda_item_sort_order":28,"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":15240,"status":"agreed","reservation_date":"2020-01-16 02:42:09","uploaded":"2020-01-18 01:57:51","revisionof":"S2-2000716","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2088.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200062","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001246.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001247","title":"NAS signalling of CP Relocation Indication Truncated 5G-S-TMSI Parameters Procedures","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: During the registration procedure the AMF can also assign the configuration to allow the UE to create the Truncated 5G-S-TMSI.","secretary_remarks":"Revision of S2-2000717. Agreed in parallel session. Block approved","agenda_item_sort_order":28,"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":15260,"status":"agreed","reservation_date":"2020-01-16 02:42:10","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2000717","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2049.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200063","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001247.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001248","title":"Reply LS on 5G-S-TMSI Truncation Procedure","source":"SA WG2","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3, RAN WG2, CT WG1. CC: CT WG4. Attachments: S2-2001246 (TS 23.501 CR#2088) S2-2001247 (TS 23.502 CR#2049).","secretary_remarks":"Revision of S2-2000089. Agreed in parallel session. Block approved","agenda_item_sort_order":28,"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":15140,"status":"approved","reservation_date":"2020-01-16 02:42:11","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2000089","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2000053","lsto":"SA WG3, RAN WG2, CT WG1","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001248.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001249","title":"Assistance indication for WUS grouping","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":84607,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce WUS assistance information in 5GC.","secretary_remarks":"Revision of S2-2000504. Agreed in parallel session. Block approved. Revised at S2#137E in S2-2001802 (agreed)","agenda_item_sort_order":28,"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":15300,"status":"revised","reservation_date":"2020-01-16 02:42:11","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2000504","revisedto":"S2-2001769, S2-2001802","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"TEI16"},{"winame":"5G_CIoT"}],"crnumber":2053.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001249.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001250","title":"WUS assistance information procedures","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":84607,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce WUS assistance between in 5GC in the following procedures\u00a0: Registration procedure (UE-AMF) Network triggered service request procedure (AMF to ng-eNB). UPF anchored MT Data Transport in Control Plane CIoT 5GS Optimisation (AMF to ng-eNB). UE Context Transfer","secretary_remarks":"Revision of S2-2000516. Agreed in parallel session. Block approved","agenda_item_sort_order":28,"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":15320,"status":"agreed","reservation_date":"2020-01-16 02:42:13","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2000516","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2025.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"SP-200063","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001250.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001251","title":"Reply LS on Enhanced coverage restriction","source":"SA WG2","contact":"Meghashree D Kedalagudde","contact-id":49483,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. Cc: CT WG3. Attachments: 23.502 CR 2054 (S2-2000730).","secretary_remarks":"Revision of S2-2000272. Agreed in parallel session. Block approved","agenda_item_sort_order":28,"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":15230,"status":"approved","reservation_date":"2020-01-16 02:42:15","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2000272","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2000009","lsto":"CT WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001251.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001252","title":"Alignment with TS 23.502 and clarification on Extended Buffering","source":"ORANGE","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) Replacement of 'Extended Buffering Status Change' by 'Downlink Data Delivery Status'. 2) Removal of the editor's note in 5.31.9 about the support of the monitoring events via SMF.","secretary_remarks":"Revision of S2-2000104, merging S2-2000728. Agreed in parallel session. Block approved","agenda_item_sort_order":28,"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":15390,"status":"agreed","reservation_date":"2020-01-16 02:42:15","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2000104","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1691.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-200062","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001252.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001253","title":"Idle mode mobility with data fowarding","source":"Ericsson, Qualcomm Incorporated","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) A flow for 5GS to EPS idle mobility with data forwarding is added. 2) A flow for EPS to 5GS idle mobility with data forwarding is added 3) Clause 4.11.1.3.2 is updated to remove the data forwarding text","secretary_remarks":"Revision of S2-2000294. Agreed in parallel session. Block approved","agenda_item_sort_order":28,"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":15440,"status":"agreed","reservation_date":"2020-01-16 02:42:17","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2000294","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1590.0,"crrevision":6.0,"crcategory":"F","tsg_crp":"SP-200063","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001253.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001254","title":"Corrections on Extended Buffering","source":"Orange","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) SMF is added in the list of NFs able to report directly to the NEF about monitoring events 2) The UPF reports data notification only if configured and if this is the first downlink packet to be buffered 3) Removal of the possibility for the SMF to indicate to the UPF to stop data notification 4) Clarify that the buffering mentioned in the last paragraph of step 2h is in SMF. 5) Editorial fixes.","secretary_remarks":"Revision of S2-2000105. Agreed in parallel session. Block approved","agenda_item_sort_order":28,"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":15410,"status":"agreed","reservation_date":"2020-01-16 02:42:17","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2000105","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1667.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-200063","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001254.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001255","title":"Update to AMF exposure of mobility events for extended buffering in NEF","source":"ETRI, UANGEL","contact":"Seungik Lee","contact-id":48790,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In the clause 4.15.4.2, add the case that NEF performs Extended Buffering for a PDU session using Control Plane CIoT 5GS Optimisation.","secretary_remarks":"Revision of S2-2000885. Agreed in parallel session. Block approved","agenda_item_sort_order":28,"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":16070,"status":"agreed","reservation_date":"2020-01-16 02:42:18","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2000885","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2072.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200063","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001255.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001256","title":"Availability after DDN Failure in 5GC","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: UDM subscribes Availability after DDN Failure event only to AMF with DNN, S-NSSAI and Traffic Descriptor if available. AMF sends the Traffic Descriptor in Nsmf_PDUSession_CreateSMContext or Nsmf_PDUSession_UpdateSMContext\/ to the SMF, requesting SMF to report DDN Failure if packet from an AF (represented by the Traffic Descriptor) are dropped. SMF reports DDN Failure to AMF using Nsmf_PDUSession_SMContextStatusNotify service operation. Remove Availability after DDN Failure event from Nsmf_EventExposure Service operation.","secretary_remarks":"Revision of S2-2000292. Agreed in parallel session. Block approved. Revised at S2#137E in S2-2002115 (agreed)","agenda_item_sort_order":28,"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":15470,"status":"revised","reservation_date":"2020-01-16 02:42:20","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2000292","revisedto":"S2-2002115","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1983.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001256.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001257","title":"DDD status event with UPF buffering procedure","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Specify how to subcribe to data delivery status notifications if buffering in the UPF is used. Some mirror correction to the Information flow for downlink data delivery status with SMF buffering.","secretary_remarks":"Revision of S2-2000722. Confirm CR Revision - CR states 0! Revised in parallel session to S2-2001333.","agenda_item_sort_order":28,"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":15510,"status":"revised","reservation_date":"2020-01-16 02:42:21","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2000722","revisedto":"S2-2001333","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1930.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001257.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001258","title":"NEF service update for NIDD","source":"Ericsson, ETRI, UANGEL","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Service operation name in 4.25.4 is updated New service operation is included in 5.2.6.1 and defined in 5.2.6.15.x to synch with stage 3.","secretary_remarks":"Revision of S2-2000300, merging S2-2000620. Revised in parallel session to S2-2001326.","agenda_item_sort_order":28,"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":15580,"status":"revised","reservation_date":"2020-01-16 02:42:24","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2000300","revisedto":"S2-2001326","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1985.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001258.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001270","title":"Reply LS on NIDD service modelling on N29","source":"SA WG2","contact":"Qian Cheng","contact-id":59114,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. Attachments: 23.502 CR1985 (S2-2001326)","secretary_remarks":"Revision of S2-2000301. Agreed in parallel session. Block approved","agenda_item_sort_order":28,"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":15450,"status":"approved","reservation_date":"2020-01-16 02:42:39","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2000301","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1910855","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001270.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001271","title":"[DRAFT] Reply on Small Data RAte Control and APN Rate Control","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC:","secretary_remarks":"Revision of S2-2000392. Revised in parallel session to S2-2001327.","agenda_item_sort_order":28,"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":15530,"status":"revised","reservation_date":"2020-01-16 02:42:39","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2000392","revisedto":"S2-2001327","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_136AH_Incheon\/Docs\/S2-2001271.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001272","title":"Correction for MO Exception Data Rate and its inclusion CDRs","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct UPF to SMF for which NF includes the MO Exception Data Indication in the CDRs. Clarify that the exception rate is added to the normal rate when MO Exception Data is indicated.","secretary_remarks":"Revision of S2-2000719, merging S2-2000660. Revised in parallel session to S2-2001328.","agenda_item_sort_order":28,"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":15730,"status":"revised","reservation_date":"2020-01-16 02:42:40","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2000719","revisedto":"S2-2001328","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2089.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001272.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001273","title":"Add Serving PLMN rate control in the PDU Session Establishment","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add Serving PLMN rate control in the PDU Session Establishment Procedure.","secretary_remarks":"Revision of S2-2000727. Agreed in parallel session. Block approved","agenda_item_sort_order":28,"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":15770,"status":"agreed","reservation_date":"2020-01-16 02:42:41","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2000727","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2052.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200063","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001273.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001274","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 LS to S2-2000011\/C3-194445 on Service on I-NEF Event Exposure","secretary_remarks":"Revision of S2-2000723. Revised in parallel session to S2-2001330.","agenda_item_sort_order":28,"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":15700,"status":"revised","reservation_date":"2020-01-16 02:42:42","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2000723","revisedto":"S2-2001330","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_136AH_Incheon\/Docs\/S2-2001274.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001275","title":"Corrections on I-NEF call flow","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: I-NEF call flow and service operation parameters are corrected: - AMF\/SMF store the I-NEF event notification address from the Ninef_EventNotification_Subscribe Response. - For a given monitoring event, either AMF or SMF configures the I-NEF, but not both (depending on which one of the two is monitoring that event) - If I-NEF is needed, the AMF\/SMF configures I-NEF with routing path to NEF and sends notifications to that I-NEF. - In clause 4.15.3.2.3a step 2-3, the I-NEF need not subscribe to notifications from the AMF or SMF. - Monitoring event notifications are conditional, subject to the notification event detection. - Unnecessary Event Filter parameter is removed from the I-NEF configuration. - user is identified by SUPI or Internal Group Identifier between SMF\/AMF and I-NEF. - the old SMF removes its I-NEF association after SMF change. Various editorial mistakes are also corrected.","secretary_remarks":"Revision of S2-2000394, merging S2-2000724. Revised in parallel session to S2-2001329.","agenda_item_sort_order":28,"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":15810,"status":"revised","reservation_date":"2020-01-16 02:42:42","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2000394","revisedto":"S2-2001329","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2002.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001275.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001276","title":"Addition of eDRX parameter to subscription data types","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Subscribed eDRX parameter is added to Subscription Data Types.","secretary_remarks":"Revision of S2-2000397. Agreed in parallel session. Block approved","agenda_item_sort_order":28,"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":15920,"status":"agreed","reservation_date":"2020-01-16 02:42:44","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2000397","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2003.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200063","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001276.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001277","title":"Correction of Nsmf_SendMOData parameter list","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Superfluous data container parameter is removed.","secretary_remarks":"Revision of S2-2000398. Agreed in parallel session. Block approved","agenda_item_sort_order":28,"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":15940,"status":"agreed","reservation_date":"2020-01-16 02:42:46","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2000398","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2004.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200063","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001277.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001278","title":"Clarification to MICO mode and Periodic Registration Timer Control","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In the timer control clause 5.31.7.5: Clarify that MICO mode and peridoic registration timer control are decided by the AMF at the same time according to Expected UE Behaviour. Clarify that a 'large periodic registration timer value' can be determined based on Network Configuration parameters. Remove the word 'just'. It is up to the AMF's implementation to decide how much earlier than the scheduled DL communication time. Add 'value' after the 'periodic registration timer' as it is the value not the timer that is included in the registration accept message. In the general MICO clause 5.4.1.3: Clarify that the AMF can get the Expected UE Behaviour parameters and Network Configuration parameters from the UDM.","secretary_remarks":"Revision of S2-2000718. Agreed in parallel session. Block approved","agenda_item_sort_order":28,"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":15960,"status":"agreed","reservation_date":"2020-01-16 02:42:48","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2000718","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1668.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-200062","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001278.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001279","title":"Correction for non MO-Exception Data cause signalling","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removal of the way to signal non MO-Exception data RRC establisment cause and redundant text that could cause confusion and clarify that NFs are also informed about non MO-Exception Data RRC establishment causes. Spellings corrected.","secretary_remarks":"Revision of S2-2000720. Revised in parallel session to S2-2001331.","agenda_item_sort_order":28,"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":15980,"status":"revised","reservation_date":"2020-01-16 02:42:49","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2000720","revisedto":"S2-2001331","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2050.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001279.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001280","title":"Correction of WB-E-UTRA and WB-E-UTRAN terminology","source":"Orange","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - a definition for 'WB-E-UTRA' is added. - all occurences of 'WB-E-UTRAN' are replaced by 'WB-E-UTRA'; in two placesone occurence this change is accompanied by the removal of 'connected to 5GC', which is not needed, and by some necessary rewording.","secretary_remarks":"Revision of S2-2000257. Revised in parallel session to S2-2001332.","agenda_item_sort_order":28,"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":16040,"status":"revised","reservation_date":"2020-01-16 02:42:51","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2000257","revisedto":"S2-2001332","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2034.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001280.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001282","title":"Small Data Rate Control enforcement corrections","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Incorrect requirement to include a non-existing parameter is removed in clause 4.3.4.3. The 'maximum allowed rate' applies when it has been configured by H-SMF and the 'MO exception data' is detected by the network based on RRC Establishment cause. The criteria for considering MT data as exception data after 'MO exception data' is received is added. The SMF holds back the Exception Data until the 'MO exception data' indication has reached the anchor UPFs and NEFs. H-SMF informing the V-SMF on whether rate control is applied on a PDU session and V-SMF obtaining the SM Context including the Small Data Rate Control Status is added in the 5GS to EPS Handover using N26 interface for the roaming case. 'MO Exception Data Counter' parameter is added to Nsmf_PDUSession_SendMOData and Nsmf_PDUSession_UpdateSMContext service operation definitions.","secretary_remarks":"Revision of S2-2000391. Agreed in parallel session. Block approved","agenda_item_sort_order":28,"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":15670,"status":"agreed","reservation_date":"2020-01-16 02:42:52","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2000391","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2001.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200063","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001282.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001326","title":"NEF service update for NIDD","source":"Ericsson, ETRI, UANGEL","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Service operation name in 4.25.4 is updated New service operation is included in 5.2.6.1 and defined in 5.2.6.15.x to synch with stage 3.","secretary_remarks":"Revision of S2-2001258. Agreed in parallel session. Block approved","agenda_item_sort_order":28,"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":15590,"status":"agreed","reservation_date":"2020-01-18 01:19:33","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2001258","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1985.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-200063","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001326.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001327","title":"[DRAFT] Reply on Small Data RAte Control and APN Rate Control","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC:","secretary_remarks":"Revision of S2-2001271. Revised in parallel session to S2-2001573.","agenda_item_sort_order":28,"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":15540,"status":"revised","reservation_date":"2020-01-18 01:19:34","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2001271","revisedto":"S2-2001573","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_136AH_Incheon\/Docs\/S2-2001327.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001328","title":"Correction for MO Exception Data Rate and its inclusion in charging information","source":"Huawei, HiSilicon, Nokia, Nokia Shanghai Bell","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct UPF to SMF for which NF includes the MO Exception Data Indication in the charging information. Clarify that the exception rate is added to the normal rate when MO Exception Data is indicated.","secretary_remarks":"Revision of S2-2001272. Revised in parallel session to S2-2001574.","agenda_item_sort_order":28,"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":15580,"status":"revised","reservation_date":"2020-01-18 01:19:34","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2001272","revisedto":"S2-2001574","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2089.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001328.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001329","title":"Corrections on I-NEF call flow","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: I-NEF call flow and service operation parameters are corrected: - AMF\/SMF store the I-NEF event notification address from the Ninef_EventNotification_Subscribe Response. - For a given monitoring event, either AMF or SMF configures the I-NEF, but not both (depending on which one of the two is monitoring that event) - If I-NEF is needed, the AMF\/SMF configures I-NEF with routing path to NEF and sends notifications to that I-NEF. - In clause 4.15.3.2.3a step 2-3, the I-NEF need not subscribe to notifications from the AMF or SMF. - Monitoring event notifications are conditional, subject to the notification event detection. - Unnecessary Event Filter parameter is removed from the I-NEF configuration. - user is identified by SUPI or Internal Group Identifier between SMF\/AMF and I-NEF. - the old SMF removes its I-NEF association after SMF change. - Ninef_EventExposure_Notify service operation is removed, as the use of Namf and Nsmf notification allows more optimal re-use of the existing service operations both in specification and implementation. Various editorial mistakes are also corrected.","secretary_remarks":"Revision of S2-2001275. Agreed in parallel session. Block approved. Revised at S2#137E in S2-2001885 (noted) and S2-2002257 (noted)","agenda_item_sort_order":28,"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":15820,"status":"agreed","reservation_date":"2020-01-18 01:19:37","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2001275","revisedto":"S2-2001885, S2-2002257","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2002.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-200063","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001329.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001330","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 LS to S2-2000011\/C3-194445 on Service on I-NEF Event Exposure","secretary_remarks":"Revision of S2-2001274. Revised in parallel session to S2-2001575.","agenda_item_sort_order":28,"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":15710,"status":"revised","reservation_date":"2020-01-18 01:19:39","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2001274","revisedto":"S2-2001575","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_136AH_Incheon\/Docs\/S2-2001330.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001331","title":"Correction for non MO-Exception Data cause signalling","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removal of the way to signal non MO-Exception data RRC establisment cause and redundant text that could cause confusion and clarify that NFs are also informed about non MO-Exception Data RRC establishment causes. Spellings corrected.","secretary_remarks":"Revision of S2-2001279. Agreed in parallel session. Block approved","agenda_item_sort_order":28,"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":15990,"status":"agreed","reservation_date":"2020-01-18 01:19:39","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2001279","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2050.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-200063","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001331.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001332","title":"Correction of WB-E-UTRA and WB-E-UTRAN terminology","source":"Orange","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - a definition for 'WB-E-UTRA' is added. - all occurences of 'WB-E-UTRAN' are replaced by 'WB-E-UTRA'; in two places this change is accompanied by the removal of 'connected to 5GC', which is not needed, and by some necessary rewording.","secretary_remarks":"Revision of S2-2001280. Postponed in parallel session","agenda_item_sort_order":28,"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":15890,"status":"postponed","reservation_date":"2020-01-18 01:19:41","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2001280","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2034.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001332.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001333","title":"DDD status event with UPF buffering procedure","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Specify how to subcribe to data delivery status notifications if buffering in the UPF is used. Some mirror correction to the Information flow for downlink data delivery status with SMF buffering.","secretary_remarks":"Revision of S2-2001257. Confirm CR Revision - CR states 1 3! Agreed in parallel session. This was removed from block approval. This was left for e-mail approval. e-mail revision 1 approved. Revised to S2-2001687.","agenda_item_sort_order":28,"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":15510,"status":"revised","reservation_date":"2020-01-18 01:19:42","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2001257","revisedto":"S2-2001687","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1930.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001333.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001573","title":"LS on Small Data Rate Control and APN Rate Control","source":"SA WG2","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. Attachments: 23.502 CR 2001, CR 2050 and 23.501 CR 2089","secretary_remarks":"Revision of S2-2001327. Agreed in parallel session. Block approved","agenda_item_sort_order":28,"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":15550,"status":"approved","reservation_date":"2020-01-18 01:20:10","uploaded":"2020-01-18 02:07:52","revisionof":"S2-2001327","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2000015","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001573.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001574","title":"Correction for MO Exception Data Rate and its inclusion in charging information","source":"Huawei, HiSilicon, Nokia, Nokia Shanghai Bell","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct UPF to SMF for which NF includes the MO Exception Data Indication in the charging information. Clarify that the exception rate is added to the normal rate when MO Exception Data is indicated.","secretary_remarks":"Revision of S2-2001328. Agreed in parallel session. Block approved","agenda_item_sort_order":28,"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":15750,"status":"agreed","reservation_date":"2020-01-18 01:20:10","uploaded":"2020-01-18 02:07:52","revisionof":"S2-2001328","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":2089.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-200062","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001574.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001575","title":"Reply LS on Service on I-NEF Event Exposure","source":"SA WG2","contact":"Steven Wenham","contact-id":48132,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC: CT WG4. Attachments: TS 23.502 CR2002 (S2-2001329)","secretary_remarks":"Revision of S2-2001330. Agreed in parallel session. Block approved","agenda_item_sort_order":28,"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":15720,"status":"approved","reservation_date":"2020-01-18 01:20:11","uploaded":"2020-01-18 02:07:52","revisionof":"S2-2001330","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2000011","lsto":"CT WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001575.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001678","title":"Availability after DDN Failure event with UPF buffering","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: #1 SMF provisions the Traffic Descriptor (if received) in PDR and the UPF reports what traffic has been dropped. #2 Replace the non-existing clause 4.15.3.2a with clause 4.15.3.2.7. #3 Correct the heading of 4.15.3.3 Information flow for availability after DDN Failure event with UPF buffering.","secretary_remarks":"e-mail revision 1 of S2-2000293. This CR was agreed. Revised at S2#137E in S2-2001811 (postponed)","agenda_item_sort_order":28,"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":15490,"status":"agreed","reservation_date":"2020-01-27 09:23:36","uploaded":"2020-01-27 09:28:17","revisionof":"S2-2000293","revisedto":"S2-2001811","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1984.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200063","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001678.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001687","title":"DDD status event with UPF buffering procedure","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Specify how to subcribe to data delivery status notifications if buffering in the UPF is used. Some mirror correction to the Information flow for downlink data delivery status with SMF buffering.","secretary_remarks":"e-mail revision 1 of S2-2001333. This CR was agreed. Revised at S2#137E in S2-2001810 (agreed)","agenda_item_sort_order":28,"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":15530,"status":"revised","reservation_date":"2020-01-27 09:23:47","uploaded":"2020-01-27 09:28:18","revisionof":"S2-2001333","revisedto":"S2-2001810","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1930.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001687.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]