[{"name":"R5-225919","title":"Reply LS on TT work for NR FR1 TRP TRS","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"3GPP RAN4 would like to thank RAN5 for their LS on TT work for NR FR1 TRP TRS.\nIn RAN#96 meeting, June 2022, the WID for FR1 TRP TRS was updated with TT work as an objective for performance part WI [1]. \nRAN4 has discussed the TT value, the agreements are listed as follow:\n?\tTT value is recommended as a ratio of MU, where TT=0.62*MU; according to currently available analysis of preliminary MU in RAN4, these values are 1.1 dB for TRP, and 1.4 dB for TRS. \n?\tThe above recommended TT values for NR FR1 TRP and TRS are decided based on the assessed preliminary MU budget and outcome of FR1 TRP TRS lab alignment activity, thereby incorporating the actual bounds of the lab alignment measurements and associated uncertainties [3]. \n?\tConsidering the deep relation between requirements and TT for FR1 TRP TRS, RAN4 suggests not to further modify the TT value if MU values are further modified in RAN5.  \nWith regards to the core requirements definition process, RAN4 agree a detailed working procedure in [2] to guide FR1 TRP TRS requirements definition work, some of the key aspects are listed as following:\n?\tRAN4 performed a successful FR1 TRP TRS Lab alignment activity [3], all the participated 8 labs (ISO 17025 accredited labs) are well aligned based on test campaign of reference LAD devices with anechoic chamber test system. \no\tThe pass\/fail limits for lab alignment activity is defined as 1.2dB for TRP, and 1.5dB for TRS\n?\tRAN4 performed a performance test campaign to collect measurement results from aligned test labs with an anonymous approach\no\tWorking scope for Performance Test campaign is limited to gather group efforts to collect sufficient measurement results\n?\tRAN4 focus on DUT size 1 (width >72mm and =92mm) smartphone with 1Tx, \n?\tPC2 is selected as 1st priority\n?\tUse scenario: Hand phantom only (Browsing mode), i.e., Hand Left and Hand Right\no\tMinimum number of devices for defining requirements for each band is 50\n?\tThe TRP TRS requirements are defined based on per-band Data driven approach with CDF analysis of all the collected measurement results in [4].\n2\tActions: To RAN5: 3GPP RAN4 respectfully asks RAN5 to take the above feedback into account when developing NR FR1 TRP TRS conformance test specification.","secretary_remarks":"","agenda_item_sort_order":20,"ainumber":"5.2","ainame":"Review incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":59190,"status":"noted","reservation_date":"2022-06-10 05:38:31","uploaded":"2022-10-06 15:01:20","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"NR_FR1_TRP_TRS-Perf"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"R5-223638","lsto":"TSG WG RAN5","Cc":"TSG RAN","lsoriginalls":"R4-2214797","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_97_Toulouse\/Docs\/R5-225919.zip","group":"R5","meeting":"R5-97","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-225920","title":"Reply LS on ModifiedMPR-Behaviour clarification for different power classes","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"RAN4 would like to thank RAN5 for clarification questions on ModifiedMPR-Behaviour for different power classes.\nWith regard to the questions raised by RAN5, the answers from RAN4 are as follows:\nQuestion a) For Rel-15 PC3 UE, is the MPR as defined in 38.101-2 v16.2.0 applicable if the UE supports modifiedMPR-Behaviour bit 0 UE capability?\nAnswer: Yes, for Rel-15 PC3 UE, MPR defined in 38.101-2 v16.2.0 is also applicable if the UE reports modifiedMPR-Behaviour bit 0 UE capability, but this modified MPR is optional for a Rel-15 UE.\nQuestion b) For Rel-15 PC2 and PC4 UEs, is modifiedMPR-Behaviour bit 0 capability applicable?\nAnswer: No, modifiedMPR-Behaviour bit 0 capability is not applicable for Rel-15 PC2 and PC4 UEs.\nQuestion c) For Rel-16 PC3 UE, is the MPR as defined in 38.101-2 v16.2.0 mandatory or optional? In case it is mandatory then is the Rel-16 UE expected to signal modifiedMPR-Behaviour bit 0=true?\nAnswer: No consensus reached in RAN4 yet. RAN4 will keep RAN5 updated for the conclusion of the question.\nQuestion d) For Rel-16 PC3 UE, which version of specification is taken as default MPR requirement, 38.101-2 v16.2.0 or latest version (v16.11.0 released in Apr 2022)? What are the Rel-16 MPR requirements if the UE signals respectively modifiedMPR-Behaviour bit 0=false and modifiedMPR-Behaviour bit 0=true?\nAnswer: No consensus reached in RAN4 yet. RAN4 will keep RAN5 updated for the conclusion of the question.\nQuestion e) For Rel-16 PC2, PC4 and PC5 UEs is modifiedMPR-Behaviour bit 0 capability applicable?\nAnswer: No, modifiedMPR-Behaviour bit 0 capability is not applicable for Rel-16 PC2, PC4 and PC5 UEs.\nQuestion f) For Rel-17 PC3 UE, what are the MPR requirements if the UE signals respectively modifiedMPR-Behaviour bit 0=false and modifiedMPR-Behaviour bit 0=true?\nAnswer: For a Rel-17 PC3 UE, it shall comply with the improved MPR defined in the latest Rel-17 version of 38.101-2 and may not set this bit 0 to false.\n2. Actions: To RAN5: RAN4 asks RAN5 to take the above feedback into account for the future work.","secretary_remarks":"","agenda_item_sort_order":20,"ainumber":"5.2","ainame":"Review incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":59200,"status":"noted","reservation_date":"2022-06-10 05:38:31","uploaded":"2022-10-06 15:01:20","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"NR_RF_FR2_req_enh-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"R5-223635","lsto":"TSG WG RAN5","Cc":"","lsoriginalls":"R4-2215091","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_97_Toulouse\/Docs\/R5-225920.zip","group":"R5","meeting":"R5-97","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-225996","title":"LS to RAN5 on MU work of Rel-18 FR1 TRP TRS WI","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"RAN4 would like to thank RAN5 for the efforts on MU assessment to ensure the successfully finalization of Rel-17 Work Item on NR_FR1_TRP_TRS, in RAN#97-e meeting, September 2022. \nAt the same time, a new Rel-18 TRP TRS Work Item (NR_FR1_TRP_TRS_enh) was approved with RAN5 as secondary responsible group in the WID [1], to develop test methods and TRP TRS requirements. The WI has been discussed in RAN4#104-bis-e meeting, with the WI workplan [2] and TR 38.870 skeleton [3] being approved. \nFor Rel-18 Work Item, MU assessment is important topic to finalize the whole work, to facilitate the discussion and coordination between groups, RAN4 suggest to keep the Rel-17 coordinator-based approach [4] for MU work management. \nRAN4 respectfully asks RAN5 to take the above information into account.\n2\tActions: To RAN5: RAN4 asks RAN5 to take the above information into account.","secretary_remarks":"","agenda_item_sort_order":20,"ainumber":"5.2","ainame":"Review incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":59960,"status":"noted","reservation_date":"2022-10-25 10:29:39","uploaded":"2022-10-25 10:32:27","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_FR1_TRP_TRS_enh"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"R4-2217458","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_97_Toulouse\/Docs\/R5-225996.zip","group":"R5","meeting":"R5-97","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]