[{"name":"S2-1908645","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-1906839 from S2#134. Responses drafted in S2-1909251, S2-1909803 and S2-1909894. Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":17910,"status":"postponed","reservation_date":"2019-09-16 19:37:37","uploaded":"2019-09-16 21:37:53","revisionof":"S2-1906839","revisedto":"S2-1910849","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C3-191407","lsreply":"S2-1910641","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908645.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908649","title":"LS from RAN WG3: Reply LS on Mobile-terminated Early Data Transmission","source":"RAN WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 thanks RAN WG2 for their liaison and would like to inform RAN WG2 that upon RAN WG2 request referenced here-above, RAN WG3 has evaluated the RAN WG3 impact of adding an MT-EDT indication in the S1 paging message to inform eNB that MME initiates MT-EDT. RAN WG3 has considered to introduce an explicit MT-EDT indicator in S1 Paging message from MME to inform eNB about possibility to initiate MT-EDT session. However, some companies stressed the fact that this indicator may not be sufficient to set up MT-EDT and that having information about DL data size in S1 paging would help the eNB to decide more precisely if MT EDT should be triggered. RAN WG3 assumes that in any case the eNB needs to be able to fallback to non-EDT operation (e.g. at least depending on propagation conditions), and also that frequent occurrence of such fallback would not be desirable. Therefore, RAN WG3 would appreciate feedback from RAN WG2 on whether RAN WG2 would see benefit in MME providing the data size in the S1 paging message.","secretary_remarks":"Postponed S2-1906876 from S2#134. Response drafted in S2-1908905. Final response in S2-1910804","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":17200,"status":"replied to","reservation_date":"2019-09-16 19:37:37","uploaded":"2019-09-16 21:37:53","revisionof":"S2-1906876","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"SA WG2, CT WG1, CT WG4","lsoriginalls":"R3-193156","lsreply":"S2-1910804","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908649.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908659","title":"LS from CT WG1: Reply LS on NAS Aspects of Mobile-terminated Early Data Transmission","source":"CT WG1","contact":"Mahmoud Watfa","contact-id":72074,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 thanks SA WG2 for their LS on Mobile-terminated Early Data Transmission (MT EDT). CT WG1 has discussed the security and incorrect charging issue, and the applicability of MT EDT in 5GC that were raised in S2-1908629. Regarding the security and incorrect charging issue, CT WG1 would like to provide an answer to the following question from SA WG2: Q1: SA WG2 asks SA WG3, RAN WG2, RAN WG3 and CT WG1 to consider the security procedure for the message 2 solution for both CP CIoT EPS Optimisation and UP CIoT EPS Optimisation. Answer: CT WG1 has analysed the message 2 solution for CP CIoT EPS optimization and would like to indicate that this solution would lead to major NAS impacts especially related to NAS security. A secure NAS signalling connection is currently only established with a UE-triggered procedure e.g. when the UE sends a CONTROL PLANE SERVICE REQUEST message from EMM-IDLE mode. The message 2 solution requires a network-initiated delivery of a security protected NAS message for a UE in EMM-IDLE mode which is not supported and is not in accordance with the basic NAS procedures for the establishment of a secure NAS connection. This solution has other NAS impacts such as delivering MT data in a session management (ESM) message for a UE in EMM-IDLE mode whereas ESM messages can only be sent in EMM-CONNECTED mode. - CT WG1 would like to indicate that message 2 option for CP CIoT EPS optimization involves numerous associated NAS impacts. Regarding the message 2 solution for UP CIoT EPS optimization, a NAS solution to confirm that a legitimate UE has received the MT data would defeat the purpose of UP CIoT EPS optimization which usually does not require sending of a SERVICE REQUEST message to resume a connection for user-plane data. - CT WG1 would like to indicate that message 2 option for UP CIoT EPS optimization cannot provide benefits compared to message 4 option if this requires a NAS message to confirm the legitimacy of the recipient UE. CT WG1 would like to indicate that: - Message 4 option for CP CIoT EPS optimization can be supported without NAS impacts, and - Message 4 option for UP CIoT EPS optimization may have NAS impacts. CT WG1 has not fully analyzed this. Regarding MT EDT in 5GC, message 4 option can also be used for CP CIoT 5GS optimization and UP CIoT 5GS optimization. However, CT WG1 would like to highlight that in Release 15, there is a requirement to allocate a new 5G-GUTI after the establishment of a NAS signalling connection following a network paging procedure. This SA WG3 requirement may have an impact on the MT EDT solutions for both CP CIoT 5GS optimization and UP CIoT 5GS optimization. CT WG1 would like to ask SA WG3 whether the allocation of a new 5G-GUTI will still be required for MT EDT and inform SA WG2 to consider this requirement if confirmed by SA WG3. Action: CT WG1 kindly requests SA WG2 to take the responses above into account and consider SA WG3's response regarding 5G-GUTI re-allocation in the MT EDT solutions accordingly","secretary_remarks":"Response drafted in S2-1910389. Final response in S2-1910804","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":17180,"status":"replied to","reservation_date":"2019-09-16 19:37:37","uploaded":"2019-09-16 21:37:53","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3","Cc":"RAN WG2, RAN WG3, CT WG4","lsoriginalls":"C1-195111","lsreply":"S2-1910804","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908659.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908663","title":"LS from CT WG1: LS on support for flow based QoS for NB-IoT connected to 5GC","source":"CT WG1","contact":"Mahmoud Watfa","contact-id":72074,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 thanks SA WG2 for their LS on support for flow based QoS for NB-IoT connected to 5GC. Related to the text below (from S2-1908552), CT WG1 discussed the enforcement of this requirement in the network when a UE in NB-IoT requests the establishment of user plane resources for more than 2 PDU sessions (e.g. with a service request procedure, or PDU session establishment procedure when UP CIoT 5GS optimization is being used). SA WG2 Answer 2: As per SA WG2 answer 1, there is one QoS flow per PDU session. SA WG2 agreed the support of a maximum of 2 PDU sessions with active user plane resources for NB-IoT connected to 5GC. Therefore, a maximum of 2 QoS flows with active user plane resources is supported for NB-IoT connected to 5GC. Note the UE can have more than 2 PDU sessions, with one or more PDU sessions using Control Plane CIoT 5GS Optimisation for small data transmission. Action: CT WG1 kindly asks SA WG2 to provide guidance on how the network can enforce the requirement above.","secretary_remarks":"Responses drafted in S2-1908932 and S2-1909911. Final response in S2-1910643","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":18350,"status":"replied to","reservation_date":"2019-09-16 19:37:37","uploaded":"2019-09-16 21:37:53","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG3","lsoriginalls":"C1-195166","lsreply":"S2-1910643","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908663.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908668","title":"LS from CT WG4: 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 kindly ask SA WG2 to answer to the following questions. {...}. Action: CT WG4 kindly asks SA WG2 group to answer to the above questions and to clarify the Stage 2 specification requirements.","secretary_remarks":"Responses drafted in S2-1909223 and S2-1909444. Final response in S2-1910805","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":18110,"status":"replied to","reservation_date":"2019-09-16 19:37:37","uploaded":"2019-09-16 21:37:53","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1","lsoriginalls":"C4-193642","lsreply":"S2-1910805","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908668.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908669","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","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":18560,"status":"postponed","reservation_date":"2019-09-16 19:37:37","uploaded":"2019-09-16 21:37:53","revisionof":"","revisedto":"S2-1910855","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C4-193769","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908669.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908680","title":"LS from RAN WG2: Reply LS on LTE-M identification in 5GC","source":"RAN WG2","contact":"Mungal Singh Dhanda","contact-id":38917,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 thanks SA WG2 for their LS on LTE-M identification in 5GC. RAN WG2 investigated solutions to enable LTE-M identification from Initial UE message that is sent to the AMF and from RAN WG2 stand point it is feasible to include LTE-M indication by Cat-M UE in RRC Connection Setup Complete message if UE selected 5GC. Action: RAN WG2 respectfully asks SA WG2 and RAN WG3 to take into account the above answers during their work on cellular 5GC IoT.","secretary_remarks":"Response drafted in S2-1910393. Final response in S2-1910644","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":17560,"status":"replied to","reservation_date":"2019-09-16 19:37:38","uploaded":"2019-09-16 21:37:53","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG3","Cc":"TSG RAN","lsoriginalls":"R2-1911601","lsreply":"S2-1910644","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908680.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908681","title":"LS from RAN WG2: Reply LS on Mobile-terminated Early Data Transmission","source":"RAN WG2","contact":"Tuomas Tirronen","contact-id":73195,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 thanks SA WG2 for the Reply LS on Mobile-terminated Early Data Transmission in S2-1908629 and would like to provide the following information regarding agreements made in RAN WG2: - Msg2 based solution is not pursued in this release. Regarding SA WG2 considerations in S2-1908629 on fallback to normal user plane DL data transmission, RAN WG2 has made the following agreement: - Fallback is supported in the case there is more downlink data to be sent, i.e. network can move the UE to connected mode in Msg4. RAN WG2 also thanks RAN WG3 for the Reply LS on Mobile-terminated Early Data Transmission in R3-193156 and would like to provide the following reply: - From RAN WG2 stand point indicating the DL data size in the S1 paging message would be beneficial and sufficient, i.e. separate indication is not required. Action: RAN WG2 kindly asks SA WG2 and RAN WG3 to take the above information into account and provide feedback, if any.","secretary_remarks":"Responses drafted in S2-1908905 and S2-1909227. Final response in S2-1910804","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":17190,"status":"replied to","reservation_date":"2019-09-16 19:37:38","uploaded":"2019-09-16 21:37:53","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG3","Cc":"SA WG3, CT WG1, CT WG4","lsoriginalls":"R2-1911603","lsreply":"S2-1910804","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908681.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908684","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","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":18440,"status":"postponed","reservation_date":"2019-09-16 19:37:38","uploaded":"2019-09-16 21:37:53","revisionof":"","revisedto":"S2-1910858","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_135_Split\/Docs\/S2-1908684.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908690","title":"LS from RAN WG2: Reply LS on UAC for NB-IoT","source":"RAN WG2","contact":"Mungal Singh Dhanda","contact-id":38917,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 thanks SA WG1 for their response LS on UAC for NB-IoT. RAN WG2 has considered the SA WG1 response to Question 2. RAN WG2 would like to point out that mo-ExceptionData is different from any other mobile originated data as follows: - it has higher priority than other mobile originated data (i.e. UE may be barred for mobile originated data but not barred for mo-ExceptionData). - not same as Emergency calls because mo-ExceptionData can only be sent by a UE that is registered with the network. - it can be barred according to PLMN selection category a, b & c. Therefore, RAN WG2 recommends that SA WG1 assigns a new Access Category to mo-ExceptionData.","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":17210,"status":"noted","reservation_date":"2019-09-16 19:37:38","uploaded":"2019-09-16 21:37:53","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"CT WG1, SA WG2, RAN WG3","lsoriginalls":"R2-1911865","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908690.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908693","title":"LS from RAN WG3: Reply LS on LTE-M identification in 5GC","source":"RAN WG3","contact":"Luis Lopes","contact-id":47178,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 would like to thank SA WG2 for the LS on LTE-M identification in 5GC. RAN WG3 understands that SA WG2 would like to enable LTE-M to be identified from the Initial UE message that is sent to AMF. From RAN WG3 point of view, it is feasible to introduce this functionality in NGAP, provided RAN WG2 confirms that it is also feasible from their perspective (through an indication in msg5, or otherwise). Action: RAN WG3 requests SA WG2 and RAN WG2 to take the above information into account, and to provide updates as needed.","secretary_remarks":"Response drafted in S2-1910393. Final response in S2-1910644","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":17550,"status":"replied to","reservation_date":"2019-09-16 19:37:38","uploaded":"2019-09-16 21:37:53","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, TSG RAN, RAN WG2","Cc":"SA WG3","lsoriginalls":"R3-194748","lsreply":"S2-1910644","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908693.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908701","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","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":18780,"status":"postponed","reservation_date":"2019-09-16 19:37:38","uploaded":"2019-09-16 21:37:53","revisionof":"","revisedto":"S2-1910863","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_135_Split\/Docs\/S2-1908701.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908703","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":"Response drafted in S2-1909065. 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":18430,"status":"postponed","reservation_date":"2019-09-16 19:37:38","uploaded":"2019-09-16 21:37:53","revisionof":"","revisedto":"S2-1910864","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_135_Split\/Docs\/S2-1908703.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908707","title":"LS from SA WG3: Reply LS on RRC Connection Reestablishment for CP for NB-IoT connected to 5GC","source":"SA WG3","contact":"Wu Rong","contact-id":49499,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 thanks RAN WG2 for their LS on RRC Connection Re-Establishment for the control plane for NB-IoT connected to 5GC. SA WG3 has discussed the LS and agreed to study the security of RRC Connection Re-Establishment for the control plane for NB-IoT connected to 5GC. As part of the study, the security impacts of truncated 5G S-TMSI will be considered. Action: SA WG3 kindly requests RAN WG2 and SA WG2 to take the above information into account.","secretary_remarks":"Response drafted in S2-1909254. Final response in S2-1910789","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":17770,"status":"replied to","reservation_date":"2019-09-16 19:37:38","uploaded":"2019-09-16 21:37:53","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, SA WG2","Cc":"CT WG4","lsoriginalls":"S3-192394","lsreply":"S2-1910789","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908707.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908711","title":"LS from SA WG3: Reply LS on Reply LS on Mobile-terminated Early Data Transmission","source":"SA WG3","contact":"Suresh Nair","contact-id":70166,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 thanks SA WG2 for their LS on Mobile-terminated Early Data Transmission (MT EDT). SA WG3 discussed the LS from SA WG2 and acknowledge the security issues related to the delivery of packet to the correct UE and the need to avoid incorrect charging. SA WG3 would like to provide following answers to the questions. Q1: SA WG2 asks SA WG3, RAN WG2, RAN WG3 and CT WG1 to consider the security procedure for the message 2 solution for both CP CIoT EPS Optimisation and UP CIoT EPS Optimisation. SA WG3 Answer: For message 2 based solutions, new security solutions are required to ensure the delivery of packet to the correct UE and to avoid incorrect charging. This is true for MT-EDT for both CP and UP CIoT optimization UEs. Q2: SA WG2 asks SA WG3 to provide feedback on the SA WG2 assumptions and potential security issues for MT-EDT options discussed above. SA WG3 Answer: SA WG3 confirm that SA WG2's assumption on the re-use of the MO-EDT for UP and CP optimization security procedures for Message 4 solutions are correct. No new security solutions are required to secure Message4 based solutions. Action: SA WG3 kindly requests SA WG2, RAN WG2, RAN WG3, CT WG1 to take the above answers into consideration. Please inform SA WG3 the final choice of solutions so that SA WG3 can develop new solution if Message2 based solution is chosen.","secretary_remarks":"Response drafted in S2-1908905. Final response in S2-1910804","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":0,"status":"replied to","reservation_date":"2019-09-16 19:37:38","uploaded":"2019-09-16 21:37:53","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG2, RAN WG3, CT WG1","Cc":"","lsoriginalls":"S3-193059","lsreply":"S2-1910804","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908711.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908737","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":"Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18470,"status":"not treated","reservation_date":"2019-09-24 06:54:37","uploaded":"2019-10-04 23:07:57","revisionof":"","revisedto":"S2-1910903","release":"Rel-16","crspec":"23.501","crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1685.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908737.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908741","title":"Identification of LTE-M (eMTC) traffic","source":"ORANGE, Ericsson, Qualcomm","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. - The eNB provides a 'Category M Indication' to the AMF in the Initial UE Message. - 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, when 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 (unhandled) S2-1905289 from S2#133. Revised in parallel session to S2-1910390.","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":17570,"status":"revised","reservation_date":"2019-09-24 07:36:36","uploaded":"2019-10-04 19:56:34","revisionof":"S2-1905289","revisedto":"S2-1910390","release":"Rel-16","crspec":"23.501","crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1363.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908741.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908742","title":"Identification of LTE-M (eMTC) traffic","source":"Orange","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) Relevant clauses of the specification updated according to the principles from 23.501 CR#1363. Clarification that the signaling of RAT Type is also for charging differentiation. 2) Alignment with stage 3 specifications for RAT Type information spreading during PDU Session Establishment 3) Some typos fixed.","secretary_remarks":"Revision of (unhandled) S2-1905292 from S2#133. Revised in parallel session to S2-1910391.","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":17600,"status":"revised","reservation_date":"2019-09-24 07:40:24","uploaded":"2019-10-04 20:01:19","revisionof":"S2-1905292","revisedto":"S2-1910391","release":"Rel-16","crspec":"23.502","crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1372.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908742.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908744","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":"Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18480,"status":"not treated","reservation_date":"2019-09-24 09:04:39","uploaded":"2019-10-04 23:07:57","revisionof":"","revisedto":"S2-1910904","release":"Rel-16","crspec":"23.502","crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1665.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908744.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908745","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":"Check and correct TS base version used. Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18750,"status":"not treated","reservation_date":"2019-09-24 09:08:09","uploaded":"2019-10-04 20:01:19","revisionof":"","revisedto":"S2-1910905","release":"Rel-16","crspec":"23.501","crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1689.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908745.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908746","title":"Control Plane CIoT 5GS Optimisations restriction on NR","source":"ORANGE, Vodafone, AT&T, Nokia, Nokia Shanghai Bell","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When connected over any other 5G AN than E-UTRA, a UE which negotiated the use of the CP CIoT 5GS optimisation, may use the Control Plane CIoT 5GS Optimisation, but without using EDT or RAI (as those capabilities would require AN support).","secretary_remarks":"Add clauses affected. Revised in parallel session to S2-1910491.","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":18060,"status":"revised","reservation_date":"2019-09-24 09:17:05","uploaded":"2019-10-04 20:05:15","revisionof":"","revisedto":"S2-1910491","release":"Rel-16","crspec":"23.501","crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1690.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908746.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908747","title":"Control Plane CIoT 5GS Optimisations restriction on NR","source":"ORANGE, Vodafone","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adds restrictions in the procedure for UPF anchored Mobile Originated Data Transport in Control Plane CIoT 5GS Optimisation, to prevent the UE to use EDT or RAI.","secretary_remarks":"Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18090,"status":"not treated","reservation_date":"2019-09-24 09:25:21","uploaded":"2019-10-04 20:05:15","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1666.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908747.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908748","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":"Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18580,"status":"not treated","reservation_date":"2019-09-24 09:34:52","uploaded":"2019-10-04 20:14:50","revisionof":"","revisedto":"S2-1911080","release":"Rel-16","crspec":"23.501","crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1691.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908748.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908749","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. 'Data delivery Status' replaced by 'Downlink Data delivery Status' in 4.15.3.2.5. Editorial fixes.","secretary_remarks":"Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18590,"status":"not treated","reservation_date":"2019-09-24 09:38:18","uploaded":"2019-10-04 23:07:57","revisionof":"","revisedto":"S2-1911081","release":"Rel-16","crspec":"23.502","crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1667.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908749.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908750","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":"Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18510,"status":"not treated","reservation_date":"2019-09-24 09:49:57","uploaded":"2019-10-04 23:07:57","revisionof":"","revisedto":"S2-1910906","release":"Rel-16","crspec":"23.502","crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1668.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908750.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908752","title":"Service Exposure in Interworking Scenarios","source":"ORANGE","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":"Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18620,"status":"not treated","reservation_date":"2019-09-24 13:13:19","uploaded":"2019-10-04 23:23:51","revisionof":"","revisedto":"S2-1910907","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1693.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908752.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908901","title":"Discussion on supporting MT-EDT","source":"OPPO","contact":"Jianhua Liu","contact-id":72698,"tdoctype":"discussion","for":"Decision","abstract":"DIscuss the issues when introducing MT-EDT","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":17250,"status":"noted","reservation_date":"2019-09-30 05:13:09","uploaded":"2019-10-04 01:19:58","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908901.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908902","title":"Introduction of MT-EDT","source":"OPPO","contact":"Jianhua Liu","contact-id":72698,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce the method for MT-EDT determination; Introduce the release indication to release UE immediately after the EDT data is transmitted completely.","secretary_remarks":"Merged into S2-1910387","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":17340,"status":"merged","reservation_date":"2019-09-30 05:16:12","uploaded":"2019-10-04 01:19:58","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1719.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908902.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908903","title":"Introduction of MT-EDT","source":"OPPO","contact":"Jianhua Liu","contact-id":72698,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce the method for MT-EDT.","secretary_remarks":"Revised, merging S2-1909878, to S2-1909954.","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":17360,"status":"revised","reservation_date":"2019-09-30 05:19:32","uploaded":"2019-10-04 01:19:58","revisionof":"","revisedto":"S2-1909954","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1695.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908903.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908904","title":"Introduction of MT-EDT","source":"OPPO","contact":"Jianhua Liu","contact-id":72698,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR introduces the MT-EDT.","secretary_remarks":"Revised, merging S2-1909876, to S2-1909953.","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":17280,"status":"revised","reservation_date":"2019-09-30 05:25:17","uploaded":"2019-10-04 01:19:58","revisionof":"","revisedto":"S2-1909953","release":"Rel-16","crspec":"23.401","crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":3542.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908904.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908905","title":"[DRAFT] Reply LS on Mobile-terminated Early Data Transmission","source":"OPPO","contact":"Jianhua Liu","contact-id":72698,"tdoctype":"LS out","for":"Approval","abstract":"Relpy LS on MT-EDT on UE capability issue and relationship with MO-EDT.","secretary_remarks":"Response to S2-1908649 and S2-1908711. Revised in parallel session to S2-1910389.","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":17490,"status":"revised","reservation_date":"2019-09-30 05:29:14","uploaded":"2019-10-04 01:19:58","revisionof":"","revisedto":"S2-1910389","release":"","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_135_Split\/Docs\/S2-1908905.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908918","title":"[CIoT] 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":"Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18520,"status":"not treated","reservation_date":"2019-09-30 06:40:51","uploaded":"2019-10-04 10:05:20","revisionof":"","revisedto":"S2-1911431","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1721.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908918.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908932","title":"[DRAFT] Reply LS on support for flow based QoS for NB-IoT connected to 5GC","source":"ZTE","contact":"Yingjie Hong","contact-id":76103,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: RAN WG3","secretary_remarks":"Response to S2-1908663. Merged into S2-1910499","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":18390,"status":"merged","reservation_date":"2019-09-30 08:13:35","uploaded":"2019-10-03 08:56:49","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"RAN WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908932.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908933","title":"Clarifications to number of PDU sessions for NB-IoT","source":"ZTE","contact":"Yingjie Hong","contact-id":76103,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that the NB-IoT UE can have at most two non-CP only PDU session.","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":18360,"status":"noted","reservation_date":"2019-09-30 08:23:01","uploaded":"2019-10-03 08:56:49","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1724.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908933.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908935","title":"Clarification of CIoT","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 optional supported in WB-E-UTRA connected to 5GC in clause 5.31.7.2.1.","secretary_remarks":"Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18740,"status":"not treated","reservation_date":"2019-09-30 08:32:00","uploaded":"2019-10-03 08:56:49","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1725.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908935.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908953","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 authorizes 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 (unhandled) S2-1907210 from S2#134 Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18630,"status":"not treated","reservation_date":"2019-09-30 09:42:56","uploaded":"2019-10-04 14:12:15","revisionof":"S2-1907210","revisedto":"S2-1911649","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1516.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908953.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909047","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":"Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18650,"status":"not treated","reservation_date":"2019-10-01 01:29:49","uploaded":"2019-10-04 14:04:06","revisionof":"","revisedto":"S2-1911048","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1721.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909047.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909062","title":"Extended NAS timers for CE mode B","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If UE supports CE mode B and use of CE mode B is not restricted for the UE then AMF shall use extended NAS-MM timers and shall indicate to SMF to use extended NAS-SM timers. If use of CE mode B changes from restricted to unrestricted or vice versa in the Enhanced Coverage Restriction information in the UE context in the AMF (e.g. due to a subscription change or due to EPS to 5GS mobility), and the UE has already established PDU sessions, then AMF shall trigger a PDU session modification to the SMFs serving the UE's PDU sessions and include the extended NAS-SM indication only if use of CE mode B is unrestricted in the Enhanced Coverage Restriction information in the UE context in the AMF.","secretary_remarks":"Agreed in parallel session This was 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":18290,"status":"agreed","reservation_date":"2019-10-01 07:37:00","uploaded":"2019-10-04 19:00:17","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1745.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-191068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909062.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909063","title":"Extended NAS timers for CE mode B","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If UE supports CE mode B and use of CE mode B is not restricted for the UE then AMF shall use extended NAS-MM timers and shall indicate to SMF to use extended NAS-SM timers in PDU session establishment, Subscriber Data Update Notification to AMF (if use of CE mode B changes from restricted to unrestricted or vice versa) and during EPS to 5GS mobility. Update Nsmf_PDUSession_Create service operation and Nsmf_PDUSession_Update service operation to support extended NAS-SM timer indication.","secretary_remarks":"Revised in parallel session to S2-1910496.","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":18300,"status":"revised","reservation_date":"2019-10-01 07:39:37","uploaded":"2019-10-04 19:00:17","revisionof":"","revisedto":"S2-1910496","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1727.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909063.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909064","title":"Requirements on Efficient bulk operations for IoT","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"discussion","for":"Agreement","abstract":"This paper discusses requirements on efficient bulk operations for IoT and proposes a way forward.","secretary_remarks":"Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18450,"status":"not treated","reservation_date":"2019-10-01 07:41:30","uploaded":"2019-10-04 19:00:17","revisionof":"","revisedto":"S2-1911073","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909064.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909065","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":"Response to S2-1908703 Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18460,"status":"not treated","reservation_date":"2019-10-01 07:44:05","uploaded":"2019-10-04 19:00:17","revisionof":"","revisedto":"S2-1911079","release":"","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_135_Split\/Docs\/S2-1909065.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909066","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":"Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18530,"status":"not treated","reservation_date":"2019-10-01 07:46:57","uploaded":"2019-10-04 19:00:17","revisionof":"","revisedto":"S2-1911093","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1728.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909066.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909067","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":"Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18500,"status":"not treated","reservation_date":"2019-10-01 07:49:20","uploaded":"2019-10-04 19:00:17","revisionof":"","revisedto":"S2-1911092","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1746.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909067.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909222","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":"Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18540,"status":"not treated","reservation_date":"2019-10-02 09:50:36","uploaded":"2019-10-04 11:56:56","revisionof":"","revisedto":"S2-1911647","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1775.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909222.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909223","title":"[DRAFT] Reply LS on Small Data Rate Control and APN Rate Control","source":"Huawei","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"This LS replies to S2-1908668","secretary_remarks":"Response to S2-1908668. Revised in parallel session to S2-1910494.","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":18190,"status":"revised","reservation_date":"2019-10-02 09:50:37","uploaded":"2019-10-04 11:56:56","revisionof":"","revisedto":"S2-1910494","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909223.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909224","title":"Corrections to Small Data Rate Control and Exception Reporting","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce the 'MO Exception data counter' reporting function.","secretary_remarks":"Revision of (unhandled) S2-1907718 from S2#134. Agreed in parallel session This was 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":18280,"status":"agreed","reservation_date":"2019-10-02 09:50:37","uploaded":"2019-10-04 11:56:56","revisionof":"S2-1907718","revisedto":"S2-1911504","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1645.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909224.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909225","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":"Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18760,"status":"not treated","reservation_date":"2019-10-02 09:50:38","uploaded":"2019-10-04 11:56:56","revisionof":"","revisedto":"S2-1911658","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1776.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909225.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909226","title":"System level impacts of CIoT MT-EDT","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"discussion","for":"Discussion","abstract":"This document discusses the system level impacts of CIoT MT-EDT.","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":17240,"status":"noted","reservation_date":"2019-10-02 09:50:39","uploaded":"2019-10-04 11:56:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909226.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909227","title":"[DRAFT] Reply LS on Mobile-terminated Early Data Transmission","source":"Huawei","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"This LS informs the relavant WGs of the decision taken by SA2 with respect to the support of CIoT MT-EDT","secretary_remarks":"Response to S2-1908681 and S2-1908659 Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":17530,"status":"not treated","reservation_date":"2019-10-02 09:50:39","uploaded":"2019-10-04 11:56:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3, CT WG1, SA WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909227.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909228","title":"Clarification to MICO mode and Periodic Registration Control","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In the timer control clause 5.31.7.5: Clarify that MICO mode and peridoic registration timer control are decided by the AMF at the same time according to Expected UE Behaviour. Clarify that a 'large periodic registration timer value' can be determined based on Network Configuration parameters. Remove the word 'just'. It is up to the AMF's implementation to decide how much earlier than the scheduled DL communication time. Add 'value' after the 'periodic registration timer' as it is the value not the timer that is included in the registration accept message. In the general MICO clause 5.4.1.3: Clarify that the AMF can get the Expected UE Behaviour parameters and Network Configuration parameters from the UDM.","secretary_remarks":"Revision of (unhandled) S2-1907724 from S2#134 Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18770,"status":"not treated","reservation_date":"2019-10-02 09:50:39","uploaded":"2019-10-04 11:56:56","revisionof":"S2-1907724","revisedto":"S2-1911646","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1668.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909228.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909248","title":"Correction to Availabilty after DDN failure event","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The procedures for buffering at the SMF and UPF are defined. In case of ETSUN or HR roaming case, the V-SMF and I-SMF is involved. During the subscription procedure, when the AMF received the UDM's subscription, it will responds with AMF notification point combination which will be provide to the SMF by UDM. Traffic descriptors are an optional input parameter for the Nudm_EventExposure_Subscribe service operation. AMF notification endpoint is an optional output parameter for Namf_EventExposure_Subscribe service operation.","secretary_remarks":"Merged into S2-1910488","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":17920,"status":"merged","reservation_date":"2019-10-02 11:53:48","uploaded":"2019-10-04 11:56:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1778.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909248.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909249","title":"Correction to DDD status event with SMF buffering procedure","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the figure to include the unsubscribe procedure. Clarify that the UDM will send the subscribe request to serving SMF with PDU Session established with DNN and S-NSSAI corresponding to the traffic descriptor. Specifiy how the DDD event is subscribed and reported to I-SMF or V-SMF. Some wording enhancement.","secretary_remarks":"Revised in parallel session to S2-1910489.","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":17930,"status":"revised","reservation_date":"2019-10-02 11:53:49","uploaded":"2019-10-04 11:56:56","revisionof":"","revisedto":"S2-1910489","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1779.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909249.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909250","title":"Corrections of call flows for DDD status event with UPF buffering","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":"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":17960,"status":"withdrawn","reservation_date":"2019-10-02 11:53:50","uploaded":"2019-10-04 11:56:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1780.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909250.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909251","title":"[DRAFT] Reply LS on Nsmf_EventExposure and Nnef_EventExposure service handling of the 'Downlink data delivery status' and ' Availability after DDN Failure' events","source":"Huawei","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"This LS replies to S2-1908645","secretary_remarks":"Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18000,"status":"not treated","reservation_date":"2019-10-02 11:53:51","uploaded":"2019-10-04 11:56:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909251.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909252","title":"Introduction of RRC Connection Re-Establishment for CP","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"discussion","for":"Discussion","abstract":"This document proposes a way forward for supporting RRC Connection Re-Establishment for NB-IoT connected to 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":17780,"status":"noted","reservation_date":"2019-10-02 11:53:51","uploaded":"2019-10-04 11:56:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909252.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909253","title":"Introduction of RRC Connection Re-Establishment for CP","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduced a new subclause describing the Control Plane Relocation Indication procedure.","secretary_remarks":"Revision of (unhandled) S2-1907720 from S2#134. Revised in parallel session to S2-1910486.","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":17790,"status":"revised","reservation_date":"2019-10-02 11:53:51","uploaded":"2019-10-04 11:56:56","revisionof":"S2-1907720","revisedto":"S2-1910486","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"},{"winame":"NB_IOTenh3-Core"}],"crnumber":1667.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909253.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909254","title":"[DRAFT] Reply LS on RRC Connection Reestablishment for CP for NB-IoT connected to 5GC","source":"Huawei","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"This LS replies to S2-1908707","secretary_remarks":"Response to S2-1908707. Revised in parallel session to S2-1910487.","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":17830,"status":"revised","reservation_date":"2019-10-02 11:53:52","uploaded":"2019-10-04 11:56:56","revisionof":"","revisedto":"S2-1910487","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, CT WG4, SA WG3","Cc":"CT WG1, RAN WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909254.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909255","title":"Corrections to Small Data Rate Control and Exception Reporting","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce the 'MO Exception data counter' reporting function.","secretary_remarks":"Revision of (postponed) S2-1908440 from S2#134. Revised in parallel session to S2-1910495.","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":18250,"status":"revised","reservation_date":"2019-10-02 11:53:52","uploaded":"2019-10-04 11:47:41","revisionof":"S2-1908440","revisedto":"S2-1910495","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1666.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909255.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909334","title":"Generalized MO EDT for UP 5GS Optimisation","source":"Ericsson, Sony, Verizon","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding a Connection Resume with MO EDT procedure. Updating the existing Connection Suspend and Connection Resume procedures (without EDT) with release assistance. Leaving an Editor's Note that it is FFS how early release is determined by NG-RAN.","secretary_remarks":"Merged into S2-1910633.","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":17720,"status":"merged","reservation_date":"2019-10-02 19:57:01","uploaded":"2019-10-04 18:25:14","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1787.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909334.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909335","title":"Expected UE Behaviour parameters forwarded to RAN for LTE-M UEs","source":"Ericsson, Sony","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The procedure is updated, a new Event Id is defined.","secretary_remarks":"Uploaded document contains S2-1909305. Revised to S2-1909936.","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":18720,"status":"revised","reservation_date":"2019-10-02 19:57:02","uploaded":"2019-10-04 14:04:06","revisionof":"","revisedto":"S2-1909936","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1788.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909335.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909336","title":"Evaluation of solutions for handling pending DL data","source":"Ericsson, Sony, Verizon","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"Evaluation of solutions for handling pending DL data","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":17660,"status":"noted","reservation_date":"2019-10-02 19:57:03","uploaded":"2019-10-04 18:25:14","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909336.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909337","title":"Pending data indication","source":"Ericsson, Sony, Verizon","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding Pending Data Indication towards RAN for HLCOM in clause 5.31.8. The text is copied and 5GS aligned from EPS TS 23.401 clause 4.3.17.7 last paragraph.","secretary_remarks":"Revised in parallel session to S2-1910634.","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":17680,"status":"revised","reservation_date":"2019-10-02 19:57:03","uploaded":"2019-10-04 18:25:15","revisionof":"","revisedto":"S2-1910634","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1792.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909337.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909338","title":"Pending data indication","source":"Ericsson, Sony, Verizon","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarified NGAP message to be used for the Pending data indication for Network Triggered Service Request. Clarified that the Pending data indication shall only be done once in a power saving cycle regardless if there are one or several MT events (MT data\/signaling\/SMS). This minimizes NGAP signaling.","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":17710,"status":"noted","reservation_date":"2019-10-02 19:57:04","uploaded":"2019-10-04 18:25:15","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1789.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909338.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909339","title":"Clarification of HLCOM Extended Buffering","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removing step 0 in 4.15.3.2.5. Some editorial clean up also done.","secretary_remarks":"Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18600,"status":"not treated","reservation_date":"2019-10-02 19:57:05","uploaded":"2019-10-04 18:25:15","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1790.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909339.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909340","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 (unhandled) S2-1907491 from S2#134 Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18680,"status":"not treated","reservation_date":"2019-10-02 19:57:05","uploaded":"2019-10-04 16:39:27","revisionof":"S2-1907491","revisedto":"S2-1911111","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1587.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909340.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909341","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 (revised and postponed) S2-1907495 from S2#134 Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18610,"status":"not treated","reservation_date":"2019-10-02 19:57:07","uploaded":"2019-10-04 18:25:15","revisionof":"S2-1907495","revisedto":"S2-1911108","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1590.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909341.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909342","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":"Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18570,"status":"not treated","reservation_date":"2019-10-02 19:57:08","uploaded":"2019-10-04 18:25:15","revisionof":"","revisedto":"S2-1911109","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1791.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909342.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909343","title":"MT EDT for UP EPS Optimization","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding Network Triggered Connection Resume with MT EDT, based on RAN WG2 answers. The MME determines to use MT-EDT based on the preconfigured Traffic Profile.","secretary_remarks":"Merged into S2-1910386","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":17470,"status":"merged","reservation_date":"2019-10-02 19:57:09","uploaded":"2019-10-04 18:25:15","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.401","crspecversion":"16.4.0","workitem":[{"winame":"TEI16"},{"winame":"5G_CIoT"}],"crnumber":3546.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909343.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909437","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":"Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18690,"status":"not treated","reservation_date":"2019-10-03 07:01:59","uploaded":"2019-10-04 12:59:28","revisionof":"","revisedto":"S2-1911507","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1817.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909437.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909438","title":"AMF and SMF merging subscription data 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":"Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18700,"status":"not treated","reservation_date":"2019-10-03 07:02:01","uploaded":"2019-10-04 12:59:28","revisionof":"","revisedto":"S2-1911508","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1807.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909438.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909442","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: AMF stores Small Data Rate Control status per DNN. During mobility from EPS, the source of this information can be APN Rate Control parameters stored by the MME. In that case, the Small Data Rate Control status is applied on DNN that is the same as the APN in the stored APN Rate Control. Small Data Rate Control does not apply per RAT type, but per DNN and S-NSSAI. The use of the term Small Data Rate Control status is aligned between TS 23.501 and TS 23.502.","secretary_remarks":"Revised in parallel session to S2-1910492.","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":18120,"status":"revised","reservation_date":"2019-10-03 07:02:02","uploaded":"2019-10-04 12:59:28","revisionof":"","revisedto":"S2-1910492","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1818.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909442.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909443","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: AMF stores Small Data Rate Control status per DNN. During mobility from EPS, the source of this information can be APN Rate Control parameters stored by the MME. In that case, the Small Data Rate Control status is applied on DNN that is the same as the APN in the stored APN Rate Control. Small Data Rate Control does not apply per RAT type, but per DNN and S-NSSAI. The use of the term Small Data Rate Control status is aligned between TS 23.501 and TS 23.502.","secretary_remarks":"Revised in parallel session to S2-1910493.","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":18150,"status":"revised","reservation_date":"2019-10-03 07:02:03","uploaded":"2019-10-04 12:59:28","revisionof":"","revisedto":"S2-1910493","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1808.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909443.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909444","title":"[DRAFT] Reply LS on Small Data Rate Control and APN Rate Control","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC: CT WG1. Attachments: TS 23.501 CR 1818 and TS 23.502 CR 1808.","secretary_remarks":"Response to S2-1908668. 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":18230,"status":"noted","reservation_date":"2019-10-03 07:02:04","uploaded":"2019-10-04 12:59:28","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909444.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909446","title":"Correction to Group NIDD","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":"Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18550,"status":"not treated","reservation_date":"2019-10-03 07:02:04","uploaded":"2019-10-04 12:59:28","revisionof":"","revisedto":"S2-1911509","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1809.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909446.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909447","title":"Monitoring event trigger","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. Downlink Data delivery status monitoring does not notify on every packet, but only on the first packet that is buffered, transmitted or dropped.","secretary_remarks":"Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18640,"status":"not treated","reservation_date":"2019-10-03 07:02:05","uploaded":"2019-10-04 12:59:28","revisionof":"","revisedto":"S2-1911510","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1810.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909447.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909448","title":"Discussion on connection Re-establishment procedure","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"discussion","for":"Decision","abstract":"Comparison of available alternatives for control plane Connection Re-establishment over NB-IoT","secretary_remarks":"Revised to S2-1910415.","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":17860,"status":"revised","reservation_date":"2019-10-03 07:02:06","uploaded":"2019-10-04 12:59:28","revisionof":"","revisedto":"S2-1910415","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909448.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909450","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 (unhandled) S2-1907368 from S2#134 Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18660,"status":"not treated","reservation_date":"2019-10-03 07:02:07","uploaded":"2019-10-04 12:59:28","revisionof":"S2-1907368","revisedto":"S2-1911511","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1555.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909450.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909575","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 (unhandled) S2-1907449 from S2#134 Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18670,"status":"not treated","reservation_date":"2019-10-03 19:59:24","uploaded":"2019-10-04 14:39:40","revisionof":"S2-1907449","revisedto":"S2-1911095","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1594.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909575.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909629","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":"Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18490,"status":"not treated","reservation_date":"2019-10-04 01:10:17","uploaded":"2019-10-04 14:40:38","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1864.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909629.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909694","title":"Support Fallback from MT-EDT","source":"Samsung","contact":"Sunghoon Kim","contact-id":59112,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: For MT-EDT, in DDN, Serving GW provides DL data size to the MME, if it is less than or equal to the configured value. In Paging procedure, MME provides DL data size to eNodeB. In S1AP Initial UE msg, eNodeB indicates MT-EDT is enabled to the MME In S1AP Downlink msg, MME indicates that MT-EDT needs to be disabled due to other DL data, SMS, or signaling in order to fallback to normal mode Serving GW is able to send second DDN for the UE which the first DDN has been sent with DL data size.","secretary_remarks":"Check and correct TS base version used. Merged into S2-1910386","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":17480,"status":"merged","reservation_date":"2019-10-04 07:23:23","uploaded":"2019-10-04 07:51:21","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.401","crspecversion":"16.4.0","workitem":[{"winame":"TEI16"},{"winame":"CIoT"}],"crnumber":3551.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909694.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909740","title":"MT-EDT procedure based on message 4 solution","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"discussion","for":"Discussion","abstract":"Discusses the MT-Early Data Transmission 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":17260,"status":"noted","reservation_date":"2019-10-04 07:40:36","uploaded":"2019-10-04 15:21:29","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"TEI16"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909740.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909741","title":"MT-EDT introduction","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - add the MT-EDT for CP optimization. - add the MT-EDT procedure for UP optimization.","secretary_remarks":"Merged into S2-1910386","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":17390,"status":"merged","reservation_date":"2019-10-04 07:44:18","uploaded":"2019-10-04 15:21:29","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.401","crspecversion":"16.4.0","workitem":[{"winame":"TEI16"}],"crnumber":3554.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909741.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909742","title":"MT-EDT introduction","source":"Qualcomm Incorporated","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":"This was revised, merging S2-1908902, in S2-1910387.","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":17400,"status":"revised","reservation_date":"2019-10-04 07:49:55","uploaded":"2019-10-04 15:21:29","revisionof":"","revisedto":"S2-1910387","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1894.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909742.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909743","title":"MT-EDT introduction","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - add MT-EDT procedure for UP optimization. - add MT-EDT procedure for CP optimization.","secretary_remarks":"This was revised, merging S2-1909954, in S2-1910388.","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":17430,"status":"revised","reservation_date":"2019-10-04 07:52:52","uploaded":"2019-10-04 15:21:29","revisionof":"","revisedto":"S2-1910388","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1848.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909743.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909788","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":"Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18710,"status":"not treated","reservation_date":"2019-10-04 11:43:37","uploaded":"2019-10-04 16:06:35","revisionof":"","revisedto":"S2-1911352","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1899.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909788.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909801","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 (unhandled) S2-1907062 from S2#134. Revised in parallel session to S2-1910497.","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":18320,"status":"revised","reservation_date":"2019-10-04 12:29:54","uploaded":"2019-10-04 18:25:15","revisionof":"S2-1907062","revisedto":"S2-1910497","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1485.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909801.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909802","title":"Serving PLMN rate control parameters in modification procedure","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: PDU Session Modification procedure is added as a procedure in which the network can provide the UE with Serving PLMN Rate Control parameters.","secretary_remarks":"Revision of (unhandled) S2-1907063 from S2#134. Agreed in parallel session This was 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":18240,"status":"agreed","reservation_date":"2019-10-04 12:29:55","uploaded":"2019-10-04 18:25:15","revisionof":"S2-1907063","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1486.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_135_Split\/Docs\/S2-1909802.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909803","title":"[DRAFT] Reply LS on Nsmf_EventExposure and Nnef_EventExposure service handling of the 'Downlink data delivery status' and 'Availability after DDN Failure' events","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Postponed Nokia draft with Ericsson comments","secretary_remarks":"Response to S2-1908645 Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18010,"status":"not treated","reservation_date":"2019-10-04 12:29:56","uploaded":"2019-10-04 18:25:15","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909803.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909849","title":"Discussion on security context handling in fast RRC release","source":"LG Electronics","contact":"Seokjung Kim","contact-id":70180,"tdoctype":"discussion","for":"Discussion","abstract":"This paper discusses how to maintain security context synchronization between the UE and NG-RAN in fast RRC release case.","secretary_remarks":"Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18790,"status":"not treated","reservation_date":"2019-10-04 15:48:47","uploaded":"2019-10-04 16:10:57","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909849.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909865","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 (noted) S2-1908399 from S2#134. Check and correct TS base version used. Revised in parallel session, merging S2-1909248, to S2-1910488.","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":17970,"status":"revised","reservation_date":"2019-10-04 16:36:34","uploaded":"2019-10-04 18:57:11","revisionof":"S2-1908399","revisedto":"S2-1910488","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1482.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909865.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909876","title":"Support for MT-EDT in Mobile Terminating Data Transport Procedure","source":"Intel","contact":"Meghashree D Kedalagudde","contact-id":49483,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: New parameter defined in MT Data Transport Procedure to support MT-EDT. SGi Tunnel parameter updated to include MT-EDT indication.","secretary_remarks":"Revision of (unhandled) S2-1907561 from S2#134. Merged into S2-1909953.","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":17270,"status":"merged","reservation_date":"2019-10-04 17:13:58","uploaded":"2019-10-04 23:00:18","revisionof":"S2-1907561","revisedto":"","release":"Rel-16","crspec":"23.401","crspecversion":"16.4.0","workitem":[{"winame":"TEI16"},{"winame":"LTE_eMTC5"},{"winame":"NB_IOTenh3"}],"crnumber":3535.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909876.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909878","title":"Support for MT-EDT in Mobile Terminating Data Transport Procedure in 5GC","source":"Intel","contact":"Meghashree D Kedalagudde","contact-id":49483,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In the Registration procedure, MT-EDT support in UE in included as UE capability. New parameters defined in MT Data Transport Procedure for Control Plane CIoT 5GS Optimsation to support MT-EDT.","secretary_remarks":"Revision of (unhandled) S2-1907577 from S2#134. Merged into S2-1909954.","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":17350,"status":"merged","reservation_date":"2019-10-04 17:17:07","uploaded":"2019-10-04 23:00:18","revisionof":"S2-1907577","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"TEI16"},{"winame":"LTE_eMTC5"},{"winame":"NB_IOTenh3"}],"crnumber":1612.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909878.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909879","title":"Support for MT-EDT in MT NIDD Procedure","source":"Intel","contact":"Meghashree D Kedalagudde","contact-id":49483,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: New parameters defined in MT NIDD Procedure to support MT-EDT.","secretary_remarks":"Revision of (unhandled) S2-1907575 from S2#134. 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":17380,"status":"noted","reservation_date":"2019-10-04 17:19:55","uploaded":"2019-10-04 23:00:18","revisionof":"S2-1907575","revisedto":"","release":"Rel-16","crspec":"23.682","crspecversion":"16.4.0","workitem":[{"winame":"TEI16"},{"winame":"LTE_eMTC5"},{"winame":"NB_IOTenh3"}],"crnumber":460.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909879.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909894","title":"[DRAFT] Reply LS on Nsmf_EventExposure and Nnef_EventExposure service handling of the 'Downlink data delivery status' and 'Availability after DDN Failure' events.","source":"Nokia, Nokia Shanghai-Bell","contact":"Thomas Belling","contact-id":68266,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC: CT WG4","secretary_remarks":"Response to S2-1908645. Revised in parallel session to S2-1910490.","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":18020,"status":"revised","reservation_date":"2019-10-04 18:11:40","uploaded":"2019-10-04 18:57:11","revisionof":"","revisedto":"S2-1910490","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909894.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909904","title":"Handling of LTE-M and 5G CIoT features for WB-E-UTRA and NR capable UEs","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"discussion","for":"Approval","abstract":"Addresses potential issues of how to handle CIoT supporting UEs that also support NR.","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":18050,"status":"noted","reservation_date":"2019-10-04 18:43:24","uploaded":"2019-10-04 21:35:09","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909904.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909905","title":"[DRAFT] LS on category M devices and NR","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"LS out","for":"Approval","abstract":"Requests RAN WG2 to confirm asumptions in SA WG2 on category M indication and NR support indication from the UE are correct.","secretary_remarks":"Revised in parallel session to S2-1910392.","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":17620,"status":"revised","reservation_date":"2019-10-04 18:43:24","uploaded":"2019-10-04 21:35:09","revisionof":"","revisedto":"S2-1910392","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_135_Split\/Docs\/S2-1909905.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909906","title":"Control Plane CIoT 5GS optimisation for UEs supporting WB-E-UTRAN and NR","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - The UE negotiates PNB\/SNB when accessing 5GC either via WB-E-UTRA or NR. - The UE does not use CP optimization when camping on NR, and instead initiates service request procedure to establish user plane resources. - If a UE has established a PDU session for Control Plane only, the UE disables NR.","secretary_remarks":"Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18100,"status":"not treated","reservation_date":"2019-10-04 18:43:24","uploaded":"2019-10-04 21:35:09","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1915.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909906.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909907","title":"Handling of EDT with UP optimization","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"discussion","for":"Approval","abstract":"Addresses the remaining open issue of how to handle EDT with UP optimization","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":17670,"status":"noted","reservation_date":"2019-10-04 18:43:25","uploaded":"2019-10-04 21:35:09","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909907.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909908","title":"Introduce MO EDT for User Plane CIoT 5GS Optimisation","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding Connection Resume with Early Data Transmission","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":17730,"status":"noted","reservation_date":"2019-10-04 18:43:25","uploaded":"2019-10-04 21:35:09","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1866.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909908.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909909","title":"MO EDT for User Plane CIoT 5GS Optimisation - Potential Compromise","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding Connection Resume with Early Data Transmission Compromise Option","secretary_remarks":"Revised in parallel session, merging S2-1909334, to S2-1910633.","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":17740,"status":"revised","reservation_date":"2019-10-04 18:43:26","uploaded":"2019-10-04 21:35:09","revisionof":"","revisedto":"S2-1910633","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1867.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909909.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909910","title":"Enforcing maximum UP resources activation of 2 PDU sessions for NB-IoT","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"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.","secretary_remarks":"Revised in parallel session to S2-1910498.","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":18370,"status":"revised","reservation_date":"2019-10-04 18:43:27","uploaded":"2019-10-04 21:35:09","revisionof":"","revisedto":"S2-1910498","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1868.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909910.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909911","title":"[DRAFT] Reply LS on support for flow based QoS for NB-IoT connected to 5GC","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"LS out","for":"Approval","abstract":"Provides CT groups with feedback on SA WG2 agreement for enforcement of 2 active UP rsources for PDU sessions for NB-IoT","secretary_remarks":"Response to S2-1908663. Revised in parallel session, merging S2-1908932, to S2-1910499.","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":18400,"status":"revised","reservation_date":"2019-10-04 18:43:28","uploaded":"2019-10-04 21:35:09","revisionof":"","revisedto":"S2-1910499","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, CT WG4","Cc":"RAN WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909911.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909912","title":"Discussion on System aspects of Connection Reestablishment for Control Plane for NB-IoT","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"discussion","for":"Approval","abstract":"Proposes a way forward for the system architecture related aspects of incoming LS from RAN WG2 R2-1908264","secretary_remarks":"Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":17880,"status":"not treated","reservation_date":"2019-10-04 18:43:28","uploaded":"2019-10-04 21:35:09","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909912.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909913","title":"Handling RRC connection reestablishment for Control Plane for NB-IoT connected to 5GC","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce truncated 5G-S-TMSI defintion for use in RRC reestablihment procedure in NB-IoT. Introduce reference to ng-eNB CP Relocation Indication 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":17890,"status":"noted","reservation_date":"2019-10-04 18:43:28","uploaded":"2019-10-04 21:35:09","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1916.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909913.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909914","title":"[DRAFT] Reply LS on RRC Connection Re-Establishment for CP for NB-IoT connected to 5GC","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"LS out","for":"Approval","abstract":"Provides SA WG2 solution for connection reestabishment for CP in NB-IoT","secretary_remarks":"Response to S2-1906867 (also replied to at S2#134) Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":17900,"status":"not treated","reservation_date":"2019-10-04 18:43:29","uploaded":"2019-10-04 21:35:09","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3, CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909914.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909936","title":"Expected UE Behaviour parameters forwarded to RAN for LTE-M UEs","source":"Ericsson, Sony","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The procedure is updated, a new Event Id is defined.","secretary_remarks":"Revision of S2-1909335 to include the correct CR. LATE DOC: Rx 08\/10, 14:00 Not Handled","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18730,"status":"not treated","reservation_date":"2019-10-08 12:08:47","uploaded":"2019-10-08 12:10:48","revisionof":"S2-1909335","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1788.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909936.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909953","title":"Introduction of MT-EDT","source":"OPPO, Intel","contact":"Jianhua Liu","contact-id":72698,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR introduces the MT-EDT.","secretary_remarks":"Revision of S2-1908904, merging S2-1909876. Revised in parallel session, merging S2-1909343, S2-1909694 and S2-1909741, to S2-1910386.","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":17290,"status":"revised","reservation_date":"2019-10-11 06:24:29","uploaded":"2019-10-11 07:46:51","revisionof":"S2-1908904","revisedto":"S2-1910386","release":"Rel-16","crspec":"23.401","crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":3542.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909953.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909954","title":"Introduction of MT-EDT","source":"OPPO, Intel","contact":"Jianhua Liu","contact-id":72698,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce the method for MT-EDT.","secretary_remarks":"Revision of S2-1908903, merging S2-1909878. Merged into S2-1910388","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":17370,"status":"merged","reservation_date":"2019-10-11 06:24:35","uploaded":"2019-10-11 07:46:51","revisionof":"S2-1908903","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1695.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909954.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909963","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":"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":17230,"status":"postponed","reservation_date":"2019-10-11 13:25:15","uploaded":"2019-10-11 13:25:45","revisionof":"","revisedto":"S2-1910873","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_135_Split\/Docs\/S2-1909963.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909983","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","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":17540,"status":"postponed","reservation_date":"2019-10-15 06:40:06","uploaded":"2019-10-19 07:48:01","revisionof":"","revisedto":"S2-1910880","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"C3-194445","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909983.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910386","title":"Introduction of MT-EDT","source":"OPPO, Intel, Ericsson, Sumsung, Qualcomm? NEC?","contact":"Jianhua Liu","contact-id":72698,"tdoctype":"CR","for":"Endorsement","abstract":"Summary of change: This CR introduces the MT-EDT.","secretary_remarks":"Revision of S2-1909953, merging S2-1909343, S2-1909694 and S2-1909741. Revised in parallel session to S2-1910628.","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":17300,"status":"revised","reservation_date":"2019-10-15 06:41:29","uploaded":"2019-10-19 07:48:02","revisionof":"S2-1909953","revisedto":"S2-1910628","release":"Rel-16","crspec":"23.401","crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":3542.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910386.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910387","title":"MT-EDT introduction","source":"Qualcomm Incorporated, OPPO\u00a0?, NEC\u00a0?","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Endorsement","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-1909742, merging S2-1908902. Revised in parallel session to S2-1910629.","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":17410,"status":"revised","reservation_date":"2019-10-15 06:41:32","uploaded":"2019-10-19 07:48:02","revisionof":"S2-1909742","revisedto":"S2-1910629","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1894.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910387.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910388","title":"MT-EDT introduction","source":"Qualcomm Incorporated, OPPO\u00a0?, Intel\u00a0?, Ericsson\u00a0?, Samsung, NEC\u00a0?","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Endorsement","abstract":"Summary of change: - add MT-EDT procedure for UP optimization. - add MT-EDT procedure for CP optimization.","secretary_remarks":"Revision of S2-1909743, merging S2-1909954. Revised in parallel session to S2-1910630.","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":17440,"status":"revised","reservation_date":"2019-10-15 06:41:33","uploaded":"2019-10-19 07:48:02","revisionof":"S2-1909743","revisedto":"S2-1910630","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1848.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910388.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910389","title":"[DRAFT] Reply LS on Mobile-terminated Early Data Transmission","source":"SA WG2","contact":"Jianhua Liu","contact-id":72698,"tdoctype":"LS out","for":"Approval","abstract":"Relpy LS on MT-EDT on UE capability issue and relationship with MO-EDT.","secretary_remarks":"Revision of S2-1908905. Revised in parallel session to S2-1910631.","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":17500,"status":"revised","reservation_date":"2019-10-15 06:41:35","uploaded":"2019-10-19 07:48:02","revisionof":"S2-1908905","revisedto":"S2-1910631","release":"","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_135_Split\/Docs\/S2-1910389.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910390","title":"Identification of LTE-M (eMTC) traffic","source":"ORANGE, Ericsson, Qualcomm","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. - The eNB provides a 'Category M Indication' to the AMF in the Initial UE Message. - 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, when 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-1908741. Revised in parallel session to S2-1910632.","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":17580,"status":"revised","reservation_date":"2019-10-15 06:41:35","uploaded":"2019-10-19 07:48:02","revisionof":"S2-1908741","revisedto":"S2-1910632","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1363.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910390.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910391","title":"Identification of LTE-M (eMTC) traffic","source":"ORANGE, Ericsson","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) Relevant clauses of the specification updated according to the principles from 23.501 CR#1363. Clarification that the signaling of RAT Type is also for charging differentiation. 2) Alignment with stage 3 specifications for RAT Type information spreading during PDU Session Establishment 3) Some typos fixed.","secretary_remarks":"Revision of S2-1908742. Agreed in parallel session This was 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":17610,"status":"agreed","reservation_date":"2019-10-15 06:41:37","uploaded":"2019-10-19 07:48:02","revisionof":"S2-1908742","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1372.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"SP-191069","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910391.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910392","title":"[DRAFT] LS on category M devices and NR","source":"SA WG2","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"LS out","for":"Approval","abstract":"Requests RAN WG2 to confirm asumptions in SA WG2 on category M indication and NR support indication from the UE are correct.","secretary_remarks":"Revision of S2-1909905. This was left for e-mail approval. Noted","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":17630,"status":"noted","reservation_date":"2019-10-15 06:41:38","uploaded":"2019-10-19 07:48:02","revisionof":"S2-1909905","revisedto":"S2-1911345","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_135_Split\/Docs\/S2-1910392.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910393","title":"[DRAFT] Reply LS on LTM identification in 5GC.","source":"SA WG2","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2, RAN WG3","secretary_remarks":"Created at meeting. Response to S2-1908693 and S2-1908680. Revised in parallel session to S2-1910644.","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":17640,"status":"revised","reservation_date":"2019-10-15 06:41:38","uploaded":"2019-10-19 07:48:02","revisionof":"","revisedto":"S2-1910644","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_135_Split\/Docs\/S2-1910393.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910415","title":"Discussion on connection Re-establishment procedure","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"discussion","for":"Decision","abstract":"Comparison of available alternatives for control plane Connection Re-establishment over NB-IoT","secretary_remarks":"Revision of S2-1909448. 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":17870,"status":"noted","reservation_date":"2019-10-15 06:41:43","uploaded":"2019-10-19 07:48:03","revisionof":"S2-1909448","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910415.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910486","title":"Introduction of RRC Connection Re-Establishment for CP","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduced a new subclause describing the Control Plane Relocation Indication procedure.","secretary_remarks":"Revision of S2-1909253. Revised in parallel session to S2-1910635.","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":17800,"status":"revised","reservation_date":"2019-10-19 05:41:13","uploaded":"2019-10-19 07:48:12","revisionof":"S2-1909253","revisedto":"S2-1910635","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"},{"winame":"NB_IOTenh3-Core"}],"crnumber":1667.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910486.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910487","title":"[DRAFT] Reply LS on RRC Connection Reestablishment for CP for NB-IoT connected to 5GC","source":"Huawei","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"This LS replies to S2-1908707","secretary_remarks":"Revision of S2-1909254. This was left for e-mail approval. e-mail agreed. Revised to remove 'draft' and revision marks in S2-1910789","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":17840,"status":"revised","reservation_date":"2019-10-19 05:41:14","uploaded":"2019-10-19 07:48:12","revisionof":"S2-1909254","revisedto":"S2-1910789","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, CT WG4, SA WG3","Cc":"CT WG1, RAN WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910487.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910488","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-1909865, merging S2-1909248. Revised in parallel session to S2-1910636.","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":17980,"status":"revised","reservation_date":"2019-10-19 05:41:14","uploaded":"2019-10-19 07:48:12","revisionof":"S2-1909865","revisedto":"S2-1910636","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1482.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910488.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910489","title":"Correction to DDD status event with SMF buffering procedure","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the figure to include the unsubscribe procedure. Clarify that the UDM will send the subscribe request to serving SMF with PDU Session established with DNN and S-NSSAI corresponding to the traffic descriptor. Specifiy how the DDD event is subscribed and reported to I-SMF or V-SMF. Some wording enhancement.","secretary_remarks":"Revision of S2-1909249. Revised in parallel session to S2-1910637.","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":17940,"status":"revised","reservation_date":"2019-10-19 05:41:16","uploaded":"2019-10-19 07:48:12","revisionof":"S2-1909249","revisedto":"S2-1910637","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1779.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910489.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910490","title":"[DRAFT] Reply LS on Nsmf_EventExposure and Nnef_EventExposure service handling of the 'Downlink data delivery status' and 'Availability after DDN Failure' events.","source":"SA WG2","contact":"Thomas Belling","contact-id":68266,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC: CT WG4","secretary_remarks":"Revision of S2-1909894. Revised in parallel session to S2-1910641.","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":18030,"status":"revised","reservation_date":"2019-10-19 05:41:17","uploaded":"2019-10-19 07:48:12","revisionof":"S2-1909894","revisedto":"S2-1910641","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910490.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910491","title":"Control Plane CIoT 5GS Optimisations restriction on NR","source":"ORANGE, Vodafone, AT&T, Nokia, Nokia Shanghai Bell","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When connected over any other 5G AN than E-UTRA, a UE which negotiated the use of the CP CIoT 5GS optimisation, may use the Control Plane CIoT 5GS Optimisation, but without using EDT or RAI (as those capabilities would require AN support).","secretary_remarks":"Revision of S2-1908746. This was left for e-mail approval. e-mail revision 2 (+cover sheet fixes) approved. Revised to S2-1910790.","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":18070,"status":"revised","reservation_date":"2019-10-19 05:41:17","uploaded":"2019-10-19 07:48:12","revisionof":"S2-1908746","revisedto":"S2-1910790","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1690.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910491.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910492","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: AMF stores Small Data Rate Control status per DNN. During mobility from EPS, the source of this information can be APN Rate Control parameters stored by the MME. In that case, the Small Data Rate Control status is applied on DNN that is the same as the APN in the stored APN Rate Control. Small Data Rate Control does not apply per RAT type, but per DNN and S-NSSAI. The use of the term Small Data Rate Control status is aligned between TS 23.501 and TS 23.502.","secretary_remarks":"Revision of S2-1909442. Revised in parallel session to S2-1910638.","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":18130,"status":"revised","reservation_date":"2019-10-19 05:41:18","uploaded":"2019-10-19 07:48:12","revisionof":"S2-1909442","revisedto":"S2-1910638","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1818.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910492.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910493","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: AMF stores Small Data Rate Control status per DNN. During mobility from EPS, the source of this information can be APN Rate Control parameters stored by the MME. In that case, the Small Data Rate Control status is applied on DNN that is the same as the APN in the stored APN Rate Control. Small Data Rate Control does not apply per RAT type, but per DNN and S-NSSAI. The use of the term Small Data Rate Control status is aligned between TS 23.501 and TS 23.502.","secretary_remarks":"Revision of S2-1909443. Revised to S2-1910767.","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":18160,"status":"revised","reservation_date":"2019-10-19 05:41:19","uploaded":"2019-10-19 07:48:12","revisionof":"S2-1909443","revisedto":"S2-1910767","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1808.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910493.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910494","title":"[DRAFT] Reply LS on Small Data Rate Control and APN Rate Control","source":"SA WG2","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"This LS replies to S2-1908668","secretary_remarks":"Revision of S2-1909223. Revised in parallel session to S2-1910642.","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":18200,"status":"revised","reservation_date":"2019-10-19 05:41:21","uploaded":"2019-10-19 07:48:12","revisionof":"S2-1909223","revisedto":"S2-1910642","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910494.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910495","title":"Corrections to Small Data Rate Control and Exception Reporting","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce the 'MO Exception data counter' reporting function.","secretary_remarks":"Revision of S2-1909255. Revised in parallel session to S2-1910639.","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":18260,"status":"revised","reservation_date":"2019-10-19 05:41:21","uploaded":"2019-10-19 07:48:12","revisionof":"S2-1909255","revisedto":"S2-1910639","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1666.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910495.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910496","title":"Extended NAS timers for CE mode B","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If UE supports CE mode B and use of CE mode B is not restricted for the UE then AMF shall use extended NAS-MM timers and shall indicate to SMF to use extended NAS-SM timers in PDU session establishment, Subscriber Data Update Notification to AMF (if use of CE mode B changes from restricted to unrestricted or vice versa) and during EPS to 5GS mobility. Update Nsmf_PDUSession_Create service operation and Nsmf_PDUSession_Update service operation to support extended NAS-SM timer indication.","secretary_remarks":"Revision of S2-1909063. Agreed in parallel session This was 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":18310,"status":"agreed","reservation_date":"2019-10-19 05:41:22","uploaded":"2019-10-19 07:48:13","revisionof":"S2-1909063","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1727.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_135_Split\/Docs\/S2-1910496.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910497","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-1909801. Revised in parallel session to S2-1910640.","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":18330,"status":"revised","reservation_date":"2019-10-19 05:41:24","uploaded":"2019-10-19 07:48:13","revisionof":"S2-1909801","revisedto":"S2-1910640","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1485.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910497.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910498","title":"Enforcing maximum UP resources activation of 2 PDU sessions for NB-IoT","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"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.","secretary_remarks":"Revision of S2-1909910. Agreed in parallel session This was 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":18380,"status":"agreed","reservation_date":"2019-10-19 05:41:25","uploaded":"2019-10-19 07:48:13","revisionof":"S2-1909910","revisedto":"S2-1911110","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1868.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910498.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910499","title":"[DRAFT] Reply LS on support for flow based QoS for NB-IoT connected to 5GC","source":"SA WG2","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"LS out","for":"Approval","abstract":"Provides CT groups with feedback on SA WG2 agreement for enforcement of 2 active UP rsources for PDU sessions for NB-IoT","secretary_remarks":"Revision of S2-1909911, merging S2-1908932. Revised in parallel session to S2-1910643.","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":18410,"status":"revised","reservation_date":"2019-10-19 05:41:27","uploaded":"2019-10-19 07:48:13","revisionof":"S2-1909911","revisedto":"S2-1910643","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, CT WG4","Cc":"RAN WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910499.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910628","title":"Introduction of MT-EDT","source":"OPPO, Intel, Ericsson, Sumsung, Qualcomm, NEC","contact":"Jianhua Liu","contact-id":72698,"tdoctype":"CR","for":"Endorsement","abstract":"Summary of change: This CR introduces the MT-EDT.","secretary_remarks":"Revision of S2-1910386. Revised to S2-1910762.","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":17310,"status":"revised","reservation_date":"2019-10-19 05:42:48","uploaded":"2019-10-19 07:48:13","revisionof":"S2-1910386","revisedto":"S2-1910762","release":"Rel-16","crspec":"23.401","crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":3542.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910628.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910629","title":"MT-EDT introduction","source":"Qualcomm Incorporated, OPPO, Intel, NEC","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Endorsement","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-1910387. This was Technically Endorsed in parallel session. Block Endorsed","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":17420,"status":"endorsed","reservation_date":"2019-10-19 05:42:49","uploaded":"2019-10-19 07:48:13","revisionof":"S2-1910387","revisedto":"S2-1911723","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1894.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910629.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910630","title":"MT-EDT introduction","source":"Qualcomm Incorporated, OPPO, Intel, Ericsson, Samsung, NEC","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Endorsement","abstract":"Summary of change: - add MT-EDT procedure for UP optimization. - add MT-EDT procedure for CP optimization.","secretary_remarks":"Revision of S2-1910388. Revised to S2-1910763.","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":17450,"status":"revised","reservation_date":"2019-10-19 05:42:51","uploaded":"2019-10-19 07:48:13","revisionof":"S2-1910388","revisedto":"S2-1910763","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1848.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910630.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910631","title":"[DRAFT] Reply LS on Mobile-terminated Early Data Transmission","source":"SA WG2","contact":"Jianhua Liu","contact-id":72698,"tdoctype":"LS out","for":"Approval","abstract":"Relpy LS on MT-EDT on UE capability issue and relationship with MO-EDT.","secretary_remarks":"Revision of S2-1910389. This was left for e-mail approval. e-mail revision 6 approved. Revised to S2-1910804.","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":17510,"status":"revised","reservation_date":"2019-10-19 05:42:52","uploaded":"2019-10-19 07:48:13","revisionof":"S2-1910389","revisedto":"S2-1910804","release":"","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_135_Split\/Docs\/S2-1910631.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910632","title":"Identification of LTE-M (eMTC) traffic","source":"ORANGE, Ericsson, Qualcomm","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. - The eNB provides a 'Category M Indication' to the AMF in the Initial UE Message. - 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, when 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-1910390. Agreed in parallel session This was Block approved. Revised at S2#136 in S2-1911822 (but not handled)","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":17590,"status":"agreed","reservation_date":"2019-10-19 05:42:52","uploaded":"2019-10-19 07:48:13","revisionof":"S2-1910390","revisedto":"S2-1911822","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1363.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"SP-191068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910632.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910633","title":"MO EDT for User Plane CIoT 5GS Optimisation - Potential Compromise","source":"Qualcomm Incorporated, Sony, Samsung","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding Connection Resume with Early Data Transmission Compromise Option","secretary_remarks":"Revision of S2-1909909, merging S2-909334. Revised to S2-1910765.","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":17750,"status":"revised","reservation_date":"2019-10-19 05:42:53","uploaded":"2019-10-19 07:48:13","revisionof":"S2-1909909","revisedto":"S2-1910765","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1867.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910633.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910634","title":"Pending data indication","source":"Ericsson, Sony, Verizon","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding Pending Data Indication towards RAN for HLCOM in clause 5.31.8. The text is copied and 5GS aligned from EPS TS 23.401 clause 4.3.17.7 last paragraph.","secretary_remarks":"Revision of S2-1909337. Revised to S2-1910764.","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":17690,"status":"revised","reservation_date":"2019-10-19 05:42:55","uploaded":"2019-10-19 07:48:13","revisionof":"S2-1909337","revisedto":"S2-1910764","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1792.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910634.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910635","title":"Introduction of RRC Connection Re-Establishment for CP","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduced a new subclause describing the Control Plane Relocation Indication procedure.","secretary_remarks":"Revision of S2-1910486. Revised to S2-1910766.","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":17810,"status":"revised","reservation_date":"2019-10-19 05:42:56","uploaded":"2019-10-19 07:48:13","revisionof":"S2-1910486","revisedto":"S2-1910766","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"},{"winame":"NB_IOTenh3-Core"}],"crnumber":1667.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910635.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910636","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-1910488. Agreed in parallel session This was 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":17990,"status":"agreed","reservation_date":"2019-10-19 05:42:57","uploaded":"2019-10-19 07:48:13","revisionof":"S2-1910488","revisedto":"S2-1911308, S2-1911883","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1482.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910636.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910637","title":"Correction to DDD status event with SMF buffering","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the figure to include the unsubscribe procedure. Clarify that the UDM will send the subscribe request to serving SMF with PDU Session established with DNN and S-NSSAI corresponding to the traffic descriptor. Specifiy how the DDD event is subscribed and reported to I-SMF or V-SMF. Some wording enhancement.","secretary_remarks":"Revision of S2-1910489. Agreed in parallel session This was 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":17950,"status":"agreed","reservation_date":"2019-10-19 05:42:59","uploaded":"2019-10-19 07:48:13","revisionof":"S2-1910489","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1779.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_135_Split\/Docs\/S2-1910637.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910638","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: AMF stores Small Data Rate Control status per DNN. During mobility from EPS, the source of this information can be APN Rate Control parameters stored by the MME. In that case, the Small Data Rate Control status is applied on DNN that is the same as the APN in the stored APN Rate Control. Small Data Rate Control does not apply per RAT type, but per DNN and S-NSSAI. The use of the term Small Data Rate Control status is aligned between TS 23.501 and TS 23.502.","secretary_remarks":"Revision of S2-1910492. 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":18140,"status":"agreed","reservation_date":"2019-10-19 05:43:00","uploaded":"2019-10-19 07:48:13","revisionof":"S2-1910492","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1818.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_135_Split\/Docs\/S2-1910638.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910639","title":"Corrections to Small Data Rate Control and Exception Reporting","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce the 'MO Exception data counter' reporting function.","secretary_remarks":"Revision of S2-1910495. Agreed in parallel session This was 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":18270,"status":"agreed","reservation_date":"2019-10-19 05:43:01","uploaded":"2019-10-19 07:48:13","revisionof":"S2-1910495","revisedto":"S2-1911503","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1666.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910639.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910640","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-1910497. Agreed in parallel session This was Block approved. Revised at S2#136 in S2-1911057 (but not handled)","agenda_item_sort_order":28,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT","tdoc_agenda_sort_order":18340,"status":"agreed","reservation_date":"2019-10-19 05:43:03","uploaded":"2019-10-19 07:48:13","revisionof":"S2-1910497","revisedto":"S2-1911057","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1485.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_135_Split\/Docs\/S2-1910640.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910641","title":"Reply LS on Nsmf_EventExposure and Nnef_EventExposure service handling of the 'Downlink data delivery status' and 'Availability after DDN Failure' events.","source":"SA WG2","contact":"Thomas Belling","contact-id":68266,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC: CT WG4. Attachments: S2-1910636, S2-1910637","secretary_remarks":"Revision of S2-1910490. This was left for e-mail approval. 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":18040,"status":"approved","reservation_date":"2019-10-19 05:43:04","uploaded":"2019-10-19 07:48:13","revisionof":"S2-1910490","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1908645","lsto":"CT WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910641.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910642","title":"[DRAFT] Reply LS on Small Data Rate Control and APN Rate Control","source":"SA WG2","contact":"Steven Wenham","contact-id":48132,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC: CT WG1. Attachments: TS 23.501 CR181 and TS 23.502 CR1808","secretary_remarks":"Revision of S2-1910494. This was left for e-mail approval. Agreed. Revised to remove 'draft' in S2-1910805.","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":18210,"status":"revised","reservation_date":"2019-10-19 05:43:05","uploaded":"2019-10-19 07:48:13","revisionof":"S2-1910494","revisedto":"S2-1910805","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910642.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910643","title":"Reply LS on support for flow based QoS for NB-IoT connected to 5GC","source":"SA WG2","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1, CT WG4. CC: RAN WG3. Attachments: S2-1910498 (TS 23.502 CR#1868)","secretary_remarks":"Revision of S2-1910499. Agreed in parallel session This was 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":18420,"status":"approved","reservation_date":"2019-10-19 05:43:05","uploaded":"2019-10-19 07:48:13","revisionof":"S2-1910499","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1908663","lsto":"CT WG1, CT WG4","Cc":"RAN WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910643.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910644","title":"Reply LS on LTE-M identification in 5GC","source":"SA WG2","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2, RAN WG3. CC: TSG RAN. Attachments: S2-1910632 (23.501 CR1373), S2-1910391 (23.502 CR1372)","secretary_remarks":"Revision of S2-1910393. Agreed in parallel session This was 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":17650,"status":"approved","reservation_date":"2019-10-19 05:43:05","uploaded":"2019-10-19 07:48:13","revisionof":"S2-1910393","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1908693","lsto":"RAN WG2, RAN WG3","Cc":"TSG RAN","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910644.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910762","title":"Introduction of MT-EDT","source":"OPPO, Intel, Ericsson, Sumsung, Qualcomm, NEC, Orange","contact":"Jianhua Liu","contact-id":72698,"tdoctype":"CR","for":"Endorsement","abstract":"Summary of change: This CR introduces the MT-EDT.","secretary_remarks":"Revision of S2-1910628. This was left for e-mail approval. e-mail revision 4 technically endorsed. Revised to S2-1910801.","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":17320,"status":"revised","reservation_date":"2019-10-19 05:44:13","uploaded":"2019-10-21 08:38:03","revisionof":"S2-1910628","revisedto":"S2-1910801","release":"Rel-16","crspec":"23.401","crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":3542.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910762.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910763","title":"MT-EDT introduction","source":"Qualcomm Incorporated, OPPO, Intel, Ericsson, Samsung, NEC","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Endorsement","abstract":"Summary of change: - add MT-EDT procedure for UP optimization. - add MT-EDT procedure for CP optimization.","secretary_remarks":"Revision of S2-1910630. This was left for e-mail approval. Technically Endorsed","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":17460,"status":"endorsed","reservation_date":"2019-10-19 05:44:14","uploaded":"2019-10-21 08:38:03","revisionof":"S2-1910630","revisedto":"S2-1911724","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1848.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910763.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910764","title":"EDT support for UP CIoT Optimisation","source":"Ericsson, Sony, Verizon","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding Pending Data Indication towards RAN for HLCOM in clause 5.31.8. The text is copied and 5GS aligned from EPS TS 23.401 clause 4.3.17.7 last paragraph.","secretary_remarks":"Revision of S2-1910634. 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":17700,"status":"agreed","reservation_date":"2019-10-19 05:44:17","uploaded":"2019-10-19 07:48:17","revisionof":"S2-1910634","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1792.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_135_Split\/Docs\/S2-1910764.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910765","title":"MO EDT for User Plane CIoT 5GS Optimisation","source":"Qualcomm Incorporated, Sony, Samsung","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding Connection Resume with Early Data Transmission Compromise Option","secretary_remarks":"Revision of S2-1910633. This CR was agreed with an objection from Ericsson","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":17760,"status":"agreed","reservation_date":"2019-10-19 05:44:18","uploaded":"2019-10-19 07:48:18","revisionof":"S2-1910633","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1867.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-191059","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910765.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910766","title":"Introduction of RRC Connection Re-Establishment for CP","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduced a new subclause describing the Control Plane Relocation Indication procedure.","secretary_remarks":"Revision of S2-1910635. 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":17820,"status":"agreed","reservation_date":"2019-10-19 05:44:19","uploaded":"2019-10-19 07:48:18","revisionof":"S2-1910635","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"},{"winame":"NB_IOTenh3-Core"}],"crnumber":1667.0,"crrevision":4.0,"crcategory":"B","tsg_crp":"SP-191068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910766.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910767","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: AMF stores Small Data Rate Control status per DNN. During mobility from EPS, the source of this information can be APN Rate Control parameters stored by the MME. In that case, the Small Data Rate Control status is applied on DNN that is the same as the APN in the stored APN Rate Control. Small Data Rate Control does not apply per RAT type, but per DNN and S-NSSAI. The use of the term Small Data Rate Control status is aligned between TS 23.501 and TS 23.502.","secretary_remarks":"Revision of S2-1910493. This was left for e-mail approval. e-mail revision 1 approved. Revised to S2-1910802.","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":18170,"status":"revised","reservation_date":"2019-10-19 05:44:21","uploaded":"2019-10-19 07:48:18","revisionof":"S2-1910493","revisedto":"S2-1910802","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1808.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910767.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910789","title":"Reply LS on RRC Connection Reestablishment for CP for NB-IoT connected to 5GC","source":"SA WG2","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2, CT WG4, SA WG3. CC: CT WG1, RAN WG3. Attachments: S2-1910766 (23.501 CR#1667)","secretary_remarks":"Revision of S2-1910487. 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":17850,"status":"approved","reservation_date":"2019-10-28 11:11:12","uploaded":"2019-10-28 11:12:07","revisionof":"S2-1910487","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1908707","lsto":"RAN WG2, CT WG4, SA WG3","Cc":"CT WG1, RAN WG3","lsoriginalls":"","lsreply":"S3-194320","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910789.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910790","title":"Control Plane CIoT 5GS Optimisations restriction on NR","source":"ORANGE, Vodafone, AT&T, Nokia, Nokia Shanghai Bell","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When connected over any other 5G AN than E-UTRA, a UE which negotiated the use of the CP CIoT 5GS optimisation, may use the Control Plane CIoT 5GS Optimisation, but without using EDT or RAI (as those capabilities would require AN support).","secretary_remarks":"e-mail revision 2 of S2-1910491. 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":18080,"status":"agreed","reservation_date":"2019-10-28 11:11:12","uploaded":"2019-10-28 15:13:49","revisionof":"S2-1910491","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1690.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_135_Split\/Docs\/S2-1910790.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910801","title":"Introduction of MT-EDT","source":"OPPO, Intel, Ericsson, Sumsung, Qualcomm, NEC, Orange","contact":"Jianhua Liu","contact-id":72698,"tdoctype":"CR","for":"Endorsement","abstract":"Summary of change: This CR introduces the MT-EDT.","secretary_remarks":"e-mail revision 4 of.S2-1910762. This CR was technically endorsed","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":17330,"status":"endorsed","reservation_date":"2019-10-28 11:11:29","uploaded":"2019-10-28 15:13:49","revisionof":"S2-1910762","revisedto":"S2-1911757, S2-1911758","release":"Rel-16","crspec":"23.401","crspecversion":"16.4.0","workitem":[{"winame":"5G_CIoT"},{"winame":"LTE_eMTC5"},{"winame":"NB_IOTenh3"}],"crnumber":3542.0,"crrevision":5.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910801.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910802","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: AMF stores Small Data Rate Control status per DNN. During mobility from EPS, the source of this information can be APN Rate Control parameters stored by the MME. In that case, the Small Data Rate Control status is applied on DNN that is the same as the APN in the stored APN Rate Control. Small Data Rate Control does not apply per RAT type, but per DNN and S-NSSAI. The use of the term Small Data Rate Control status is aligned between TS 23.501 and TS 23.502.","secretary_remarks":"e-mail revision 1 of.S2-1910767. 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":18180,"status":"agreed","reservation_date":"2019-10-28 11:11:30","uploaded":"2019-10-28 15:13:49","revisionof":"S2-1910767","revisedto":"S2-1911505","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1808.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910802.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910804","title":"Reply LS on Mobile-terminated Early Data Transmission","source":"SA WG2","contact":"Jianhua Liu","contact-id":72698,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2, RAN WG3, TSG RAN. CC: TSG SA","secretary_remarks":"e-mail revision 6 of.S2-1910631. 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":17520,"status":"approved","reservation_date":"2019-10-28 11:11:31","uploaded":"2019-10-28 11:12:07","revisionof":"S2-1910631","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1908649","lsto":"RAN WG2, RAN WG3, TSG RAN","Cc":"TSG SA","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910804.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910805","title":"Reply LS on Small Data Rate Control and APN Rate Control","source":"SA WG2","contact":"Steven Wenham","contact-id":48132,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC: CT WG1. Attachments: S2-1910638 (TS 23.501 CR1818), S2-1910802 (TS 23.502 CR1808)","secretary_remarks":"e-mail revision of S2-1910642. 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":18220,"status":"approved","reservation_date":"2019-10-28 11:11:31","uploaded":"2019-10-28 11:12:07","revisionof":"S2-1910642","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1908668","lsto":"CT WG4","Cc":"CT WG1","lsoriginalls":"","lsreply":"C4-195471","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910805.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]