[{"name":"R5-240096","title":"Discussion on handling of MDT IDC problem","source":"CMCC","contact":"Dan Song","contact-id":86282,"tdoctype":"discussion","for":"Endorsement","abstract":"Observation 1: For TC 8.1.6.1.2.14, it is assumed once UEs are configured as \u201cT1\u201d, IDC problem will be detected by the UEs.\nActually, for UEs with good IDC mechanism and solutions, no IDC problems might be detected by the UEs. Hence, UEs may NOT suspend measurement logging or tag MDT report with inDeviceCoexDetected-r17 flag as expected. And these UEs will FAIL TC 8.1.6.1.2.14. Proposal 1: Before testing the IDC mechanism, to confirm UE will detect IDC problem with \u201cT1\u201dconfiguration.\nObservation 2: For TC 8.1.6.1.2.14, it is assumed once UEs are configured as \u201cT0\/T2\u201d, IDC problem will NOT be detected by the UEs.\nActually, UEs with \u201cT0\/T2\u201d configuration may still detect IDC problems. Hence, UEs may NOT resume logging as expected. And these UEs will FAIL TP2 of TC 8.1.6.1.2.14.Proposal 2: Before testing the IDC mechanism, to confirm UE will NOT detect IDC problem with \u201cT0\/T2\u201dconfiguration.\nObservation 3: In cl. 23.4, it says \u201cIDC problem can happen when the UE (intends to) uses WLAN on the overlapped carrier\/band or adjacent carrier\/band to the unlicensed carrier used for LAA operation, e.g. when related UE hardware components, such as antennas, are shared between LAA and WLAN operations\u201d.\nObservation 4: As per cl.5.7.4.2 in TS 38.331, UE detecting IDC problem will providing IDC assistance information in RRC_CONNECTED if the UE was configured to do so. \nObservation 5: If UEAssistanceInformation message including IDC-Assistance-r16 is received by NW\/SS, it is confirmed that UE can detect IDC problem.\nProposal 3: When checking whether UE will suspends measurement logging when IDC problem is detected, if UE detects IDC problem in RRC_CONNECTED with some configuration, to configure the IDLE UE with the same configuration as in RRC_CONNECTED to make the UE detect IDC problem in RRC_IDLE.\nProposal 4: When checking whether UE will resume logging when IDC problem is resolved, if UE does NOT detect IDC problem in RRC_CONNECTED with some configuration, to configure the IDLE UE with the same configuration as in RRC_CONNECTED to make the UE NOT detect IDC problem in RRC_IDLE.","secretary_remarks":"","agenda_item_sort_order":925,"ainumber":"6.4.7","ainame":"Discussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":960,"status":"revised","reservation_date":"2024-01-29 16:09:34","uploaded":"2024-02-09 01:08:15","revisionof":"","revisedto":"R5-241634","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"},{"winame":" NR_ENDC_SON_MDT_enh-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__102_Athens\/Docs\/R5-240096.zip","group":"R5","meeting":"R5-102","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-240431","title":"Discussion to update MUSIM gap TC","source":"Huawei, HiSilicon,China Telecom","contact":"Ya Zhao","contact-id":81385,"tdoctype":"discussion","for":"Discussion","abstract":"Issue: How to make sure that RAN5 TC are testing the MUSIM gap pattern supported by UE?\nObservation 1: 38.133 list 27 periodic MUSIM gaps and 2 aperiodic MUSIM gaps, but 38.306 only require UE to support 3 periodic MUSIM gaps and 1 aperiodic MUSIM gap. \n\nTherefore, core spec does not require UE to support all kinds of gaps and it does not list which gap pattern is mandatory and which gap pattern is optional, either.\n\nObservation 2: According to 38.331, for periodic gap, network always configured the musim-GapLength and musim-GapRepetitionAndOffset as indicated by the UE's preferred periodic MUSIM gap configuration. For aperiodic gap, network always configured the same musim-Starting-SFN-AndSubframe as indicated by the UE's preferred aperiodic MUSIM gap configuration. The UE's preferred MUSIM gap configuration is indicated in the MUSIM UAI.\nTherefore, if UE only support part of MUSIM gap listed in 38.133, and UE always indicated that supported MUSIM gap pattern to network through MUSIM UAI, network have no chance to configure MUSIM gap pattern unsupported by the UE. In addition, If TC directly (e.g 38.523-1 8.1.2.1.6) configure MUSIM gap to UE, the UE behaviour is not specified by 38.331.\nObservation 3: Accroding to 38.331, UE may not trigger MUSIM UAI automatically after network configuration. In order to trigger MUSIM UAI, RAN5 design Set MUSIM UAI test function to force UE to report any type of MUSIM gap in MUSIM UAI.\n\n\u201cSet MUSIM UAI test function\u201d is designed based on an assumption that UE support all the MUSIM gap pattern listed in 38.133. However based on observation 1\/2, there is not enough evidence to support this assumption.\nObservation 4: RAN4 has defined the RRM requirement for Rel-17 MUSIM gaps in R18 WI NR_DualTxRx_MUSIM. It is highly possible that RRM MUSIM gaps TC will face similar issue in the future.\n\n2\tProposal\nBased on the above discussion, the followings are proposed:\nProposal 1: Add 4 PIXIT in 38.523-3, UE tester can fill the PIXIT based on the MUSIM gap supported by UE.\nProposal 2: Update 38.523-1 8.1.2.1.6 to add MUSIM UAI trigger procedure (MUSIM UAI triggered by \u201cSet MUSIM UAI test function\u201d or other method) before MUSIM gap configuration. Only the gap pattern filled in the px_NR_SupportPeriodicMusimGapPattern_First\/px_NR_SupportPeriodicMusimGapPattern_Second\/px_NR_SupportAperiodicMusimGapPattern can be test in this test case.","secretary_remarks":"","agenda_item_sort_order":925,"ainumber":"6.4.7","ainame":"Discussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":4310,"status":"revised","reservation_date":"2024-08-02 10:15:46","uploaded":"2024-02-17 09:39:45","revisionof":"","revisedto":"R5-241633","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17_Test"},{"winame":" LTE_NR_MUSIM_plus_CT1-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__102_Athens\/Docs\/R5-240431.zip","group":"R5","meeting":"R5-102","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-240663","title":"Discussion Paper for Rel-17 eNS_Ph2 WI tests case applicability","source":"Qualcomm CDMA Technologies","contact":"Yogesh Tugnawat","contact-id":63855,"tdoctype":"discussion","for":"Discussion","abstract":"Observation #1 \u2013 The R-17 UE has capability to indicate support of ER-NSSAI; UE\u2019s can set this to \u201csupported\u201d after network IOT\nProposal#1 \u2013 Based on Observation#1, The following test cases under NR Protocol test cases defined in TS38.523-1 [2] for NSAC Mobility Management aspects test cases (Cl 9.1.12.1-5) and NSAC interworking with EPC shall be defined with an applicability in TS38.523-2 [3] and associated PICS shall be defined in 38.508-2 [4].\n\nBelow is a recap of some alternate proposals which can be considered to address this and were also discussed in RAN5#101\nAlt Proposal-1 \u2013 The rapportuer of this WI to ensure that sufficient evidence exists of this feature commecialization along with IOT opportunities and ONLY then introduce this WI in certification bodies.\nAlt Proposal-2 \u2013 For features, like the ones discussed in this paper, RAN5 can control the Optionality by using existing tables in TS 38.508-2 (ex- below column M) and then keep revisiting every meeting if the status of column M needs to be changed, this can be a running AP as well.\n\nObservation#2 - None of the SM test case introduced are testing unique UE requirement specific to R-17 eNS_Ph2 WI. This may cause even earlier UE release to PASS this test case but more importantly the UE requirements are not part of R-17 eNS_Ph2 WI\nProposal#2 \u2013 The session management test cases introduced in the NSAC WI are not R-17 eNS_Ph2 unique requirements for UE hence they are misaligned in specification; these tests are currently mandatory for R-17 UE which is incorrect. \nProposal#2-1 \u2013 All NSAC SM test cases to be \u201cVOIDED\u201d from Spec (TS38.523-1[2] and TS 523-2 [3]) \nProposal#2-2 \u2013 Study them again to be reintroduced as R-15 through 5GS maintenance WI on a need basis. Any R-17 eNS_Ph2 UE specific requirement, if found, can be covered in TEI_17 WI.\n\nAs this AP has not progressed, below w\/f can be applied \u2013\n\nProposal 2-2A \u2013 Add note in applicabilty that these tests have open issues to be addressed, verification of new tests shall be paused unitl the AP is complete.","secretary_remarks":"","agenda_item_sort_order":925,"ainumber":"6.4.7","ainame":"Discussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":6630,"status":"revised","reservation_date":"2024-02-14 22:51:26","uploaded":"2024-02-17 03:07:20","revisionof":"","revisedto":"R5-241479","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17_Test"},{"winame":" eNS_Ph2-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__102_Athens\/Docs\/R5-240663.zip","group":"R5","meeting":"R5-102","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-240870","title":"TS 38.523-1 Tracker status before RAN5-102","source":"Huawei, Hisilicon","contact":"zhaobing yang","contact-id":80062,"tdoctype":"other","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":925,"ainumber":"6.4.7","ainame":"Discussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":8700,"status":"noted","reservation_date":"2024-02-15 16:16:36","uploaded":"2024-02-17 06:43:54","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__102_Athens\/Docs\/R5-240870.zip","group":"R5","meeting":"R5-102","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-241479","title":"Discussion Paper for Rel-17 eNS_Ph2 WI tests case applicability","source":"Qualcomm CDMA Technologies","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":925,"ainumber":"6.4.7","ainame":"Discussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":6631,"status":"noted","reservation_date":"2024-07-03 14:09:53","uploaded":"2024-03-07 14:11:13","revisionof":"R5-240663","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17_Test"},{"winame":" eNS_Ph2-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__102_Athens\/Docs\/R5-241479.zip","group":"R5","meeting":"R5-102","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-241633","title":"Discussion to update MUSIM gap TC","source":"Huawei, HiSilicon,China Telecom","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":925,"ainumber":"6.4.7","ainame":"Discussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":4311,"status":"noted","reservation_date":"2024-07-03 14:49:33","uploaded":"2024-03-07 14:51:17","revisionof":"R5-240431","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17_Test"},{"winame":" LTE_NR_MUSIM_plus_CT1-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__102_Athens\/Docs\/R5-241633.zip","group":"R5","meeting":"R5-102","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-241634","title":"Discussion on handling of MDT IDC problem","source":"CMCC","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":925,"ainumber":"6.4.7","ainame":"Discussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":961,"status":"noted","reservation_date":"2024-07-03 14:49:33","uploaded":"2024-03-07 14:51:17","revisionof":"R5-240096","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"},{"winame":" NR_ENDC_SON_MDT_enh-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__102_Athens\/Docs\/R5-241634.zip","group":"R5","meeting":"R5-102","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]