[{"name":"R5-260438","title":"Discussion on aligning NTN event (D1\/D2) test cases with core spec","source":"Qualcomm Incorporated","contact":"Yogesh Tugnawat","contact-id":63855,"tdoctype":"discussion","for":"Endorsement","abstract":"Rel-17 event reporting test case 8.1.3.1.26 was introduced for Event D1. Subsequently, for Rel-18 event reporting test case 8.1.3.1.27 was introduced for Event D2 in NR- NTN.\nIn the legacy event based measurement procedures (e.g. A3), UE derives cell measurement results based on SSB or CSI-RS measurements for the trigger quantity and measurement quantity indicated in reportQuantityCell individually. However, for NTN trigger quantity is not defined for eventD1 or D2. So, if the network configures eventD1 or d2 without an associated event-based measurement, UE is not expected to perform measurement. \nDuring RAN2#131 following clarifications (outlined in cl 5.5.3.1 of TS 38.331[3]) have been added to the UE behavior, for event D1\/D2, which have impact on below RAN5 test cases in TS38.523-1,\n\u2022\t8.1.3.1.26\tNR NTN \/ Measurement configuration control and reporting \/ Event D1 \/ Measurement of Neighbour NR cell\n\u2022\t8.1.3.1.27\tNR NTN Enhancements \/ Measurement configuration control and reporting \/ Event D2\n2\tDiscussion\nIn RAN5 NTN event reporting test procedures are written with the previous core spec understanding where UE must perform measurement for neighbour cells. However, latest core spec[3] has following changes, \n...\nIt was clarified in RAN2 with [1][2] that For measId configured with only eventD1\/D2 for neighbour cells, UE does not need to perform RRM measurement or report result for neighbour cells in the report of the measId.\nIt was further observed that, for event trigger test cases, the reporting amount is set to infinity, which does not reflect a realistic deployment scenario, this needs to be changed in the test cases too.\nSummarizing, \nObservation 1: RAN5 NR-NTN event D1 and D2 reporting test cases (8.1.3.1.26, 8.1.3.1.27) expects RSRP reporting in the measurement reports without associated event-based mechanism. \nAs per the latest core spec clarification (TS38.331, [1][2]), it is not required by the UE to perform measurement when the measID is only configured with event D1\/D2 \nObservation 2: RAN5 event reporting test cases (8.1.3.1.26, 8.1.3.1.27) are defined with ReportAmount set to infinity\nReport quantity to be set to 1. UE will get triggered to send one MR at the entry and one MR at the exit of the condition. This will be more aligned with real world NTN deployments. \n3\tProposals\nTo address these, followings are proposed for both eventD1 (8.1.3.1.26) and eventD2 (8.1.3.1.27) test cases are as below., \nProposal1: In the measurement report check only measID but not RSRP (or RSRQ or other measurements)\nProposal2: Aligning the report quantity to real world deployment to 1.\nAssociated Prose CR correcting TC 8.1.3.1.26\/27[5] [6] have been raised during RAN5#110","secretary_remarks":"","agenda_item_sort_order":982,"ainumber":"6.3.15.7","ainame":"Discussion Papers, Work Plan, TC lists","tdoc_agenda_sort_order":4380,"status":"noted","reservation_date":"2026-01-29 01:11:49","uploaded":"2026-01-31 01:56:11","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"NR_NTN_enh_plus_CT-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__110_Gothenburg\/Docs\/R5-260438.zip","group":"R5","meeting":"R5-110","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]