[{"name":"R5-250136","title":"Disc on handling XR PDCP discard TCs","source":"CMCC","contact":"Dan Song","contact-id":86282,"tdoctype":"discussion","for":"Endorsement","abstract":"This disc paper is related to CR R5-250133, R5-250134 and R5-250135._x000D_\n_x000D_\nXR PDCP discard TCs need to define RTP header extension_x000D_\nObservation 1:  RTP header extension includes some key parameters related to XR PDCP discard PDUSet Discard\/PSI and DSR triggering TCs._x000D_\nSome test assumptions for XR PDCP discard TCs:_x000D_\nAssumption 1 (SS side):  SS\/TTCN can create RTP packet in internet PDU session without IMS voice\/video call and RTP packets include RTP header extension for PDU set Marking._x000D_\nAssumption 2 (UE side):  UE can recognize the loop backed packet as RTP packet and perform PDU set\/PSI identification based on RTP header extension._x000D_\nAssumption 3 (UE side):  UE can treat the PSI=15 (lowest value) packet as low importance, and can treat the PSI=1 (highest value) packet as high importance._x000D_\nProposal 1: PDCP discard TCs are tested based on these assumptions and can be tested only if all assumptions are met._x000D_\nProposal 2a: It is proposed to capture these assmuptions in TCs editor notes in TS 38.523-1._x000D_\nProposal 2b: It is proposed to capture these assmuptions in TS 38.508-2 PICS._x000D_\nProposal 3: It is proposed to endorse the methodology in R5-250135 to define RTP header extension for PDU Set Marking._x000D_\n Proposal 4:  It is proposed to endorse methdologies in Slide 4,5 and 6 as test procedures of PDCP discard TCs .","secretary_remarks":"","agenda_item_sort_order":833,"ainumber":"6.3.13.7","ainame":"Discussion Papers, Work Plan, TC lists","tdoc_agenda_sort_order":1360,"status":"revised","reservation_date":"2025-01-24 08:05:05","uploaded":"2025-02-08 08:49:44","revisionof":"","revisedto":"R5-251367","release":"","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__106_Athens\/Docs\/R5-250136.zip","group":"R5","meeting":"R5-106","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-250570","title":"Discussion on XR UTO-UCI test case","source":"Huawei, HiSilicon","contact":"Ya Zhao","contact-id":81385,"tdoctype":"discussion","for":"Discussion","abstract":"\u201cHow to specify rules for the determination of unused CG occasions\u201d is discussed in RAN2#124, and the agreements is below[1], the UE determines the unused CG PUSCH by consider the amount of buffered data available for CGO._x000D_\nIn RAN2#125, DP R2-2400148[3] is raised by Qualcomm and RAN2 agree that UE may make the future buffer data determination. CR R2-2406092 [4] remove the restriction of only considering the already buffered data in UE\u2019s determination of unused CG occasions._x000D_\nThe latest core spec indicated that UE determines the unused CG PUSCH by consider at least the amount of buffered data available for CGO . The amount of buffered data available is not the only factors, and details for the rule of others factors is not indicated in the spec. For example, how long UE has to wait to make sure UE is confident that no more data will arrive before the concerned CG occasion._x000D_\nTherefore, it is not easy to check the value of UTO-UCI in RAN5 test case._x000D_\n2\tDiscussion_x000D_\nAt present, the test configurations of UTO-UCI test case (38.523-1 7.1.1.6.8) are listed below:_x000D_\n1. CG period is 40ms and Multi-CG does not configured (nrofSlotsInCG-Period=0)._x000D_\n2. UE need to report 8 bits UTO-UCI in CG PUSCH (nrofBitsInUTO-UCI=8)._x000D_\n3. SS transmits 4 RLC SDU (4 X 99 Bytes), and UE loops back the 4 RLC SDU in 4 CG PUSCH._x000D_\n4. SS check the UTO-UCI in the 4 CG PUSCH._x000D_\n_x000D_\nThe problem is how to check the 8 bit UTO-UCI reported by UE. The check for unused bits of UTO-UCI is FFS now in the test spec (Figure.2).Option1: SS does not check the unused bits in UTO-UCI for all kinds of UE._x000D_\nOption2: Create a new PICS in 38.508-1 to distinguish different UE implementation, only check the unused bits in UTO-UCI for the UE which only consider the current buffer data when it determine UTO-UCI.","secretary_remarks":"","agenda_item_sort_order":833,"ainumber":"6.3.13.7","ainame":"Discussion Papers, Work Plan, TC lists","tdoc_agenda_sort_order":5700,"status":"noted","reservation_date":"2025-06-02 03:38:24","uploaded":"2025-02-06 09:36:48","revisionof":"","revisedto":"","release":"","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__106_Athens\/Docs\/R5-250570.zip","group":"R5","meeting":"R5-106","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-251367","title":"Disc on handling XR PDCP discard TCs","source":"CMCC","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":833,"ainumber":"6.3.13.7","ainame":"Discussion Papers, Work Plan, TC lists","tdoc_agenda_sort_order":1361,"status":"noted","reservation_date":"2025-03-03 20:00:09","uploaded":"2025-03-03 20:01:06","revisionof":"R5-250136","revisedto":"","release":"","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__106_Athens\/Docs\/R5-251367.zip","group":"R5","meeting":"R5-106","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]