[{"name":"R5-235987","title":"LS on FR2 ACS\/IBB testing","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Action","abstract":"In current TS38.521-2 Annex K1.8, the signal and interferer need to be reduced by 3 dB for each polarization in ACS\/IBB testing as shown below:\n\u2026\u2026\n3)\tEstablish a connection between the DUT and the SS with the downlink signal applied to the ?-polarization of the measurement antenna\n4)\tPosition the UE so that the beam is formed towards the measurement antenna in the RX beam peak direction.\n5)\tApply a signal with the specified reference measurement channel on the ?-polarization, setting the power level of the signal 3dB below the EIS level stated in the requirement.\n\u2026\u2026\nThis reduction tries to maintain the ratio between signal and interferer when each polarization is tested sequentially, and the 3 dB came from the EIS formula in R15, as shown below:\n    EIS = [1\/EIS? +1\/EIS?]-1\nHowever, in the current spec, a new \u201caverage EIS\u201d formula is used:\t\n\tEIS = 2* [1\/EIS? +1\/EIS?]-1\nBased on this new formula, the 3dB reduction for each polarization is not needed anymore.\nActions: To: 3GPP TSG RAN WG5\nRAN4 asks RAN5 to remove the 3dB reduction for each polarization in ACS\/IBB testing.","secretary_remarks":"LS R5-206259 on failing initial registration without Retry-After header field from RAN5","agenda_item_sort_order":44,"ainumber":"5.2","ainame":"\tReview incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":59870,"status":"noted","reservation_date":"2023-09-19 16:18:24","uploaded":"2023-10-03 09:15:36","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__101_Chicago\/Docs\/R5-235987.zip","group":"R5","meeting":"R5-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-235988","title":"Reply LS on clarifications for Non-Terrestrial Networks","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"3GPP RAN4 would like to thank RAN5 for the LS (R5-233672) on clarifications for Non-Terrestrial Networks.\nRAN4#108 has discussed the concerns raised by RAN5 with the following conclusions:\nRequirements applicability to different types of satellites:\nActions To: RAN5\nACTION: \tRAN4 asks TSG RAN5 to take the above conclusions into account.","secretary_remarks":"LS R5-206259 on failing initial registration without Retry-After header field from RAN5","agenda_item_sort_order":44,"ainumber":"5.2","ainame":"\tReview incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":59880,"status":"noted","reservation_date":"2023-09-19 16:18:24","uploaded":"2023-10-03 09:15:36","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"NR_NTN_solutions"},{"winame":" LTE_NBIOT_eMTC_NTN_req"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__101_Chicago\/Docs\/R5-235988.zip","group":"R5","meeting":"R5-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-235989","title":"Reply LS on additional UE Gain parameters","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"RAN4 thanks RAN5 for the LS [1] on additional UE Gain parameters. RAN4#108 discussed the questions raised by RAN5 and reached the following conclusions:\nQ1: Is the D parameter applicable only to SS-RSRP relative accuracy test requirement in test cases A.5.7.1.2 and A.7.7.1.2 or it should be also applied to SS-RSRP absolute accuracy test requirement in A.5.7.1.2 and A.7.7.1.2, and other test cases as well?\nRAN4 response: D parameter is applicable only to RSRP relative accuracy test cases, including A.5.7.1.2, A.5.7.7.2.2, A.7.7.1.2 and A.7.7.7.2. RAN4 also agreed CRs to introduce D parameter in A.5.7.7.2.2 and A.7.7.7.2.\nQ2: Is the Ginter parameter applicable only to SS-RSRP relative accuracy test requirement in FR2 inter-frequency measurement accuracy test cases A.5.7.1.2 and A.7.7.1.2 or it should be also applied to other FR2 inter-frequency test cases as well?\nRAN4 response: Ginter parameter is applicable only to RSRP relative accuracy test cases, including A.5.7.1.2, A.5.7.7.2.2, A.7.7.1.2 and A.7.7.7.2. RAN4 also agreed CRs to introduce Ginter parameter in A.5.7.7.2.2 and A.7.7.7.2.\nActions: To RAN5 group RAN4 asks RAN5 to take above RAN4 agreements into consideration.","secretary_remarks":"LS R5-206259 on failing initial registration without Retry-After header field from RAN5","agenda_item_sort_order":44,"ainumber":"5.2","ainame":"\tReview incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":59890,"status":"noted","reservation_date":"2023-09-19 16:18:24","uploaded":"2023-10-03 09:15:36","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"TEI15_Test"},{"winame":" 5GS_NR_LTE-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__101_Chicago\/Docs\/R5-235989.zip","group":"R5","meeting":"R5-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-235990","title":"Reply LS on RRM test cases with testability issues","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"RAN4 appreciates the analysis on the testability issues on LTE\/FR1 + FR2 test cases. The test cases included in R5-233782 are under assessment in RAN4 to check testability and if they are untestable, whether those can be modified and enabled to verify UE requirements partially. The assessment is expected to be concluded in RAN4 #108-bis meeting, and the relevant CRs will be agreed in the same meeting.\nActions: To RAN5: RAN4 asks RAN5 to take into account the RAN4 plan on the testability issue in the work.","secretary_remarks":"LS R5-206259 on failing initial registration without Retry-After header field from RAN5","agenda_item_sort_order":44,"ainumber":"5.2","ainame":"\tReview incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":59900,"status":"noted","reservation_date":"2023-09-19 16:18:25","uploaded":"2023-10-03 09:15:36","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"TEI15_Test"},{"winame":" 5GS_NR_LTE-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__101_Chicago\/Docs\/R5-235990.zip","group":"R5","meeting":"R5-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-235991","title":"Reply LS on CA\/DC MSD requirements","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"RAN4 thanks RAN5\u2019s response on the three scenarios with regard to the test configurations of CA\/DC MSD requirements as described in RAN4 LS (R4-2306591). For scenario 3, it can be understood by RAN4 that having RAN5 define conformance tests for a requirement that does not exist in TS38.101-1 would not be feasible. Considering the rarity of scenario 3 and MSD requirements are meant to test UE RF components performance which can also be verified via single-band RF requirements under the same band combination, RAN4 has agreed that if the specified MSD test configurations are not supported by UE, the corresponding MSD verification can be waived.\nActions: To: 3GPP TSG RAN WG5\nRAN4 asks RAN5 to take RAN4\u2019s agreement on CA\/DC MSD requirements into consideration for UE conformance tests.","secretary_remarks":"LS R5-206259 on failing initial registration without Retry-After header field from RAN5","agenda_item_sort_order":44,"ainumber":"5.2","ainame":"\tReview incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":59910,"status":"noted","reservation_date":"2023-09-19 16:18:25","uploaded":"2023-10-03 09:15:36","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__101_Chicago\/Docs\/R5-235991.zip","group":"R5","meeting":"R5-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-235992","title":"LS on frequency separation for power imbalance testing","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"RAN4 has completed the specification work for R18 WI on support of intra-band non-collocated EN-DC\/NR-CA deployment. Power imbalance requirement is specified in 38.101-1 section 7.10A for UE indicating [intraBandNonColocatedCA-r18] and in 38.101-3 section 7.10B for UE indicating interBandMRDC-WithOverlapDL-Bands-r16.\nRAN4 agreed that the following test condition should be introduced in the corresponding conformance test defined in RAN5.\n\u2022\tCenter of BWanother relative to edge of BWwanted is assumed to be at least 80MHz+BWanother\/2 away from the edge of the wanted CC in R18.\nActions To RAN5: RAN4 asks RAN5 to consider the agreed test condition in their future specification work.","secretary_remarks":"LS R5-206259 on failing initial registration without Retry-After header field from RAN5","agenda_item_sort_order":44,"ainumber":"5.2","ainame":"\tReview incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":59920,"status":"noted","reservation_date":"2023-09-19 16:18:25","uploaded":"2023-10-03 09:15:36","revisionof":"","revisedto":"","release":"Rel-18","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__101_Chicago\/Docs\/R5-235992.zip","group":"R5","meeting":"R5-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-235994","title":"LS to RAN5 for measurement grid based on the assumption of 6x2 for PC3","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"During the Rel-17 Study on enhanced test methods for FR2, RAN4 had concluded that FR2 test time can be reduced based on the optional measurement grid associated with the 4x2 array assumption, as documented in TS38.884, Clause 8.2 [1].\nIt is the RAN4 understanding that the PC3 measurement grids based on the 8 \u00d7 2 worst-case configuration are applied by default unless the device manufacturer explicitly declares that all antenna arrays with M \u00d7 N (M = N) comply with M = 4 and N = 2; in that case, measurement grids based on the 4 \u00d7 2 configuration can be applied to testing.\nRAN4 has discussed the need to accommodate devices with antenna configurations up to M = 6 in light of the current understanding that for such devices only the worst-case (8 \u00d7 2) grid configuration is applicable. In an effort to enable test time reduction, RAN4 kindly asks RAN5 to consider defining an additional vendor declaration in 38.502-2 and measurement grids based on the 6 \u00d7 2 antenna configuration in 38.521-2 as part of the ongoing NR RF FR2 Enhanced Test Methods work in RAN5 [2].\nAction To RAN5 group: RAN4 asks RAN5 to consider defining an additional vendor declaration in 38.508-2 and the measurement grids based on the 6 \u00d7 2 antenna configuration in 38.521-2.","secretary_remarks":"","agenda_item_sort_order":44,"ainumber":"5.2","ainame":"\tReview incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":59940,"status":"noted","reservation_date":"2023-09-19 16:18:25","uploaded":"2023-10-24 04:52:11","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"FS_FR2_enhTestMethods"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__101_Chicago\/Docs\/R5-235994.zip","group":"R5","meeting":"R5-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-235995","title":"LS on frequency separation for Type 2 UE NR-CA PDSCH demodulation requirements","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"RAN4 has agreed to define NR-CA PDSCH demodulation requirements for Rel-18 WI on supporting intra-band non-colocated EN-DC\/NR-CA deployment. PDSCH demodulation requirements are specified in TS 38.101-4 for UE indicating [intraBandNonColocatedCA-r18].\nIt was previously agreed [1] that RF conformance tests should introduce the following test condition in RAN5: \n\u2022\tCenter of BWanother relative to edge of BWwanted is assumed to be at least 80MHz+BWanother\/2 away from the edge of the wanted CC in R18.\nThe same agreement should be applied to NR-CA PDSCH demodulation requirement.\nActions To RAN5: RAN4 asks RAN5 to consider the agreed test condition in their future specification work.","secretary_remarks":"","agenda_item_sort_order":44,"ainumber":"5.2","ainame":"\tReview incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":59950,"status":"noted","reservation_date":"2023-09-19 16:18:25","uploaded":"2023-10-24 04:52:11","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NonCol_intraB_ENDC_NR_CA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__101_Chicago\/Docs\/R5-235995.zip","group":"R5","meeting":"R5-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-236040","title":"Further Reply LS on clarifications for Non-Terrestrial Networks","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"RAN4#108bis has further discussed the concerns raised in the LS on clarifications for Non-Terrestrial Networks (R5-233672) after initial responses provided in RAN4#108 (R4-2314001) and recommended way forward after further discussions held in RAN#101 (RP-232682).\nRelated agreements have been compiled in R4-2316967 (attached). \nAdditionally, answer to question Q2d has been reviewed as follows:\nQ2d: Are the zero Doppler or time varying assumptions applicable for conformance testing of demod performance requirements in section 8 in TS 38.101-5 and 36.102?\nQ2d: In previous LS response (R4-2314001), it was indicated that zero orbit Doppler conditions related to satellite motion for DL in service link were applicable to demodulation cases in section 8 in TS 38.101-5 and TS 36.102. However, demodulation requirements were specified with TDL channel model which implemented a separate Doppler shift into channel model. \nAs a conclusion of RAN4#108bis, RAN4 would like to add the following clarifications regarding conformance demod test cases:\n\u2022\tDelay will be constant.\no\tConstant delay value to be derived from the ephemeris (i.e., orbit emulation) for the zero orbit Doppler condition.\n\u2022\tThe same ephemeris info will be maintained by the TE during each demod measurement.\nActions To: RAN5: RAN4 asks TSG RAN5 to take the above conclusions into account.","secretary_remarks":"","agenda_item_sort_order":44,"ainumber":"5.2","ainame":"\tReview incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":60400,"status":"noted","reservation_date":"2023-10-24 05:05:56","uploaded":"2023-10-24 05:31:23","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"NR_NTN_solutions"},{"winame":" LTE_NBIOT_eMTC_NTN_req"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__101_Chicago\/Docs\/R5-236040.zip","group":"R5","meeting":"R5-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-236041","title":"Reply LS on RRM test cases with testability issues","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"RAN4 thanks RAN5 for the LS [1] on RRM test cases with testability issues. RAN4#108bis discussed the issue and reached the following conclusion.\nRAN4 agreed to update the lists of test cases UE does not have to pass in Table A.3.13A.2-1 and A.3.13A.3-1 (TS38.133 v17.10.0). The update can be found in appendix.\nActions: To RAN5 group: RAN4 asks RAN5 to take above RAN4 agreements into consideration.","secretary_remarks":"","agenda_item_sort_order":44,"ainumber":"5.2","ainame":"\tReview incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":60410,"status":"noted","reservation_date":"2023-10-24 05:05:56","uploaded":"2023-10-24 05:31:23","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"TEI15_Test"},{"winame":" 5GS_NR_LTE-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__101_Chicago\/Docs\/R5-236041.zip","group":"R5","meeting":"R5-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-236043","title":"LS to RAN5 on Multi-Rx DL 2AoA spherical coverage test","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"RAN4 agreed that core requirement for multi-Rx shall be defined for all supported channel bandwidths, and it is sufficient to verify a single CBW as representative of UE performance. For this purpose, 100MHz CBW is recommended as the single CBW.\nRAN4 also agreed that it is sufficient to verify multi-RX spherical coverage requirement over NTC (normal temperature conditions) as representative of UE performance, i.e., no verification under ETC (extreme temperature conditions) is necessary.\nActions: To RAN5: ACTION: RAN4 requests RAN5 to take the above into account in the future work.","secretary_remarks":"","agenda_item_sort_order":44,"ainumber":"5.2","ainame":"\tReview incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":60430,"status":"noted","reservation_date":"2023-10-24 05:05:56","uploaded":"2023-10-24 05:31:23","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_FR2_multiRX_DL"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__101_Chicago\/Docs\/R5-236043.zip","group":"R5","meeting":"R5-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-236044","title":"LS on testability issues of beam correspondence requirement for initial access","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"One of the objectives of Rel-18 NR_RF_FR2_Ph3 WI is to study the beam correspondence requirements in initial access. RAN4 has achieved following agreements:\n-\tSpecify the beam correspondence requirements for PRACH msg1.\n-\tThe PRACH beam correspondence requirements are specified as an EIRP spherical coverage requirement \n-\tEnable multiple PRACH transmissions in testing mode, including holding RAR.\n-\tThe accumulated PRACH power measurement period is at least 1ms.\n-\tThe requirement is verified with the test metric of EIRP (Link=spherical coverage grid, Meas=Link angle).\nRAN4 has agreed on the PRACH EIRP spherical coverage requirement based on working assumptions of test condition as below. RAN4 respectfully asks RAN5 to evaluate following working assumptions and provide feedback if RAN5 identifies any issue related to the working assumptions.\n-\tRAN4 has agreed to inform RAN5 to develop the beamlock function in initial access.\n-\tUE locks the beam direction after requested by test equipment\n-\tUE is kept in RRC_IDLE state to ensure at least 1ms EIRP measurement period for PRACH.\n-\tEnable multiple PRACH transmissions in testing mode, including holding RAR.\n-\tUE transmits with the optimal Tx beam that is autonomously selected by UE.\n-\tUE achieves Pcmax before PRACH EIRP measurement.\n-\tUE transmits PRACH with gap <=20ms.\n-\tTo accelerate the testing, it\u2019s recommended to use the longest applicable PRACH preamble format and minimum gap between PRACH transmission.\nActions To RAN5: RAN4 request RAN5 to take above RAN4 agreement into account in future work; RAN4 also respectfully asks RAN5 to evaluate above working assumptions and provide feedback if RAN5 identifies any issue related to the working assumptions.","secretary_remarks":"","agenda_item_sort_order":44,"ainumber":"5.2","ainame":"\tReview incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":60440,"status":"noted","reservation_date":"2023-10-24 05:05:56","uploaded":"2023-10-24 05:31:23","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_RF_FR2_req_Ph3-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__101_Chicago\/Docs\/R5-236044.zip","group":"R5","meeting":"R5-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]