[{"name":"S2-2310150","title":"On the use of Namf_Communication_N1N2MessageTransfer instead of Namf_MT_EnableUEReachability service operation.","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"discussion","for":"Decision","abstract":"The contribution argues that the Namf_Communication_N1N2MessageTransfer service can be used in all cases where the Namf_MT_EnableUEReachability service is used.","secretary_remarks":"Revision of S2-2308404. Not Handled","agenda_item_sort_order":29,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT)","tdoc_agenda_sort_order":10800,"status":"not treated","reservation_date":"2023-09-21 15:14:04","uploaded":"2023-09-29 16:57:56","revisionof":"S2-2308404","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310150.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310151","title":"How to handle the erroneous call flow on Mobile Terminated Data Transport in Control Plane CIoT 5GS Optimisation across releases .","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"discussion","for":"Decision","abstract":"The contribution describes the errors in the call flow on Mobile Terminated Data Transport in Control Plane CIoT 5GS Optimisation and proposes how to fix the problem across multiple releases.","secretary_remarks":"Revision of S2-2309253. Not Handled","agenda_item_sort_order":29,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT)","tdoc_agenda_sort_order":10810,"status":"not treated","reservation_date":"2023-09-21 15:15:09","uploaded":"2023-09-29 16:57:56","revisionof":"S2-2309253","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310151.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310152","title":"Correction to UPF anchored Mobile Terminated Data Transport in Control Plane CIoT 5GS Optimisation","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: As discussed in S2-2310151, the following changes are proposed: 1. For buffering in the UPF, when the UE is not reachable, it is proposed that the SMF should retry the Namf_Communication_N1N2MessageTransfer request to the AMF shortly ahead of the Estimated Maximum Wait time. 2. For buffering in the SMF, when the UE is not reachable, it is proposed that the SMF should retry the Namf_MT_EnableUEReachability request to the AMF shortly ahead of the Estimated Maximum Wait time. 3. Steps 7a, 7b and 7c are enclosed in a Failure cases box. 4. Moreover, based on the discussion in S2-2310150, added NOTEs to clarify that the SMF can also invoke the Namf_Communication_N1N2MessageTransfer service operation instead of the Namf_MT_EnableUEReachability service operation.","secretary_remarks":"Revision of S2-2308405. Revised in parallel session to S2-2311484 (withdrawn). Postponed in parallel session","agenda_item_sort_order":29,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT)","tdoc_agenda_sort_order":10820,"status":"revised","reservation_date":"2023-09-21 15:16:07","uploaded":"2023-09-29 16:57:56","revisionof":"S2-2308405","revisedto":"S2-2311484, S2-2312010","release":"Rel-16","crspec":"23.502","crspecversion":"16.17.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":4253.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310152.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.24.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310153","title":"Correction to UPF anchored Mobile Terminated Data Transport in Control Plane CIoT 5GS Optimisation","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Rel-17 mirror CR: Summary of change: As discussed in S2-2310151, the following changes are proposed: 1. For buffering in the UPF, when the UE is not reachable, it is proposed that the SMF should retry the Namf_Communication_N1N2MessageTransfer request to the AMF shortly ahead of the Estimated Maximum Wait time. 2. For buffering in the SMF, when the UE is not reachable, it is proposed that the SMF should retry the Namf_MT_EnableUEReachability request to the AMF shortly ahead of the Estimated Maximum Wait time. 3. Steps 7a, 7b and 7c are enclosed in a Failure cases box. 4. Moreover, based on the discussion in S2-2310150, added NOTEs to clarify that the SMF can also invoke the Namf_Communication_N1N2MessageTransfer service operation instead of the Namf_MT_EnableUEReachability service operation.","secretary_remarks":"Revision of S2-2308406. Revised in parallel session to S2-2311485 (withdrawn). Postponed in parallel session.","agenda_item_sort_order":29,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT)","tdoc_agenda_sort_order":10840,"status":"revised","reservation_date":"2023-09-21 15:17:54","uploaded":"2023-09-29 16:57:56","revisionof":"S2-2308406","revisedto":"S2-2311485, S2-2312011","release":"Rel-17","crspec":"23.502","crspecversion":"17.10.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":4254.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310153.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.24.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310154","title":"Correction to UPF anchored Mobile Terminated Data Transport in Control Plane CIoT 5GS Optimisation","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: As discussed in S2-2310151, the following changes are proposed: 1. Clarified that, when UE is not reachable, the following happens: If UE is in MICO mode, the procedure ends in step 2d (or step 2h). If UE is configured for extended idle mode DRX, the AMF stores the information received in the SMF request and proceeds with the rest of the procedure when the UE becomes reachable. Note that a similar clarification was made in SA WG2#157 in the context of the NR_RedCap work item (refer to S2-2307731). In steps 2d\/2h the AMF implicitly subscribes the SMF for notification when the UE becomes reachable. 2. Step 8a has been taken out of the Buffering configured in the UPF box, as it is used to indicate a successful outcome for both buffering in UPF and buffering in SMF. The service operation in step 8a is now a notification (Namf_EventExposureNotify), in response to the implicit subscription in steps 2d\/2h. 3. Steps 7a, 7b and 7c are enclosed in a Failure cases box. 4. Moreover, based on the discussion in S2-2310150, added NOTEs to clarify that the SMF can also invoke the Namf_Communication_N1N2MessageTransfer service operation instead of the Namf_MT_EnableUEReachability service operation. In future similar NOTEs could be introduced in other clauses (e.g. clause 4.8.2.2b).","secretary_remarks":"Revision of S2-2308407. Revised in parallel session to S2-2311486.","agenda_item_sort_order":29,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT)","tdoc_agenda_sort_order":10860,"status":"revised","reservation_date":"2023-09-21 15:18:59","uploaded":"2023-09-29 16:57:56","revisionof":"S2-2308407","revisedto":"S2-2311486","release":"Rel-18","crspec":"23.502","crspecversion":"18.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":4255.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310154.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310387","title":"MICO capability synchronization","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update description in steps of the registration procedure to synch with the term MICO Indication defined in CT WG1 specification.","secretary_remarks":"Agreed in parallel session. Block approved","agenda_item_sort_order":29,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT)","tdoc_agenda_sort_order":10890,"status":"agreed","reservation_date":"2023-09-27 19:18:45","uploaded":"2023-09-29 20:28:45","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.502","crspecversion":"18.3.0","workitem":[{"winame":"5G_CIoT"},{"winame":" TEI18"}],"crnumber":4483.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-231248","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310387.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.2.2.2.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311016","title":"Support of NR coverage enhancements","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the references to the RAN E-UTRA and NR specifications to indicate the support of EC and EC restriction correctly.","secretary_remarks":"Revised in parallel session to S2-2311487.","agenda_item_sort_order":29,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT)","tdoc_agenda_sort_order":10900,"status":"revised","reservation_date":"2023-09-29 10:44:00","uploaded":"2023-09-29 11:16:22","revisionof":"","revisedto":"S2-2311487","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"5G_CIoT"},{"winame":" TEI18"}],"crnumber":5041.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311016.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":true,"cn_affected":false,"clauses_affected":"5.31.12, 5.31.13","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311484","title":"Correction to UPF anchored Mobile Terminated Data Transport in Control Plane CIoT 5GS Optimisation","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: As discussed in S2-2310151, the following changes are proposed: 1. For buffering in the UPF, when the UE is not reachable, it is proposed that the SMF should retry the Namf_Communication_N1N2MessageTransfer request to the AMF shortly ahead of the Estimated Maximum Wait time. 2. For buffering in the SMF, when the UE is not reachable, it is proposed that the SMF should retry the Namf_MT_EnableUEReachability request to the AMF shortly ahead of the Estimated Maximum Wait time. 3. Steps 7a, 7b and 7c are enclosed in a Failure cases box. 4. Moreover, based on the discussion in S2-2310150, added NOTEs to clarify that the SMF can also invoke the Namf_Communication_N1N2MessageTransfer service operation instead of the Namf_MT_EnableUEReachability service operation.","secretary_remarks":"Revision of S2-2310152. WITHDRAWN","agenda_item_sort_order":29,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT)","tdoc_agenda_sort_order":10830,"status":"withdrawn","reservation_date":"2023-10-10 06:02:50","uploaded":null,"revisionof":"S2-2310152","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.17.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":4253.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311485","title":"Correction to UPF anchored Mobile Terminated Data Transport in Control Plane CIoT 5GS Optimisation","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Rel-17 mirror CR: Summary of change: As discussed in S2-2310151, the following changes are proposed: 1. For buffering in the UPF, when the UE is not reachable, it is proposed that the SMF should retry the Namf_Communication_N1N2MessageTransfer request to the AMF shortly ahead of the Estimated Maximum Wait time. 2. For buffering in the SMF, when the UE is not reachable, it is proposed that the SMF should retry the Namf_MT_EnableUEReachability request to the AMF shortly ahead of the Estimated Maximum Wait time. 3. Steps 7a, 7b and 7c are enclosed in a Failure cases box. 4. Moreover, based on the discussion in S2-2310150, added NOTEs to clarify that the SMF can also invoke the Namf_Communication_N1N2MessageTransfer service operation instead of the Namf_MT_EnableUEReachability service operation.","secretary_remarks":"Revision of S2-2310153. WITHDRAWN","agenda_item_sort_order":29,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT)","tdoc_agenda_sort_order":10850,"status":"withdrawn","reservation_date":"2023-10-10 06:02:51","uploaded":null,"revisionof":"S2-2310153","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.10.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":4254.0,"crrevision":2.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311486","title":"Correction to UPF anchored Mobile Terminated Data Transport in Control Plane CIoT 5GS Optimisation","source":"Intel, Ericsson, E","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: As discussed in S2-2310151, the following changes are proposed: 1. Clarified that, when UE is not reachable, the following happens: If UE is in MICO mode, the procedure ends in step 2d (or step 2h). If UE is configured for extended idle mode DRX, the AMF stores the information received in the SMF request and proceeds with the rest of the procedure when the UE becomes reachable. Note that a similar clarification was made in SA WG2#157 in the context of the NR_RedCap work item (refer to S2-2307731). In steps 2d\/2h the AMF implicitly subscribes the SMF for notification when the UE becomes reachable. 2. Step 8a has been taken out of the Buffering configured in the UPF box, as it is used to indicate a successful outcome for both buffering in UPF and buffering in SMF. The service operation in step 8a is now a notification (Namf_EventExposureNotify), in response to the implicit subscription in steps 2d\/2h. 3. Steps 7a, 7b and 7c are enclosed in a Failure cases box. 4. Moreover, based on the discussion in S2-2310150, added NOTEs to clarify that the SMF can also invoke the Namf_Communication_N1N2MessageTransfer service operation instead of the Namf_MT_EnableUEReachability service operation. In future similar NOTEs could be introduced in other clauses (e.g. clause 4.8.2.2b).","secretary_remarks":"Revision of S2-2310154. Revised in parallel session to S2-2311793.<br\/><br\/>Source modified on 16\/10\/2023. Original source : Intel, Ericsson","agenda_item_sort_order":29,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT)","tdoc_agenda_sort_order":10870,"status":"revised","reservation_date":"2023-10-10 06:02:51","uploaded":"2023-10-16 11:31:14","revisionof":"S2-2310154","revisedto":"S2-2311793","release":"Rel-18","crspec":"23.502","crspecversion":"18.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":4255.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311486.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311487","title":"Support of NR coverage enhancements","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the references to the RAN E-UTRA and NR specifications to indicate the support of EC and EC restriction correctly.","secretary_remarks":"Revision of S2-2311016. Revised in parallel session to S2-2311891.<br\/><br\/>Source modified on 16\/10\/2023. Original source : Nokia, Nokia Shanghai Bell","agenda_item_sort_order":29,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT)","tdoc_agenda_sort_order":10910,"status":"revised","reservation_date":"2023-10-10 06:02:52","uploaded":"2023-10-16 11:31:14","revisionof":"S2-2311016","revisedto":"S2-2311891","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"5G_CIoT"},{"winame":" TEI18"}],"crnumber":5041.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311487.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":true,"cn_affected":false,"clauses_affected":"5.31.12, 5.31.13","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311793","title":"Correction to UPF anchored Mobile Terminated Data Transport in Control Plane CIoT 5GS Optimisation","source":"Intel, Ericsson","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Clarified that, when UE is not reachable, the following happens: If UE is in MICO mode, the procedure ends in step 2h. If UE is configured for extended idle mode DRX, the AMF takes a note of the SMF s request and proceeds with the rest of the procedure when the UE becomes reachable. Note that a similar clarification was made in SA WG2#157 in the context of the NR_RedCap_Ph2 work item (refer to S2-2307731). In steps 2d\/2h the AMF considers the SMF implicitly subscribed for notification when the UE becomes reachable. 2. Step 8a has been taken out of the Buffering configured in the UPF box and has been replaced with steps 8aa and 8ab: - step 8aa (Namf_MT-EnableUEReachability Response) applies when the AMF has determined in step 2c that the UE was reachable - step 8ab (Namf_EventExposure Notify) applies when in step 2d or 2h the AMF has considered the implicitly subscribed for notification when the UE becomes reachable. 3. Step 8e has been taken out of the Buffering configured in UPF box because it applies to both buffering in UPF and buffering in SMF (in the latter case only if in step 2h the AMF has considered the SMF implicitly subscribed for notification when the UE becomes reachable). 4. Steps 7a, 7b and 7c are enclosed in a Failure cases box.","secretary_remarks":"Revision of S2-2311486. Agreed in parallel session. Block approved. Revised at S2#160 in S2-2312009","agenda_item_sort_order":29,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT)","tdoc_agenda_sort_order":10880,"status":"revised","reservation_date":"2023-10-16 08:39:53","uploaded":"2023-10-16 11:31:16","revisionof":"S2-2311486","revisedto":"S2-2312009","release":"Rel-18","crspec":"23.502","crspecversion":"18.3.0","workitem":[{"winame":"5G_CIoT"}],"crnumber":4255.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311793.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311891","title":"Support of NR coverage enhancements","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the references to the RAN E-UTRA and NR specifications to indicate the support of EC and EC restriction correctly.","secretary_remarks":"Revision of S2-2311487. Revised to S2-2311906.","agenda_item_sort_order":29,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT)","tdoc_agenda_sort_order":10920,"status":"revised","reservation_date":"2023-10-16 08:40:22","uploaded":"2023-10-16 11:31:17","revisionof":"S2-2311487","revisedto":"S2-2311906","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"5G_CIoT"},{"winame":" TEI18"}],"crnumber":5041.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311891.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311906","title":"Support of NR coverage enhancements","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clauses 5.31.12 and 5.31.13 were written for E-UTRA, so the text is updated to it explicitly.","secretary_remarks":"Revision of S2-2311891. This was approved.","agenda_item_sort_order":29,"ainumber":"7.4","ainame":"Cellular IoT support and evolution for the 5G System (5G_CIoT)","tdoc_agenda_sort_order":10930,"status":"agreed","reservation_date":"2023-10-16 08:40:39","uploaded":"2023-10-16 11:31:17","revisionof":"S2-2311891","revisedto":"","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"5G_CIoT"},{"winame":" TEI18"}],"crnumber":5041.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-231248","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311906.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]