[{"name":"R5-254102","title":"SON\/MDT IDC test for band n41","source":"CMCC","contact":"Dan Song","contact-id":86282,"tdoctype":"discussion","for":"Endorsement","abstract":"In R17 SON\/MDT WI \u201cNR_ENDC_SON_MDT_enh-UEConTest\u201d, for IDC test case, only band n40 is supported to test the IDC mechanism, such as suspend measurement logging when IDC is detected and tag MDT report with inDeviceCoexDetected-r17 flag, resume measurement logging when IDC problems detected by the UE is resolved during the last logging interval. \nMore frequency band needs to be added to enhance the coverage of logged MDT IDC test case.\n2\tDiscussion\nIn-device coexistence (IDC) problem occurs when the UE (intends to) uses WLAN on the overlapped carrier\/band or adjacent carrier\/band to its 3GPP frequency. In R17, RAN2 introduced an IDC solution for logged MDT that UE can suspend measurement logging when IDC problem is detected and resume measurement logging when IDC problem is resolved, and reporting it to the network to enable the network aware that IDC problem exists. Then, RAN5 introduces a test case (TC) to validate this logging and reporting mechanism. \nHowever, to enable the IDC problem can be detected with WLAN AP, the test frequency is only limited to band n40 as in SON\/MDT TC 8.1.6.1.2.14 Logged MDT \/ RRC_IDLE \/ Logging and reporting \/ IDC mechanism. To enhance the coverage of the IDC test case, more frequency band needs to be added, such as band n41.\nWhy Band n41 needs to be tested?\n?\tMandatory in China: Band n41 is a required frequency for all of the 5G devices in China, ensuring 100% adoption.\n?\tBroad Global Support: The GCF Device Technology Trends Report 2025 [7] highlights the strong global support for band n41, which is supported in almost every 5G device.\n?\tHigh IDC problem risk: Band n41 (2.5\u20132.6 GHz) is adjacent to the 2.4 GHz Wi-Fi band (up to 2.483GHz), making IDC interference highly probable in 5G devices.\n?\tLarge amount of 2.4GHz Wi-Fi support: Most 5G devices support both Band n41 and 2.4GHz Wi-Fi, further increasing the likelihood of interference.\nMoreover, RP-182466, which provides the analysis when introduce the in-device co-existence issues in NR, explicitly identifies Band n41 as prone to 2.4GHz Wi-Fi interference, further justifying the need to include n41 testing in IDC test case.\nThe purpose of this document is to agree a way forward for IDC test case for band n41. Some observation and proposal:\nObservation 1:\nTest coverage for logged MDT IDC TC text is limited.  \nObservation 2:\nBand n41 and 2.4GHz Wi-Fi are supported in almost every 5G devices, which further increasing the likelihood of IDC interference.\nObservation 3:\nThe analysis when discuss the introduction of in-device co-existence issues in NR explicitly identifies Band n41 as prone to 2.4GHz Wi-Fi interference.\nProposal 1:\nIt\u2019s proposed to add new SON\/MDT IDC test case to support the test frequency band n41.","secretary_remarks":"","agenda_item_sort_order":1113,"ainumber":"6.4.7","ainame":"Discussion Papers, Work Plan, TC lists","tdoc_agenda_sort_order":41020,"status":"noted","reservation_date":"2025-08-13 01:59:48","uploaded":"2025-08-15 03:27:49","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__108_Bangalore\/Docs\/R5-254102.zip","group":"R5","meeting":"R5-108","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-254126","title":"TS 38.523-1 Tracker status before RAN5-108","source":"Huawei, HiSilicon","contact":"Ya Zhao","contact-id":81385,"tdoctype":"other","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":1113,"ainumber":"6.4.7","ainame":"Discussion Papers, Work Plan, TC lists","tdoc_agenda_sort_order":41260,"status":"noted","reservation_date":"2025-08-13 02:35:32","uploaded":"2025-08-13 07:46:03","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__108_Bangalore\/Docs\/R5-254126.zip","group":"R5","meeting":"R5-108","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-254177","title":"Duplicate conditions and their usage in test case selection expression","source":"Qualcomm Sweden","contact":"Yogesh Tugnawat","contact-id":63855,"tdoctype":"discussion","for":"Discussion","abstract":"3GPP TS 38.523-2 have duplicate conditions and these duplicates conditions are used for the same test case selection expression. This may create confusion to automation entity, readability and needs to be cleaned up for better clarity in the specification and remove ambiguity.\n2.\tDiscussion\nBelow data\\tables outlines the duplicate condition and how to remove redundancy to ensure no impact for the test case selection for a given DUT with specific set of feature support.\n...\nProposal -1, TS 38.523-2\nA.\tVoid C159 and change condition for?TC10.3.1.1 as C29 \u2013 May change C29- WLAN Access\nB.\tVoid C144 and change condition for?TC8.1.6.2.2  as C32a\nC.\tVoid C44A and change condition for TC 7.1.1.7.1.1.ENDC? as C67\nD.\tVoid C45A and change condition for TC 7.1.1.7.1.2.ENDC?  as C69\nE.\tVoid C46A and change condition for TC 7.1.1.7.1.3.ENDC?  as C68\nF.\tVoid C397 and change condition for ?TC7.1.1.13.8 as C385\n\nProposal -2\nInvestigate future checks either in TTCN or by other ways to avoid introducing duplicate conditions. There may be more such conditions which may need to be identified.","secretary_remarks":"","agenda_item_sort_order":1113,"ainumber":"6.4.7","ainame":"Discussion Papers, Work Plan, TC lists","tdoc_agenda_sort_order":41770,"status":"noted","reservation_date":"2025-08-14 05:48:22","uploaded":"2025-08-15 18:02:15","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__108_Bangalore\/Docs\/R5-254177.zip","group":"R5","meeting":"R5-108","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-254208","title":"Proposal for new test case related to UE mobility in inter-system upon receiving the 5GMM cause value #15 in the REGISTRATION REJECT message","source":"NTT DOCOMO INC.","contact":"Takuya Yashima","contact-id":104606,"tdoctype":"discussion","for":"Endorsement","abstract":"I have two proposals to check UE mobility in inter-system upon receiving the 5GMM cause value #15 in the REGISTRATION REJECT message.\nThe primary proposal is to make a new test case, while an alternative proposal involving updating the current test case has also been prepared.\nIf one is considered more appropriate and agreed upon, the other will be withdrawn.\n\nProposal 1: RAN5 make a new test case to check whether UE successfully attach on E-UTRA Cell after receiving the 5GMM cause value #15 in the REGISTRATION REJECT message. This test case is applied to UE supporting Rel.15.\n\nIf this proposal is agreed upon, the following new test case has already been proposed.\n# test case:\nR5-254203: Addition of new test case 9.3.1.7 related to Inter-system mobility registration update \/ Rejected \/ No suitable cells in tracking area \/ 5GC to EPC\n\n# Test applicability: \nR5-254204: Applicability update to Inter-system mobility registration update \/ Rejected \/ No suitable cells in tracking area \/ 5GC to EPC test case\n\nProposal 2: RAN5 updates current test case (9.1.5.1.13\/TS38.523-1) \u2018s check points to check UE successfully attach on E-UTRA Cell after receiving the 5GMM cause value #15 in the REGISTRATION REJECT message.\n\nThe current test case (9.1.5,1,13\/TS38.523-1) checks whether UE successfully perform registration on NGC Cell belonging to the other TAI after receiving the 5GMM cause value #15 in the REGISTRATION REJECT message. However, it does not check whether UE successfully attach on E-UTRA Cell after receiving the 5GMM cause value #15 in the REGISTRATION REJECT message.\nTherefore, we would like to add a Test Purpose and a Test description regarding UE mobility in inter-system upon receiving the 5GMM cause value #15 in the REGISTRATION REJECT message.\n\nIf this proposal is agreed upon, the following update to the current test case has already been proposed.\n# test case:\nR5-254206: Correction of test case 9.1.5.1.13","secretary_remarks":"","agenda_item_sort_order":1113,"ainumber":"6.4.7","ainame":"Discussion Papers, Work Plan, TC lists","tdoc_agenda_sort_order":42080,"status":"revised","reservation_date":"2025-08-14 08:19:16","uploaded":"2025-08-14 09:19:12","revisionof":"","revisedto":"R5-254930","release":"Rel-19","crspec":"38.523-1","crspecversion":"","workitem":[{"winame":"TEI15_Test"},{"winame":" 5GS_NR_LTE-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__108_Bangalore\/Docs\/R5-254208.zip","group":"R5","meeting":"R5-108","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-254544","title":"Discussion on addition of test coverage for Rel-17 Search space set group switching","source":"Qualcomm Incorporated","contact":"Bharadwaj Kumar Cheruvu","contact-id":68613,"tdoctype":"discussion","for":"Discussion","abstract":"3GPP Release 17 includes a work item focused on UE power saving enhancements, with RAN5 addressing the corresponding UE conformance aspects in [1]. However, the signalling test cases from [2] in this WI only cover paging improvements in idle\/inactive mode. Other power-saving features, such as Search space set group (SSSG) switching for further PDCCH monitoring reduction, were not included. These aspects are part of clause 10.4 of [3].\n2.\tDiscussion\nThere is an industry interest in the Release 17 Search space set group switching feature for enhanced UE power savings. This feature currently lacks signalling test coverage. It is proposed to add test cases in [2] for verification of this functionality.\n3.  Proposals\/Way Forward\nProposal: Introduce new test cases for Search space set group switching in TS 38.523-1\t5: GS; User Equipment (UE) conformance specification; Part 1: Protocol.","secretary_remarks":"","agenda_item_sort_order":1113,"ainumber":"6.4.7","ainame":"Discussion Papers, Work Plan, TC lists","tdoc_agenda_sort_order":45440,"status":"revised","reservation_date":"2025-08-15 07:55:33","uploaded":"2025-08-15 08:19:18","revisionof":"","revisedto":"R5-254931","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__108_Bangalore\/Docs\/R5-254544.zip","group":"R5","meeting":"R5-108","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-254930","title":"Proposal for new test case related to UE mobility in inter-system upon receiving the 5GMM cause value #15 in the REGISTRATION REJECT message","source":"NTT DOCOMO INC.","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":1113,"ainumber":"6.4.7","ainame":"Discussion Papers, Work Plan, TC lists","tdoc_agenda_sort_order":42081,"status":"noted","reservation_date":"2025-09-04 11:28:12","uploaded":"2025-09-04 11:31:05","revisionof":"R5-254208","revisedto":"","release":"Rel-19","crspec":"38.523-1","crspecversion":"","workitem":[{"winame":"TEI15_Test"},{"winame":" 5GS_NR_LTE-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__108_Bangalore\/Docs\/R5-254930.zip","group":"R5","meeting":"R5-108","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-254931","title":"Discussion on addition of test coverage for Rel-17 Search space set group switching","source":"Qualcomm Incorporated","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":1113,"ainumber":"6.4.7","ainame":"Discussion Papers, Work Plan, TC lists","tdoc_agenda_sort_order":45441,"status":"noted","reservation_date":"2025-09-04 11:28:12","uploaded":"2025-09-04 11:31:05","revisionof":"R5-254544","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__108_Bangalore\/Docs\/R5-254931.zip","group":"R5","meeting":"R5-108","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]