[{"name":"R5-203310","title":"Quality of the Quiet Zone measurement results for enhanced IFF","source":"ROHDE & SCHWARZ","contact":"Adrian Cardalda Garcia","contact-id":66591,"tdoctype":"discussion","for":"Endorsement","abstract":"The QoQZ for enhanced IFF setup is still FFS. This contribution provides the measurements of the QoQZ in an Enhanced IFF test system and proposed the value of the QoQZ based on the results.\nProposal 1: Use 0.6 dB as QoQZ Measurement Uncertainty for enhanced IFF.\nProposal 2: Use 0.4 dB as QoQZ Measurement Uncertainty for calibration for enhanced IFF.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":33100,"status":"revised","reservation_date":"2020-07-30 14:52:52","uploaded":"2020-08-05 06:06:44","revisionof":"","revisedto":"R5-204737","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-203310.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-203311","title":"Uncertainty assessment DL AWGN absolute power for enhanced IFF","source":"ROHDE & SCHWARZ","contact":"Adrian Cardalda Garcia","contact-id":66591,"tdoctype":"discussion","for":"Endorsement","abstract":"The uncertainty assessment for DL AWGN absolute power for enhanced IFF method is captured in TR 38.903 [1]. However, the uncertainty values for several uncertainty sources are missing:\n\u2022\tQoQZ\n\u2022\tMismatch\n\u2022\tInfluence of the XPD\n\u2022\tMultiple measurement antenna uncertainty\n\u2022\tDUT repositioning\n\u2022\tQoQZ for the calibration process\nThe uncertainty values for the 2 QoQZ measurements are proposed in [2] based on measurement results. This paper will focus on the other 4 sources.\nProposal 1: re-use the mismatch from IFF also for enhanced IFF.\nProposal 2: re-use the influence of the XPD from IFF also for enhanced IFF.\nProposal 3: re-use the multiple measurement antenna uncertainty from IFF also for enhanced IFF\nProposal 4: re-use the DUT repositioning from IFF also for enhanced IFF","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":33110,"status":"revised","reservation_date":"2020-07-30 14:52:52","uploaded":"2020-08-05 06:06:44","revisionof":"","revisedto":"R5-204742","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-203311.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-203312","title":"MTSU DL AWGN absolute power for RRM","source":"ROHDE & SCHWARZ","contact":"Adrian Cardalda Garcia","contact-id":66591,"tdoctype":"discussion","for":"Endorsement","abstract":"The uncertainty assessment for DL AWGN absolute power for enhanced IFF method has been finalized in [1] and [2]. The uncertainty assessment DL AWGN absolute power for IFF was already concluded in RAN5 #87-e.\nThis contribution proposed a value for the MTSU DL AWGN absolute power for RRM in order to progress with the RRM FR2 test case definition.\nProposal 1: Use 5.19 dB as the MTSU for RRM DL AWGN absolute power","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":33120,"status":"noted","reservation_date":"2020-07-30 14:52:52","uploaded":"2020-08-05 06:06:44","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-203312.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-203321","title":"FR2 RRM test cases: dB range in Spherical coverage","source":"ANRITSU LTD","contact":"Ian Rose","contact-id":9381,"tdoctype":"discussion","for":"Discussion","abstract":"Where a test case has an angle of arrival from Spherical Coverage directions, there is only a small dB range of applied signal level which meets both the minimum side condition at the lower end, and the maximum side condition at the higher end.\nThis Tdoc","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":33210,"status":"noted","reservation_date":"2020-07-31 14:30:34","uploaded":"2020-08-06 17:10:15","revisionof":"","revisedto":"","release":"","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_88_Electronic\/Docs\/R5-203321.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-203322","title":"Test Tolerance review process for FR2 RRM Test cases","source":"ANRITSU LTD","contact":"Ian Rose","contact-id":9381,"tdoctype":"discussion","for":"Discussion","abstract":"Current status\nRAN5 focus is now on FR2, with many new challenges for MU\/TT\nSignificant TT effort required to complete FR2 RRM Test cases\nFR2 RRM has new features to be handled and needs new templates\nFR2 RRM Test cases developed in parallel by multiple companies\nFirst FR2 RRM TT analyses have started to appear\nFR2 SS-RSRP TT templates R5-201713, 14: proposals endorsed at RAN5#87-e\nComplete FR2 Tx timing TT analysis provided at RAN5#87-e in R5-202867, not agreed because some MU values are in [ ]\nNew FR2 RRM TT analysis features discussed \nR5-198363 technical discussion of features provided at RAN5#85\nR5-200163 added handling of common FR2 TT Topics in 38.903 A.2 \n\nProposed Way Forward \n\u201cStartup\u201d stage leading up to RAN5#88-e\nAnritsu will prepare some basic FR2 TT templates as \u201ctoolkit\u201d for selected test cases to start the process, at RAN5#88-e and RAN5#89-e \nWe propose putting the available draft templates into TR38.903, with editor\u2019s notes per TT analysis stating the incomplete items\nFR2 RRM Test Tolerance review process for RAN5#89-e onwards\nFollowing similar process currently used for FR1\nProviding companies to develop FR2 TT analyses based on toolkit  \nShare review workload between FR2 TT reviewing companies\nLeading up to RAN5#88-e, RAN5#89-e \nAnritsu will prepare FR2 TT analysis templates for selected test casesLeading up to RAN5#88-e, RAN5#89-e\nBaseline for list of test cases was the Representative test cases to start FR2 RRM MU analysis in R5-201155, also considering\nRandom Access test cases have issues with signalled absolute thresholds and the range of allowed UE gain. Anritsu has proposed a method of handling this in RAN4, awaiting agreement \nThe same issue with signalled absolute thresholds also affects the Inter-frequency reselection test case  \nAim for most FR2 RRM test case providing companies to contribute  \nFR2 RRM test case providing companies can become familiar with the analysis method and toolkit\nAll analyses will need to be updated, according to outcome of FR2 MU agreements\nFR2 RRM Test Tolerance review process for RAN5#89-e onwards\n\u201cDeclaration\u201d date: normally (meeting upload deadline \u2013 4 weeks)\n\u201cDrafts available\u201d date: normally (meeting upload deadline \u2013 2 weeks)\nProviding companies to develop FR2 TT analyses based on toolkit\nShare review workload between FR2 RRM reviewing companies\nNR TT review process runs at main meetings only (4 times per year)\nTest case sign-up companies resolve any associated RAN4 issues\nRRM TT reviewing companies so far for FR2 (thanks): \nQualcomm, Rohde & Schwarz, Ericsson, Anritsu, Keysight\nOther companies welcome to join\n\nOpen issues\nFR2 Uncertainties\/MUs\nRAN5 has not yet agreed some of the key FR2 MU values\nRAN4 Core requirements in TS 38.133 and 38.101-2 \nMany FR2 requirements \/ conditions only defined for Power Class 3\nAoA of RRM test cases in TS 38.133 Annex A\nLikely that some RRM Test cases with 2 AoA will need to be changed from setup 3 (both AoA Spherical coverage) to setup 4 (one AoA Spherical coverage, one AoA Rx beam peak) to avoid huge variations \nRRM test cases in TS 38.133 Annex A using absolute thresholds\nSignalled value may need to be derived from a calibration process\nUnknown unknowns in TS 38.133 Annex A\nTest cases may reveal problems and immaturities when analysed\n\nSummary: Way Forward for FR2\nRAN5 is asked to endorse key points for FR2 TT review process:\n\u201cDeclaration\u201d date: normally (meeting upload deadline \u2013 4 weeks)\n\u201cDrafts available\u201d date: normally (meeting upload deadline \u2013 2 weeks)\nProviding companies to develop FR2 TT analyses based on toolkit\nShare review workload between NR-reviewing companies\nNR TT review process runs at main meetings only (4 times per year)\nTest case sign-up companies resolve any associated RAN4 issues\nRAN5 is also asked to endorse: \nScope is RRM, and currently Power Class 3\nTechnical basis as given on slide 7 \nIdentify any test cases where special handling of TT is required","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":33220,"status":"revised","reservation_date":"2020-07-31 14:34:43","uploaded":"2020-08-07 11:27:13","revisionof":"","revisedto":"R5-204848","release":"","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_88_Electronic\/Docs\/R5-203322.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-203485","title":"On ACS FR2 Measurement Uncertainty definition","source":"Keysight Technologies UK Ltd","contact":"Adan Toril","contact-id":62705,"tdoctype":"discussion","for":"Endorsement","abstract":"The acceptable uncertainty of Test System is not defined yet for Adjacent Channel Selectivity (ACS) test in FR2. In this document it will be discussed and proposed both the main contributions to consider and how to consider them in the overall calculation of the measurement uncertainty (MU).\nIn order to define the acceptable uncertainty of Test System for Adjacent Channel Selectivity (ACS) test in FR2, the following observations and proposals were made in this contribution:\nProposal 1: reuse approach followed for ACS in FR1 and calculate overall ACS MU as [SQRT (wanted_level_error2 + interferer_level_error2)] + ACLR effect.\nProposal 2: For the wanted signal level error, reuse the calculations for the reference sensitivity test uncertainty in [2], section B.19.\nProposal 3: For the interferer signal level error, consider only those MU factors uncorrelated with the wanted signal, reducing the list of contributions essentially to mismatch, interferer generator uncertainty, amplifier and insertion lost uncertainties and assume for them the same value as for the wanted signal.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":34850,"status":"revised","reservation_date":"2020-08-04 11:03:29","uploaded":"2020-08-07 14:11:02","revisionof":"","revisedto":"R5-204743","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-203485.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-203489","title":"On IBB FR2 Measurement Uncertainty definition","source":"Keysight Technologies UK Ltd","contact":"Adan Toril","contact-id":62705,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":34890,"status":"revised","reservation_date":"2020-08-04 11:03:32","uploaded":"2020-08-07 14:11:02","revisionof":"","revisedto":"R5-204744","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-203489.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-203669","title":"FR2 Demod MU due to finite test time","source":"Qualcomm Korea","contact":"Vijay Balasubramanian","contact-id":84569,"tdoctype":"discussion","for":"Endorsement","abstract":"One of the MU contributors for FR2 DEMOD scenarios is result variation due to finite test time. In this paper we present our view on this MU contributor.\nEndorse the below proposals and accordingly update Annex F of 38.521-4 for overall uncertainty for test tolerance calculations.\nProposal 1: For all FR2 PDSCH Demodulation scenarios add a SNR uncertainty of +\/- 0.3 dB due to finite test time in the overall test system uncertainty. \nProposal 2: For all FR2 PDCCH Demodulation scenarios add a SNR uncertainty of +\/- 0.4 dB due to finite test time in the overall test system uncertainty.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":36690,"status":"revised","reservation_date":"2020-08-06 07:33:29","uploaded":"2020-08-08 08:38:10","revisionof":"","revisedto":"R5-204738","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-203669.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-203686","title":"Discussion about proposals in LS R4-2005205","source":"Huawei, Hisilicon","contact":"Yuxin Hao","contact-id":82979,"tdoctype":"discussion","for":"Discussion","abstract":"associated CR in R5-203683, R5-203684, R5-203685\nIntroduction\nSince RAN4 has identified that the NR UE receiver ACS test requirements for PDCCH\/DCI could be tighter than PDSCH due to that the PDCCH\/DCI may not occupy the entire channel bandwidth where the signal power is lower than that of PDSCH as defined in ACS core specifications, two solutions were proposed to mitigate this potential issue in LS R4-2005205 [1].  \nThis paper is to discuss the possibility of implementation of these solutions in RAN5. \n________________________________________\n2.\tDiscussion\nThere were two solutions suggested by RAN4 to avoid potential risks. We show our views on these solutions in the sub-clauses below [..]\nIn this contribution we introduced our views to the proposed solutions in LS R4-2005205. The conclusions are listed below.\nProposal 1: For FR1, the PDCCH Aggregation Level in TS 38.521-1[2] C.3-Connection is configured as table 2.1-1.\nProposal 2: For FR2, the PDCCH Aggregation Level in TS 38.521-2[3] C.3-Connection is configured as table 2.1-2.\nProposal 3: Modify the nrofcandidates of SearchSpace in TS 38.508-1 [4] for AL=1, AL=8 and AL=16 to n2.\nProposal 4: Modify frequencyDomainResources in TS 38.508-1 [4] to align with candidates for AL=8 and AL=16.\nProposal 5: Removing both edge PDCCH allocations from full bandwidth isn\u2019t implemented.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":36860,"status":"revised","reservation_date":"2020-08-06 07:39:16","uploaded":"2020-08-07 09:49:41","revisionof":"","revisedto":"R5-204721","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-203686.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-203819","title":"Discussion on PCC prioritization for FR1 and FR2 UL CA testing","source":"Qualcomm Inc, Verizon Inc.","contact":"Hemish Parikh","contact-id":61982,"tdoctype":"discussion","for":"Discussion","abstract":"The purpose of this discussion paper is to discuss 5G NR PCC prioritization configuration for FR1 and FR2 UL CA testing. \nThis paper provides background for a potential discrepancy across 3GPP RAN 1, RAN 4 and RAN 5 TS regarding 5G NR PCC and SCC power allocation during FR1 and FR2 UL CA testing.\n\nObservation 1: RAN 5 test points are intended to be tested in their worst cases configuration. Currently for all UL CA test cases a UE under test gets configured to prioritize PCC (per RAN 1 spec). This results in no power being allocated to SCC. Thus all FR1 and FR2 UL CA test cases that require configuring maximum power (worst case) for all CCs are not being tested as intended. \nProposal 1: For all UL CA test cases add following editor\u2019s note: \u201cIncomplete as tests prioritize power allocation to PCC resulting in no power in SCC. PCC prioritization needs to be disabled for UL CA testing\u201d.\nProposal 2: RAN 5 to discuss and design a new dedicated test mode signaling to be used in the test procedure of UL CA tests to allow disabling of PCC prioritization in a test mode as opposed to mission mode of operation where PCC has prioritization.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":38190,"status":"noted","reservation_date":"2020-08-07 00:58:03","uploaded":"2020-08-07 22:30:09","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-203819.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-203868","title":"Discussion on Scope, Purpose and drafting guideline for 38.522","source":"CAICT","contact":"Yufeng Zhang","contact-id":86588,"tdoctype":"discussion","for":"Endorsement","abstract":"Corresponding CR: R5-203869.\nDuring RAN5#87-e there was an email discussion about scope, purpose and drafting guideline for TS 38.522, but no formal agreement was achieved. Moreover no agreement could be reached on how to handle\u201cTested Bands\u201d column and \u201cBranch\u201d column at RAN5#87-e, the disagreement is essentially about Scope, Purpose and drafting guideline for 38.522, such as what information shall be put in TS 38.522 and how to put the information in TS 38.522.\nThis paper highlights the scope and purpose of 38.522 according to the current definition in 38.522 (Scope in section 1 & definition of each column in the beginning of section 4), proposes to correct some corresponding incorrect or ambiguous content in 38.522, and also provides some drafting guidelines for TS 38.522.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":38680,"status":"revised","reservation_date":"2020-08-07 02:19:10","uploaded":"2020-08-07 13:50:34","revisionof":"","revisedto":"R5-204951","release":"Rel-16","crspec":"38.522","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-203868.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-203972","title":"Discussion on QZ size","source":"Huawei, HiSilicon","contact":"Chunying Gu","contact-id":65493,"tdoctype":"discussion","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":39720,"status":"withdrawn","reservation_date":"2020-08-07 06:29:47","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_NR_LTE-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204022","title":"Discussion on FR2 absolute power control MU","source":"Samsung R&D Institute UK","contact":"Carolyn Taylor","contact-id":81481,"tdoctype":"discussion","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":40220,"status":"noted","reservation_date":"2020-08-07 08:27:04","uploaded":"2020-08-07 23:37:09","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204022.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204027","title":"Discussion on remaining parameters for FR2 EIRP Tx OFF power MU","source":"Samsung R&D Institute UK","contact":"Carolyn Taylor","contact-id":81481,"tdoctype":"discussion","for":"Discussion","abstract":"It was decided at previous meetings to include an editor\u2019s note for \u201ctestability of OFF power needs further study\u201d [1] in all test cases that are dependent on EIRP OFF power that consist of the following test cases:\n\u2022\t6.3.3.2: General ON\/OFF time mask\n\u2022\t6.3A.3.1: Transmit ON\/OFF time mask for CA (2UL CA)\n\u2022\t6.3D.3.1: General ON\/OFF time mask for UL MIMO\n\u2022\t6.3D.3.4: SRS time mask for UL MIMO\nThe test cases listed above minimum conformance requirements are as such: [..]\nAt RAN5#87-e meeting EIRP measurements for Transmit OFF power was included to Annex B.8 [2]. However, there are still some remaining parameters for FR2 EIRP Tx OFF power MU that are still open. In this contribution, we briefly discuss and provide our views and recommendations for some of the remaining parameters concerning FR2 EIRP Tx OFF power. \nIn this contribution, we further discussed our views on some of the remaining parameters for FR2 EIRP Tx OFF power MU that are still open. Based on the discussion, our observation and proposals are summarized as follows:\n Proposal 1: Agree to the MU threshold for EIRP measurement for Transmit OFF power values with brackets.\nProposal 2: Set Uncertainty of the Network Analyzer as 1.5dB for FR2 EIRP OFF Power MU and Standard uncertainty as 0.75 dB and remove the brackets.\nProposal 3: Set Influence of noise to reference ACLR Table B.17.2-3 for FR2 EIRP OFF Power MU.\nProposal 4: Set EIRP Expanded uncertainty to [5.09] with brackets + influence of noise to be in alignment with ACLR.\nProposal 5: Set FR2 EIRP OFF Power TT = 0.65xMU.\nProposal 6: Test proposals 1-5 are agreed to be included in TR38.903.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":40270,"status":"noted","reservation_date":"2020-08-07 08:47:10","uploaded":"2020-08-07 23:37:09","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204027.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204042","title":"Discussion on multi-band relaxation framework requirement enhancement","source":"Samsung R&D Institute UK","contact":"Carolyn Taylor","contact-id":81481,"tdoctype":"discussion","for":"Discussion","abstract":"At RAN5#85, a LS on multiband relaxation for FR2 in [1] asking RAN4 to consider defining an upper limit of MBR (either ?MBP or ?MBP) which will be of high value for RAN5 when defining measurement uncertainty or to consider MBR per band instead of summation across all bands. At RAN4#95e meeting, a LS response on multiband relaxation for FR2 in [2] was approved by RAN4 based on further testability analysis of MBR.\nRAN4 asked RAN5 to take the information below into consideration concerning the Release 15 and Release 16 MBR requirements: [..]\nIn this contribution, we briefly discuss and provide our view on Release 15 and Release 16 MBR requirements.\nIn this contribution, we further discussed our views on Release 15 and Release 16 MBR requirements and related test cases. Based on the discussion, our observation and proposal are summarized as follows:\nObservation 1: The MBR definition factors currently defined in TR 38.903 [7] are no longer valid for Release 16 since ?MB is an obsolete definition as it has been removed.\nProposal 1: Update the MBR definition in the calculation method to account for the changes to the MBR framework requirements in RAN4.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":40420,"status":"noted","reservation_date":"2020-08-07 09:21:43","uploaded":"2020-08-07 23:37:09","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204042.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204081","title":"On AWGN and signal flatness uncertainty for FR2 Performance tests","source":"Anritsu","contact":"Hiroyuki Baba","contact-id":65585,"tdoctype":"discussion","for":"Endorsement","abstract":"In [2], frequency flatness uncertainty is proposed in RAN5#87e however that was not endorsed due to some TEV\u2019s requested for double-checking the value. This paper (re)propose the DL signal flatness uncertainty and also mention the sensitivity factor for the flatness uncertainty used for FR2 perf test.\nRAN5 is asked to endorse following proposals.\nProposal 1: Apply +\/-3.0 dB(1.96sigma) for MU term of AWGN and signal flatness for both FR2a and FR2b for up to 400MHz.\nProposal 2: Apply x0.25 sensitivity factor for frequency faltness of signal and AWGN for FR2 performance test cases.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":40810,"status":"noted","reservation_date":"2020-08-07 09:38:58","uploaded":"2020-08-07 14:21:36","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204081.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204082","title":"On FR2 DL absolute level uncertainty for DFF.","source":"Anritsu","contact":"Hiroyuki Baba","contact-id":65585,"tdoctype":"discussion","for":"Endorsement","abstract":"In FR2 RRM, DFF(or Hybrid) is listed as available test method for RRM, however no estimation of total MU for DFF has been provided in RAN5 which prevents the TT analysis where the common MU among all test methodology regardless of test method or their test case types(1AoA, 2AoA) is desired. With this background, in this paper, we provide our view on the FR2 DL absolute level uncertainty for DFF.\nIn this contribution, we present our view on the FR2 DL absolute level uncertainty \nObservation 1 : Impact from finite far field measurement distance(Measurement distance uncertainty and phase curvature) is estimated with in the order of +\/- 0.15  ~ +\/- 0.5 dB \nObservation 2 : Need to clarify which MU element (Measurement distance uncertainty\/phase curvature) applies and which is set to 0.\nObservation 3: The total FR2 DFF MU is close to 6.0dB rather than 5.0dB, and it could be bigger than 6.0dB depending on the final QoQZ value.\nProposal 1 : For FR2 DFF MU, reuse green highlighted values in Table 1 from FR2 IFF MU budget table\nProposal 2 : For FR2 DFF MU, reuse blue highlighted values in Table 1 from FR2 IFF MU budget table\nProposal 3 : Adopt +\/- 0.30dB for \u201cPhase centre offset of calibration\u201d for DFF budget table.\nRecommendation 1 : Concerning parties are encouraged to provide analysis for remaining FR2 DFF MU elements, especially quality of quiet zone value.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":40820,"status":"revised","reservation_date":"2020-08-07 09:38:58","uploaded":"2020-08-07 14:21:36","revisionof":"","revisedto":"R5-204745","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204082.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204083","title":"On gNB emulator fading model impairments for FR2 Performance tests","source":"Anritsu","contact":"Hiroyuki Baba","contact-id":65585,"tdoctype":"discussion","for":"Endorsement","abstract":"In this paper we propose gNB emulator fading model impairments uncertainty for FR2 demodulation test case.\nRAN5 is asked to endorse following proposals.\nProposal 1: Apply +\/- 0.5dB for 1Tx and +\/- 0.7dB for 2Tx for gNB emulator fading impairments.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":40830,"status":"noted","reservation_date":"2020-08-07 09:38:58","uploaded":"2020-08-07 14:21:36","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204083.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204084","title":"On FR2 ACS and IBB Test Implementation and MU","source":"Anritsu","contact":"Hiroyuki Baba","contact-id":65585,"tdoctype":"discussion","for":"Endorsement","abstract":"In this paper, we discuss the FR2 ACS and IBB implementation variations and how to define MUs in RAN5.\nWe present our view for the implementation variation of blocker test and MU definitions.\nFollowing observations are made in this paper.\nObservation 1 : Wanted signal and interfering(blocker) signal is not necessarily emitted from the same physical antenna. Implementation using slightly offset antenna can be discussed as part of MU discussion in RAN5 from practical implementation PoV.\nRegarding the need of offset antenna use for blocker signal, following observations (reasons) are made.\nObservation 2 : Offset antenna approach does not give impact to the signal path of the wanted signal which is the primary path for all the test cases other than blocking test. This is very important aspect when test system used in e.g. regulatory test(as early stage demand) is rectified to support blocker test with minimum impact.\nObservation 3 : Additional combiner in the RF path would reduce the dynamic range of the test system where the dynamic range is very precious in FR2 OTA test system as discussed ever for low PSD\/high Power test case testability topics in RAN5. In this situation, sacrificing the dynamic range due to the very small number of test case would not a reasonable choice from our PoV.\nObservation 4 : Independence of signal path is more promising for less complexity and more scalability than having tightly combined paths from long term perspective. It should be noted RAN5 anyway already permitted offset antenna for spurious emission test, then having offset antenna itself is not a serious issue from complexity perspective.\nObservation 5 : As blocker test is to test the DUT\u2019s capability of filtering or intermodulation inside a UE RF frontend, then the blocker\u2019s power level that UE RF frontend receives is the primary matter rather than the angle of arrival.\nObservation 6 : The UE reception power reduction from offset angle can be compensated at some extent. Details need to be studied further.\nRAN5 is asked to endorse followings.\nProposal 1 : RAN5 to study the MU of blocker test case considering the implementation of Type 1, 2 and 3.\nProposal 2 : As long as the MTSU is met, all the implementation Type 1, 2 or 3 are allowed. Which case the MTSU value is finalized is determined on the way to finalize the MU.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":40840,"status":"noted","reservation_date":"2020-08-07 09:38:58","uploaded":"2020-08-07 14:21:36","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204084.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204085","title":"On FR2 OBW MU","source":"Anritsu","contact":"Hiroyuki Baba","contact-id":65585,"tdoctype":"discussion","for":"Endorsement","abstract":"OBW MUs have been discussed in [1-16] but no conclusion was reached as of now. In [9], action item for UE\/Chip vendors for the spectrum assumption for deriving the OBW MUs are made, and the reference spectrum is provided in [10]. In RAN5#86e, OBW MU analyses based on the reference spectrum [10] are provided [11]-[16]. This paper provide the simulation result and proposes MU for FR2 OBW considering the discussions in RAN5#87-e.\nIn this paper FR2 OBW MU and testability limit is studied based on the previous discussions. \nFollowing observations are made.\nObservation 1 : For 100MHz and below, 2.0[%CBW] error is reasonable choice. \nObservation 2 : For 400MHz BW, by setting OBW measurement span to 28GHz, the OBWsignal (w\/o noise\/ripple) is now 397.8MHz(1.5x BW) or 398.6MHz(2.0x BW), then there is only 2.2MHz or 1.4MHz margin from core requirement.\nObservation 3 : For 400MHz BW, even  though SNR is enough good(40dB), 97.5% tile value excess the upper limit of measurement error. \nObservation 4 : The current MU evaluation assumption may have a gap from typical situation(UE performance, TE performance) \nRAN5 is asked to endorse following proposals.\nProposal 1 : Define OBW Measurement Error based with (OBWmeas - OBWsignal) \/ CBW *100 [%CBW] \nProposal 2 : Agree on the Table 2 for FR2 OBW MTSU\/measurement span","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":40850,"status":"revised","reservation_date":"2020-08-07 09:38:58","uploaded":"2020-08-07 14:21:36","revisionof":"","revisedto":"R5-204849","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204085.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204086","title":"Noise impact for FR2 test case where MPR applies","source":"Anritsu","contact":"Hiroyuki Baba","contact-id":65585,"tdoctype":"discussion","for":"Endorsement","abstract":"This paper provides the SNR estimations for FR2 test cases for MPR and ACLR, and proposes the testability limit and MU value for \u201cinfluence of noise\u201d.\nRAN5 is asked to endorse following proposals.\nProposal 1 : For FR2 MPR test case, apply ?SNR=0.2dB for FR2a and ?SNR=0.4dB for FR2b for MPR test case up to 400MHz aggregated BW for PC3\nProposal 2 : For FR2 ACLR test case, test FR2 ACLR without relaxation for the configuration with MPR not greater than the values in Table 2.\nProposal 3 : For FR2 ACLR test case for FR2a, apply the relaxation of (MPR for test points \u2013 value in Table 2) > 0 for dBc value.\nProposal 4 : For FR2 ACLR test case for FR2b, do not test the test points with MPR values bigger than Table 2 \nProposal 5 : Apply ?SNR in Table 3 for FR2 ACLR for up to 400MHz aggregated BW for PC3.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":40860,"status":"revised","reservation_date":"2020-08-07 09:38:58","uploaded":"2020-08-07 19:04:48","revisionof":"","revisedto":"R5-204746","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204086.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204087","title":"On MU for FR2 MPR Test","source":"Anritsu","contact":"Hiroyuki Baba","contact-id":65585,"tdoctype":"discussion","for":"Endorsement","abstract":"This paper proposes the measurement uncertainty for FR2 MPR test case. Though the MPR test is categorized in P3 test, as it is tightly relating to P2 test ACLR and SEM, it should be prioritized as well.\nProposal 1 : For FR2 MPR test, apply the same MU budget as for EIRP MOP except for the \u201cinfluence of noise\u201d.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":40870,"status":"noted","reservation_date":"2020-08-07 09:38:58","uploaded":"2020-08-07 14:21:36","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204087.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204088","title":"On frequency flatness uncertainty for FR2 RRM and Performance tests","source":"Anritsu","contact":"Hiroyuki Baba","contact-id":65585,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":40880,"status":"withdrawn","reservation_date":"2020-08-07 09:38:58","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_NR_LTE-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204089","title":"On gNB emulator SNR uncertainty for FR2","source":"Anritsu","contact":"Hiroyuki Baba","contact-id":65585,"tdoctype":"discussion","for":"Endorsement","abstract":"In RAN5#87e, FR2 gNB emulator SNR Uncertainty was proposed in [1] and proposals endorsed. The gNB emulator SNR uncertainty value itself was agreed with [0.3dB] for double checking from other TEVs. This paper is resubmission of [1] to fix the \u201cgNB emulator SNR uncertainty\u201d. Some detailed background information described already in [1] is omitted in this paper.\nRAN5 is asked to endorse following proposal.\nProposal 1 : For baseband-combining approach and for up to DL 64QAM, apply +\/-0.3dB(1.96sigma)  for FR2a and FR2b for up to 400MHz BW for\u201d gNB emulator SNR uncertainty\u201d.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":40890,"status":"noted","reservation_date":"2020-08-07 09:38:58","uploaded":"2020-08-07 14:21:36","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204089.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204090","title":"Proposal of MUs for FR2 spurious emission UE co-existence","source":"Anritsu","contact":"Hiroyuki Baba","contact-id":65585,"tdoctype":"discussion","for":"Endorsement","abstract":"In this contribution, we present our view on the MU value for FR2 spurious UE-coexisting test.\nFollowings are observed:\nObservation 1 : The same MU values as General spurious emission can be applied for spurious UE co-existence for corresponding frequency range except for influence of noise.\nRAN5 is asked to endorse following proposals.\nProposal 1: For PC3 spurious emission UE-coexistence (protected=n260, aggressor=n257 and n261), apply the same MU values as general spurious for f=23.45 GHz to 40.8 GHz except for DSNR which was agreed in [1]\nProposal 2: For PC3 spurious emission UE-coexistence (protected=n257\/n261, aggressor=n250), apply the same MU values as general spurious for f=23.45 GHz to 40.8 GHz except for DSNR which was agreed in [1]\nProposal 3: For PC3 spurious emission UE-coexistence (protected=57 GHz = f  =  66GHz), apply the same MU values as general spurious for f= 40.8 GHz to 66 GHz\nProposal 4 : For PC3 spurious emission UE-coexistence (protected=57 GHz = f  =  66GHz), apply DSNR=1.0dB with no relaxation for core requirement. (Just removing [ ])","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":40900,"status":"noted","reservation_date":"2020-08-07 09:38:58","uploaded":"2020-08-07 14:21:36","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204090.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204136","title":"Review on FR1 TRx test point analysis for Extreme Condition","source":"DOCOMO Communications Lab.","contact":"Takashi Akao","contact-id":83320,"tdoctype":"discussion","for":"Endorsement","abstract":"The purpose of this contribution is to review existing test point analysis for Extreme condition and to discuss the necessity of optimization.\n2\tDiscussion\n3GPP compliant UEs shall fulfil all RF core requirements not only in NC (Normal Condition) but also in EC (Extreme Temperature, Voltage) according to the Annex E of core specification [2]. \nRegarding temperature\/voltage depended test cases, in RAN5, (1) are tested for each test ID. This makes some test cases much larger in terms of number of the test points.\nTotal test point (including testing time) can be reduced if we can optimize these EC test points. Following figures describe some options for optimization. RAN5 can adopt these options if we prove applicability or reasonability to skip specific EC test points (purple highlighted) with technical justification.\n?\t(b) Option 1\t: Test EC with some test ID (e.g. #01, 05), and test only NC with the other test IDs\n?\t(c) Option 2\t: Test only corner cases (TL\/VL, TH\/VH) and skip TL\/VH and TH\/VL\nObservation 1\t: EC is fully tested in the current approach and there is a chance to optimize EC test points.\nTherefore, it is proposed that UE vendors provide technical justification in order to make the analysis of EC test points more meaningful.\nProposal 1\t:  UE vendors to provide technical justification for whether Option 1 or Option 2 is applicable in FR1 RF tests.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":41360,"status":"revised","reservation_date":"2020-08-07 12:51:42","uploaded":"2020-08-07 13:01:56","revisionof":"","revisedto":"R5-204952","release":"Rel-16","crspec":"38.521-1","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204136.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204186","title":"On Beam Peak Searches for different test configurations","source":"Keysight Technologies UK Ltd","contact":"Thorsten Hertel","contact-id":77978,"tdoctype":"discussion","for":"Endorsement","abstract":"This contribution addresses the need to perform TX and RX beam peak searches for different test configurations.\n\nThe following observations and proposals were made in this contribution\nObservation 1: Whether the beam peak searches need to be performed for different channel bandwidths, SCS, modulation, waveforms has not been decided yet.\nObservation 2: The beam peak results at the reference beam peak direction do not change between different modulations and waveforms\nProposal 1: Beam peak searches shall be performed for every CBW and SCS by default.\nProposal 2: Beam peak searches shall be performed for every modulation by default unless the device manufacturer explicitly declares that the beam peak at the QPSK modulation is applicable for the remaining 16QAM and 64QAM modulation\nProposal 3: Beam peak searches shall be performed for every waveform by default unless the device manufacturer explicitly declares that the beam peak from one waveform is applicable for the other waveform.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":41860,"status":"noted","reservation_date":"2020-08-07 15:11:41","uploaded":"2020-08-07 22:57:24","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204186.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204189","title":"Preliminary QoQZ and EIRP MU results for ETC testing","source":"Keysight Technologies UK Ltd","contact":"Thorsten Hertel","contact-id":77978,"tdoctype":"discussion","for":"Endorsement","abstract":"This contribution is providing preliminary QoQZ and EIRP MU values for a test system capable of full 3D testing under ETC.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":41890,"status":"revised","reservation_date":"2020-08-07 15:11:44","uploaded":"2020-08-07 22:57:24","revisionof":"","revisedto":"R5-204739","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204189.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204191","title":"On Larger Quiet Zone Sizes","source":"Keysight Technologies UK Ltd","contact":"Thorsten Hertel","contact-id":77978,"tdoctype":"discussion","for":"Endorsement","abstract":"This contribution addresses the need for larger quiet zone sizes and provides our view on this topic.\nThe following observations and proposals were made in this contribution\nObservation 1: It is desirable to limit the total number of quiet zone sizes\nObservation 2: It is unknown which quiet zone size will guarantee a 100% coverage for PC3 and PC1 devices.\nObservation 3: A grey-box approach, i.e., declaration of a reference point to be aligned with the centre of the quiet zone and the maximum antenna panel displacement from this reference point, could significantly increase test case coverage and allow more compact FR2 OTA system sizes.\n\nProposal 1: RAN5 to strive for 100% test coverage for PC1 and PC3 devices and close AP#87e.22\nProposal 2: Hold off on defining a quiet zone larger than 30cm until sufficient feedback has been received on AP#87e.24 and AP#87e.23","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":41910,"status":"revised","reservation_date":"2020-08-07 15:11:45","uploaded":"2020-08-07 22:57:24","revisionof":"","revisedto":"R5-204747","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204191.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204192","title":"QoQZ Verification Clarification","source":"Keysight Technologies UK Ltd","contact":"Thorsten Hertel","contact-id":77978,"tdoctype":"discussion","for":"Endorsement","abstract":"The Quality of Quiet Zone (QoQZ) procedure has been defined initially in [1] and was later incorporated in [2]. After further review of the procedure, additional clarifications are needed.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":41920,"status":"noted","reservation_date":"2020-08-07 15:11:45","uploaded":"2020-08-07 22:57:24","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204192.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204194","title":"On Re-Positioning Concept for RRM 2 AoA QoQZ Validation and DFF QoQZ MU","source":"Keysight Technologies UK Ltd","contact":"Thorsten Hertel","contact-id":77978,"tdoctype":"discussion","for":"Endorsement","abstract":"This contribution is addressing the need to clarify the re-positioning concept for QoQZ validation applied to RRM 2 AoA testing. Additionally, sample values of DFF QoQZ MU for 2 AoA RRM are presented.\nThe following observations and proposals were made in this contribution\nObservation 1: The re-positioning approach for the QoQZ is generally not applicable to RRM 2 AoA testing\nProposal 1: It is proposed that the QoQZ validation and MTSU for RRM 2 AoA test cases does not consider the re-positioning concept.\nProposal 2: Set the MU element of Quality of Quiet Zone for FR2_A, FR2_B, and FR2_C to 1.2dB for Stage 2 and to 0.3dB for Stage 1 for 2 AoA RRM test cases based on DFF implementation.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":41940,"status":"noted","reservation_date":"2020-08-07 15:11:46","uploaded":"2020-08-07 22:57:24","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204194.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204200","title":"Discussion on size of Quiet Zone above 30cm","source":"ROHDE & SCHWARZ","contact":"Jose M. Fortes Lopez","contact-id":78787,"tdoctype":"discussion","for":"Endorsement","abstract":"Following the discussion in previous meetings regarding QZ sizes bigger than 30cm in diameter, we present here our views on the next steps.\nThis is a resubmission of R5-202082 [1] with additional proposals.\nIn this contribution, the following observations and proposals were made:\nObservation 1: The attempt to cover all possible devices sizes with a discrete number of QZ sizes is not a sustainable approach.\nObservation 2: ~85% of the devices in the available dataset are covered with a 55cm QZ.\nObservation 3: a cylindrical volume defining the maximum size of the DUT becomes a sphere when DUT is rotated.\nObservation 4: maximum DUT volume defined as a cylinder has many practical advantages.\n\nProposal 1: Select 55cm as the QZ size to test devices larger than current QZ limited to 30cm.\nProposal 2: define the QZ size based on the full spherical volume occupied by the DUT.\nProposal 3: for devices not fitting the 30cm QZ, define the maximum DUT volume as a cylinder with 48cm diameter and 26cm height.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":42000,"status":"noted","reservation_date":"2020-08-07 16:29:02","uploaded":"2020-08-07 16:44:46","revisionof":"","revisedto":"","release":"Rel-16","crspec":"38.521-2","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_88_Electronic\/Docs\/R5-204200.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204213","title":"Discussion on RAN5 impact of updated Multi-Band Relaxation requirements","source":"Ericsson","contact":"Mikael Ziren","contact-id":88614,"tdoctype":"discussion","for":"Endorsement","abstract":"During the last 2 years RAN5 have worked on implementing the multi-band relaxation (MBR) requirements from 38.101-2 resulting in multiple LS exchanges with RAN4 and certification organisations GCF and PTCRB [1-5]. A solution involving multi-band testing in certification and UE declaration of MBR has been decided and implemented for a few test cases. When analysing the solution possible to achieve, RAN5 concluded that multiband relaxation cannot be fully verified in certification [6]. Hence, another LS was sent to RAN4 [5] at RAN5#85 to inform about the problems associated with MBR test implementation.\nRAN4 have now changed the MBR requirements and have sent the following response to the LS.\nProposal 1: It is proposed that RAN5 go with option 2 above that completely remove the need of MBR declaration and multiband testing. Since this will impact certification, send LS to GCF and PTCRB to inform of the decision so that they can remove the multi-band testing requirement in certification.\nProposal 2: Update MU calculation in TR38.903 changing the worst case MBR assumption from 1.75 to 0.75 dB.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":42130,"status":"noted","reservation_date":"2020-08-07 16:56:29","uploaded":"2020-08-07 19:55:31","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204213.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204214","title":"Discussion on EN-DC reference sensitivity test case structure","source":"Ericsson","contact":"Mikael Ziren","contact-id":88614,"tdoctype":"discussion","for":"Endorsement","abstract":"At RAN5#87-e meeting, a re-structuring of standalone refsens test cases in 38.521-1 was agreed in [1] with corresponding TP analysis in 38.905 [2]. This re-structuring was the outcome of AP#85.21 \u201cDefine framework for NR CA Rx test optimization by re-using higher order fallbacks results\u201d.\nSince [1] and [2] only considered standalone test cases, a new AP was created to expand with EN-DC and FR2.\nAP#87e.25\tDefine framework for NR CA (ENDC and FR2) Rx test optimization by re-using higher order fallbacks results\tE\/\/\/, Huawei, Anritsu, Qualcomm, CAICT, Samsung, DCM, CMCC, DISH , WE Certrification\tR5-202375\n\n\nThis paper addresses this action point for EN-DC Rx test cases. \nThis proposal includes a re-structuring of EN-DC Reference Sensitivity test cases in TS38.521-3 as well as a change of test coverage.\nIn this paper the definitions \u201cdefault\u201d and \u201cadditional\u201d Reference Sensitivity (refsens) test cases that were created as part of AP#85.21 are re-used. \nThe purpose of \u201cadditional\u201d test cases is to verify the exception requirements from 38.101-3. The exception requirement is only defined for two carriers normally where one is the aggressor and one is the victim. For this reason, there is no need for more than a 2CC test case.\nThe purpose of \u201cdefault\u201d test cases is to verify the non-exception requirements from 36.101 and 38.101-1. These test cases are defined from 2CC up to the max number of NR CCs possible so that the maximum NR configuration in the UE can be tested.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":42140,"status":"revised","reservation_date":"2020-08-07 16:56:29","uploaded":"2020-08-07 19:55:31","revisionof":"","revisedto":"R5-204953","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204214.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204253","title":"On FR2 Minimum Output Power relaxation and measurement uncertainty","source":"Keysight Technologies UK Ltd","contact":"Flores Fernandez Martos","contact-id":47301,"tdoctype":"discussion","for":"Endorsement","abstract":"In RAN5#85, FR2 Transmit OFF power relaxations and impact of noise were agreed in [1] and [2], based on the way forward previously agreed in RAN5#84 in [3] and [4]. This way forward was based on inputs from different TE vendors according to [5], [6], [7] and [8]. Such relaxations were aligned with the statements already drafted in [13].\nThis document describes an analysis on FR2 Minimum output power feasibility and proposes relaxations and noise impact measurement uncertainty based on a comparison with previous agreements on FR2 Tx OFF power: \nProposal 1: define FR2 Minimum output power relaxation and noise impact as per tables 1 & 2 in this document.\nProposal 2: For PC3 devices, lLeverage from EIRP measurement for FR2 Transmit OFF power (IFF) all MU factor including values except for influence of noise, which should be defined as per tables 1 and 2 above","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":42530,"status":"revised","reservation_date":"2020-08-07 18:59:40","uploaded":"2020-08-07 19:57:02","revisionof":"","revisedto":"R5-204740","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204253.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204260","title":"Discussion on DC_41C_n41A and DC_41D_n41A","source":"ROHDE & SCHWARZ","contact":"Edwin Menzel","contact-id":65839,"tdoctype":"discussion","for":"Endorsement","abstract":"Since no exceptional requirements are defined these combinations would be tested with the anchor agnostic approach, i.e., in exactly the same way as DC_41A_n41A. Since an UE has to support the fallback DC_41A_n41A for these combinations, the test coverage is fulfilled.\n\nThe summary is as follows and for further details I refer to the content of the paper:\nObservation 1: Exceptional requirements do not exist for DC_41C_n41A and DC_41D_n41A.\nObservation 2: Due to the lack of exceptional requirements and the anchor agnostic test approach a test point analysis is not required.\nObservation 3: An update of TS 38.521-4 is not required as there are no specific requirements for DC_41C-n41A and DC_41D_n41.\nObservation 4: An update of the general section 5 of TS 38.521-3 is not required since the information is already present in the specification.\nProposal 1: Set the status of DC_41C-n41A and DC_41D_n41 as complete in the work plan without updating TS 38.521-3, TS 38.521-4, TR 38.903 and TR 38.905.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":42600,"status":"revised","reservation_date":"2020-08-07 19:15:42","uploaded":"2020-08-07 23:47:38","revisionof":"","revisedto":"R5-204846","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204260.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204269","title":"On gNB emulator fading model impairments","source":"ROHDE & SCHWARZ","contact":"Edwin Menzel","contact-id":65839,"tdoctype":"discussion","for":"Endorsement","abstract":"For performance test cases of mode 1, i.e. testing under conditions with external noise, one of the MU contributors is the gNB emulator fading model impairments uncertainty. In this paper we present our assessment of this MU contributor for the baseline approach of baseband combining.\nIn summary, the uncertainty associated to gNB emulator fading model impairments been analyzed. \nObservation 1: The fading model is implemented in the baseband and thus its uncertainty does not depend on the RF frequency range nor other RF characteristics.\nObservation 2: For FR1 the MU contributor is called differently and depends on the number of TE Tx ports applied in the test.\nProposal 1: Discuss the interpretation of Fading profile power uncertainty and consider to apply the absolute DL power uncertainty in the test case.\nProposal 2: OEMs\/UE vendors to clarify whether the absolute DL power in mode 1 performance test cases has an influence on the throughput.\nProposal 3: Apply a value of \u00b10.5 dB for the MU contributor gNB emulator fading model impairments for 1Tx and \u00b10.7 dB for 2Tx.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":42690,"status":"noted","reservation_date":"2020-08-07 19:15:49","uploaded":"2020-08-07 23:48:33","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204269.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204270","title":"On the MU of FR2 OBW","source":"ROHDE & SCHWARZ","contact":"Edwin Menzel","contact-id":65839,"tdoctype":"discussion","for":"Endorsement","abstract":"The measurement uncertainty (MU) of occupied bandwidth (OBW) has been discussed during the last meetings [1] to [15]. However, no final conclusion has been reached. This contribution is an updated version of the paper submitted to RAN5#87-e [13] with respect to the agreement under TE vendors to apply 28.0 GHz as center frequency for the data provided in [9].\nProposal 1: For the MU due to frequency response apply 1.0% for 50 MHz and 100 MHz CHBWs and 2.1% for 200 MHz and 400 MHz CHBWs.\nIt has been agreed to apply DFT-s-OFDM as waveform for OBW test in the last meeting in order to optimize the SNR ratio.\nIn order to combine the MU based due to SNR and frequency response, we propose the following equations: [..]\nIn the last equation a linear sum is used since the impact of noise is systematic and acts always in the same direction\nProposal 2: Calculate the total MU based on equations (1) to (3).","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":42700,"status":"noted","reservation_date":"2020-08-07 19:15:49","uploaded":"2020-08-07 23:57:18","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204270.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204271","title":"On the AWGN flatness and signal flatness","source":"ROHDE & SCHWARZ","contact":"Edwin Menzel","contact-id":65839,"tdoctype":"discussion","for":"Endorsement","abstract":"Associated CRs in R5-204272 and R5-204273.\nFor performance test cases of mode 1, i.e. testing under conditions with external noise, one of the MU contributors is the Test System Frequency Flatness Uncertainty for AWGN. In this paper, we present our assessment of this MU contributor for the baseline approach of baseband combining.\nIn summary, the uncertainty associated to AWGN flatness and signal flatness been analyzed. \nProposal 1: Align the name and definition of the MU contributor Test System Frequency Flatness Uncertainty for AWGN to the one of LTE for FR1 and FR2 in TS 38.521-4 and TR 38.903. \nProposal 2: Apply a sensitivity factor of 0.25 in the MU calculation by specifying a divisor of 4 and Actual as the distribution in Table D-1 and Table D-2 of TR 38.903.\nProposal 3: Apply a value of \u00b13.6 dB for the MU Contributor AWGN flatness and signal flatness.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":42710,"status":"revised","reservation_date":"2020-08-07 19:15:49","uploaded":"2020-08-07 23:48:33","revisionof":"","revisedto":"R5-204748","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204271.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204274","title":"On the SNR for FR2 TRx test cases","source":"ROHDE & SCHWARZ","contact":"Edwin Menzel","contact-id":65839,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":42740,"status":"withdrawn","reservation_date":"2020-08-07 19:15:51","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_NR_LTE-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204277","title":"On FR2 EIRP OFF Power relaxation and measurement uncertainty","source":"Keysight Technologies UK Ltd, Samsung","contact":"Flores Fernandez Martos","contact-id":47301,"tdoctype":"discussion","for":"Endorsement","abstract":"In RAN5#85, FR2 Transmit OFF power relaxations and impact of noise were agreed in [1] and [2], based on the way forward previously agreed in RAN5#84 in [3] and [4]. This way forward was based on inputs from different TE vendors according to [5], [6], [7] and [8]. Such relaxations were aligned with the statements already drafted in [13].\nThis document describes an analysis on FR2 EIRP OFF output power feasibility and proposes relaxations and noise impact measurement uncertainty based on a comparison with previous agreements on FR2 Tx OFF power (TRP): \nObservation 1: EIRP OFF power requirement in PRACH Time Mask test case should be -30 dBm + TT according to core requirement and relaxations should be reviewed (correction over [14])\nProposal 1: define FR2 EIRP OFF power relaxation and noise impact as per table 1 in this document.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":42770,"status":"revised","reservation_date":"2020-08-07 19:17:03","uploaded":"2020-09-01 13:51:13","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204277.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204282","title":"PC1 Assumptions for CDF Curve for MOP EIRP Spherical Coverage","source":"Qualcomm Incorporated","contact":"Shahab Mohammad","contact-id":77324,"tdoctype":"discussion","for":"Endorsement","abstract":"This contribution proposes assumptions for PC1 device type, for CDF curve for MOP CIRP Spherical Coverage, as a response to AP coming out of RAN5-87e, R5-202845, Proposal 9.#\nProposal 1: UE Antenna Element Pattern can be refrred from TR 38.803 Table 5.2.3.3-1, with appropriate changes adhering to agreement from R5-198203.\nProposal 2: Assume 120 equally spaced beams with constant density packed in a cone that represents 20% of the area of the sphere.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":42820,"status":"noted","reservation_date":"2020-08-07 19:24:48","uploaded":"2020-08-08 07:01:22","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204282.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204293","title":"On Spurious measurement uncertainty","source":"Keysight Technologies UK Ltd","contact":"Flores Fernandez Martos","contact-id":47301,"tdoctype":"discussion","for":"Endorsement","abstract":"This document includes some proposals in order to progress on spurious measurement uncertainty gaps of the specification.\nFollowing proposals are made:\nProposal 1: Confirm ?SNR and relaxation for frequency range 57 GHz =  f  =  66GHz described in R5-202848 [1] for PC3 devices.\nProposal 2: Noise impact and relaxation for frequency range between 36 and 37 GHz for PC3 devices in spurious co-existence is defined as [1.0 dB] and [6 dB] respectively.\nProposal 3: For spurious co-existence test case, leverage other MU terms different from influence of noise from general spurious test.\nProposal 4: Follow Text proposal in Annex 1 to define MU terms for spurious co-existence test.\nProposal 5: For additional spurious test case, define influence of noise and relaxations as defined in tables 2 and 3.\nProposal 6: For additional spurious test case, leverage other MU terms different from influence of noise from general spurious test.\nProposal 7: Follow Text proposal in Annex 1 to define MU terms for additional spurious test.\nProposal 8: Adjust General spurious MU tables as shown in Annex 1.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":42930,"status":"revised","reservation_date":"2020-08-07 19:25:51","uploaded":"2020-09-01 13:51:13","revisionof":"","revisedto":"R5-204749","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204293.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204294","title":"On OBW measurement uncertainty","source":"Keysight Technologies UK Ltd","contact":"Flores Fernandez Martos","contact-id":47301,"tdoctype":"discussion","for":"Endorsement","abstract":"RAN5 has been discussing FR2 Occupied bandwidth measurement uncertainty for several meetings already ([1-[16]) with the following agreements:\n\u2022\tIn [15] the following proposals were endorsed:\n\nProposal 1: Apply a span of 1.5 CHBW for 400 MHz and use the same span for the other channel bandwidth in order to optimize the impact of noise. \nProposal 2: Select DFT-s-OFDM QPSK as waveform and modulation since it has the lowest MPR and allows to reduce the impact of noise on the OBW MU.\n\u2022\tIn [16] the following proposals were endorsed: \n\nProposal 1: OEM and chipset vendors to provide the information on the Tx spectrum shape (PSD, slope), to help determine MU of FR2 OBW test for frequency band n260.\nProposal 2: Reduce FR2 OBW span from 2*CBW to 1.5 *CBW.\nDuring offline discussions in RAN5#87e, it was indicated that same waveforms as defined in [10] could be used for FR2b (n260).\nAdditionally, simulations of noise impact and signal flatness from different test equipment vendors during RAN5#87e were diverging due to different centre frequencies. After double-checking which centre frequency was used in [10], it was agreed during offline discussions to use 28 GHz in the simulations as centre frequency.\nThis document provides updated simulation results on the noise and signal flatness impact on the FR2 OBW measurement uncertainty and makes proposals to progress\/conclude on this discussion.\nThis document provides updated simulation results on the noise and signal flatness impact on the FR2 OBW measurement uncertainty and makes proposals to progress\/conclude on this discussion.\nFollowing proposals and observations are made:\nProposal 1: Use (OBWmeas - OBWsignal) \/ CBW *100 as the metric to define OBW MU.\nProposal 2: Analyze OBW MU for SNR=15-40 dB and signal flatness \u00b12.19 dB.\nObservation 1: Big difference between RX signal flatness statistical analysis for Cases 2 & 3. \nProposal 3: Use normal distribution of variance \u00b12.19dB in each frequency point of the analyzed span to determine Rx signal flatness impact on FR2 OBW MU.\nObservation 2: At least 18 dB SNR are required to avoid a failing OBW verdict when measuring 100 MHz CBW signals.\nObservation 3: At least 25 dB SNR are required to avoid a failing OBW verdict when measuring 400 MHz CBW signals.\nObservation 4: Around 2 dB improvement could be expected in OBW SNR dynamic range when using DFT-s-OFDM instead of CP-OFDM waveforms for the same channel bandwidth.\nObservation 5: Around 4.5 dB improvement could be expected in OBW SNR dynamic range when using DFT-s-OFDM instead of CP-OFDM waveforms and CBW=400 MHz instead of CBW=4x100 MHz.\nObservation 6: Different analysis should be performed for single CC CBW=400 MHz and CA CBW = 4x 100 MHz.\nProposal 4: Define measurement uncertainty for FR2 OBW as described in Table 4.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":42940,"status":"revised","reservation_date":"2020-08-07 19:27:12","uploaded":"2020-09-01 13:51:13","revisionof":"","revisedto":"R5-204850","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204294.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204721","title":"Discussion about proposals in LS R4-2005205","source":"Huawei, Hisilicon","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":36861,"status":"noted","reservation_date":"2020-09-02 09:21:26","uploaded":"2020-09-02 09:31:11","revisionof":"R5-203686","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204721.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204729","title":"WF on SA 2Tx and NSA PC2","source":"Huawei, Hisilicon","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Discussion","abstract":"Based on the online discussion, the RAN4 dependent CRs R5-203964 and R5-203966 can\u2019t be agreed if RAN4 only agrees draft CR. So the Proposal 1 and Proposal 4 in this WF request RAN5 to endorse the contents of changes based on RAN4 agreed draft CR, so that TE vendors can start early investigation and development.","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":474200,"status":"revised","reservation_date":"2020-09-02 09:21:34","uploaded":"2020-09-02 09:31:12","revisionof":"","revisedto":"R5-204954","release":"Rel-16","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_88_Electronic\/Docs\/R5-204729.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204737","title":"Quality of the Quiet Zone measurement results for enhanced IFF","source":"ROHDE & SCHWARZ","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":33101,"status":"noted","reservation_date":"2020-09-02 09:21:42","uploaded":"2020-09-02 09:31:12","revisionof":"R5-203310","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204737.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204738","title":"FR2 Demod MU due to finite test time","source":"Qualcomm Korea","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":36691,"status":"noted","reservation_date":"2020-09-02 09:21:42","uploaded":"2020-09-02 09:31:12","revisionof":"R5-203669","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204738.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204739","title":"Preliminary QoQZ and EIRP MU results for ETC testing","source":"Keysight Technologies UK Ltd","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":41891,"status":"noted","reservation_date":"2020-09-02 09:21:42","uploaded":"2020-09-02 09:31:12","revisionof":"R5-204189","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204739.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204740","title":"On FR2 Minimum Output Power relaxation and measurement uncertainty","source":"Keysight Technologies UK Ltd","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":42531,"status":"noted","reservation_date":"2020-09-02 09:21:42","uploaded":"2020-09-02 09:31:12","revisionof":"R5-204253","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204740.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204741","title":"On FR2 EIRP OFF Power relaxation and measurement uncertainty","source":"Keysight Technologies UK Ltd, Samsung","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":42771,"status":"noted","reservation_date":"2020-09-02 09:21:42","uploaded":"2020-09-02 09:31:12","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204741.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204742","title":"Uncertainty assessment DL AWGN absolute power for enhanced IFF","source":"ROHDE & SCHWARZ","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":33111,"status":"noted","reservation_date":"2020-09-02 09:21:42","uploaded":"2020-09-02 09:31:12","revisionof":"R5-203311","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204742.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204743","title":"On ACS FR2 Measurement Uncertainty definition","source":"Keysight Technologies UK Ltd","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":34851,"status":"noted","reservation_date":"2020-09-02 09:21:42","uploaded":"2020-09-02 09:31:12","revisionof":"R5-203485","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204743.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204744","title":"On IBB FR2 Measurement Uncertainty definition","source":"Keysight Technologies UK Ltd","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":34891,"status":"noted","reservation_date":"2020-09-02 09:21:43","uploaded":"2020-09-02 09:31:12","revisionof":"R5-203489","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204744.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204745","title":"On FR2 DL absolute level uncertainty for DFF.","source":"Anritsu","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":40821,"status":"noted","reservation_date":"2020-09-02 09:21:43","uploaded":"2020-09-02 09:31:12","revisionof":"R5-204082","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204745.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204746","title":"Noise impact for FR2 test case where MPR applies","source":"Anritsu","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":40861,"status":"noted","reservation_date":"2020-09-02 09:21:43","uploaded":"2020-09-02 09:31:12","revisionof":"R5-204086","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204746.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204747","title":"On Larger Quiet Zone Sizes","source":"Keysight Technologies UK Ltd","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":41911,"status":"noted","reservation_date":"2020-09-02 09:21:43","uploaded":"2020-09-02 09:31:12","revisionof":"R5-204191","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204747.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204748","title":"On the AWGN flatness and signal flatness","source":"ROHDE & SCHWARZ","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":42711,"status":"noted","reservation_date":"2020-09-02 09:21:43","uploaded":"2020-09-02 09:31:12","revisionof":"R5-204271","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204748.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204749","title":"On Spurious measurement uncertainty","source":"Keysight Technologies UK Ltd","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":42931,"status":"noted","reservation_date":"2020-09-02 09:21:43","uploaded":"2020-09-02 09:31:12","revisionof":"R5-204293","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204749.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204846","title":"Discussion on DC_41C_n41A and DC_41D_n41A","source":"ROHDE & SCHWARZ","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":42601,"status":"noted","reservation_date":"2020-09-02 09:24:09","uploaded":"2020-09-02 09:31:14","revisionof":"R5-204260","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204846.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204848","title":"Test Tolerance review process for FR2 RRM Test cases","source":"ANRITSU LTD","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":33221,"status":"noted","reservation_date":"2020-09-02 09:24:09","uploaded":"2020-09-02 09:31:14","revisionof":"R5-203322","revisedto":"","release":"","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_88_Electronic\/Docs\/R5-204848.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204849","title":"On FR2 OBW MU","source":"Anritsu","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":40851,"status":"noted","reservation_date":"2020-09-02 09:24:09","uploaded":"2020-09-02 09:31:14","revisionof":"R5-204085","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204849.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204850","title":"On OBW measurement uncertainty","source":"Keysight Technologies UK Ltd","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":42941,"status":"noted","reservation_date":"2020-09-02 09:24:09","uploaded":"2020-09-02 09:31:14","revisionof":"R5-204294","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204850.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204951","title":"Discussion on Scope, Purpose and drafting guideline for 38.522","source":"CAICT","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":38681,"status":"noted","reservation_date":"2020-09-02 09:26:19","uploaded":"2020-09-02 09:31:17","revisionof":"R5-203868","revisedto":"","release":"Rel-16","crspec":"38.522","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204951.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204952","title":"Review on FR1 TRx test point analysis for Extreme Condition","source":"DOCOMO Communications Lab.","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":41361,"status":"noted","reservation_date":"2020-09-02 09:26:19","uploaded":"2020-09-02 09:31:17","revisionof":"R5-204136","revisedto":"","release":"Rel-16","crspec":"38.521-1","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204952.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204953","title":"Discussion on EN-DC reference sensitivity test case structure","source":"Ericsson","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":42141,"status":"noted","reservation_date":"2020-09-02 09:26:19","uploaded":"2020-09-02 09:31:17","revisionof":"R5-204214","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"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_88_Electronic\/Docs\/R5-204953.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204954","title":"WF on SA 2Tx and NSA PC2","source":"Huawei, Hisilicon","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":88,"ainumber":"5.3.2.17","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":474201,"status":"noted","reservation_date":"2020-09-02 09:26:19","uploaded":"2020-09-02 19:01:09","revisionof":"R5-204729","revisedto":"","release":"Rel-16","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_88_Electronic\/Docs\/R5-204954.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]