[{"name":"S2-1906839","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. This flow includes the following steps: 1. AF sends Nnef_EventExposure_Subscribe Request to NEF requesting data delivery status. The IP Filter information is included in the message to identify the IP PDU traffic or the Ethernet packet filter. The Downlink delivery status events include: - Downlink Packet(s) in extended buffering event, including Extended Buffering time. - This event is triggered every time a new downlink data packet is buffered with extended buffering matching the IP filter information. - the SMF provides the Extended Buffering time as determined in clause 4.2.3.3. - Downlink Packet(s) discarded. - This event occurs when Extended Buffering time, as determined in clause 4.2.3.3, expires. - Downlink Packet(s) transmitted. - This event occurs when the UE becomes CM-CONNECTED, and buffered data can be delivered to UE as per clause 4.2.3.3. 2. NEF sends the Npcf_EventExposure_Subscribe Request to PCF. IP Filter information, monitoring event received from step 1 are included in the message. 3. PCF sends the Nsmf_EventExposure_Subscribe Request message to the SMF which serves the PDU Session relevant to the IP Filter information and includes the notification endpoint of NEF. \u2026 7. The SMF detects a change in Downlink Delivery Status event as described in clause 4.2.3. 8. The SMF sends the Nsmf_EventExposure_Notify with Downlink Delivery Status event message to NEF 9. The NEF sends Nnef_EventExposure_Notify with Downlink Delivery Status event message to AF. CT WG3 has the following related questions: a. How does the SMF detect the downlink delivery status in step 7? (CT WG3 had problems identifying the relevant information in the quoted subclause 4.2.3.) Does the SMF make that determination based on information on the UE status or based on information obtained from the UPF? b. Is any traffic filter information included in step 3? c. If so, is there a need to install any traffic filters for traffic detection in the UPF in step 3? d. If so, how would such filters interact with packet filters derived by the SMF from PCC rules obtained via the Npcf_SMPolicyControl service? e. Can multiple traffic filters be supplied in steps 1 and 2? f. If so, is there a need to identify the related flows in step 8? g. Can ethernet traffic filters be supplied in steps 1 and 2 (despite the term IP filters)? CT WG3 was also discussing the 'NEF service operations information flow' in subclause 4.15.3.3 of TS 23.502. This flow includes the following steps: 1. The AF subscribes to one or several Event(s) (identified by Event ID) and provides the associated notification endpoint of the AF by sending Nnef_EventExposure_Subscribe request. \u2026 The AF may also provides Traffic Descriptor (e.g. IP 3-tuples) information to support 'Availability after DDN Failure' for multiple AFs case. 2. [Conditional - depending on authorization in step 1] The NEF subscribes to received Event(s) (identified by Event ID) and provides the associated notification endpoint of the NEF to UDM by sending Nudm_EventExposure_Subscribe request\u2026. 3a. [Conditional] If the requested event (e.g. monitoring of Loss of Connectivity) requires AMF assistance, then the UDM sends the Namf_EventExposure_Subscribe to the AMF serving the requested user. \u2026 3c. [Conditional] If the requested event (e.g. 'Availability after DDN Failure' with traffic descriptor) requires SMF assistance, then for existing PDU session(s) or during the PDU session establishement procedure, the UDM selects the SMF based on the Slice information, the DNN and\/or the AF Service ID and sends the Nsmf_EventExposure_Subscribe with the event type 'Availability after DDN Failure' and Traffic Descriptor to the SMF(s) serving the requested user. As the UDM itself is not the Event Receiving NF, the UDM shall provide","secretary_remarks":"Postponed S2-1904878 from S2#133. Responses drafted in S2-1907005 and S2-1907711. Postponed","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18230,"status":"postponed","reservation_date":"2019-06-10 18:36:16","uploaded":"2019-06-11 14:48:56","revisionof":"S2-1904878","revisedto":"S2-1908645","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C3-191407","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1906839.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906863","title":"LS from RAN WG2: LS on support for flow based QoS & slicing for NB-IoT & eMTC connected to 5GC","source":"RAN WG2","contact":"Veera Prasada Kadiri","contact-id":72325,"tdoctype":"LS in","for":"Action","abstract":"In R15 5GC, flow based QoS concept was introduced and applied for LTE connected to 5GC. In order to support mapping between NAS based QoS flows (identified as QoS Flow Id) and AS DRBs, a new user plane AS protocol SDAP (Service Data Adaptation Layer) was introduced. SDAP protocol is used only when LTE UE is connected to 5GC. In case of NB-IoT connected to EPS, there are restrictions on what is supported in the user plane, e.g. at most two DRBs. For NB-IoT connected to 5GC, it is not clear how many 5GC QoS flows are supported , how mapping between 5GC QoS flows and DRBs are expected to work and whether SDAP is needed or not. Some multimode UEs will have support for NB-IoT and other RATs like eMTC, NR, LTE etc. How QoS mapping works in case of inter RAT mobility between NB-IoT connected to 5GC and other RATs (eMTC, LTE, NR) connected to 5GC is also not clear. R15 5GC introduced the concept of core network slicing. R15 LTE connecting to 5GC UEs will support up to 8 slices simultaneously and S-NSSAI is provided in Msg 5 during RRC Connection Setup procedure to assist eNB AMF selection. In case of NB-IoT\/eMTC, it is not clear whether slicing is supported for eMTC and NB-IoT connected to 5GC and if supported how many slices to be supported simultaneously in the devices. It is also not clear whether S-NSSAI will be used by the ng-eNB in addition to the indications of the supported 5G CIoT optimizations for AMF selection. Thus, RAN WG2 kindly asks SA WG2 to clarify the following questions. 1) Whether the 5GC QoS framework is supported for NB-IoT connected to 5GC? 2) If 5GC QoS framework is supported for NB-IoT connected to 5GC, what should be the maximum number of 5GC QoS flows supported when NB-IoT UE is connected to 5GC? 3) If 5GC QoS framework is supported for NB-IoT connected to 5GC, how mapping between 5GC QoS flows and NB-IoT DRBs is expected to work? 4) If 5GC QoS framework is supported for NB-IoT connected to 5GC, how does QoS mapping is expected to work in case of inter RAT idle mobility between NB-IoT connected to 5GC and other RATs (eMTC, LTE, NR) connected to 5GC? 5) Whether slicing is applicable for eMTC and NB-IoT devices connected to 5GC? 6) If slicing is supported, what is the maximum number of slices to be supported simultaneously for NB-IoT and eMTC UEs connected to 5GC? 7) If slicing is supported, will S-NSSAI be used by the ng-eNB in addition to the indications of the supported 5G CIoT optimizations for AMF selection?. Action: RAN WG2 respectfully asks SA WG2 to provide answers to the above questions.","secretary_remarks":"Response drafted in S2-1906925. Final response in S2-1908552","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17200,"status":"replied to","reservation_date":"2019-06-10 18:36:16","uploaded":"2019-06-12 11:37:53","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1, RAN WG3","lsoriginalls":"R2-1908190","lsreply":"S2-1908552","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1906863.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906864","title":"LS from RAN WG2: Reply LS for Conclusion on 5G CIoT user plane small data solution","source":"RAN WG2","contact":"Veera Prasada Kadiri","contact-id":72325,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 thanks SA WG2 for their LS on Conclusion on 5G CIoT user plane small data solution. Following SA WG2's agreement, RAN WG2 will introduce support for User Plane CIoT optimisations for NB-IoT and eMTC when connected to 5GC. RAN WG2 discussed whether to support RRC-Inactive with short eDRX (sleep cycles up to the NAS transmission timer) for eMTC and\/or NB-IoT connected to 5GC in Rel-16 and reached the following conclusions: - RRC-INACTIVE state in NB-IoT connected to 5GC is not supported. - RRC-INACTIVE state with short eDRX cycles is optionally supported for eMTC connected to 5GC with capability signalling. - FFS if EDT in RRC-INACTIVE state is not supported in Rel-16. - UP optimization solution is supported for both eMTC and NB-IoT connected to 5GC with capability signalling. Action: RAN WG2 respectfully asks SA WG2 and RAN WG3 to take into account the above answers during their work on cellular IoT.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17800,"status":"noted","reservation_date":"2019-06-10 18:36:16","uploaded":"2019-06-12 11:37:53","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG3","Cc":"TSG SA, TSG CT, TSG RAN","lsoriginalls":"R2-1908202","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1906864.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906866","title":"LS from RAN WG2: LS on UAC for NB-IoT","source":"RAN WG2","contact":"Odile Rollinger","contact-id":60606,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 has discussed support of UAC for NB-IoT connected to 5GC and is not sure whether UAC needs to be introduced for NB-IoT connected to 5GC or whether the access barring scheme used in EPS can be used for NB-IoT connected to 5GC. If UAC is supported for NB-IoT connected to 5GC, then it is RAN WG2 understanding that NB-IoT needs to support 5 access categories corresponding to mt-Access, mo-Signalling, mo-Data, delayTolerantAccess, mo-ExceptionData for UAC to support the existing NB-IoT establishment causes. However, the UAC mechanism provides the possibility to provide barring parameters for up to 64 access categories, most of which are reserved for future use or for operator definition. The operator defined access categories are intended to provide slice or service-specific barring. For RAN WG2 it is not clear whether it is necessary to support up to 64 categories. There is currently no access category in UAC corresponding to mo-Exception data, and it is not clear whether it is needed to introduce a new access category for this purpose. In R15 UAC, any access attempt which does not belong to access identity 1, 2, 11-15 are mapped to access identity 0. For RAN WG2, it is not clear whether access identity 0 corresponds to legacy access classes 0-9 and whether RAN WG2 has to consider access barring mechanism for barring access classes 0-9 (mapped to access identity 0) as well. In R15 UAC, barring for access identities 1, 2, 11 to 15 is independently controlled for different access categories in RAN WG2 specification. For RAN WG2, it is not clear whether barring for access identities 1, 2, 11 to 15 should be common for all access categories or independently controlled for different access categories for NB-IoT connected to 5GC. Thus, RAN WG2 has the following queries for SA WG1. 1) Whether UAC should be supported for NB-IoT connected to 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). 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. 4) Whether access class 0-9 is applicable for UAC and whether access class 0-9 access attempts are mapped to 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.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17280,"status":"noted","reservation_date":"2019-06-10 18:36:16","uploaded":"2019-06-12 11:37:53","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, CT WG1","Cc":"SA WG2, RAN WG3","lsoriginalls":"R2-1908263","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1906866.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906867","title":"LS from RAN WG2: LS on RRC Connection Re-Establishment for CP for NB-IoT connected to 5GC","source":"RAN WG2","contact":"Odile Rollinger","contact-id":60606,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 has discussed RRC Connection Re-Establishment for the control plane for NB-IoT connected to 5GC. RAN WG2 has concluded that not supporting it would mean a functionality gap between 5GC and EPC for mobility handling in NB-IoT. RAN WG2 would like to ask SA WG3 and SA WG2 on the feasibility of introducing RRC Connection Re-Establishment for the control plane for NB-IoT connected to 5GC and if found feasible to introduce RRC Connection Re-Establishment for the control plane for NB-IoT connected to 5GC in their specifications. RAN WG2 would like to inform SA WG3 and SA WG2 that, due to the limited size of the message, if the same security procedure and token (ul-NAS-MAC and ul-NAS-Count) as in EPS is used, there is not sufficient space to carry the 5G S-TMSI and a truncated 5G S TMSI (e.g. 40 bits) may need to be defined. Action: RAN WG2 kindly requests SA WG3 and SA WG2 feedback on the feasibility of introducing RRC Connection Re-Establishment for the control plane for NB-IoT connected to 5GC and, if found feasible, to introduce RRC Connection Re-Establishment for the control plane for NB-IoT connected to 5GC in their specifications.","secretary_remarks":"Responses drafted in S2-1907103 and S2-1907719. Final response in S2-1908553","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17290,"status":"replied to","reservation_date":"2019-06-10 18:36:16","uploaded":"2019-06-12 11:37:53","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, SA WG2","Cc":"CT WG1, RAN WG3, CT WG4","lsoriginalls":"R2-1908264","lsreply":"S2-1908553","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1906867.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906887","title":"NIDD Description Update for Maximum Packet Size","source":"Convida Wireless LLC, Intel","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updated the NIDD section to explain that the PCO can include the Maximum Packet Size. Update the sentence in the reliable data service section by replacing 'it' with 'the SMF'.","secretary_remarks":"Revision of S2-1905291 from S2#133. Agreed in parallel session. This was Block approved","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17800,"status":"agreed","reservation_date":"2019-06-11 20:51:41","uploaded":"2019-06-17 15:07:30","revisionof":"S2-1905291","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1364.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1906887.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906888","title":"NIDD Configuration Procedure Update for RDS and Maximum Packet Size","source":"Convida Wireless LLC, Intel","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updated the NIDD Configuration procedure for RDS support by adding the Reliable Data Service Configuration parameter to the NIDD Configuration procedure and updating the NIDD Configuration Procedure so that the AF can update the Reliable Data Service configuration (as is done in EPC). Updated the NIDD Configuration procedure so that the Maximum Packet Size is sent to the AF","secretary_remarks":"Revision of S2-1905293 from S2#133. Revised in parallel session to S2-1908378.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17580,"status":"revised","reservation_date":"2019-06-11 20:54:18","uploaded":"2019-06-17 15:07:30","revisionof":"S2-1905293","revisedto":"S2-1908378","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1373.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1906888.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906904","title":"NAS RAI corrections","source":"BlackBerry UK Ltd.","contact":"John-Luc Bakker","contact-id":37326,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change 'no further Uplink and Downlink Data transmissions are expected' into 'no further Uplink and no further Downlink Data transmissions are expected'. Remove undefined condition.","secretary_remarks":"Revised in parallel session to S2-1908379.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17610,"status":"revised","reservation_date":"2019-06-12 18:26:41","uploaded":"2019-06-17 12:44:00","revisionof":"","revisedto":"S2-1908379","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1461.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1906904.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906905","title":"NAS RAI corrections","source":"BlackBerry UK Ltd.","contact":"John-Luc Bakker","contact-id":37326,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change 'no further Uplink or Downlink Data transmissions are expected' into 'no further Uplink and no further Downlink Data transmissions are expected'.","secretary_remarks":"Revised in parallel session to S2-1908380.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17640,"status":"revised","reservation_date":"2019-06-12 18:26:42","uploaded":"2019-06-17 12:44:00","revisionof":"","revisedto":"S2-1908380","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1457.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1906905.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906924","title":"Discussion Paper in support of Reply LS to S2-1906863\/R2-1908190","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":57486,"tdoctype":"discussion","for":"Approval","abstract":"Discusses the questions provided by RAN WG2 in LS S2-1906863\/R2-1908190 and proposed answers","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17210,"status":"noted","reservation_date":"2019-06-12 21:55:15","uploaded":"2019-06-17 23:34:22","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_134_Sapporo\/Docs\/S2-1906924.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906925","title":"[DRAFT] Reply LS on support for flow based QoS & slicing for NB-IoT & eMTC connected to 5GC","source":"Qualcomm UK Ltd","contact":"Miguel Griot","contact-id":57486,"tdoctype":"LS out","for":"Approval","abstract":"Proposed answers to RAN WG2 regarding NB-IoT\/eMTC connected to 5GC","secretary_remarks":"Response to S2-1906863. Revised in parallel session to S2-1908315.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17220,"status":"revised","reservation_date":"2019-06-12 22:00:26","uploaded":"2019-06-17 23:34:22","revisionof":"","revisedto":"S2-1908315","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, CT WG1","Cc":"RAN WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1906925.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906926","title":"Clarifications to QoS support for NB-IoT","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":57486,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: QoS model for NB-IoT: New section to include requirement of only a default QoS rule per PDU session, maximum of 2 Data Radio Bearers. Inter-RAT idle mode mobility to Nb-IoT: SMF needs to initiate PDU sesion modification to remove any non-default QoS rule. Network slicing for NB-IoT: The UE shall not provide NSSAI in the Access stratum for NB-IoT. The NAS Requested NSSAI limited to 2 S-NSSAIs","secretary_remarks":"Revised in parallel session to S2-1908316.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17250,"status":"revised","reservation_date":"2019-06-12 22:09:06","uploaded":"2019-06-17 23:34:22","revisionof":"","revisedto":"S2-1908316","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1461.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1906926.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906927","title":"Discussion on System aspects of Connection Reestablishment for Control Plane for NB-IoT (based on S2-1906867\/ R2-1908264)","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":57486,"tdoctype":"discussion","for":"Approval","abstract":"Proposes a way forward to handle Connection Reestablishment for Control Plane for NB-IoT.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17300,"status":"noted","reservation_date":"2019-06-12 22:15:10","uploaded":"2019-06-17 23:34:22","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_134_Sapporo\/Docs\/S2-1906927.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906928","title":"Handling RRC connection reestablishment for Control Plane for NB-IoT connected to 5GC","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":57486,"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":"Not Handled","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17320,"status":"not treated","reservation_date":"2019-06-12 22:20:29","uploaded":"2019-06-17 23:34:22","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1462.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1906928.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906945","title":"Detection of 'Downlink data delivery status' and 'Availability after DDN Failure' events","source":"Nokia, Nokia Shanghai-Bell","contact":"Thomas Belling","contact-id":68266,"tdoctype":"discussion","for":"Approval","abstract":"This contribution aims to investigate issues raised in the incoming LS S2-1904878, including questions how the 'Downlink data delivery status' (buffered, transmitted, discarded) is detected by the SMF and how packet filters are handled in this context. Related change requests are in S2-1906946 (TS 23.501), S2-1907002, S2-1907003 (TS 23.502), S2-1907004, (TS 23.503), and a suggested reply LS is in. S2-1907005.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18010,"status":"noted","reservation_date":"2019-06-13 15:42:14","uploaded":"2019-06-18 13:19:20","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_134_Sapporo\/Docs\/S2-1906945.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906946","title":"Adding N4 Notification about buffered packets beeing dropped","source":"Nokia, Nokia Shanghai-Bell","contact":"Thomas Belling","contact-id":68266,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The N4 interface is extended with notification about buffered packets being discarded similar to the existing notification about the arrival of the first downlink packet. The request for this notification is expressed via new action values in the FAR. It is also clarified for the existing reporting about the arrival of the first downlink packet that it relates to a Packet Detection Rule (PDR), as this is the way to describe 'user plane path' (existing term) on the N4 interface.","secretary_remarks":"Revised in parallel session to S2-1908397.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18040,"status":"revised","reservation_date":"2019-06-13 16:04:11","uploaded":"2019-06-18 13:19:20","revisionof":"","revisedto":"S2-1908397","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1465.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1906946.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907002","title":"Update to downlink data delivery status event to support PCC and HR roaming","source":"Nokia, Nokia Shanghai Bell","contact":"Thomas Belling","contact-id":68266,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Interactions of the SMF with the UPF for subscribing to downlink data delivery status are added to subclause 4.15.3.2.5. Subscription is via UDM. However, if PCC is used, the PCF is notified about the subscription. Then, the subscription to the Nsmf_EventExposure notification is indirect via PCC rule information of the Npcf_SMPolicyControl service and comes from the PCF rather than the UDM. For the home routed roaming case, the V-SMFF and an attached UPF detect downlink data delivery status events and the V-SMF sends related notifications.","secretary_remarks":"Revised in parallel session, merging S2-1907493, to S2-1908398.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18070,"status":"revised","reservation_date":"2019-06-14 11:23:43","uploaded":"2019-06-18 13:19:20","revisionof":"","revisedto":"S2-1908398","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1481.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907002.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907003","title":"Update to Availability after DDN Failure event to support PCC and HR roaming","source":"Nokia, Nokia Shanghai Bell","contact":"Thomas Belling","contact-id":68266,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Interactions of the SMF with the UPF for subscribing to downlink data delivery status are added to subclause 4.15.3.2.5. Subscription is via UDM. However, if PCC is used, the PCF is notified about the subscription. Then, the subscription to the Nsmf_EventExposure notification is indirect via PCC rule information of the Npcf_SMPolicyControl service and comes from the PCF rather than the UDM. For the home routed roaming case, the V-SMF and an attached UPF detect downlink data delivery status events and the V-SMF sends related notifications. Traffic filters are an optional input parameter for the Nudm_EventExposure_Subscribe service operation","secretary_remarks":"Revised in parallel session to S2-1908399.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18140,"status":"revised","reservation_date":"2019-06-14 11:32:45","uploaded":"2019-06-18 13:19:20","revisionof":"","revisedto":"S2-1908399","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1482.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907003.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907004","title":"Subscription to downlink data delivery status event via PCC","source":"Nokia, Nokia Shanghai-Bell","contact":"Thomas Belling","contact-id":68266,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The subscription to the Nsmf_EventExposure notification is indirect via PCC rule information of the Npcf_SMPolicyControl service. For that purpose, an AF subscription to downlink data delivery status events IE (similar to the existing Information on AF subscription to UP change events IE) is added to the PCC rule. If PCC is used, the PCF is notified about the subscription to the Downlink data delivery status at the SMF to allow the PCF to provide policies as described above,","secretary_remarks":"This was postponed.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18160,"status":"postponed","reservation_date":"2019-06-14 11:37:02","uploaded":"2019-06-18 13:19:20","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.503,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":294.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907004.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907005","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":"Revision of S2-1906075 from S2#133. Response to S2-1906839. Revised in parallel session to S2-1908401.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18110,"status":"revised","reservation_date":"2019-06-14 11:42:51","uploaded":"2019-06-18 13:19:20","revisionof":"S2-1906075","revisedto":"S2-1908401","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_134_Sapporo\/Docs\/S2-1907005.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907012","title":"Aligning Terminology referring to the CIoT 5GS Optimisations","source":"Orange","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Aligning the terminology to 'Control Plane CIoT 5GS Optimisation' and 'User Plane CIoT 5GS Optimisation'.","secretary_remarks":"Revised in parallel session to S2-1908372.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17380,"status":"revised","reservation_date":"2019-06-14 13:00:15","uploaded":"2019-06-16 05:37:02","revisionof":"","revisedto":"S2-1907013, S2-1908372","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1479.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907012.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907014","title":"Aligning Terminology referring to the CIoT 5GS Optimisations","source":"Orange","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Aligning the terminology to 'Control Plane CIoT 5GS Optimisation' and 'User Plane CIoT 5GS Optimisation'.","secretary_remarks":"Agreed in parallel session. This was Block approved","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17630,"status":"agreed","reservation_date":"2019-06-14 13:08:17","uploaded":"2019-06-15 11:27:54","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1485.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907014.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907061","title":"Follow-on indication in initial registration for Service Gap","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove limitation of Mobility and Periodiv registation to not include Follow-on Request indication when Service Gap timer is running. I.e. the limitation is applicable to all cases of registration.","secretary_remarks":"Agreed in parallel session. This was Block approved","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18580,"status":"agreed","reservation_date":"2019-06-14 15:26:03","uploaded":"2019-06-18 03:21:21","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1496.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907061.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907062","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":"Not Handled","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18360,"status":"not treated","reservation_date":"2019-06-14 15:26:05","uploaded":"2019-06-18 03:21:21","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1485.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907062.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907063","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":"Not Handled","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18370,"status":"not treated","reservation_date":"2019-06-14 15:26:06","uploaded":"2019-06-18 03:21:21","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1486.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907063.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907103","title":"[DRAFT] Reply LS on RRC Connection Re-Establishment for CP for NB-IoT connected to 5GC","source":"Qualcomm UK Ltd","contact":"Miguel Griot","contact-id":57486,"tdoctype":"LS out","for":"Approval","abstract":"Provides answers to RAN WG2 with a way forward for feasibility of RRC Connection Re-Establishment for CP for NB-IoT connected to 5GC","secretary_remarks":"Response to S2-1906867. Not Handled","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17310,"status":"not treated","reservation_date":"2019-06-14 21:33:09","uploaded":"2019-06-17 23:34:22","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_134_Sapporo\/Docs\/S2-1907103.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907152","title":"Impacts for supporting or not supporting the CIoT 5GS Optimisations over NR","source":"Orange","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"discussion","for":"Discussion","abstract":"This paper analyses the impacts of supporting or not supporting the CIoT 5GS Optimisations over NR and proposes a way forward.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17410,"status":"noted","reservation_date":"2019-06-16 04:11:50","uploaded":"2019-06-18 15:03:40","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_134_Sapporo\/Docs\/S2-1907152.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907153","title":"Handling of CIoT optimisations not supported over NR","source":"ORANGE","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introducing the support of Control Plane CIoT 5GS Optimisation without EDT and RAI feautures over NR.","secretary_remarks":"Revised in parallel session to S2-1908373.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17420,"status":"revised","reservation_date":"2019-06-16 04:16:38","uploaded":"2019-06-18 15:06:02","revisionof":"","revisedto":"S2-1908373","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1509.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907153.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907154","title":"Handling of CIoT optimisations not supported over NR","source":"ORANGE","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: RAI handling and EDT are not to be sent by the UE when covered in NR.","secretary_remarks":"Not Handled","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17450,"status":"not treated","reservation_date":"2019-06-16 04:19:05","uploaded":"2019-06-18 15:09:35","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1509.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907154.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907155","title":"Correction on Control Plane Only Indication Setting","source":"Orange","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change in the 4th bullet of clause 5.31.4.1 to correctly handle the case of PDU Sessions of type other than Unstructured for a UE whose subscription includes a NEF Identity for NIDD for the DNN considered.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17460,"status":"noted","reservation_date":"2019-06-16 04:53:52","uploaded":"2019-06-16 05:37:02","revisionof":"","revisedto":"S2-1908743","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1510.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907155.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907156","title":"UE Indication of support for the User Plane CIoT Optimisation in RRC","source":"ORANGE","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding the indication of the support of the User Plane CIoT 5GS Optimisation in the RRC Message that helps the RAN select an AMF.","secretary_remarks":"Revised in S2-1907766","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17910,"status":"revised","reservation_date":"2019-06-16 05:15:06","uploaded":"2019-06-16 05:37:02","revisionof":"","revisedto":"S2-1907766","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1510.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907156.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907157","title":"Corrections on setting the Invoke NEF Flag during PDU Session Establishment","source":"ORANGE","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) Removing the check of the 'Invoke NEF Indication' and the setting of the 'Invoke NEF' flag by the AMF in step 3 2) Adding the PDU Session Type check when the SMF receives the 'Invoke NEF' flag.","secretary_remarks":"Agreed in parallel session. This was Block approved","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17900,"status":"agreed","reservation_date":"2019-06-16 05:51:53","uploaded":"2019-06-17 15:49:57","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1511.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907157.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907210","title":"Monitoring Event Subscription and Network Configuration correction","source":"Huawei, HiSilicon,","contact":"Runze Zhou","contact-id":60945,"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":"Not Handled","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18440,"status":"not treated","reservation_date":"2019-06-17 00:45:21","uploaded":"2019-06-18 14:13:13","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"TEI16"},{"winame":"5G_CIoT"}],"crnumber":1516.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907210.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907262","title":"Addition of missing CIoT services","source":"Orange","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adds the following services to clause 7.2 with references to TS 23.502: Nsmf_NIDD Nudm_ NIDDAuthorisation Nnef_MSISDN-less_MO_SMS Nnef_NIDDConfiguration Nnef_NIDD Nnef_SMContext Nnef_NetworkStatus Ninef_EventExposure","secretary_remarks":"Revised in parallel session to S2-1908381.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17680,"status":"revised","reservation_date":"2019-06-17 04:24:31","uploaded":"2019-06-17 15:47:56","revisionof":"","revisedto":"S2-1908381","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1541.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907262.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907368","title":"Group reporting Guard Time correction","source":"Nokia, Nokia Shanghai Bell, Samsung","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The text is updated to say it clearly that the detection (and accumulation) of the notification events on the requested group of UEs is done in the network.","secretary_remarks":"Not Handled","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18450,"status":"not treated","reservation_date":"2019-06-17 10:20:53","uploaded":"2019-06-17 13:41:08","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1555.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907368.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907369","title":"Conditions to use CP or UP CIoT","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: All AMF input parameters to determine whether to apply Control Plane Only Indicator or not is enumerated in the summary clause to avoid impression that the AMF local policy alone could determine the use of Control Plane Only Indicator. The use of Control Plane CIoT 5GS Optimisation at the same time as User Plane CIoT 5GS Optimisation is forbidden.","secretary_remarks":"Revised in parallel session to S2-1908374.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17470,"status":"revised","reservation_date":"2019-06-17 10:25:22","uploaded":"2019-06-17 13:41:08","revisionof":"","revisedto":"S2-1908374","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1573.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907369.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907370","title":"Conditions to use CP or UP CIoT","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The use of Control Plane CIoT 5GS Optimisation at the same time as User Plane CIoT 5GS Optimisation is forbidden. In the MO case, the step where this applies on the SMF and the UE is different, since the UE can only detect the availability of N3 data berers at step 13.","secretary_remarks":"Revised in parallel session to S2-1908375.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17500,"status":"revised","reservation_date":"2019-06-17 10:28:35","uploaded":"2019-06-17 13:41:08","revisionof":"","revisedto":"S2-1908375","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1556.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907370.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907371","title":"T8 \/ N33 configuration","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: TS 23.501 text is updated to refer to a recent call flow update in TS 23.502 CR1223 (S2-1903537) in clause 4.25.3.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17710,"status":"noted","reservation_date":"2019-06-17 10:31:26","uploaded":"2019-06-17 13:41:08","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1574.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907371.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907389","title":"Corrections to Control Plane CIoT 5GS Optimisation description","source":"Sony","contact":"Lars Nord","contact-id":82070,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove last part of first sentence Replacing the duplication of text with a reference to the next clause 5.31.4.2 Aligning the term 'user plane resources' in 5.31.4.1 with the term used in 5.31.4.2 'N3 data transfer' in a couple of places","secretary_remarks":"Revised in parallel session to S2-1908382.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17720,"status":"revised","reservation_date":"2019-06-17 12:08:41","uploaded":"2019-06-18 07:03:31","revisionof":"","revisedto":"S2-1908382","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1580.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907389.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907390","title":"Corrections to N3 data transfer establishment procedures","source":"Sony","contact":"Lars Nord","contact-id":82070,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 4.2.10.1: Adding 'TS 23.501' to the clause reference, moving text up since it could be read as the 'local decision' is to set the Control Plane Only indicator, adding a missing 'transfer' and use 'established N3 data transfer' instead of 'activated user plane resources' in a couple of places 4.2.10.2: Remove the case when the UE is in CM-IDLE Change step 6 to step 4a (step 4a in clause 4.2.3.3 is when the UE is in CM-CONNECTED) Removing the duplication of text in step 3","secretary_remarks":"Revised in parallel session to S2-1908383.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17750,"status":"revised","reservation_date":"2019-06-17 12:11:24","uploaded":"2019-06-18 07:03:31","revisionof":"","revisedto":"S2-1908383","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1565.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907390.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907391","title":"Aligment of the term Early Data Transmission","source":"Sony","contact":"Lars Nord","contact-id":82070,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Align EDT text with clause 5.31.4","secretary_remarks":"Agreed in parallel session. This was Block approved","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18010,"status":"agreed","reservation_date":"2019-06-17 12:16:52","uploaded":"2019-06-18 07:03:31","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1581.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907391.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907449","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":"Not Handled","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18460,"status":"not treated","reservation_date":"2019-06-17 15:09:54","uploaded":"2019-06-17 15:13:27","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1594.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907449.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907465","title":"Clarify short DRX cycle length CM-CONNECTED with RRC inactive for eMTC","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":57486,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Maximum eDRX cycle value for CM-CONNECTED with RRC inactive is 10.24 seconds. Clarify RRC inactive does not apply to NB-IoT in this release.","secretary_remarks":"Revised in parallel session to S2-1908411.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18260,"status":"revised","reservation_date":"2019-06-17 16:14:09","uploaded":"2019-06-17 23:34:22","revisionof":"","revisedto":"S2-1908411","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1596.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907465.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907490","title":"CIoT Enforcement","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Checking RAT when negotiating PNB\/SNB","secretary_remarks":"Postponed in parallel session","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17440,"status":"postponed","reservation_date":"2019-06-17 19:04:59","uploaded":"2019-06-18 13:27:27","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1586.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907490.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907491","title":"Support for PDN Connectivity Status monitoring event","source":"Ericsson","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":"Not Handled","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18470,"status":"not treated","reservation_date":"2019-06-17 19:05:00","uploaded":"2019-06-18 13:27:27","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1587.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907491.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907492","title":"Introducing of UP CIoT 5GS Optimisation capability","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding UP CIoT 5GS optimization capability indication in selection functions.","secretary_remarks":"Revision of S2-1905232 from S2#133. Revised in parallel session, merging S2-1907659, to S2-1908407.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17850,"status":"revised","reservation_date":"2019-06-17 19:05:02","uploaded":"2019-06-18 13:27:27","revisionof":"S2-1905232","revisedto":"S2-1908407","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1347.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907492.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907493","title":"Downlink Data Delivery Notifications for UP","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarified what information is expected. Only first buffered packet (per AF) is triggering a notification, to avoid the possibility of a denial of service attack or overload using DL data. The events 'Downlink packet(s) discarded' and 'Downlink packet(s) transmitted' has been removed.","secretary_remarks":"Merged into S2-1908398.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18030,"status":"merged","reservation_date":"2019-06-17 19:05:05","uploaded":"2019-06-18 13:27:27","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1588.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907493.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907494","title":"5GS to EPS Idle mode mobility with N26 interface with RRC inactive and data forwarding","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce a new 5GS to EPS idle mode mobility procedure with N26 interface for RRC inactive with data forwarding, following the data forwarding principle exists in EPS (TS 23.401 clause 5.3.3.1A)","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18200,"status":"noted","reservation_date":"2019-06-17 19:05:05","uploaded":"2019-06-18 13:27:27","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1589.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907494.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907495","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: It's proposed to introduce a new flow descrbing the handling of the data forwarding considering the mechanism specified in TS 23.401 clause 5.3.3.1A.","secretary_remarks":"Revised in parallel session to S2-1908403.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18210,"status":"revised","reservation_date":"2019-06-17 19:05:07","uploaded":"2019-06-18 13:27:27","revisionof":"","revisedto":"S2-1908403","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1590.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907495.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907524","title":"Clarification of Control Plane CIoT 5GS Optimisation","source":"ZTE","contact":"Yingjie Hong","contact-id":76103,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1, Remove feature of header compression for Ethernet data. 2, 'NEF Identity for NIDD' is replaced by 'Invoke NEF indication', since 'NEF Identity for NIDD' is a SMF subscription data and is not suitable for AMF.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17790,"status":"noted","reservation_date":"2019-06-18 02:13:06","uploaded":"2019-06-18 07:47:00","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1613.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907524.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907526","title":"Clarification of service exporsure in interworking scenario","source":"ZTE","contact":"Yingjie Hong","contact-id":76103,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1, Suggest that all of the subclauses of 5.17.6 are moved into clause 5.17.5, e.g. clause 5.17.6.1 is moved and assigneded a new number 5.17.5.3, and clause 5.17.6 is empty.","secretary_remarks":"Not Handled","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18480,"status":"not treated","reservation_date":"2019-06-18 02:45:59","uploaded":"2019-06-18 07:47:00","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1615.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907526.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907585","title":"Clarification on strictly periodic timer in relation to MICO mode","source":"Samsung","contact":"Lalith Kumar","contact-id":80547,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If MICO is disabled then periodic registration timer shall not apply indication 'Strictly Periodic Registration Timer Indication'","secretary_remarks":"Revised in parallel session to S2-1908412.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18300,"status":"revised","reservation_date":"2019-06-18 05:45:20","uploaded":"2019-06-18 06:42:31","revisionof":"","revisedto":"S2-1908412","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1632.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907585.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907622","title":"Clarification of Service Gap Control Capability indication","source":"ZTE","contact":"Yingjie Hong","contact-id":76103,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Service Gap Control Capability as a separate parameter in registration request messge is removed.","secretary_remarks":"Agreed in parallel session. This was Block approved","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18610,"status":"agreed","reservation_date":"2019-06-18 07:35:16","uploaded":"2019-06-18 07:51:09","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1620.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907622.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907623","title":"Clarification of User Plane CIoT 5GS Optimisation","source":"ZTE","contact":"Yingjie Hong","contact-id":76103,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: During PDU session establishment procedure, AMF sends User Plane CIoT 5GS Optimasation indication to NG-RAN via N2 message.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17950,"status":"noted","reservation_date":"2019-06-18 07:41:50","uploaded":"2019-06-18 07:51:09","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1621.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907623.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907649","title":"Update the SMF discovery and selection regarding the Contorl Plane\/User Plane CIoT 5GS Optimisations","source":"Samsung","contact":"Kisuk Kweon","contact-id":80126,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding Inputs, Optional for Control Plane CIoT 5GS Optimisation or User Plane CIoT Optimisation Indication in the Nnrf_NFDiscovery_Request service operation.","secretary_remarks":"Agreed in parallel session. This was Block approved","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17750,"status":"agreed","reservation_date":"2019-06-18 08:33:07","uploaded":"2019-06-18 09:00:13","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1629.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907649.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907656","title":"Clarification on the buffered data delivery","source":"CATT","contact":"Qiang Deng","contact-id":74437,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the extended data delivery handling for all cases in Registration and Service Request procedure.","secretary_remarks":"Revised in parallel session to S2-1908404.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18230,"status":"revised","reservation_date":"2019-06-18 08:49:15","uploaded":"2019-06-18 09:10:47","revisionof":"","revisedto":"S2-1908404","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1630.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907656.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907659","title":"Update NF functional description of SMF and AMF for User Plane CIoT 5GS Optimisation","source":"Samsung","contact":"Kisuk Kweon","contact-id":80126,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding supporing User Plane 5GS Optimisation in SMF and AMF functional description and SMF discovery and selection.","secretary_remarks":"Merged into S2-1908407","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17960,"status":"merged","reservation_date":"2019-06-18 08:51:30","uploaded":"2019-06-18 09:00:13","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1649.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907659.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907661","title":"Update the PDU Session Establishment procedure regarding the User Plane CIoT 5GS Optimisations","source":"Samsung","contact":"Kisuk Kweon","contact-id":80126,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removes AMF's informing the SMF of User Plane CIoT 5GS Optimisations in the PDU Session Establishment procedure","secretary_remarks":"Not Handled","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17970,"status":"not treated","reservation_date":"2019-06-18 08:56:50","uploaded":"2019-06-18 09:00:13","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1631.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907661.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907709","title":"Discussion on Information Flow for Downlink Data Delivery Status","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"discussion","for":"Approval","abstract":"This document gives an analysis on solutions about information flow for downlink data delivery status.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18020,"status":"noted","reservation_date":"2019-06-18 11:25:20","uploaded":"2019-06-18 13:46:10","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_134_Sapporo\/Docs\/S2-1907709.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907710","title":"Corrections to information flow for downlink data delivery status","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Changes include: PCF is modified to UDM for monitoring events. IP packet is revised to traffic descriptor. Clarify how the SMF detects a change in Downlink Delivery Status event.","secretary_remarks":"Revision of S2-1905600 from S2#133. Merged into to S2-1908551.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18180,"status":"merged","reservation_date":"2019-06-18 11:25:20","uploaded":"2019-06-18 13:46:10","revisionof":"S2-1905600","revisedto":"S2-1908402","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1284.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907710.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907711","title":"Reply LS on Nsmf_EventExposure and Nnef_EventExposure service handling of the 'Downlink data delivery status' and ' Availability after DDN Failure' events.","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on Nsmf_EventExposure and Nnef_EventExposure service handling of the 'Downlink data delivery status' and ' Availability after DDN Failure' events.","secretary_remarks":"Response to S2-1906839. Not Handled","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18130,"status":"not treated","reservation_date":"2019-06-18 11:25:21","uploaded":"2019-06-18 13:46:10","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_134_Sapporo\/Docs\/S2-1907711.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907712","title":"Stateless IPv6 Address Autoconfiguration for Control Plane CIoT 5GS optimisation","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In Non-roaming and Roaming with Local Breakout case when CP Optimisation is used: The step that sends the IPv6 Router Advertisement is not skipped, and the IPv6 Router Advertisement is sent to the AMF for transmission to the UE, and Don't skip SMF registration with the UDM and error recovery steps. In the Home-routed case: Provide the IPv6 Router Advertisement to the V-UPF to send to the UE via the home-routed CP data path through the home and visited networks, and Clarify that step 20 (sending Nsmf_PDUSession_UpdateSMContext Response) is skipped, as step 18 (Nsmf_PDUSession_UpdateSMContext Request) is skipped in the CP Optimisation case in the referred to non-roaming and LBO clause.","secretary_remarks":"Revision of S2-1905622 from S2#133. Agreed in parallel session. This was Block approved","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17830,"status":"agreed","reservation_date":"2019-06-18 11:25:21","uploaded":"2019-06-18 13:46:10","revisionof":"S2-1905622","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1429.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907712.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907713","title":"Clarification on Preferred Network Behavior for CIoT 5GS optimisations","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When the UE performs ATTACH\/TAU it includes its 5GC Preferred Network Behaviour if the EPC Preferred Network Behaviour is included. The AMF provides an indication of support of UP CIoT 5GS Optimisations per UE and not a generic indication of support.","secretary_remarks":"Revised in parallel session to S2-1908376.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17530,"status":"revised","reservation_date":"2019-06-18 11:25:22","uploaded":"2019-06-18 13:46:10","revisionof":"","revisedto":"S2-1908376","release":"Rel-16","crspec":23.501,"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_134_Sapporo\/Docs\/S2-1907713.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907714","title":"Clarification on Preferred Network Behaviour for CIoT 5GS Optimisations","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When the UE performs ATTACH\/TAU it includes its 5GC Preferred Network Behaviour if the EPC Preferred Network Behaviour is included.","secretary_remarks":"Revised in parallel session to S2-1908377.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17550,"status":"revised","reservation_date":"2019-06-18 11:25:23","uploaded":"2019-06-18 13:46:10","revisionof":"","revisedto":"S2-1908377","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1643.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907714.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907715","title":"RAI Terminology Alignment on CIoT 5GS Optimisaitons","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Release Assistance Information\/Indication has been made consistently Release Assistance Information, matching TS 23.501.","secretary_remarks":"Revised in parallel session to S2-1908409.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17980,"status":"revised","reservation_date":"2019-06-18 11:25:24","uploaded":"2019-06-18 13:46:10","revisionof":"","revisedto":"S2-1908409","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1644.0,"crrevision":"","crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907715.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907716","title":"Discussion on Small Data Rate Control and Exception Reporting","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"discussion","for":"Approval","abstract":"This discussion paper elaborates on the issues of applicability of Small Data Rate Control to MO Exception Data","secretary_remarks":"Not Handled","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18390,"status":"not treated","reservation_date":"2019-06-18 11:25:25","uploaded":"2019-06-18 13:46:10","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_134_Sapporo\/Docs\/S2-1907716.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907717","title":"Corrections to Small Data Rate Control and Exception Reporting","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce the 'MO Exception data counter' reporting function. A new IE\/flag in the NAS message to indicate whether the embedded PDU is MO Exception Data or not, and the AMF sends an indication to (H-)SMF for indicating that a certain PDU is MO Exception Data, and then onto the UPF\/NEF for PDU Sessions using Control Plane data transfer.","secretary_remarks":"Revised in parallel session to S2-1908413.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18400,"status":"revised","reservation_date":"2019-06-18 11:25:25","uploaded":"2019-06-18 13:46:10","revisionof":"","revisedto":"S2-1908413","release":"Rel-16","crspec":23.501,"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_134_Sapporo\/Docs\/S2-1907717.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907718","title":"Corrections to Small Data Rate Control and Exception Reporting","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce the 'MO Exception data counter' reporting function. A new IE\/flag in the NAS message to indicate whether the embedded PDU is MO Exception Data or not, and the AMF sends an indication to (H-)SMF for indicating that a certain PDU is MO Exception Data, and then onto the UPF\/NEF for PDU Sessions using Control Plane data transfer.","secretary_remarks":"Not Handled","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18430,"status":"not treated","reservation_date":"2019-06-18 11:25:26","uploaded":"2019-06-18 13:46:10","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1645.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907718.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907719","title":"Response to RAN WG2 LS on RRC Connection Re-Establishment for CP for NB-IoT connected to 5GC","source":"Huawei","contact":"Runze Zhou","contact-id":60945,"tdoctype":"LS out","for":"Approval","abstract":"Response LS to Response to RAN WG2 LS (R2-1908264) on RRC Connection Re-Establishment for CP for NB-IoT connected to 5GC","secretary_remarks":"Response to S2-1906867. Revised in parallel session to S2-1908371.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17330,"status":"revised","reservation_date":"2019-06-18 11:25:28","uploaded":"2019-06-18 13:46:10","revisionof":"","revisedto":"S2-1908371","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, SA WG3, CT WG4","Cc":"CT WG1, RAN WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907719.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907720","title":"Corrections to RRC Connection Re-Establishment for CP","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduced a new subclause describing the Control Plane Relocation Indication procedure.","secretary_remarks":"Not Handled","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17370,"status":"not treated","reservation_date":"2019-06-18 11:25:28","uploaded":"2019-06-18 13:46:10","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1667.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907720.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907724","title":"Clarification to MICO mode and Periodic Registration Control","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"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":"Not Handled","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18340,"status":"not treated","reservation_date":"2019-06-18 11:25:30","uploaded":"2019-06-18 13:46:10","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"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_134_Sapporo\/Docs\/S2-1907724.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907725","title":"Removal of eDRX support with RRC_INACTIVE for NB-IoT","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that extended DRX in CM-IDLE is supported by WB-E-UTRA and NB-IoT, extended DRX in CM-CONNECTED with RRC_Inactive is supported by WB-E-UTRA and not NB-IoT and neither is supported by NR. The UEs accepted idle mode extended DRX cycle and parameters are only passed to NG-RAN for RATs that support extended DRX in CM-CONNECTED with RRC_Inactive.","secretary_remarks":"Revised in parallel session to S2-1908410.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18280,"status":"revised","reservation_date":"2019-06-18 11:25:32","uploaded":"2019-06-18 13:46:10","revisionof":"","revisedto":"S2-1908410","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1669.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907725.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907728","title":"Disc on UPF service area for UP CIoT 5GS Optimisation","source":"Samsung Electronics Romania","contact":"Sunghoon Kim","contact-id":59112,"tdoctype":"discussion","for":"Decision","abstract":"It is related with EDT. It discusses handling of UPF service area for UP CIoT Optimisation.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17810,"status":"noted","reservation_date":"2019-06-18 11:28:59","uploaded":"2019-06-18 11:46:06","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_134_Sapporo\/Docs\/S2-1907728.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907729","title":"Handling UPF Service Area for UP CIoT Optimisation","source":"Samsung","contact":"Sunghoon Kim","contact-id":59112,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If UPF Service Area is considered by the SMF during PDU Session Establishment procedure, the SMF provides UPF Service Area to the NG-RAN as N2 SM information. NG-RAN uses this information to check whether UE is out of UPF Service Area if UE performs Connection Resume procedure with UL EDT.","secretary_remarks":"Revised in parallel session to S2-1908406.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17820,"status":"revised","reservation_date":"2019-06-18 11:32:14","uploaded":"2019-06-18 11:46:06","revisionof":"","revisedto":"S2-1908406","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1670.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907729.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907733","title":"Clarification on Service Operation for Extended Buffering Support","source":"Samsung","contact":"Sunghoon Kim","contact-id":59112,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding 'Extended Bufffering Support' indication in Nsmf_NIDD_Delivery and Adding 'Extended Buffering Time' in Nsmf_NIDD_Delivery_Response","secretary_remarks":"Agreed in parallel session. This was Block approved","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18480,"status":"agreed","reservation_date":"2019-06-18 11:41:51","uploaded":"2019-06-18 11:46:06","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1646.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907733.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907766","title":"UE Indication of support for the User Plane CIoT Optimisation in RRC","source":"Orange","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding the indication of the support of the User Plane CIoT 5GS Optimisation in the RRC Message that helps the RAN select an AMF. Adding a condition to send the support of the CIoT optimisations in RRC Messages.","secretary_remarks":"Revision of S2-1907156. Revised in parallel session to S2-1908408.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17920,"status":"revised","reservation_date":"2019-06-18 14:06:19","uploaded":"2019-06-18 14:17:15","revisionof":"S2-1907156","revisedto":"S2-1908408","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1510.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907766.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908315","title":"[DRAFT] Reply LS on support for flow based QoS & slicing for NB-IoT & eMTC connected to 5GC","source":"SA WG2","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2, CT WG1, RAN WG3. Attachments: [CR 1461 to 23.501]","secretary_remarks":"Revision of S2-1906925. Revised in parallel session to S2-1908552.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17230,"status":"revised","reservation_date":"2019-07-04 09:15:27","uploaded":"2019-07-04 09:17:59","revisionof":"S2-1906925","revisedto":"S2-1908552","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, CT WG1, RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908315.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908316","title":"Clarifications to QoS support for NB-IoT","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":57486,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: QoS model for NB-IoT: New section to include requirement of only a default QoS rule per PDU session, maximum of 2 Data Radio Bearers. Inter-RAT idle mode mobility to Nb-IoT: SMF needs to initiate PDU sesion modification to remove any non-default QoS rule. Network slicing for NB-IoT: Recommendation to minimize number of subscribed S-NSSAis in subscriptions for NB-IoT UEs.","secretary_remarks":"Revision of S2-1906926. Revised in parallel session to S2-1908441.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17260,"status":"revised","reservation_date":"2019-07-04 09:15:27","uploaded":"2019-07-04 09:17:59","revisionof":"S2-1906926","revisedto":"S2-1908441","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1461.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908316.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908371","title":"[DRAFT] Reply LS on RRC Connection Re-Establishment for CP for NB-IoT connected to 5GC","source":"SA WG2","contact":"Runze Zhou","contact-id":60945,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2, SA WG3. CC: CT WG1, RAN WG3, CT WG4.","secretary_remarks":"Revision of S2-1907719. Revised in parallel session to S2-1908443.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17340,"status":"revised","reservation_date":"2019-07-04 09:16:21","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1907719","revisedto":"S2-1908443","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, SA WG3","Cc":"CT WG1, RAN WG3, CT WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908371.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908372","title":"Aligning Terminology referring to the CIoT 5GS Optimisations","source":"Orange","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Aligning the terminology to 'Control Plane CIoT 5GS Optimisation' and 'User Plane CIoT 5GS Optimisation'.","secretary_remarks":"Revision of S2-1907012. Agreed in parallel session. Not available in time and removed from block approval. For e-mail approval. This CR was agreed","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17620,"status":"agreed","reservation_date":"2019-07-04 09:16:21","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1907012","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1479.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908372.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908373","title":"Handling of CIoT optimisations not supported over NR","source":"ORANGE","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adds a condition for the initiation of EDT by the UE.","secretary_remarks":"Revision of S2-1907153. Agreed in parallel session. Not available in time and removed from block approval. For e-mail approval. This CR was agreed","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17660,"status":"agreed","reservation_date":"2019-07-04 09:16:23","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1907153","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1509.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908373.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908374","title":"Conditions to use CP or UP CIoT","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: All AMF input parameters to determine whether to apply Control Plane Only Indicator or not is enumerated in the summary clause to avoid impression that the AMF local policy alone could determine the use of Control Plane Only Indicator. The use of Control Plane CIoT 5GS Optimisation at the same time as User Plane CIoT 5GS Optimisation is forbidden.","secretary_remarks":"Revision of S2-1907369. Revised in parallel session to S2-1908430.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17480,"status":"revised","reservation_date":"2019-07-04 09:16:25","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1907369","revisedto":"S2-1908430","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1573.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908374.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908375","title":"Conditions to use CP or UP CIoT","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The use of Control Plane CIoT 5GS Optimisation at the same time as User Plane CIoT 5GS Optimisation is forbidden. In the MO case, the step where this applies on the network and the UE is different, since the UE can only detect the availability of N3 data berers at step 13.","secretary_remarks":"Revision of S2-1907370. Agreed in parallel session. This was Block approved","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17740,"status":"agreed","reservation_date":"2019-07-04 09:16:26","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1907370","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1556.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908375.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908376","title":"Clarification on Preferred Network Behaviour for CIoT 5GS Optimisations","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When the UE performs ATTACH\/TAU it includes its 5GC Preferred Network Behaviour if the EPC Preferred Network Behaviour is included. The AMF provides an indication of support of UP CIoT 5GS Optimisations per UE and not a generic indication of support.","secretary_remarks":"Revision of S2-1907713. Agreed in parallel session. This was Block approved","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17770,"status":"agreed","reservation_date":"2019-07-04 09:16:27","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1907713","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1665.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908376.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908377","title":"Clarification on Preferred Network Behaviour for CIoT 5GS Optimisations","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When the UE performs ATTACH\/TAU it includes its 5GC Preferred Network Behaviour if the EPC Preferred Network Behaviour is included.","secretary_remarks":"Revision of S2-1907714. Agreed in parallel session. This was Block approved","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17790,"status":"agreed","reservation_date":"2019-07-04 09:16:29","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1907714","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1643.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908377.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908378","title":"NIDD Configuration Procedure Update for RDS and Maximum Packet Size","source":"Convida Wireless LLC, Intel","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updated the NIDD Configuration procedure for RDS support by adding the Reliable Data Service Configuration parameter to the NIDD Configuration procedure and updating the NIDD Configuration Procedure so that the AF can update the Reliable Data Service configuration (as is done in EPC). Updated the NIDD Configuration procedure so that the Maximum Packet Size is sent to the AF","secretary_remarks":"Revision of S2-1906888. Agreed in parallel session. This was Block approved","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17820,"status":"agreed","reservation_date":"2019-07-04 09:16:31","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1906888","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1373.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908378.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908379","title":"NAS RAI corrections","source":"BlackBerry UK Ltd.","contact":"John-Luc Bakker","contact-id":37326,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change 'no further Uplink and Downlink Data transmissions are expected' into 'no further Uplink and no further Downlink Data transmissions are expected'. Reword undefined condition. RAI has precedence over Expected UE Behavior.","secretary_remarks":"Revision of S2-1906904. Revised in parallel session to S2-1908431.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17620,"status":"revised","reservation_date":"2019-07-04 09:16:32","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1906904","revisedto":"S2-1908431","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1461.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908379.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908380","title":"NAS RAI corrections","source":"BlackBerry UK Ltd.","contact":"John-Luc Bakker","contact-id":37326,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change 'no further Uplink or Downlink Data transmissions are expected' into 'no further Uplink and no further Downlink Data transmissions are expected'.","secretary_remarks":"Revision of S2-1906905. Revised in parallel session to S2-1908432.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17650,"status":"revised","reservation_date":"2019-07-04 09:16:33","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1906905","revisedto":"S2-1908432","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1457.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908380.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908381","title":"Addition of missing CIoT services","source":"Orange","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adds the following services to clause 7.2 with references to TS 23.502: Nsmf_NIDD Nudm_ NIDDAuthorisation Nnef_MSISDN-less_MO_SMS Nnef_NIDDConfiguration Nnef_NIDD Nnef_SMContext Nnef_NetworkStatus Ninef_EventExposure","secretary_remarks":"Revision of S2-1907262. Revised in parallel session to S2-1908433.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17690,"status":"revised","reservation_date":"2019-07-04 09:16:34","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1907262","revisedto":"S2-1908433","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1541.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908381.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908382","title":"Corrections to Control Plane CIoT 5GS Optimisation description","source":"Sony","contact":"Lars Nord","contact-id":82070,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove last part of first sentence Replacing the duplication of text with a reference to the next clause 5.31.4.2 Aligning the term 'user plane resources' in 5.31.4.1 with the term used in 5.31.4.2 'N3 data transfer' in a couple of places","secretary_remarks":"Revision of S2-1907389. Revised in parallel session to S2-1908434.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17730,"status":"revised","reservation_date":"2019-07-04 09:16:37","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1907389","revisedto":"S2-1908434","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1580.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908382.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908383","title":"Corrections to N3 data transfer establishment procedures","source":"Sony","contact":"Lars Nord","contact-id":82070,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 4.2.10.1: Adding 'TS 23.501' to the clause reference, moving text up since it could be read as the 'local decision' is to set the Control Plane Only indicator, adding a missing 'transfer' and use 'established N3 data transfer' instead of 'activated user plane resources' in a couple of places 4.2.10.2: Removing the duplication of text in step 3, moving text up and correcting the wording since it could be read as the 'local decision' is to set the Control Plane Only indicator","secretary_remarks":"Revision of S2-1907390. Revised in parallel session to S2-1908435.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17760,"status":"revised","reservation_date":"2019-07-04 09:16:39","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1907390","revisedto":"S2-1908435","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1565.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908383.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908397","title":"Adding N4 Notification about buffered packets beeing dropped","source":"Nokia, Nokia Shanghai-Bell","contact":"Thomas Belling","contact-id":68266,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The N4 interface is extended with notification about buffered packets being discarded similar to the existing notification about the arrival of the first downlink packet. The request for this notification is expressed via new action values in the FAR. It is also clarified for the existing reporting about the arrival of the first downlink packet that it relates to a Packet Detection Rule (PDR), as this is the way to describe 'user plane path' (existing term) on the N4 interface.","secretary_remarks":"Revision of S2-1906946. Revised in parallel session to S2-1908444.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18050,"status":"revised","reservation_date":"2019-07-04 09:16:58","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1906946","revisedto":"S2-1908444","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1465.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908397.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908398","title":"Update to downlink data delivery status event to support PCC and HR roaming","source":"Nokia, Nokia Shanghai Bell, Ericsson?","contact":"Thomas Belling","contact-id":68266,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Interactions of the SMF with the UPF for subscribing to downlink data delivery status are added to subclause 4.15.3.2.5. Subscription is via UDM. However, if PCC is used, the PCF is notified about the subscription. Then, the subscription to the Nsmf_EventExposure notification is indirect via PCC rule information of the Npcf_SMPolicyControl service and comes from the PCF rather than the UDM. For the home routed roaming case, the V-SMFF and an attached UPF detect downlink data delivery status events and the V-SMF sends related notifications.","secretary_remarks":"Revision of S2-1907002, merging S2-1907493. Revised off-line to S2-1908446.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18080,"status":"revised","reservation_date":"2019-07-04 09:16:59","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1907002","revisedto":"S2-1908446","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1481.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908398.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908399","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: Interactions of the SMF with the UPF for subscribing to downlink data delivery status are added to subclause 4.15.3.2.5. Subscription is via UDM. However, if PCC is used, the PCF is notified about the subscription. Then, the subscription to the Nsmf_EventExposure notification is indirect via PCC rule information of the Npcf_SMPolicyControl service and comes from the PCF rather than the UDM. For the home routed roaming case, the V-SMF and an attached UPF detect downlink data delivery status events and the V-SMF sends related notifications. Traffic filters are an optional input parameter for the Nudm_EventExposure_Subscribe service operation","secretary_remarks":"Revision of S2-1907003. For e-mail approval. Noted","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18380,"status":"noted","reservation_date":"2019-07-04 09:17:00","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1907003","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1482.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908399.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908400","title":"Subscription to downlink data delivery status event via PCC","source":"Nokia, Nokia Shanghai-Bell","contact":"Thomas Belling","contact-id":68266,"tdoctype":"other","for":"Approval","abstract":"WITHDRAWN: Summary of change: The subscription to the Nsmf_EventExposure notification is indirect via PCC rule information of the Npcf_SMPolicyControl service. For that purpose, an AF subscription to downlink data delivery status events IE (similar to the existing Information on AF subscription to UP change events IE) is added to the PCC rule. If PCC is used, the PCF is notified about the subscription to the Downlink data delivery status at the SMF to allow the PCF to provide policies as described above,","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18170,"status":"withdrawn","reservation_date":"2019-07-04 09:17:02","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-16","crspec":23.503,"crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908401","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-1908399, S2-1908551","secretary_remarks":"Revision of S2-1907005. For e-mail approval. Noted","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18350,"status":"noted","reservation_date":"2019-07-04 09:17:02","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1907005","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_134_Sapporo\/Docs\/S2-1908401.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908402","title":"Corrections to information flow for downlink data delivery status","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"other","for":"Approval","abstract":"WITHDRAWN: Summary of change: Changes include: PCF is modified to UDM for monitoring events. IP packet is revised to traffic descriptor. Clarify how the SMF detects a change in Downlink Delivery Status event.","secretary_remarks":"Revision of S2-1907710. WITHDRAWN","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18190,"status":"withdrawn","reservation_date":"2019-07-04 09:17:03","uploaded":null,"revisionof":"S2-1907710","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908403","title":"EPS to 5GS Idle mode mobility with data fowarding","source":"Ericsson,","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A flow describing the data forwarding based on TS 23.401 clause 5.3.3.1A is added.","secretary_remarks":"Revision of S2-1907495. Postponed in parallel session.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18220,"status":"postponed","reservation_date":"2019-07-04 09:17:03","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1907495","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1590.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908403.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908404","title":"Clarification on the buffered data delivery","source":"CATT","contact":"Qiang Deng","contact-id":74437,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the extended data delivery handling for all cases.","secretary_remarks":"Revision of S2-1907656. Agreed in parallel session. This was Block approved","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18470,"status":"agreed","reservation_date":"2019-07-04 09:17:13","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1907656","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1630.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908404.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908406","title":"Handling UPF Service Area for UP CIoT Optimisation","source":"Samsung","contact":"Sunghoon Kim","contact-id":59112,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If NG-RAN determines that it is not able to connect to the UPF which UL N3 tunnel info stored in the UE context is addressing, the NG-RAN performs path switch procedure before sending the MO data.","secretary_remarks":"Revision of S2-1907729. Revised in parallel session to S2-1908436.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17830,"status":"revised","reservation_date":"2019-07-04 09:17:14","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1907729","revisedto":"S2-1908436","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1670.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908406.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908407","title":"Introducing of UP CIoT 5GS Optimisation capability","source":"Ericsson, Samsung (7659)","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding UP CIoT 5GS optimization capability indication in selection functions.","secretary_remarks":"Revision of S2-1907492, merging S2-1907659. Revised in parallel session to S2-1908437.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17860,"status":"revised","reservation_date":"2019-07-04 09:17:15","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1907492","revisedto":"S2-1908437","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1347.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908407.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908408","title":"UE Indication of support for the User Plane CIoT Optimisation in RRC","source":"Orange","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding the indication of the support of the User Plane CIoT 5GS Optimisation in the RRC Message that helps the RAN select an AMF. Adding a condition to send this indication when the UE is using E-UTRA.","secretary_remarks":"Revision of S2-1907766. Revised in parallel session to S2-1908438.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17930,"status":"revised","reservation_date":"2019-07-04 09:17:17","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1907766","revisedto":"S2-1908438","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1510.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908408.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908409","title":"RAI Terminology Alignment on CIoT 5GS Optimisations","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Release Assistance Information\/Indication has been made consistently Release Assistance Information, matching TS 23.501.","secretary_remarks":"Revision of S2-1907715. Agreed in parallel session. This was Block approved","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18220,"status":"agreed","reservation_date":"2019-07-04 09:17:19","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1907715","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1644.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908409.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908410","title":"Removal of eDRX support with RRC_INACTIVE for NB-IoT","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that extended DRX in CM-IDLE is supported by WB-E-UTRA and NB-IoT, extended DRX in CM-CONNECTED with RRC_Inactive is supported by WB-E-UTRA and not NB-IoT and neither is supported by NR. The UEs accepted idle mode extended DRX cycle and parameters are only passed to NG-RAN for RATs that support extended DRX in CM-CONNECTED with RRC_Inactive.","secretary_remarks":"Revision of S2-1907725. Agreed in parallel session. This was Block approved","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18520,"status":"agreed","reservation_date":"2019-07-04 09:17:21","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1907725","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1669.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908410.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908411","title":"Clarify short DRX cycle length CM-CONNECTED with RRC inactive for eMTC","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":57486,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Maximum eDRX cycle value for CM-CONNECTED with RRC inactive is 10.24 seconds.","secretary_remarks":"Revision of S2-1907465. Agreed in parallel session. This was Block approved","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18500,"status":"agreed","reservation_date":"2019-07-04 09:17:22","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1907465","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1596.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908411.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908412","title":"Clarification on strictly periodic timer in relation to MICO mode","source":"Samsung","contact":"Lalith Kumar","contact-id":80547,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If MICO is disabled then periodic registration timer shall not apply indication 'Strictly Periodic Registration Timer Indication'","secretary_remarks":"Revision of S2-1907585. Revised in parallel session to S2-1908439.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18310,"status":"revised","reservation_date":"2019-07-04 09:17:23","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1907585","revisedto":"S2-1908439","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1632.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908412.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908413","title":"Corrections to Small Data Rate Control and Exception Reporting","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce the 'MO Exception data counter' reporting function. A new IE\/flag in the NAS message to indicate whether the embedded PDU is MO Exception Data or not, and the AMF sends an indication to (H-)SMF for indicating that a certain PDU is MO Exception Data, and then onto the UPF\/NEF for PDU Sessions using Control Plane data transfer.","secretary_remarks":"Revision of S2-1907717. Revised in parallel session to S2-1908440.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18410,"status":"revised","reservation_date":"2019-07-04 09:17:25","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1907717","revisedto":"S2-1908440","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1666.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908413.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908430","title":"Conditions to use CP or UP CIoT","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: All AMF input parameters to determine whether to apply Control Plane Only Indicator or not is enumerated in the summary clause to avoid impression that the AMF local policy alone could determine the use of Control Plane Only Indicator. Not only the UE but also the network use N3 user plane resources when they are established.","secretary_remarks":"Revision of S2-1908374. Agreed in parallel session. This was Block approved","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17720,"status":"agreed","reservation_date":"2019-07-04 09:17:53","uploaded":"2019-07-04 09:27:56","revisionof":"S2-1908374","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1573.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908430.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908431","title":"NAS RAI corrections","source":"BlackBerry UK Ltd.","contact":"John-Luc Bakker","contact-id":37326,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Reword undefined condition. RAI has precedence over Expected UE Behavior.","secretary_remarks":"Revision of S2-1908379. Agreed in parallel session. This was Block approved","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17860,"status":"agreed","reservation_date":"2019-07-04 09:17:55","uploaded":"2019-07-04 09:27:56","revisionof":"S2-1908379","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1461.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908431.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908432","title":"NAS RAI corrections","source":"BlackBerry UK Ltd.","contact":"John-Luc Bakker","contact-id":37326,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change 'or' into 'and'.","secretary_remarks":"Revision of S2-1908380. Agreed in parallel session. This was Block approved","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17890,"status":"agreed","reservation_date":"2019-07-04 09:17:57","uploaded":"2019-07-04 09:27:56","revisionof":"S2-1908380","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1457.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908432.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908433","title":"Addition of missing CIoT services","source":"Orange","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adds the following services to clause 7.2 with references to TS 23.502: Nsmf_NIDD Nudm_ NIDDAuthorisation Nnef_MSISDN-less_MO_SMS Nnef_NIDDConfiguration Nnef_NIDD Nnef_SMContext Nnef_NetworkStatus Ninef_EventExposure","secretary_remarks":"Revision of S2-1908381. Agreed in parallel session. Not available in time and removed from block approval. For e-mail approval. This CR was agreed","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17930,"status":"agreed","reservation_date":"2019-07-04 09:17:58","uploaded":"2019-07-04 09:27:56","revisionof":"S2-1908381","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1541.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908433.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908434","title":"Corrections to Control Plane CIoT 5GS Optimisation description","source":"Sony","contact":"Lars Nord","contact-id":82070,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introducing a NOTE to explain for Control Plane CIoT 5GS optimization the term 'user plane resources' or 'user plane connections' refers to radio user plane resouces i.e. Data Radio Bearer and N3 tunnel. Replacing the duplication of text with a reference to the next clause 5.31.4.2","secretary_remarks":"Revision of S2-1908382. Agreed in parallel session. This was Block approved","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17970,"status":"agreed","reservation_date":"2019-07-04 09:17:59","uploaded":"2019-07-04 09:27:56","revisionof":"S2-1908382","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1580.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908434.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908435","title":"Corrections to N3 data transfer establishment procedures","source":"Sony","contact":"Lars Nord","contact-id":82070,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 4.2.10.1: Adding 'TS 23.501' to the clause reference, moving text up since it could be read as the 'local decision' is to set the Control Plane Only indicator, adding a missing 'transfer' and use 'established N3 data transfer' instead of 'activated user plane resources' in a couple of places 4.2.10.2: Removing the duplication of text in step 3, moving text up and correcting the wording since it could be read as the 'local decision' is to set the Control Plane Only indicator","secretary_remarks":"Revision of S2-1908383. Agreed in parallel session. This was Block approved","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18000,"status":"agreed","reservation_date":"2019-07-04 09:33:16","uploaded":"2019-07-04 09:37:57","revisionof":"S2-1908383","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1565.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908435.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908436","title":"UPF Service Area awareness for keeping UL N3 Tunnel available","source":"Samsung","contact":"Sunghoon Kim","contact-id":59112,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If NG-RAN determines that it is not able to connect to the UPF which UL N3 tunnel info stored in the UE context is addressing, the NG-RAN performs path switch procedure before sending the MO data.","secretary_remarks":"Revision of S2-1908406. Agreed in parallel session. This was Block approved","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18070,"status":"agreed","reservation_date":"2019-07-04 09:18:03","uploaded":"2019-07-04 09:27:56","revisionof":"S2-1908406","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1670.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908436.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908437","title":"Introducing of UP CIoT 5GS Optimisation capability","source":"Ericsson, Samsung","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding UP CIoT 5GS optimization capability indication in selection functions.","secretary_remarks":"Revision of S2-1908407. Revised in parallel session to S2-1908445.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17870,"status":"revised","reservation_date":"2019-07-04 09:18:04","uploaded":"2019-07-04 09:27:56","revisionof":"S2-1908407","revisedto":"S2-1908445","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1347.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908437.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908438","title":"UE Indication of support for the User Plane CIoT Optimisation in RRC Message when RAT Type is not NR","source":"Orange","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding the indication of the support of the User Plane CIoT 5GS Optimisation in the RRC Message that helps the RAN select an AMF. Adding a condition to send this indication when the UE is using E-UTRA.","secretary_remarks":"Revision of S2-1908408. Agreed in parallel session. Not available in time and removed from block approval. For e-mail approval. This CR was agreed","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18170,"status":"agreed","reservation_date":"2019-07-04 09:18:05","uploaded":"2019-07-04 09:27:56","revisionof":"S2-1908408","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1510.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908438.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908439","title":"Clarification on strictly periodic timer in relation to MICO mode","source":"Samsung","contact":"Lalith Kumar","contact-id":80547,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If MICO is disabled then periodic registration timer shall not apply indication 'Strictly Periodic Registration Timer Indication'","secretary_remarks":"Revision of S2-1908412. Revised in parallel session to S2-1908550.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18320,"status":"revised","reservation_date":"2019-07-04 09:18:06","uploaded":"2019-07-04 09:27:56","revisionof":"S2-1908412","revisedto":"S2-1908550","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1632.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908439.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908440","title":"Corrections to Small Data Rate Control and Exception Reporting","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce the 'MO Exception data counter' reporting function. A new IE\/flag in the NAS message to indicate whether the embedded PDU is MO Exception Data or not, and the AMF sends an indication to (H-)SMF for indicating that a certain PDU is MO Exception Data, and then onto the UPF\/NEF for PDU Sessions using Control Plane data transfer.","secretary_remarks":"Revision of S2-1908413. Agreed in parallel session. Removed from block apprval. For e-mail approval. Postponed","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18650,"status":"postponed","reservation_date":"2019-07-04 09:18:07","uploaded":"2019-07-04 09:27:56","revisionof":"S2-1908413","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1666.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908440.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908441","title":"Clarifications to QoS support for NB-IoT","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":57486,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: QoS model for NB-IoT: New section to include requirement of only a default QoS rule per PDU session, maximum of 2 Data Radio Bearers. Inter-RAT idle mode mobility to Nb-IoT: SMF needs to initiate PDU sesion modification to remove any non-default QoS rule. Network slicing for NB-IoT: Recommendation to minimize number of subscribed S-NSSAis in subscriptions for NB-IoT UEs.","secretary_remarks":"Revision of S2-1908316. Agreed in parallel session. This was Block approved","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17500,"status":"agreed","reservation_date":"2019-07-04 09:18:08","uploaded":"2019-07-04 09:27:56","revisionof":"S2-1908316","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1461.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908441.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908443","title":"[DRAFT] Reply LS on RRC Connection Re-Establishment for CP for NB-IoT connected to 5GC","source":"SA WG2","contact":"Runze Zhou","contact-id":60945,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2, SA WG3. CC: CT WG1, RAN WG3, CT WG4.","secretary_remarks":"Revision of S2-1908371. Revised in parallel session to S2-1908553.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17350,"status":"revised","reservation_date":"2019-07-04 09:18:09","uploaded":"2019-07-04 09:27:56","revisionof":"S2-1908371","revisedto":"S2-1908553","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, SA WG3","Cc":"CT WG1, RAN WG3, CT WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908443.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908444","title":"Adding N4 Notification about buffered packets being dropped","source":"Nokia, Nokia Shanghai-Bell","contact":"Thomas Belling","contact-id":68266,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The N4 interface is extended with notification about buffered packets being discarded similar to the existing notification about the arrival of the first downlink packet. The request for this notification is expressed via new action values in the FAR. It is also clarified for the existing reporting about the arrival of the first downlink packet that it relates to a Packet Detection Rule (PDR), as this is the way to describe 'user plane path' (existing term) on the N4 interface.","secretary_remarks":"Revision of S2-1908397. Agreed in parallel session. Not available in time and removed from block approval. For e-mail approval. This CR was agreed","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18290,"status":"agreed","reservation_date":"2019-07-04 09:18:09","uploaded":"2019-07-04 09:27:56","revisionof":"S2-1908397","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1465.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908444.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908445","title":"Introducing of UP CIoT 5GS Optimisation capability","source":"Ericsson, Samsung","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding UP CIoT 5GS optimization capability indication in selection functions.","secretary_remarks":"Revision of S2-1908437. Revised in parallel session to S2-1908549.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17880,"status":"revised","reservation_date":"2019-07-04 09:18:11","uploaded":"2019-07-04 09:27:56","revisionof":"S2-1908437","revisedto":"S2-1908549","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1347.0,"crrevision":4.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908445.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908446","title":"Update to downlink data delivery status event to support PCC and HR roaming","source":"Nokia, Nokia Shanghai Bell","contact":"Thomas Belling","contact-id":68266,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Interactions of the SMF with the UPF for subscribing to downlink data delivery status are added to subclause 4.15.3.2.5. Subscription is via UDM. However, if PCC is used, the PCF is notified about the subscription. Then, the subscription to the Nsmf_EventExposure notification is indirect via PCC rule information of the Npcf_SMPolicyControl service and comes from the PCF rather than the UDM. For the home routed roaming case, the V-SMFF and an attached UPF detect downlink data delivery status events and the V-SMF sends related notifications.","secretary_remarks":"Revision of S2-1908398. Revised in parallel session, merging S2-1907710, to S2-1908551.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18090,"status":"revised","reservation_date":"2019-07-04 09:18:12","uploaded":"2019-07-04 09:27:56","revisionof":"S2-1908398","revisedto":"S2-1908551","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1481.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908446.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908549","title":"Introducing of UP CIoT 5GS Optimisation capability","source":"Ericsson, Samsung","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding UP CIoT 5GS optimization capability indication in selection functions.","secretary_remarks":"Revision of S2-1908445. Revised in parallel session to S2-1908560.","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17890,"status":"revised","reservation_date":"2019-07-04 09:18:49","uploaded":"2019-07-04 09:27:56","revisionof":"S2-1908445","revisedto":"S2-1908560","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1347.0,"crrevision":5.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908549.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908550","title":"Clarification on strictly periodic timer in relation to MICO mode.","source":"Samsung","contact":"Lalith Kumar","contact-id":80547,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If MICO is disabled then periodic registration timer shall not apply indication 'Strictly Periodic Registration Timer Indication'","secretary_remarks":"Revision of S2-1908439. Agreed in parallel session. This was Block approved","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18560,"status":"agreed","reservation_date":"2019-07-04 09:18:50","uploaded":"2019-07-04 09:27:56","revisionof":"S2-1908439","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1632.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908550.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908551","title":"Update to downlink data delivery status event to support PCC and HR roaming","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. Notifications only relate to the first packets. For the home routed roaming case, the V-SMFF and an attached UPF detect downlink data delivery status events and the V-SMF sends related notifications. Procedures apply to both IP and Ethernet traffic.","secretary_remarks":"Revision of S2-1908446, merging S2-1907710. Agreed in parallel session. This was Block approved","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18330,"status":"agreed","reservation_date":"2019-07-04 09:18:51","uploaded":"2019-07-04 09:27:56","revisionof":"S2-1908446","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_CIoT"}],"crnumber":1481.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908551.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908552","title":"Reply LS on support for flow based QoS & slicing for NB-IoT & eMTC connected to 5GC","source":"SA WG2","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2, CT WG1, RAN WG3. Attachments: S2-1908441 [CR#1461 to TS 23.501].","secretary_remarks":"Revision of S2-1908315. Agreed in parallel session. This was Block approved","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17240,"status":"approved","reservation_date":"2019-07-04 09:18:52","uploaded":"2019-07-04 09:27:56","revisionof":"S2-1908315","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1906863","lsto":"RAN WG2, CT WG1, RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908552.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908553","title":"Reply LS on RRC Connection Re-Establishment for CP for NB-IoT connected to 5GC","source":"SA WG2","contact":"Dario Serafino Tonesi","contact-id":43468,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2, SA WG3. CC: CT WG1, RAN WG3, CT WG4.","secretary_remarks":"Revision of S2-1908443. Agreed in parallel session. This was Block approved","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":17360,"status":"approved","reservation_date":"2019-07-04 09:18:52","uploaded":"2019-07-04 09:27:56","revisionof":"S2-1908443","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1906867","lsto":"RAN WG2, SA WG3","Cc":"CT WG1, RAN WG3, CT WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908553.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908560","title":"Introducing of UP CIoT 5GS Optimisation capability","source":"Ericsson, Samsung","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding UP CIoT 5GS optimization capability indication in selection functions.","secretary_remarks":"Revision of S2-1908549. Agreed in parallel session. This was Block approved","agenda_item_sort_order":36,"ainumber":"6.9.2","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT) - Maintenance","tdoc_agenda_sort_order":18130,"status":"agreed","reservation_date":"2019-07-04 09:18:54","uploaded":"2019-07-04 09:27:56","revisionof":"S2-1908549","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":1347.0,"crrevision":6.0,"crcategory":"F","tsg_crp":"SP-190605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908560.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]