[{"name":"S5-254230","title":"Rel-20 CR TS 28.541 CR Correction to X2HOBlockList","source":"Rakuten Mobile, Inc.","contact":"Ravi Chamarty","contact-id":105494,"tdoctype":"CR","for":"Agreement","abstract":"","secretary_remarks":"Title modified on 10\/2\/2025. Original title : Rel-20 CR 28.541 Correction to X2HOBlockList<br\/><br\/>Source modified on 10\/2\/2025. Original source : Rakuten Mobile, Inc","agenda_item_sort_order":74,"ainumber":"6.20","ainame":"OAM Rel-20 small enhancements","tdoc_agenda_sort_order":42300,"status":"agreed","reservation_date":"2025-09-30 16:26:18","uploaded":"2025-10-02 17:52:58","revisionof":"","revisedto":"","release":"Rel-20","crspec":"28.541","crspecversion":"20.0.0","workitem":[{"winame":"TEI20"}],"crnumber":1603.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-251386","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG5_TM\/TSGS5_163\/Docs\/S5-254230.zip","group":"S5","meeting":"S5-163","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":false,"clauses_affected":"4.3.2.2, 4.3.2.3, 4.4.1, Normative stage 3 code is in Forge","crsinpack":null,"crsinpacknumber":0},
{"name":"S5-254281","title":"Rel-20 CR TS 28.622 Correct several issues for the IOCs related to MADCOL","source":"Huawei","contact":"Ruiyue Xu","contact-id":61969,"tdoctype":"CR","for":"Agreement","abstract":"","secretary_remarks":"","agenda_item_sort_order":74,"ainumber":"6.20","ainame":"OAM Rel-20 small enhancements","tdoc_agenda_sort_order":42810,"status":"revised","reservation_date":"2025-10-01 04:25:01","uploaded":"2025-10-03 02:08:09","revisionof":"","revisedto":"","release":"Rel-20","crspec":"28.622","crspecversion":"20.0.0","workitem":[{"winame":"TEI20"}],"crnumber":599.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG5_TM\/TSGS5_163\/Docs\/S5-254281.zip","group":"S5","meeting":"S5-163","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S5-254282","title":"Rel-20 CR TS 28.623 Correct several issues for the IOCs related to MADCOL","source":"Huawei","contact":"Ruiyue Xu","contact-id":61969,"tdoctype":"CR","for":"Agreement","abstract":"","secretary_remarks":"Source modified on 10\/3\/2025. Original source : Huawei","agenda_item_sort_order":74,"ainumber":"6.20","ainame":"OAM Rel-20 small enhancements","tdoc_agenda_sort_order":42820,"status":"revised","reservation_date":"2025-10-01 04:26:39","uploaded":"2025-10-03 02:08:09","revisionof":"","revisedto":"S5-254643","release":"Rel-20","crspec":"28.623","crspecversion":"19.5.0","workitem":[{"winame":"TEI20"}],"crnumber":576.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG5_TM\/TSGS5_163\/Docs\/S5-254282.zip","group":"S5","meeting":"S5-163","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"Following YAML files normatively defined in the forge are updated: - OpenAPI\/TS28623_ManagementDataCollectionNrm.yaml","crsinpack":null,"crsinpacknumber":0},
{"name":"S5-254339","title":"DP Clarify use of choice","source":"Ericsson Hungary Ltd","contact":"Balazs Lengyel","contact-id":81420,"tdoctype":"discussion","for":"Endorsement","abstract":"The usage of \"choice\" in NRMs and its definition of \"choice\" in TS 32.156 do not match.\nIn this discussion paper we adapt the YANG terminology where a \"choice\" is a possibility to select between different \"cases\", where each case may contain one or several items or data types. Having different terms for the \"choice\" and the alternative \"cases\" helps understanding.\nObservation 1: In 32.156 clause 5.3.6 choice is defined as \"represents one of a set of classes or one of a set of data types\". In the NRMs (e.g. 28.622, 28.111, 28.541) choices are used mostly to indicate a choice between attributes or a set of attributes. In a smaller number of  cases it is used to choose between data types.\nObservation 2: . In case of chosing between attributes, it is assumed, but never specified that only one of the cases can be selected. There is no way to specify whether it is allowed to select none of the cases, or if selecting one case is mandatory.\nObservation 3: . In a smaller number of  cases choice is used to chose between data types. However, the format of defining such a choice is not defined and not uniform. Below are 2 examples of how it is documented:\n...\nObservation 4: How to format the specification of a choice is not described in 32.156. Some figures are present which provide little information, as they have no relation to the actual format used in NRMs. While TS 32.160 describes the format for chosing between attribute(field)s, it provides no guidance about specifying choices between datatypes. There were complaints that specifying the format in a separate document is bad, and the current format is complicated.\nObservation 5: . The second number of choice (between attributes\/attribute sets) does not convey any useful information, and is sometimes mistaken as a subchoice. (E.g. CHOICE_2_3 means the third attribute of the second case, however it was misinterpreted such that you first chose between CHOICE _1,  2 and 3. Once you have chosen  CHOICE_2 you have to chose one of sub-choices . CHOICE_2_1 or CHOICE_2_2 or CHOICE_2_3. \n\n\nRecommendation 1: Update the TS 32.156 definition of choice. \nRecommendation 2: Update the TS 32.160 clause 5.2 W4.3.a  Attributes to indicate how to define a choice of different data types.\nRecommendation 3: Update the TS 32.160 to make the second number in a CHOICE_<X>.<Y> (\"Y\") optional, preferably not used.\n\n4\tDetailed proposal \nEndorse the modification of TS 32.156 and 32.160 according to recommendation 1, 2 and 3 for release-20.","secretary_remarks":"","agenda_item_sort_order":74,"ainumber":"6.20","ainame":"OAM Rel-20 small enhancements","tdoc_agenda_sort_order":43390,"status":"endorsed","reservation_date":"2025-10-01 16:46:33","uploaded":"2025-10-01 17:33:28","revisionof":"","revisedto":"","release":"Rel-20","crspec":"","crspecversion":"","workitem":[{"winame":"TEI20"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG5_TM\/TSGS5_163\/Docs\/S5-254339.zip","group":"S5","meeting":"S5-163","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S5-254340","title":"Rel-20 CR 28.623 Indicate disturbance","source":"Ericsson Hungary Ltd","contact":"Balazs Lengyel","contact-id":81420,"tdoctype":"CR","for":"Agreement","abstract":"","secretary_remarks":"","agenda_item_sort_order":74,"ainumber":"6.20","ainame":"OAM Rel-20 small enhancements","tdoc_agenda_sort_order":43400,"status":"agreed","reservation_date":"2025-10-01 16:51:38","uploaded":"2025-10-01 17:43:36","revisionof":"","revisedto":"","release":"Rel-20","crspec":"28.623","crspecversion":"19.5.0","workitem":[{"winame":"TEI20"}],"crnumber":577.0,"crrevision":"","crcategory":"B","tsg_crp":"SP-251386","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG5_TM\/TSGS5_163\/Docs\/S5-254340.zip","group":"S5","meeting":"S5-163","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S5-254589","title":"Rel-20 CR TS28.541 Fix multiplicity and isOrdered property for hniList","source":"ZTE Corporation","contact":"Bangqiu Ruan","contact-id":96106,"tdoctype":"CR","for":"Agreement","abstract":"","secretary_remarks":"Source modified on 10\/3\/2025. Original source : ZTE Corporation","agenda_item_sort_order":74,"ainumber":"6.20","ainame":"OAM Rel-20 small enhancements","tdoc_agenda_sort_order":45890,"status":"revised","reservation_date":"2025-10-03 17:03:31","uploaded":"2025-10-03 21:11:38","revisionof":"","revisedto":"S5-254644","release":"Rel-20","crspec":"28.541","crspecversion":"20.0.0","workitem":[{"winame":"TEI20"}],"crnumber":1637.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG5_TM\/TSGS5_163\/Docs\/S5-254589.zip","group":"S5","meeting":"S5-163","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.4.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S5-254643","title":"Rel-20 CR TS 28.623 Correct several issues for the IOCs related to MADCOL","source":"Huawei","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"CR","for":"Agreement","abstract":"","secretary_remarks":"","agenda_item_sort_order":74,"ainumber":"6.20","ainame":"OAM Rel-20 small enhancements","tdoc_agenda_sort_order":42821,"status":"revised","reservation_date":"2025-10-21 05:44:40","uploaded":"2025-10-21 05:51:06","revisionof":"S5-254282","revisedto":"S5-254890","release":"Rel-20","crspec":"28.623","crspecversion":"19.5.0","workitem":[{"winame":"TEI20"}],"crnumber":576.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG5_TM\/TSGS5_163\/Docs\/S5-254643.zip","group":"S5","meeting":"S5-163","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S5-254644","title":"Rel-20 CR TS28.541 Fix multiplicity and isOrdered property for hniList","source":"ZTE Corporation","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"CR","for":"Agreement","abstract":"","secretary_remarks":"Source modified on 21\/10\/2025. Original source : ZTE Corporation","agenda_item_sort_order":74,"ainumber":"6.20","ainame":"OAM Rel-20 small enhancements","tdoc_agenda_sort_order":45891,"status":"agreed","reservation_date":"2025-10-21 05:45:11","uploaded":"2025-10-21 05:51:06","revisionof":"S5-254589","revisedto":"","release":"Rel-20","crspec":"28.541","crspecversion":"20.0.0","workitem":[{"winame":"TEI20"}],"crnumber":1637.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-251386","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG5_TM\/TSGS5_163\/Docs\/S5-254644.zip","group":"S5","meeting":"S5-163","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.4.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S5-254890","title":"Rel-20 CR TS 28.623 Correct several issues for the IOCs related to MADCOL","source":"Huawei","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"CR","for":"Agreement","abstract":"","secretary_remarks":"","agenda_item_sort_order":74,"ainumber":"6.20","ainame":"OAM Rel-20 small enhancements","tdoc_agenda_sort_order":42822,"status":"agreed","reservation_date":"2025-10-21 05:56:01","uploaded":"2025-10-21 06:01:09","revisionof":"S5-254643","revisedto":"","release":"Rel-20","crspec":"28.623","crspecversion":"19.5.0","workitem":[{"winame":"TEI20"}],"crnumber":576.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-251386","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG5_TM\/TSGS5_163\/Docs\/S5-254890.zip","group":"S5","meeting":"S5-163","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]