[{"name":"R5-256174","title":"6G Testing discussion","source":"Huawei, HiSilicon","contact":"Ya Zhao","contact-id":81385,"tdoctype":"discussion","for":"Discussion","abstract":"After the start 6G in RAN5, RAN5 will need to maintain 4G\/5G (even 2G\/3G) while developing 6G, which will be a massive undertaking. Currently, RAN5 has initiated study on modernization of specification format and procedures for 6G. We suggest that RAN5 may also begin other discussions 6G, for example efficiency improvements and test simplification._x000D_\n2\tDiscussion_x000D_\n2.1\tEnhance standardization\/templatization of test procedure language in 6G test spec._x000D_\nEnhancing the standardization\/templatization of test procedure language improves machine readability. This enables direct mapping to TTCN code from the test step in the SIG test procedure description._x000D_\nFor Example: TS 38.508-1 clause 4.5.2.2-2 contains 6 tables (Table 4.5.2.2-1\/2\/3\/4\/5\/6). If test procedure only refered to clause number(in Figure 1), it might be difficult for an automated system to refer to the exact table\/test procedure. _x000D_\n Figure2_x000D_\nMore strict rules or Template can be introduced to standarized the test procedure description, and template can also be updated when new form test procedure is added, but How to make sure all the delegate are using the template or following the rules? The work load for checking the test procedure description may even larger than mapping test procedure to TTCN code by human._x000D_\nProposal 1: Study the rules or templates that can be introduced to standardize the test procedure description and use them when the first 6G work item starts._x000D_\nProposal 2: Tools can be introduced for both checking test procedures (such as checking overlapping Tdoc) and automatically mapping TTCN code._x000D_\n_x000D_\n2.2\tReduce the SIG and RRM test case overlap to simplify test in 6G test spec._x000D_\nNormally, SIG test case and RRM test case are designed separately, but several test case test similar UE behaviour._x000D_\nFor example, both of them test cell reselection, handover, redirection, re-establishment, and measurement procedure, while RRM test case adding delay\/measurement accuracy test requirement in these test procedure. If the RRM test case passed, part of SIG test case for this feature can be skipped._x000D_\nProposal 3: Study the possibility of skipping part of the SIG test case if an RRM test case with a similar test procedure has already passed._x000D_\nSome RRM subtest cases are testing pure signalling procedure without delay\/timing\/power\u2026 requirement. SIG is a better place to test this test scenario._x000D_\nFor example, 38.533 TC 6.3.2.2.1 Test4 only check UE can re-transmit msg3._x000D_\nProposal 4: RAN5 can make its own decision to test the Minimum conformance requirements listed by RAN4 in SIG._x000D_\n_x000D_\nConclusion_x000D_\nProposal 1: Study the rules or templates that can be introduced to standardize the test procedure description and use them when the first 6G work item starts._x000D_\nProposal 2: Tools can be introduced for both checking test procedures (such as checking overlapping Tdoc) and automatically mapping TTCN code._x000D_\nProposal 3: Study the possibility of skipping part of the SIG test case if an RRM test case with a similar test procedure has already passed._x000D_\nProposal 4: RAN5 can make its own decision to test the Minimum conformance requirements listed by RAN4 in SIG.","secretary_remarks":"","agenda_item_sort_order":14,"ainumber":"4.5.4","ainame":"Other open issues from joint sessions - original A.I. retained","tdoc_agenda_sort_order":617400,"status":"noted","reservation_date":"2025-07-11 09:29:29","uploaded":"2025-11-19 17:21:16","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__109_Dallas\/Docs\/R5-256174.zip","group":"R5","meeting":"R5-109","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-256314","title":"Discussion on test frequency simplification for inter-band CA and DC band","source":"ZTE Corporation, Huawei","contact":"Zhifeng Ma","contact-id":61569,"tdoctype":"discussion","for":"Approval","abstract":"AI 5.3.32.11_x000D_\nassociated CRs 6315r1, 6316r1 and 6317r1._x000D_\nObservation 1  In TS 38.508-1, test frequencies for inter-band NR CA band combinations are specified by NR CA downlink \/ uplink configuration component bands \/ band combinations and applicable for protocol testing. _x000D_\nObservation 2  All \u201cApplicable for protocol testing\u201d are \u201cno\u201d for inter-band NR CA\/DC with three or more bands,  \u201cno\u201d for EN-DC within FR1 with four or more bands, \u201cno\u201d for EN-DC including FR2 with three or more bands._x000D_\nObservation 3  In TS 38.508-1, there are many typos in the test frequency tables due to the redundant contents are collected in different specs and different tables._x000D_\nObservation 4  Test frequency tables for inter-band CA\/DC band combinations are also essential in signalling as they specify which combinations are applicable and are used for the TTCN implementation. The general rules for deciding test frequencies applied to different cases for NR CA and EN-DC._x000D_\nProposal 1  It is suggested to simplify the inter-band CA test frequency table with the general rules for inter-band NR CA within FR1 for = 3 bands._x000D_\nProposal 2  It is suggested to simplify the inter-band EN-DC test frequency table with the similar general rules as CA configurations. _x000D_\nInter-band EN-DC within FR1 for = 4 bands._x000D_\nInter-band EN-DC including FR2 for = 3 bands.","secretary_remarks":"","agenda_item_sort_order":14,"ainumber":"4.5.4","ainame":"Other open issues from joint sessions - original A.I. retained","tdoc_agenda_sort_order":631400,"status":"revised","reservation_date":"2025-07-11 13:17:57","uploaded":"2025-11-07 18:04:47","revisionof":"","revisedto":"R5-256701","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"NR_CADC_NR_LTE_DC_R19-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__109_Dallas\/Docs\/R5-256314.zip","group":"R5","meeting":"R5-109","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-256410","title":"Discussion on Modernization of Specification Format and Procedures for 6G","source":"Ericsson","contact":"Kuba Kolodziej","contact-id":76956,"tdoctype":"discussion","for":"Information","abstract":"Discussion paper on the topic of future of the specyfication handling in 3GPP._x000D_\nDuring TSG#108 meetings, a new Study Item (SI) was approved for \u201cModernization of Specification Format and Procedures for 6G\u201d, along with an agreed Way of Working. The SI has the following objectives:_x000D_\n\u2022\tObjective 1: Assessment of existing specification formats and working methods, and requirements for any improvements._x000D_\no\tAdvantages of current tools_x000D_\no\tShortcomings, pain-points, and potential benefits_x000D_\no\tRequirements Identification_x000D_\n\u2022\tObjective 2: (After TSG#109): Taking into account the outcome of objective 1, consider new formats, including but not necessarily limited to plain text format such as Markdown or LaTeX, or another format._x000D_\n\u2022\tObjective 3: (After TSG#109): Taking into account the outcome of objective 1, consider use of Git and ETSI FORGE database to store specifications and manage version control. Other alternatives are not precluded._x000D_\nAs part of the study, trial TSs and CRs will be created to evaluate the applicability of the considered formats and processes across different 3GPP working groups._x000D_\nIn parallel, RAN groups have initiated discussions on the future of 3GPP specifications, with ongoing tests and offline email discussions in RAN5. To ensure RAN5-relevant aspects are considered, the RAN5 leadership team formed a group of representatives to actively participate in conference calls throughout this activity._x000D_\nThis document provides a status update for the 6G specification modernization activity, highlighting RAN5 perspectives and progress to date._x000D_","secretary_remarks":"","agenda_item_sort_order":14,"ainumber":"4.5.4","ainame":"Other open issues from joint sessions - original A.I. retained","tdoc_agenda_sort_order":641000,"status":"noted","reservation_date":"2025-07-11 16:09:47","uploaded":"2025-11-21 17:41:28","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__109_Dallas\/Docs\/R5-256410.zip","group":"R5","meeting":"R5-109","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-256701","title":"Discussion on test frequency simplification for inter-band CA and DC band","source":"ZTE Corporation, Huawei","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":14,"ainumber":"4.5.4","ainame":"Other open issues from joint sessions - original A.I. retained","tdoc_agenda_sort_order":631401,"status":"noted","reservation_date":"2025-01-12 13:40:13","uploaded":"2025-12-01 13:41:12","revisionof":"R5-256314","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"NR_CADC_NR_LTE_DC_R19-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__109_Dallas\/Docs\/R5-256701.zip","group":"R5","meeting":"R5-109","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]