[{"name":"R5-245059","title":"On testing correct identification of the start of the non-integer DRX cycle","source":"Nokia","contact":"Matti Kangas","contact-id":78339,"tdoctype":"discussion","for":"Discussion","abstract":"It is necessary to test not only consecutive PDDCH occasion from few consecutive DRX cycles from the beginning, but certain DRX cycles which may occur after several cycles. This sets some requirements for the testing of the non-integer DRX regarding both testcases and test equipment. Tests must be long enough and certain key points must be carefully tested. On the other hand test equipment needs to implement non-integer DRX frame structure correctly and set PDCCH occasions according to that._x000D_\nObservation 1: During RAN2 WI phase the problem of rounding errors with non-integer DRX cycle was discussed and a note was added to TS 38.321 clause 5 indicating that MAC entity shall ensure no rounding error for non-integer DRX operations._x000D_\nObservation 2: With a wrong implementation of the DRX formula for non-integer operation, the UE may wake up a number of slots earlier or later than expected. Therefore, testing whether the UE correctly decodes the PDCCH on the boundaries of the OnDurationTimer over multiple DRX cycles is necessary for non-integer DRX operation._x000D_\nProposal 1: Test whether the UE correctly decodes the PDCCH in the first and last slots of the UE OnDurationTimer over multiple DRX cycles.","secretary_remarks":"","agenda_item_sort_order":983,"ainumber":"6.3.21.7","ainame":"Discussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":50590,"status":"noted","reservation_date":"2024-08-09 06:00:59","uploaded":"2024-08-09 23:29:11","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_XR_enh_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__104_Maastricht\/Docs\/R5-245059.zip","group":"R5","meeting":"R5-104","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-245060","title":"On testing correct handling of UL grant \/ Unused Transmission Occasion","source":"Nokia","contact":"Matti Kangas","contact-id":78339,"tdoctype":"discussion","for":"Discussion","abstract":"The paper initiates discussion about the UTO-UCI testing. As stated in the discussion part above, UTO-UCI functionality specification is unclear regarding when UE should indicate CG-PUSCH TO as unused. This paper introduces couple of proposals how to tackle difficulties in testing UTO-UCI due to this unclarity in core specification._x000D_\nThe following Observations and Proposals were made:_x000D_\nObservation 1: based on RAN1 and RAN2 specification, it is not clear when (not even when at the earliest or when at the latest) a UE should indicate a CG-PUSCH TO as \u201cunused\u201d for the first time._x000D_\nProposal 1: RAN5 to discuss and agree which option should be used to specify test case for UTO-UCI.","secretary_remarks":"","agenda_item_sort_order":983,"ainumber":"6.3.21.7","ainame":"Discussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":50600,"status":"noted","reservation_date":"2024-08-09 06:01:10","uploaded":"2024-08-09 23:42:07","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_XR_enh_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__104_Maastricht\/Docs\/R5-245060.zip","group":"R5","meeting":"R5-104","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]