[{"name":"S2-1910849","title":"LS from CT WG3: LS on Nsmf_EventExposure and Nnef_EventExposure service handling of the Downlink data delivery status and Availability after DDN Failure events.","source":"CT WG3","contact":"Thomas Belling","contact-id":68266,"tdoctype":"LS in","for":"Information","abstract":"CT WG3 was investigating how to extend the Nsmf_EventExposure and Nnef_EventExposure services with the requirements in the 'Information flow for downlink data delivery status' in subclause 4.15.3.2.5 of TS 23.502. {...}. Action: CT WG3 asks SA WG2 to kindly answer the above questions and to consider clarifying their specifications in that respect.","secretary_remarks":"Postponed S2-1908645 from S2#135. Replied to at S2#135 in S2-1910641. 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 - MT-EDT","tdoc_agenda_sort_order":16350,"status":"noted","reservation_date":"2019-10-30 08:52:08","uploaded":"2019-11-04 09:40:45","revisionof":"S2-1908645","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C3-191407","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910849.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910855","title":"LS from CT WG4: LS out on NIDD service modelling on N29","source":"CT WG4","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"TS 23.502 has defined two Nnef services on N29 for NIDD via NEF: Nnef_SMContext service for management of the SMF-NEF Connections and Nnef_NIDD service for delivery of MO data. With consideration of Restful Principles alignment and other aspects on API design, CT WG4 has decided to model one Service Based API (Nnef_SMContext API) to realize both above services in 3GPP TS 29.541. For synchronization between Stage 2 and Stage 3 specifications, TS 29.541 will visualize the mapping of each service operation defined in the API to the corresponding service operation specified in TS 23.502. Action: CT WG4 kindly asks SA WG2 group to take the information above into account.","secretary_remarks":"Postponed S2-1908669 from S2#135. 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 - MT-EDT","tdoc_agenda_sort_order":16120,"status":"noted","reservation_date":"2019-10-30 08:52:10","uploaded":"2019-11-04 09:40:46","revisionof":"S2-1908669","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C4-193769","lsreply":"S2-2001270","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910855.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910858","title":"LS from RAN WG2: Reply LS on bulk authentication issue for IoT devices","source":"RAN WG2","contact":"Baokun Shan","contact-id":70626,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 thanks SA WG3 for their LS on authentication of group of IoT devices. RAN WG2 would like to provide the following feedback: RAN WG2 has not discussed any bulk authentication issue for IoT devices and has not seen any requirement on this so far.","secretary_remarks":"Postponed S2-1908684 from S2#135. 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 - MT-EDT","tdoc_agenda_sort_order":15720,"status":"noted","reservation_date":"2019-10-30 08:52:11","uploaded":"2019-11-04 09:40:46","revisionof":"S2-1908684","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG1, SA WG2","lsoriginalls":"R2-1911790","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910858.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910863","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 related to the support of UAC for NB-IoT connected to 5GC. After discussing the specific RAN WG2 queries, SA WG1 can provide the following answers and comments: 1) Whether UAC should be supported for NB-IoT connected to 5GC. [Answer]: Yes; UAC is the only access control in 5GC. 2) RAN WG2 understands that there is no access category in the table in 22.261 which corresponds to the establishment cause 'mo-ExceptionData' and would like to ask SA WG1 whether it is necessary to introduce a new access category for this purpose, in the range 9-31 (reserved standardized access categories). [Answer]: SA WG1 would like to ask RAN WG2 to provide further clarification on the need to introduce a new access category for mo-ExceptionData, instead of using existing UAC categories (e.g. access category 7). 3) Whether up to 64 access categories need to be defined for support of UAC, given the currently supported establishment causes and necessity for operator defined categories and potential future extension. [Answer]: Yes, current requirements should also apply to NB-IOT connected to 5GC. 4) Whether access class 0-9 is applicable for UAC and whether access class 0-9 access attempts are mapped to access identity 0. [Answer]: Access classes 0-9 are not used by UAC. UAC has the concept of access identity where a UE that is not configured to be of any special type of access identity (e.g. 1, 2, 11-15) will be of access category 0. There is no direct mapping between Access Classes 0-9 and UAC access identity 0. 5) Whether barring bits for access identities 1, 2, 11 to 15 are common for all access categories or independently controlled for different access categories. [Answer]: Current UAC requirements and signalling assume that both Access IDs and Access Categories are independent concepts.","secretary_remarks":"Postponed S2-1908701 from S2#135. 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 - MT-EDT","tdoc_agenda_sort_order":15660,"status":"noted","reservation_date":"2019-10-30 08:52:11","uploaded":"2019-11-04 09:40:45","revisionof":"S2-1908701","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-192707","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910863.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910864","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-1908703 from S2#135. Response drafted in S2-1911079","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":15670,"status":"available","reservation_date":"2019-10-30 08:52:11","uploaded":"2019-11-04 09:40:45","revisionof":"S2-1908703","revisedto":"S2-2000007","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_136_Reno\/Docs\/S2-1910864.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910873","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-1909963 from S2#135. This LS was 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 - MT-EDT","tdoc_agenda_sort_order":15530,"status":"postponed","reservation_date":"2019-10-30 08:52:12","uploaded":"2019-11-04 09:40:45","revisionof":"S2-1909963","revisedto":"S2-2000009","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG3","lsoriginalls":"C4-194530","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910873.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910880","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-1909983 from S2#135. Response drafted in S2-1911648. 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 - MT-EDT","tdoc_agenda_sort_order":16160,"status":"postponed","reservation_date":"2019-10-30 08:52:13","uploaded":"2019-11-04 09:40:45","revisionof":"S2-1909983","revisedto":"S2-2000011","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"C3-194445","lsreply":"S2-2000396","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910880.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910903","title":"Preferred Behaviour for MT data","source":"ORANGE","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduction of 'Preferred Behaviour for MT data' indicator sent from AMF to SMF. For deciding to establish N3 data transfer, the SMF does not check if N3 data transfer was successfully negotiated but checks the Preferred Behaviour for MT data, if the PDU Session is not set to Control Plane Only.","secretary_remarks":"Revision of S2-1908737 from S2#135. Revised in parallel session to S2-1912330.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":15890,"status":"revised","reservation_date":"2019-10-30 11:20:25","uploaded":"2019-11-08 22:54:34","revisionof":"S2-1908737","revisedto":"S2-1912330","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1685.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910903.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910904","title":"Preferred Behaviour for MT data","source":"ORANGE","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: For deciding to establish N3 data transfer, if the PDU Session is not set to Control Plane Only, the SMF does not check if N3 data transfer was successfully negotiated but checks the Preferred Behaviour for MT data. This indication replaces the Control Plane CIoT 5GS Optimisation indication in the signaling from AMF to SMF.","secretary_remarks":"Revision of S2-1908744 from S2#135. Revised in parallel session to S2-1912331.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":15910,"status":"revised","reservation_date":"2019-10-30 11:21:55","uploaded":"2019-11-08 23:08:57","revisionof":"S2-1908744","revisedto":"S2-1912331","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1665.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910904.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910905","title":"Support of TAs with heterogeneous support of eDRX","source":"ORANGE","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding the case of a UE registering over NR. Adding a new clause for TAs with heterogeneous support of eDRX, to specify how to handle UEs doing Idle Mode mobility from NR to WB-E-UTRAN: the AMF shall ensure that the UE is reached in any cases (eDRX is used or not). Moving an Editor's Note to this new clause because it is related to heterogeneous support of eDRX.","secretary_remarks":"Revision of S2-1908745 from S2#135. Revised to S2-1912713.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":16410,"status":"revised","reservation_date":"2019-10-30 11:24:28","uploaded":"2019-11-08 23:08:57","revisionof":"S2-1908745","revisedto":"S2-1912713","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1689.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910905.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910906","title":"Clarification on provisionning of NIDD related identifiers","source":"ORANGE","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) Adding note to warn that 'NEF Identity for NIDD' and 'Invoke NEF' flag need to be configured consistently. 2) Adding in the same note that when the 'NEF Identity for NIDD' Session Management Subscription Data includes a NEF Identity for a S-NSSAI and DNN, the 'Control Plane Only Indicator' will always be set for PDU Sessions to this S-NSSAI and DNN","secretary_remarks":"Revision of S2-1908750 from S2#135. 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 - MT-EDT","tdoc_agenda_sort_order":16050,"status":"agreed","reservation_date":"2019-10-30 11:25:58","uploaded":"2019-11-08 22:54:34","revisionof":"S2-1908750","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1668.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-191069","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910906.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910907","title":"Service Exposure in Interworking Scenarios","source":"ORANGE, Convida Wireless","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Voids clause 5.17.6 and adds a clause 5.17.5.x with the title and content of clause 5.17.6.1.","secretary_remarks":"Revision of S2-1908752 from S2#135. 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 - MT-EDT","tdoc_agenda_sort_order":16320,"status":"agreed","reservation_date":"2019-10-30 11:27:21","uploaded":"2019-11-08 16:53:59","revisionof":"S2-1908752","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1693.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-191068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910907.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911008","title":"Support for Cellular IoT not constraint to any specific Access Type","source":"ORANGE, Nokia, Nokia Shanghai Bell","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarification that support for Cellular IoT is not constraint to any specific Access Type.","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 - MT-EDT","tdoc_agenda_sort_order":15730,"status":"noted","reservation_date":"2019-11-05 15:40:00","uploaded":"2019-11-08 16:53:59","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1922.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911008.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911048","title":"Correction of UDM subscription to Nsmf_EventExposure","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove 'AF service ID' from the descripton of UDM subscritpion to Nsmf_EventExposure. Clarify that NEF maps the AF-Identity into the DNN and S-NSSAI combination.","secretary_remarks":"Revision of S2-1909047 from S2#135. Revised in parallel session to S2-1912433.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":16220,"status":"revised","reservation_date":"2019-11-06 00:10:29","uploaded":"2019-11-08 04:33:35","revisionof":"S2-1909047","revisedto":"S2-1912433","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1721.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911048.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911057","title":"Service Gap Control at IWK","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Requirements are added for running Sevice Gap timers at IWK","secretary_remarks":"Revision of S2-1910640 from S2#135","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":16610,"status":"available","reservation_date":"2019-11-06 00:17:14","uploaded":"2019-11-08 04:33:35","revisionof":"S2-1910640","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1485.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911057.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911073","title":"Requirements on Efficient bulk operations for IoT.","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"discussion","for":"Decision","abstract":"This paper discusses requirements on efficient bulk operations for IoT and proposes a way forward.","secretary_remarks":"Revision of S2-1909064 from S2#135. 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 - MT-EDT","tdoc_agenda_sort_order":15680,"status":"noted","reservation_date":"2019-11-06 09:56:23","uploaded":"2019-11-08 17:46:40","revisionof":"S2-1909064","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911073.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911079","title":"[DRAFT] Reply LS on authentication of group of IoT devices","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG1. CC: SA WG3","secretary_remarks":"Revision of S2-1909065 from S2#135. Response to S2-1910864. Revised in parallel session to S2-1912325.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":15690,"status":"revised","reservation_date":"2019-11-06 11:19:17","uploaded":"2019-11-08 17:46:40","revisionof":"S2-1909065","revisedto":"S2-1912325","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911079.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911080","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: Replacement of 'Extended Buffering Status Change' by 'Downlink Data Delivery Status'. Removal of the editor's note in 5.31.9 about the support of the monitoring events via SMF.","secretary_remarks":"Revision of S2-1908748 from S2#135","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":16550,"status":"available","reservation_date":"2019-11-06 13:25:33","uploaded":"2019-11-06 13:28:46","revisionof":"S2-1908748","revisedto":"S2-2000104","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1691.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911080.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911081","title":"Corrections on Extended Buffering","source":"Orange","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: SMF is added in the list of NFs able to report directly to the NEF about monitoring events The UPF reports data notification only if configured and if this is the first downlink packet to be buffered Removal of the possibility for the SMF to indicate to the UPF to stop data notification Removal of the condition that extended buffering is not configured in UPF for header compression and encapsulation of the downlink data. Clarify that the buffering mentioned in the last paragraph of step 2h is in SMF. Editorial fixes.","secretary_remarks":"Revision of S2-1908749 from S2#135","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":16560,"status":"available","reservation_date":"2019-11-06 13:35:22","uploaded":"2019-11-08 22:54:34","revisionof":"S2-1908749","revisedto":"S2-2000105","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1667.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911081.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911087","title":"Addition of I-NEF to Network Functions","source":"ORANGE","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adds I-NEF to clause 4.2.2.","secretary_remarks":"Revision of S2-1908751 from S2#135. 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 - MT-EDT","tdoc_agenda_sort_order":16290,"status":"agreed","reservation_date":"2019-11-06 13:57:57","uploaded":"2019-11-08 22:54:34","revisionof":"S2-1908751","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1692.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-191068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911087.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911092","title":"Correcting AMF decision to set CP only indicator","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove \u00ab\u00a0of type unstructured\u00a0\u00bb from sentence quoted above.","secretary_remarks":"Revision of S2-1909067 from S2#135. 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 - MT-EDT","tdoc_agenda_sort_order":16040,"status":"agreed","reservation_date":"2019-11-06 15:01:03","uploaded":"2019-11-08 17:46:40","revisionof":"S2-1909067","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1746.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-191068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911092.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911093","title":"NIDD procedure corrections","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Refer to correct steps and remove NEF ID in clause 4.25.2. Clarify roaming case handling in clause 4.25.4. Clarify roaming case handling and buffer handling by NEF in clause 4.25.5. Remove NEF ID from clause 4.25.7. Remove NEF ID from related services in clauses 5.2.6.14.2, 5.2.6.15.2, 5.2.6.15.3, 5.2.6.15.4 Include Extended Buffering Support indication in Nnef_SMContext_Create Response instead of in Nsmf_NIDD_Delivery request. Clarify that NEF subscribes with AMF to receive an indication when UE becomes reachable and that NEF starts delivering buffered data when this indication is received from AMF.","secretary_remarks":"Revision of S2-1909066 from S2#135. Revised in parallel session to S2-1912421.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":15950,"status":"revised","reservation_date":"2019-11-06 15:04:34","uploaded":"2019-11-08 17:46:40","revisionof":"S2-1909066","revisedto":"S2-1912421","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1728.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911093.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911095","title":"I-NEF in Interworking Scenarios","source":"Convida Wireless LLC","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When interworking is possible, the UE should associate with a node that implements combined IWK-SCEF and I-NEF functionality.","secretary_remarks":"Revision of S2-1909575 from S2#135. Revised in parallel session to S2-1912432.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":16190,"status":"revised","reservation_date":"2019-11-06 16:59:39","uploaded":"2019-11-08 20:14:47","revisionof":"S2-1909575","revisedto":"S2-1912432","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1594.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911095.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911108","title":"EPS to 5GS Idle mode mobility with data fowarding","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A flow describing the data forwarding based on TS 23.401 clause 5.3.3.1A is added.","secretary_remarks":"Revision of S2-1909341 from S2#135. Revised in parallel session to S2-1912422.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":15970,"status":"revised","reservation_date":"2019-11-06 22:56:17","uploaded":"2019-11-08 18:21:47","revisionof":"S2-1909341","revisedto":"S2-1912422, S2-2000294","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1590.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911108.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911109","title":"N3 tunnel info handling during Suspend and Resume procedure","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarified N3 tunnel handling in UPF\/SMF at Suspend and Resume.","secretary_remarks":"Revision of S2-1909342 from S2#135. Revised in parallel session to S2-1912423.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":15990,"status":"revised","reservation_date":"2019-11-06 22:56:19","uploaded":"2019-11-08 18:21:47","revisionof":"S2-1909342","revisedto":"S2-1912423","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1791.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911109.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911110","title":"Enforcing maximum UP resources activation of 2 PDU sessions for NB-IoT","source":"Qualcomm Incorporated ?, Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce the AMF enforcing the maximum of 2 PDU sessions with active UP resources for RAT type NB-IoT to service request procedure and N3 data transfer procedure. Rev 2: AMF enforcing the maximum of 2 PDU sessions with active UP resources for RAT type NB-IoT to PDU session establishment procedure","secretary_remarks":"Revision of S2-1910498 from S2#135. Confirm Sources!. Revised in parallel session to S2-1912425.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":16010,"status":"revised","reservation_date":"2019-11-06 22:56:20","uploaded":"2019-11-08 18:21:47","revisionof":"S2-1910498","revisedto":"S2-1912425","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1868.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911110.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911111","title":"Support for PDN Connectivity Status monitoring event","source":"Ericsson, Verizon","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Added the PDU Session Status event to the list of monitoring events in subclause 4.15.3.1. - Added SMF event notification towards NEF for PDU Session Status - Added PDU Session Establishment to the Nsmf_EventExposure Service. - Added missing parameters PDU Session Type and DNN as optional parameters in the event notification. The NEF makes a mapping between the 5GS internal event 'PDU Session Status' and the T8 API event 'PDN Connectivity Status'.","secretary_remarks":"Revision of S2-1909340 from S2#135. Revised in parallel session to S2-1912430.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":16140,"status":"revised","reservation_date":"2019-11-06 22:56:21","uploaded":"2019-11-08 18:21:47","revisionof":"S2-1909340","revisedto":"S2-1912430","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1587.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911111.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911139","title":"Clarification of eDRX with RRC-INACTIVE and others","source":"ZTE","contact":"Yingjie Hong","contact-id":76103,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1, Change the title of clause 5.17.6; 2, Clariy that RRC-Inactive mode with short extended DRX is optionally supported in WB-E-UTRA connected to 5GC in clause 5.31.7.2.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 - MT-EDT","tdoc_agenda_sort_order":16490,"status":"noted","reservation_date":"2019-11-07 07:14:23","uploaded":"2019-11-08 01:38:23","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1930.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911139.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911308","title":"Corrections to Availability after DDN Failure event","source":"Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"WITHDRAWN: Summary of change: The Call flow only applies if buffering at the SMF is used. Subscription is via UDM. Traffic filters are an optional input parameter for the Nudm_EventExposure_Subscribe service operation","secretary_remarks":"Revision of S2-1910636 from S2#135. LATE DOC: 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 - MT-EDT","tdoc_agenda_sort_order":16360,"status":"withdrawn","reservation_date":"2019-11-07 16:52:25","uploaded":null,"revisionof":"S2-1910636","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1482.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911345","title":"[DRAFT] LS on category M devices and NR","source":"Qualcomm","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"Requests RAN WG2 to provide feedback on category M indication and NR support indication.","secretary_remarks":"Revision of S2-1910392 from S2#135. Revised in parallel session to S2-1912326.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":15740,"status":"revised","reservation_date":"2019-11-07 19:53:56","uploaded":"2019-11-08 17:46:40","revisionof":"S2-1910392","revisedto":"S2-1912326","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911345.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911352","title":"Clarifications on CN assistance information sent to the RAN","source":"Motorola Mobility, Lenovo","contact":"Genadi Velev","contact-id":70944,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to add text clarifying that the AMF may provide independent sets of 'Expected UE activity behaviour' to the RAN, i.e. UE level of 'Expected UE activity behaviour' parameters set or PDU Session level 'Expected UE activity behaviour' parameters sets.","secretary_remarks":"Revision of S2-1909788 from S2#135. Revised in parallel session to S2-1912437.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":16330,"status":"revised","reservation_date":"2019-11-07 22:01:01","uploaded":"2019-11-08 16:25:20","revisionof":"S2-1909788","revisedto":"S2-1912437","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1899.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911352.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911431","title":"Removal of ENs for control plane congestion control","source":"Vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Replace initial NAS message with uplink data with Control Plane Service Request. Remove content of NOTE 3, which related to the additional indication. Editorial modification on second bullet to make it more clear. Replace the NAS message in the third bullet with Service Accept. Modify the clause X.Y.Z in third bullet to 23.502 clause 4.2.3 (Service Request procedure) Remove the two Ens.","secretary_remarks":"Revision of S2-1908918 from S2#135. Revised in parallel session to S2-1912429.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":16100,"status":"revised","reservation_date":"2019-11-08 04:13:18","uploaded":"2019-11-08 12:47:29","revisionof":"S2-1908918","revisedto":"S2-1912429","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1721.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911431.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911503","title":"Corrections to Small Data Rate Control and Exception Reporting","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce the 'MO Exception data counter' reporting function. The AMF counts the exception data small data messages and informs the SMF when RRC Connection is set up for Exception Data.","secretary_remarks":"Revision of S2-1910639 from S2#135. Revised in parallel session to S2-1912327.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":15810,"status":"revised","reservation_date":"2019-11-08 08:45:31","uploaded":"2019-11-08 12:01:28","revisionof":"S2-1910639","revisedto":"S2-1912327","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1666.0,"crrevision":6.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911503.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911504","title":"Corrections to Small Data Rate Control and Exception Reporting","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce the 'MO Exception data counter' reporting function.","secretary_remarks":"Revision of S2-1909224 from S2#135. Revised in parallel session to S2-1912328.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":15840,"status":"revised","reservation_date":"2019-11-08 08:45:32","uploaded":"2019-11-08 12:01:28","revisionof":"S2-1909224","revisedto":"S2-1912328","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1645.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911504.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911505","title":"Correction of Small Data Rate Control interworking","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The network can consider among other criteria DNN, S-NSSAI and RAT Type when determining whether to apply Small Data Rate Control or not, but the rate control applies per PDU session and not per RAT type. APN Rate Control Status and Small Data Rate Control Status are two separate sets of information which are only used in their own respective domains in EPS and 5GS. The use of the term Small Data Rate Control Status and 5GS terminology on setting up PDU sessions towards DNN is aligned between TS 23.501 and TS 23.502. The messages carrying the stored Small Data Rate Control Status are corrected. Editorial correction by adding the word 'Request' to clause 4.3.4.2 call flow steps 1c, 1d and 1f. Superfluous condition is removed in clause 4.11.5.3 step 10a","secretary_remarks":"Revision of S2-1910802 from S2#135. 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 - MT-EDT","tdoc_agenda_sort_order":15970,"status":"agreed","reservation_date":"2019-11-08 08:45:35","uploaded":"2019-11-08 12:01:28","revisionof":"S2-1910802","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1808.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-191069","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911505.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911507","title":"Expected UE behaviour data contents","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The subscription and configuration parameters for the AMF and SMF to consider are split out of Expected UE Behaviour parameter set.","secretary_remarks":"Revision of S2-1909437 from S2#135. 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 - MT-EDT","tdoc_agenda_sort_order":16390,"status":"agreed","reservation_date":"2019-11-08 08:45:38","uploaded":"2019-11-08 12:01:28","revisionof":"S2-1909437","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1817.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-191068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911507.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911508","title":"AMF and SMF merging subscription parameters","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Merging is limited to Expected UE Behaviour.","secretary_remarks":"Revision of S2-1909438 from S2#135. 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 - MT-EDT","tdoc_agenda_sort_order":16400,"status":"agreed","reservation_date":"2019-11-08 08:45:40","uploaded":"2019-11-08 12:01:28","revisionof":"S2-1909438","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1807.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-191069","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911508.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911509","title":"Group NIDD corrections","source":"Nokia, Nokia Shanghai Bell, Convida Wireless LLC","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Following the example set in TS 23.682 clause 5.5.3 (Group NIDD) refers to unicast procedure in clause 5.13.3, a new call flow for group NIDD is introduced in TS 23.502. The new Group NIDD call flow refers to unicast call flow in 4.25.5. External Group Identifier input parameter is added in the Nnef_NIDD_Delivery service operation parameters list. Unicast call flow in clause 4.25.5. is also updated to refer to MT procedure instead of MO procedure in step 4 as intended.","secretary_remarks":"Revision of S2-1909446 from S2#135. Revised in parallel session to S2-1912436.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":16300,"status":"revised","reservation_date":"2019-11-08 08:45:42","uploaded":"2019-11-08 12:01:28","revisionof":"S2-1909446","revisedto":"S2-1912436","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1809.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911509.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911510","title":"Monitoring event triggers","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Notification event trigger criteria is made more precise and corrected where necessary. Reference to clause 4.15.1 is added to those cases where the monitoring events are triggered according to a schedule requested by the initiator of the monitoring request. Reporting condition is updated for those Monitoring Events whose reporting condition was incorrect.","secretary_remarks":"Revision of S2-1909447 from S2#135. Revised in parallel session to S2-1912435.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":16260,"status":"revised","reservation_date":"2019-11-08 08:45:43","uploaded":"2019-11-08 12:01:28","revisionof":"S2-1909447","revisedto":"S2-1912435","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1810.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911510.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911511","title":"Group reporting guard time correction","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Notification event detection is the responsibility of the CN, so the text is updated to remove the detection (and accumulation) of the notification events by the UE.","secretary_remarks":"Revision of S2-1909450 from S2#135. 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 - MT-EDT","tdoc_agenda_sort_order":16430,"status":"agreed","reservation_date":"2019-11-08 08:45:45","uploaded":"2019-11-08 12:01:28","revisionof":"S2-1909450","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1555.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-191069","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911511.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911512","title":"Small Data transfer for CP CIoT","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Nsmf_PDUSession_MessageTransfer is re-named to Nsmf_PDUSession_SendMOData service operation is added consistently in the call flow and the service operation is specified for MO Small Data. Namf_Communication_N1N2MessageTransfer service operation is used consistently instead of NAS message.","secretary_remarks":"Revised in parallel session to S2-1912426.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":16030,"status":"revised","reservation_date":"2019-11-08 08:45:47","uploaded":"2019-11-08 12:01:28","revisionof":"","revisedto":"S2-1912426","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1916.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911512.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911614","title":"Clarification on Control Plane Only Indicator","source":"Samsung","contact":"Kisuk Kweon","contact-id":80126,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: NEF Identity for NIDD is replaced with Invoke NEF indication","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 - MT-EDT","tdoc_agenda_sort_order":16160,"status":"agreed","reservation_date":"2019-11-08 10:45:37","uploaded":"2019-11-08 10:48:57","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1972.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-191068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911614.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911646","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-1909228 from S2#135","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":16570,"status":"available","reservation_date":"2019-11-08 11:27:16","uploaded":"2019-11-08 16:01:47","revisionof":"S2-1909228","revisedto":"S2-2000718","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1668.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911646.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911647","title":"Clarification on MAC AS RAI in 5GC","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that it is the RAI signalled by the absence of RAI in MAC added in Rel-14.","secretary_remarks":"Revision of S2-1909222 from S2#135. Revised in parallel session to S2-1912428.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":16080,"status":"revised","reservation_date":"2019-11-08 11:27:17","uploaded":"2019-11-08 16:01:47","revisionof":"S2-1909222","revisedto":"S2-1912428","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1775.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911647.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911648","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-1909983\/C3-194445 on Service on I-NEF Event Exposure","secretary_remarks":"Response to S2-1910880. 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 - MT-EDT","tdoc_agenda_sort_order":16170,"status":"postponed","reservation_date":"2019-11-08 11:27:18","uploaded":"2019-11-08 16:01:48","revisionof":"","revisedto":"S2-2000723","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"CT WG4","lsoriginalls":"C3-194445","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911648.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911649","title":"Monitoring Event Subscription and Network Configuration correction","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: NOTE 4 in Table 4.15.3.1-1 add the missed parameters and also correct one error. For Loss of Connectivity, the subscription may include Maximum Detection Time. For UE reachability, the subscription may include Maximum Latency, Maximum Response Time and\/or Suggested number of downlink packets. The UDM authorises the Maximum Detection Time\/Maximum Latency, Maximum Response Time and Suggested number of downlink packets. If the subscribed periodic registration timer, subscribed Active Time and\/or Suggested number of downlink packets are set or modified, the UDM sends the Nudm_SDM_Notification request to related serving AMF(s).","secretary_remarks":"Revision of S2-1908953 from S2#135. Revised in parallel session to S2-1912434.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":16240,"status":"revised","reservation_date":"2019-11-08 11:27:18","uploaded":"2019-11-08 16:01:48","revisionof":"S2-1908953","revisedto":"S2-1912434","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1516.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911649.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911650","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":"","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":16590,"status":"available","reservation_date":"2019-11-08 11:27:20","uploaded":"2019-11-08 16:01:48","revisionof":"","revisedto":"S2-2000725","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1926.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911650.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911655","title":"Corrections to Small Data Rate Control in PDU Session Establishment Procedure","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the descriptions on small data rate control parameters and statuses in PDU Session Establishment Accept message.","secretary_remarks":"Revised in parallel session to S2-1912329.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":15870,"status":"revised","reservation_date":"2019-11-08 11:27:24","uploaded":"2019-11-08 16:01:47","revisionof":"","revisedto":"S2-1912329","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1927.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911655.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911656","title":"Corrections to Control Plane data back-off timer","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Firstly, the indication for support of Control Plane data back-off timer is added in the Registration Request messahe. Then the Control Plane data back-off timer is added into the UE Context in AMF.","secretary_remarks":"","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":16620,"status":"available","reservation_date":"2019-11-08 11:27:25","uploaded":"2019-11-08 16:01:47","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1928.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911656.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911657","title":"Corrections to RDS Configuration in the PDU Session Establishment procedure","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add RDS Configuration in the PDU Session Establishment Accept message.","secretary_remarks":"Revised in parallel session to S2-1912427.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":16060,"status":"revised","reservation_date":"2019-11-08 11:27:26","uploaded":"2019-11-08 16:01:47","revisionof":"","revisedto":"S2-1912427","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1929.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911657.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911658","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 and Active Time are added in the UE context in the AMF.","secretary_remarks":"Revision of S2-1909225 from S2#135","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":16580,"status":"available","reservation_date":"2019-11-08 11:27:27","uploaded":"2019-11-08 16:01:47","revisionof":"S2-1909225","revisedto":"S2-2000721","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1776.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911658.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911659","title":"Discussion on MT-EDT in 5GS.","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"discussion","for":"Decision","abstract":"This discussion paper aims at discussing the Message 4 based solutions of MT-EDT in 5GS.","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 - MT-EDT","tdoc_agenda_sort_order":15540,"status":"noted","reservation_date":"2019-11-08 11:27:28","uploaded":"2019-11-08 16:01:47","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"","workitem":[{"winame":"5G_CIoT"},{"winame":"LTE_eMTC5"},{"winame":"NB_IOTenh3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911659.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911660","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.","secretary_remarks":"","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":16540,"status":"available","reservation_date":"2019-11-08 11:27:28","uploaded":"2019-11-08 16:01:47","revisionof":"","revisedto":"S2-2000722","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1930.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911660.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911661","title":"Availability after DDN Failure 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 and determine the Availability after DDN Failure event if buffering in the UPF is used.","secretary_remarks":"Agreed in parallel session with an objection from Nokia. This CR was agreed with an objection from Nokia","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":16510,"status":"agreed","reservation_date":"2019-11-08 11:27:30","uploaded":"2019-11-08 16:01:47","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1931.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-191060","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911661.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911720","title":"5G-GUTI allocation in MT-EDT procedure.","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"discussion","for":"Discussion","abstract":"Discusses the 5G-GUTI allocation in MT-EDT 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 - MT-EDT","tdoc_agenda_sort_order":15550,"status":"noted","reservation_date":"2019-11-08 13:21:04","uploaded":"2019-11-08 14:08:41","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911720.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911723","title":"MT-EDT introduction","source":"Qualcomm Incorporated, OPPO, Intel, NEC","contact":"Juan Zhang","contact-id":73274,"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.","secretary_remarks":"Revision of S2-1910629 from S2#135. 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 - MT-EDT","tdoc_agenda_sort_order":15560,"status":"noted","reservation_date":"2019-11-08 13:23:05","uploaded":"2019-11-08 14:08:41","revisionof":"S2-1910629","revisedto":"S2-2000263","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1894.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911723.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911724","title":"MT-EDT introduction","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"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.","secretary_remarks":"Revision of S2-1910763 from S2#135. Revised to S2-1912487.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":15490,"status":"revised","reservation_date":"2019-11-08 13:26:14","uploaded":"2019-11-08 14:08:41","revisionof":"S2-1910763","revisedto":"S2-1912487","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1848.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911724.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911725","title":"[DRAFT] LS on 5G-GUTI allocation during MT-EDT procedure","source":"Qualcomm Finland RFFE Oy","contact":"Juan Zhang","contact-id":73274,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1, SA WG3. CC:","secretary_remarks":"Revised in parallel session to S2-1912323.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":15570,"status":"revised","reservation_date":"2019-11-08 13:32:10","uploaded":"2019-11-08 14:08:41","revisionof":"","revisedto":"S2-1912323","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911725.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911758","title":"Introduction of MT-EDT","source":"OPPO, Intel, Ericsson, Sumsung, Qualcomm, NEC, Orange","contact":"Jianhua Liu","contact-id":72698,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR introduces the MT-EDT for MSG4 solution. - UE sends MT-EDT support to MME during attach procedure. - During PDN connectivity establishment, MME indicates to S-GW the PDN connectivity is for MT-EDT. - add MT-EDT procedure for UP optimization. - add MT-EDT procedure for CP optimization.","secretary_remarks":"Revision of S2-1910801 from S2#135. Confirm CR Revision! Revised in parallel session to S2-1912322.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":15590,"status":"revised","reservation_date":"2019-11-08 14:17:56","uploaded":"2019-11-08 15:14:47","revisionof":"S2-1910801","revisedto":"S2-1912322","release":"Rel-16","crspec":"23.401","crspecversion":"16.4.0","workitem":[{"winame":"LTE_eMTC5"},{"winame":"NB_IOTenh3"},{"winame":"5G_CIoT"}],"crnumber":3542.0,"crrevision":7.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911758.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911822","title":"Identification of LTE-M (eMTC) traffic","source":"ORANGE","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) New clause 5.31.x to specify the following principles: - The UE provides a Category M indication to the eNB during RRC Connection Establishment and handover procedure from NR to E-UTRA. - The eNB provides a 'Category M Indication' to the AMF in the Initial UE Message and during handover from NR to E-UTRA. - The AMF considers that the RAT type is LTE-M when it receives this indication. Since LTE-M is addded as a RAT type, addition of 'LTE-M' in places where RAT types are listed, or removal or the listed RAT types, as appropriate. 2) Addition of a definition for LTE-M (slightly different from the one in TS 23.401). 3-4) Addition of NB-IoT RAT Type and Category M Indication as factors for AMF . 5) Some editorial corrections.","secretary_remarks":"Revision of S2-1910632 from S2#135","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":15880,"status":"available","reservation_date":"2019-11-08 16:04:55","uploaded":"2019-11-08 22:54:34","revisionof":"S2-1910632","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1363.0,"crrevision":4.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911822.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911830","title":"Identification of LTE-M (eMTC) traffic upon mobility from NR to E-UTRA in CM-IDLE","source":"ORANGE","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Provision of LTE-M Indication from NG-RAN to the AMF during Service Request procedure.","secretary_remarks":"","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":15890,"status":"available","reservation_date":"2019-11-08 16:11:38","uploaded":"2019-11-08 22:54:34","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1945.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911830.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911834","title":"[DRAFT] LS on Identification of LTE-M (eMTC) traffic upon mobility from NR to E-UTRA","source":"ORANGE","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"LS out","for":"Approval","abstract":"LS on Identification of LTE-M (eMTC) traffic upon mobility from NR to E-UTRA.","secretary_remarks":"","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":15910,"status":"available","reservation_date":"2019-11-08 16:17:22","uploaded":"2019-11-08 22:54:34","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911834.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911843","title":"UE support of CP optimization over NB-IoT","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A UE that supports the NB-IoT shall always indicate support for Control Plane CIoT EPS Optimisation.","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 - MT-EDT","tdoc_agenda_sort_order":15730,"status":"agreed","reservation_date":"2019-11-08 16:35:29","uploaded":"2019-11-08 17:46:40","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1993.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-191068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911843.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911883","title":"Corrections to Availability after DDN Failure event","source":"Nokia, Nokia Shanghai Bell","contact":"Thomas Belling","contact-id":68266,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The Call flow only applies if buffering at the SMF is used. Subscription is via UDM. Traffic filters are an optional input parameter for the Nudm_EventExposure_Subscribe service operation","secretary_remarks":"Revision of S2-1910636 from S2#135. Confirm CR Revision! Revised in parallel session to S2-1912438.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":16370,"status":"revised","reservation_date":"2019-11-08 18:04:07","uploaded":"2019-11-08 18:30:18","revisionof":"S2-1910636","revisedto":"S2-1912438","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1482.0,"crrevision":6.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911883.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911905","title":"Identification of LTE-M (eMTC) traffic upon mobility from NR to E-UTRA in CM CONNECTED","source":"ORANGE","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Provision of LTE-M Indication from NG-RAN to the AMF during inter NG_x001E_RAN handover procedures.","secretary_remarks":"","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":15900,"status":"available","reservation_date":"2019-11-08 20:17:44","uploaded":"2019-11-08 22:54:34","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1951.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911905.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911936","title":"LS from CT WG1: Forwarding of Reply LS on GUTI allocation for 5G CIoT","source":"CT WG1","contact":"Mahmoud Watfa","contact-id":72074,"tdoctype":"LS in","for":"Action","abstract":"As SA WG2, RAN WG2, RAN WG3, and CT WG4 were also part of the original LS exchange (C1-195111), CT WG1 would like to forward the LS response on 'Reply LS on GUTI allocation for 5G CIoT' that was received from SA WG3 and in which the identified groups were not copied (see attachment). Action: CT WG1 kindly requests SA WG2 to consider SA WG3's response on 5G-GUTI re-allocation for MT EDT in 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 - MT-EDT","tdoc_agenda_sort_order":15520,"status":"noted","reservation_date":"2019-11-13 06:42:03","uploaded":"2019-11-13 06:43:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG2, RAN WG3, CT WG4, SA WG3","lsoriginalls":"C1-198560","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911936.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911943","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 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 - MT-EDT","tdoc_agenda_sort_order":16130,"status":"postponed","reservation_date":"2019-11-16 05:26:29","uploaded":"2019-11-16 05:26:53","revisionof":"","revisedto":"S2-2000015","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C4-195471","lsreply":"S2-2000392","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911943.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911947","title":"LS from CT WG1: LS on support of Control Plane CIoT 5GS Optimisation","source":"CT WG1","contact":"Fei Lu","contact-id":39755,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 has compared the following requirements on the support of Control Plane CIoT Optimisation in the EPS and 5GS. In the TS 23.501, subclause 5.31.2 For NB-IoT UEs that only support Control Plane CIoT 5GS Optimisation, the AMF shall include support for Control Plane CIoT 5GS Optimisation in the Registration Accept message. In the TS 23.401, subclause 4.3.5.10 For NB-IoT UEs that only support Control Plane CIoT EPS Optimisation, the MME shall include support for Control Plane CIoT EPS Optimisation in NAS accept messages. A UE that supports the NB-IoT shall always indicate support for Control Plane CIoT EPS Optimisation. Although the green highlighted texts are missing in the TS 23.501 or TS 23.502, CT WG1 still has made an assumption that the NB-IoT UE SHALL always support Control Plane CIoT Optimisation in 5GS considering that the same RAT for NB-IoT is used in EPS and 5GS. Action: CT WG1 kindly asks SA WG2 to confirm this assumption and update their specification if required.","secretary_remarks":"Response drafted in S2-1912324. Final response in S2-1912609","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":15720,"status":"replied to","reservation_date":"2019-11-16 06:41:54","uploaded":"2019-11-16 06:42:42","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C1-198593","lsreply":"S2-1912609","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911947.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911951","title":"LS from CT WG1: LS on GUTI allocation for MT-EDT in 5G CIoT","source":"CT WG1","contact":"Lin Shu","contact-id":43310,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 thanks SA WG3 for their LS 'Reply LS on GUTI allocation for 5G CIoT' in S3-193838. Mandatory 5G-GUTI re-allocation at MT-EDT for CP CIoT 5GS optimization and UP CIoT 5GS optimization implies that a dedicated NAS procedure is executed in 5GMM-CONNECTED mode. Action: CT WG1 kindly asks the above information to be taken into account when working on MT-EDT solution for 5GS.","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 - MT-EDT","tdoc_agenda_sort_order":15510,"status":"noted","reservation_date":"2019-11-16 06:41:55","uploaded":"2019-11-16 06:42:42","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG2, RAN WG3","Cc":"SA WG3, CT WG4","lsoriginalls":"C1-199005","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911951.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911953","title":"LS from CT WG1: LS on Extended NAS timers for Coverage Enhancement in 5GS","source":"CT WG1","contact":"Mikael Wass","contact-id":42217,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 has discussed extended NAS timers in 5GS to support UEs using coverage enhancement in NB-IoT and WB-IoT. As the assumption in CT WG1 is that the same possible delay in RAN due to coverage enhancement applies in the 5GS case as in the EPS case, an attached CR based on extended NAS timer calculations in EPS has been agreed. The final values will be determined after further analysis of the 5GS NAS procedures. However, if there are any differences in RAN for coverage enhancement in 5GS compared to EPS that impact the possible delay, CT WG1 would like to be informed so that extended NAS timer values for 5GS can be adjusted accordingly.","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 - MT-EDT","tdoc_agenda_sort_order":15650,"status":"noted","reservation_date":"2019-11-16 06:41:55","uploaded":"2019-11-16 06:42:42","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"RAN WG3, SA WG2","lsoriginalls":"C1-199034","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911953.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912322","title":"Introduction of MT-EDT","source":"OPPO, Intel, Ericsson, Sumsung, Qualcomm, NEC, Orange","contact":"Jianhua Liu","contact-id":72698,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR introduces the MT-EDT for MSG4 solution. - UE sends MT-EDT support to MME during attach procedure. - During PDN connectivity establishment, MME indicates to S-GW the PDN connectivity is for MT-EDT. - add MT-EDT procedure for UP optimization. - add MT-EDT procedure for CP optimization.","secretary_remarks":"Revision of S2-1911758. This was agreed with an objection from Huawei. This CR was agreed with an objection from Huawei","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":15710,"status":"agreed","reservation_date":"2019-11-19 22:36:42","uploaded":"2019-11-25 16:07:53","revisionof":"S2-1911758","revisedto":"","release":"Rel-16","crspec":"23.401","crspecversion":"16.4.0","workitem":[{"winame":"LTE_eMTC5"},{"winame":"NB_IOTenh3"},{"winame":"5G_CIoT"}],"crnumber":3542.0,"crrevision":8.0,"crcategory":"B","tsg_crp":"SP-191059","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912322.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912323","title":"[DRAFT] LS on 5G-GUTI allocation during MT-EDT procedure","source":"Qualcomm Finland RFFE Oy","contact":"Juan Zhang","contact-id":73274,"tdoctype":"LS out","for":"Approval","abstract":"WITHDRAWN: To: CT WG1, SA WG3. CC:","secretary_remarks":"Revision of S2-1911725. 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 - MT-EDT","tdoc_agenda_sort_order":15580,"status":"withdrawn","reservation_date":"2019-11-19 22:36:43","uploaded":null,"revisionof":"S2-1911725","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912324","title":"[DRAFT] Reply LS on support of Control Plane CIoT 5GS Optimisation","source":"SA WG2","contact":"Fei Lu","contact-id":39755,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Created at meeting. Response to S2-1911947. Revised in parallel session to S2-1912609.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":15630,"status":"revised","reservation_date":"2019-11-19 22:36:43","uploaded":"2019-11-25 16:07:53","revisionof":"","revisedto":"S2-1912609","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912324.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912325","title":"[DRAFT] Reply LS on authentication of group of IoT devices","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG1. CC: SA WG3","secretary_remarks":"Revision of S2-1911079. Revised in parallel session to S2-1912607.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":15700,"status":"revised","reservation_date":"2019-11-19 22:36:43","uploaded":"2019-11-25 16:07:53","revisionof":"S2-1911079","revisedto":"S2-1912607","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912325.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912326","title":"[DRAFT] LS on category M devices and NR","source":"Qualcomm","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"Requests RAN WG2 to provide feedback on category M indication and NR support indication.","secretary_remarks":"Revision of S2-1911345. Revised in parallel session to S2-1912608.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":15750,"status":"revised","reservation_date":"2019-11-19 22:36:43","uploaded":"2019-11-25 16:07:53","revisionof":"S2-1911345","revisedto":"S2-1912608","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912326.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912327","title":"Corrections to Small Data Rate Control and Exception Reporting","source":"Huawei, HiSilicon, Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce the 'MO Exception Data Counter' reporting function. The AMF counts the exception data small data messages and informs the SMF when RRC Connection is set up for Exception Data. The SMF forwards this information to UPF which counts the Exception Data packets in order to enforce the rate of the Exception Data and to mark up the Exception Data packets in the CDR.","secretary_remarks":"Revision of S2-1911503. Revised in parallel session to S2-1912605.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":15820,"status":"revised","reservation_date":"2019-11-19 22:36:43","uploaded":"2019-11-25 16:07:53","revisionof":"S2-1911503","revisedto":"S2-1912605","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1666.0,"crrevision":7.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912327.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912328","title":"Corrections to Small Data Rate Control and Exception Reporting","source":"Huawei, HiSilicon, Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce the 'MO Exception Data Counter' reporting function.","secretary_remarks":"Revision of S2-1911504. 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 - MT-EDT","tdoc_agenda_sort_order":15960,"status":"agreed","reservation_date":"2019-11-19 22:36:44","uploaded":"2019-11-25 16:07:53","revisionof":"S2-1911504","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1645.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-191069","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912328.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912329","title":"Corrections to Small Data Rate Control in PDU Session Establishment Procedure","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the descriptions on small data rate control parameters and statuses in PDU Session Establishment Accept message.","secretary_remarks":"Revision of S2-1911655. 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 - MT-EDT","tdoc_agenda_sort_order":15990,"status":"agreed","reservation_date":"2019-11-19 22:36:45","uploaded":"2019-11-25 16:07:53","revisionof":"S2-1911655","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1927.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-191069","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912329.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912330","title":"Preferred Behaviour for MT data","source":"ORANGE","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"WITHDRAWN: Summary of change: Introduction of 'Preferred Behaviour for MT data' indicator sent from AMF to SMF. For deciding to establish N3 data transfer, the SMF does not check if N3 data transfer was successfully negotiated but checks the Preferred Behaviour for MT data, if the PDU Session is not set to Control Plane Only.","secretary_remarks":"Revision of S2-1910903. 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 - MT-EDT","tdoc_agenda_sort_order":15900,"status":"withdrawn","reservation_date":"2019-11-19 22:36:46","uploaded":null,"revisionof":"S2-1910903","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1685.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912331","title":"Preferred Behaviour for MT data","source":"ORANGE","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"WITHDRAWN: Summary of change: For deciding to establish N3 data transfer, if the PDU Session is not set to Control Plane Only, the SMF does not check if N3 data transfer was successfully negotiated but checks the Preferred Behaviour for MT data. This indication replaces the Control Plane CIoT 5GS Optimisation indication in the signaling from AMF to SMF.","secretary_remarks":"Revision of S2-1910904. 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 - MT-EDT","tdoc_agenda_sort_order":15920,"status":"withdrawn","reservation_date":"2019-11-19 22:36:47","uploaded":null,"revisionof":"S2-1910904","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1665.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912421","title":"NIDD procedure corrections","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Refer to correct steps and remove NEF ID in clause 4.25.2. Clarify roaming case handling in clause 4.25.4. Clarify roaming case handling and buffer handling by NEF in clause 4.25.5. Remove NEF ID from clause 4.25.7. Remove NEF ID from related services in clauses 5.2.6.14.2, 5.2.6.15.2, 5.2.6.15.3, 5.2.6.15.4 Include Extended Buffering Support indication in Nnef_SMContext_Create Response instead of in Nsmf_NIDD_Delivery request. Clarify that NEF subscribes with AMF to receive an indication when UE becomes reachable and that NEF starts delivering buffered data when this indication is received from AMF.","secretary_remarks":"Revision of S2-1911093. 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 - MT-EDT","tdoc_agenda_sort_order":16070,"status":"agreed","reservation_date":"2019-11-20 19:44:25","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911093","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1728.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-191069","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912421.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912422","title":"EPS to 5GS Idle mode mobility with data fowarding","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"WITHDRAWN: Summary of change: A flow describing the data forwarding based on TS 23.401 clause 5.3.3.1A is added.","secretary_remarks":"Revision of S2-1911108. 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 - MT-EDT","tdoc_agenda_sort_order":15980,"status":"withdrawn","reservation_date":"2019-11-20 19:44:26","uploaded":null,"revisionof":"S2-1911108","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1590.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912423","title":"N3 tunnel info handling during Suspend and Resume procedure","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarified N3 tunnel handling in UPF\/SMF at Suspend and Resume.","secretary_remarks":"Revision of S2-1911109. 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 - MT-EDT","tdoc_agenda_sort_order":16110,"status":"agreed","reservation_date":"2019-11-20 19:44:27","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911109","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1791.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-191069","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912423.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912425","title":"Enforcing maximum UP resources activation of 2 PDU sessions for NB-IoT","source":"Qualcomm Incorporated, Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce the AMF enforcing the maximum of 2 PDU sessions with active UP resources for RAT type NB-IoT to service request procedure and N3 data transfer procedure. Rev 3: AMF enforcing the maximum of 2 PDU sessions with active UP resources for RAT type NB-IoT in PDU session establishment procedure","secretary_remarks":"Revision of S2-1911110. This CR was 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 - MT-EDT","tdoc_agenda_sort_order":16130,"status":"agreed","reservation_date":"2019-11-20 19:44:28","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911110","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1868.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-191069","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912425.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912426","title":"Small Data transfer for CP CIoT","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Nsmf_PDUSession_MessageTransfer is re-named to Nsmf_PDUSession_SendMOData service operation is added consistently in the call flow and the service operation is specified for MO Small Data. Namf_Communication_N1N2MessageTransfer service operation is used consistently instead of NAS message. The misleading use of 'NAS message' at N11 interface is removed.","secretary_remarks":"Revision of S2-1911512. 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 - MT-EDT","tdoc_agenda_sort_order":16150,"status":"agreed","reservation_date":"2019-11-20 19:44:29","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911512","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1916.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-191069","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912426.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912427","title":"Corrections to RDS Configuration in the PDU Session Establishment procedure","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add description that the RDS configuration is provided to the UE in the PDU Session Establishment Accept message.","secretary_remarks":"Revision of S2-1911657. 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 - MT-EDT","tdoc_agenda_sort_order":16180,"status":"agreed","reservation_date":"2019-11-20 19:44:30","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911657","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1929.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-191069","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912427.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912428","title":"Clarification on MAC AS RAI in 5GC","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that it is the RAI signalled by MAC using BSR added in Rel-14 is not used.","secretary_remarks":"Revision of S2-1911647. 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 - MT-EDT","tdoc_agenda_sort_order":16200,"status":"agreed","reservation_date":"2019-11-20 19:44:31","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911647","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1775.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-191069","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912428.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912429","title":"Removal of ENs for control plane congestion control","source":"Vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Replace initial NAS message with uplink data with Control Plane Service Request. Remove content of NOTE 3, which related to the additional indication. Editorial modification on second bullet to make it more clear. Replace the NAS message in the third bullet with Service Accept. Modify the clause X.Y.Z in third bullet to 23.502 clause 4.2.3 (Service Request procedure) Remove the two Ens.","secretary_remarks":"Revision of S2-1911431. 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 - MT-EDT","tdoc_agenda_sort_order":16220,"status":"agreed","reservation_date":"2019-11-20 19:44:33","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911431","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1721.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-191068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912429.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912430","title":"Support for PDN Connectivity Status monitoring event","source":"Ericsson, Verizon, Nokia","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Added the PDU Session Status event to the list of monitoring events in subclause 4.15.3.1. - Added SMF event notification towards NEF for PDU Session Status - Added PDU Session Establishment to the Nsmf_EventExposure Service. - Added missing parameters PDU Session Type and DNN as optional parameters in the event notification. The NEF makes a mapping between the 5GS internal event 'PDU Session Status' and the T8 API event 'PDN Connectivity Status'.","secretary_remarks":"Revision of S2-1911111. 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 - MT-EDT","tdoc_agenda_sort_order":16260,"status":"agreed","reservation_date":"2019-11-20 19:44:35","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911111","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1587.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-191069","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912430.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912432","title":"I-NEF in Interworking Scenarios","source":"Convida Wireless LLC","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When interworking is possible, the UE should associate with a node that implements combined IWK-SCEF and I-NEF functionality.","secretary_remarks":"Revision of S2-1911095. 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 - MT-EDT","tdoc_agenda_sort_order":16310,"status":"agreed","reservation_date":"2019-11-20 19:44:36","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911095","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1594.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-191068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912432.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912433","title":"Correction of UDM subscription to Nsmf_EventExposure","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove 'AF service ID' from the descripton of UDM subscritpion to Nsmf_EventExposure. Clarify that NEF maps the AF-Identity into the DNN and S-NSSAI combination.","secretary_remarks":"Revision of S2-1911048. 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 - MT-EDT","tdoc_agenda_sort_order":16340,"status":"agreed","reservation_date":"2019-11-20 19:44:37","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911048","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1721.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-191069","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912433.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912434","title":"Monitoring Event Subscription and Network Configuration correction","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: For Loss of Connectivity, the subscription may include Maximum Detection Time. For UE reachability, the subscription may include Maximum Latency, Maximum Response Time and\/or Suggested number of downlink packets. The UDM authorises the Maximum Detection Time\/Maximum Latency, Maximum Response Time and Suggested number of downlink packets. If the subscribed periodic registration timer, subscribed Active Time and\/or Suggested number of downlink packets are set or modified, the UDM sends the Nudm_SDM_Notification request to related serving AMF(s).","secretary_remarks":"Revision of S2-1911649. 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 - MT-EDT","tdoc_agenda_sort_order":16360,"status":"agreed","reservation_date":"2019-11-20 19:44:38","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911649","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1516.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-191069","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912434.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912435","title":"Monitoring event triggers","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Notification event trigger criteria is made more precise and corrected where necessary. Reference to clause 4.15.1 is added to those cases where the monitoring events are triggered according to a schedule requested by the initiator of the monitoring request. Reporting condition is updated for those Monitoring Events whose reporting condition was incorrect. Missing event notification parameters are added to Loss of connectivity and UE reachability monitoring events. Note 4 is corrected.","secretary_remarks":"Revision of S2-1911510. 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 - MT-EDT","tdoc_agenda_sort_order":16380,"status":"agreed","reservation_date":"2019-11-20 19:44:39","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911510","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1810.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-191069","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912435.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912436","title":"Group NIDD corrections","source":"Nokia, Nokia Shanghai Bell, Convida Wireless LLC","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Following the example set in TS 23.682 clause 5.5.3 (Group NIDD) refers to unicast procedure in clause 5.13.3, a new call flow for group NIDD is introduced in TS 23.502. The new Group NIDD call flow refers to unicast call flow in 4.25.5. External Group Identifier input parameter is added in the Nnef_NIDD_Delivery service operation parameters list. Unicast call flow in clause 4.25.5. is also updated to refer to MT procedure instead of MO procedure in step 4 as intended.","secretary_remarks":"Revision of S2-1911509. 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 - MT-EDT","tdoc_agenda_sort_order":16420,"status":"agreed","reservation_date":"2019-11-20 19:44:43","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911509","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1809.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-191069","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912436.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912437","title":"Clarifications on CN assistance information sent to the RAN","source":"Motorola Mobility, Lenovo","contact":"Genadi Velev","contact-id":70944,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to add text clarifying that the AMF may provide independent sets of 'Expected UE activity behaviour' to the RAN, i.e. UE level of 'Expected UE activity behaviour' parameters set or PDU Session level 'Expected UE activity behaviour' parameters sets.","secretary_remarks":"Revision of S2-1911352. 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 - MT-EDT","tdoc_agenda_sort_order":16450,"status":"agreed","reservation_date":"2019-11-20 19:44:45","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911352","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1899.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-191068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912437.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912438","title":"Corrections to Availability after DDN Failure event","source":"Nokia, Nokia Shanghai Bell, Huawei, HiSilicon","contact":"Thomas Belling","contact-id":68266,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The Call flow only applies if buffering at the SMF is used. Subscription is via UDM. Traffic filters are an optional input parameter for the Nudm_EventExposure_Subscribe service operation","secretary_remarks":"Revision of S2-1911883. Revised in parallel session to S2-1912606.","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":16380,"status":"revised","reservation_date":"2019-11-20 19:44:47","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911883","revisedto":"S2-1912606","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1482.0,"crrevision":7.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912438.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912487","title":"MT-EDT introduction","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"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 S2-1911724. There were 4 companies who objected to this CR. This was 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 - MT-EDT","tdoc_agenda_sort_order":15500,"status":"noted","reservation_date":"2019-11-21 16:38:04","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911724","revisedto":"S2-2000264","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1848.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912487.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912605","title":"Corrections to Small Data Rate Control and Exception Reporting","source":"Huawei, HiSilicon, Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce the 'MO Exception Data Counter' reporting function. The AMF counts the exception data small data messages and informs the SMF when RRC Connection is set up for Exception Data. The SMF forwards this information to UPF which counts the Exception Data packets in order to enforce the rate of the Exception Data and to mark up the Exception Data packets in the CDR.","secretary_remarks":"Revision of S2-1912327. 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 - MT-EDT","tdoc_agenda_sort_order":15940,"status":"agreed","reservation_date":"2019-11-25 15:21:21","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912327","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1666.0,"crrevision":8.0,"crcategory":"F","tsg_crp":"SP-191068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912605.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912606","title":"Corrections to Availability after DDN Failure event","source":"Nokia, Nokia Shanghai Bell, Huawei, HiSilicon","contact":"Thomas Belling","contact-id":68266,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The Call flow only applies if buffering at the SMF is used. Subscription is via UDM. Traffic filters are an optional input parameter for the Nudm_EventExposure_Subscribe service operation","secretary_remarks":"Revision of S2-1912438. 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 - MT-EDT","tdoc_agenda_sort_order":16500,"status":"agreed","reservation_date":"2019-11-25 15:21:23","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912438","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1482.0,"crrevision":8.0,"crcategory":"F","tsg_crp":"SP-191069","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912606.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912607","title":"[DRAFT] Reply LS on authentication of group of IoT devices","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG1. CC: SA WG3","secretary_remarks":"Revision of S2-1912325. For e-mail approval","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":15710,"status":"available","reservation_date":"2019-11-25 15:21:24","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912325","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912607.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912608","title":"LS on category M devices and NR","source":"SA WG2","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2.","secretary_remarks":"Revision of S2-1912326. 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 - MT-EDT","tdoc_agenda_sort_order":15760,"status":"approved","reservation_date":"2019-11-25 15:21:24","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912326","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912608.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912609","title":"Reply LS on support of Control Plane CIoT 5GS Optimisation","source":"SA WG2","contact":"Fei Lu","contact-id":39755,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachments: S2-1911843 (TS 23.501 CR#1993).","secretary_remarks":"Revision of S2-1912324. 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 - MT-EDT","tdoc_agenda_sort_order":15640,"status":"approved","reservation_date":"2019-11-25 15:21:24","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912324","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1911947","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912609.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912713","title":"Support of TAs with heterogeneous support of eDRX","source":"ORANGE","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding the case of a UE registering over NR. Adding a new clause for TAs with heterogeneous support of eDRX, to specify how to handle UEs doing Idle Mode mobility from NR to WB-E-UTRAN: the AMF shall ensure that the UE is reached in any cases (eDRX is used or not). Moving an Editor's Note to this new clause because it is related to heterogeneous support of eDRX.","secretary_remarks":"Revision of S2-1910905. For e-mail approval. e-mail agreed. This CR was 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 - MT-EDT","tdoc_agenda_sort_order":16530,"status":"agreed","reservation_date":"2019-11-25 15:22:29","uploaded":"2019-11-25 16:07:57","revisionof":"S2-1910905","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1689.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-191068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912713.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]