[{"name":"R5-202804","title":"LS on structure of NR CA reference sensitivity requirements in 38.101-1","source":"TSG WG RAN5","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":286,"ainumber":"5.6","ainame":"\tOutgoing liaison statements for provisional approval","tdoc_agenda_sort_order":255300,"status":"revised","reservation_date":"2020-06-01 16:35:45","uploaded":"2020-06-10 14:56:21","revisionof":"","revisedto":"R5-202963","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"R5-202375","lsto":"TSG WG RAN4","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_87_Electronic\/Docs\/R5-202804.zip","group":"R5","meeting":"R5-ah-38102","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-202805","title":"LS on ambiguity in output power requirements for power class 2 UE for EN-DC","source":"TSG WG RAN5","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS out","for":"Approval","abstract":"Release:\tRelease 15\nWork Item:\t5GS_NR_LTE-UEConTest\nRAN5 has discussed the core requirements in the Rel-15 version of TS 38.101-3 for maximum output power (MOP) for intra-band contiguous EN-DC operation in power class 2 (PC2) without reaching any agreement on how to interpret the requirements due to an ambiguity in RAN4 specifications caused by following sentence in TS38.101-3 V15.9.0, clause 6.1:\n\u201cUnless otherwise stated, if UE indicates IE maxNumberSRS-Ports-PerResource = n2 in NR standalone operation mode, the said UE shall meet the NR requirements for either power class 2 or power class 3 in EN-DC within FR1 if UE indicates IE maxNumberSRS-Ports-PerResource = n1 for EN-DC on this NR band.\u201d\nSome companies in RAN5 are of the opinion that:\n1.\ta UE supporting PC2 in EN-DC and PC2 for NR will need to fulfil a PCMAX_L,f,c,,NR = 26 dBm (the lower limit of the configured output power for NR carrier) in the tested scenario (cf TS 38.101-3,  6.2B.4.1.1)\n2.\tWith non-overlapping transmission the configured power requirements from 38.101-1 apply for NR carrier with the modifications in TS38.101-3 (PCMAX_L,f,c,,NR = 26 dBm)\n3.\tThe requirements from 38.101-1 state that if the UL-MIMO UE is not configured with UL-MIMO the SA MOP requirements in 6.2.1 applies meaning 26 dBm for PC2 UE\n4.\tA PC2 UE supporting 2 port SRS in SA mode (UL-MIMO) but only 1 port SRS in NSA mode (no UL-MIMO) is allowed to transmit either as PC2 or PC3 UE.  (cf TS 38.101-3,  6.1)\n5.\tRequirements in bullet 1 and 2 conflicts with requirements in bullet 4. \n6.\tRequirements in bullet 3 conflicts with requirements in bullet 4\nOther companies are of the opinion that PCMAX_L,f,c,,NR could be either 26 dBm or 23 dBm for the UE supporting PC2 in EN-DC and PC2 for NR due to the TS38.101-3 sentence quoted above.\nIt is observed that the quoted sentence from TS38.101-3 does not exist in Rel-16 version of the specification\nRAN5 is therefore seeking guidance from RAN4 on how to correctly test MOP for a EN-DC capable PC2 UE.\nActions: To RAN4 group: RAN5 requests RAN4 to:\n1.\tClarify the definitions of PPowerClass and PPowerClass, EN-DC, and if these parameters are identical to the UE signalled power class for NR and EN-DC respectively\n2.\tHow to evaluate PCMAX_L,f,c,,NR in the scenario indicated in the Overall Description for Rel-15.","secretary_remarks":"","agenda_item_sort_order":286,"ainumber":"5.6","ainame":"\tOutgoing liaison statements for provisional approval","tdoc_agenda_sort_order":255400,"status":"approved","reservation_date":"2020-06-01 16:35:45","uploaded":"2020-06-10 14:56:21","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_NR_LTE-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"R5-202374","lsto":"TSG WG RAN4","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_87_Electronic\/Docs\/R5-202805.zip","group":"R5","meeting":"R5-ah-38102","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-202806","title":"LS on RF testing of 4Rx capable UE","source":"TSG WG RAN5","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS out","for":"Approval","abstract":"Release:\tRelease 15\nWork Item:\t5GS_NR_LTE-UEConTest\nRAN5 has discussed on the necessity of verifying RF 2Rx requirements with 4Rx capable UE.\nIn TS 38.101-1 section 7.2, it\u2019s specified that UE shall be verified against 2Rx in all operating bands and with additional 4Rx ports requirements on the supported 4Rx operating bands. This would mean performing Rx tests twice on 4Rx bands and considering this leads to double the testing time for 4Rx bands, RAN5 would like to clarify RAN4 requirement in Clause 7:\nFor the requirements in Clause 7, the UE shall be verified with two Rx antenna ports in all supported frequency bands. Additional requirements for four Rx ports shall be verified in operating bands where the UE is equipped with four Rx antenna ports.\nThe above rules apply for all clauses with the exception of clause 7.9.\nIn 4Rx Bands, it is RAN5 view that for requirements other than single carrier REFSENS, testing the UE with 4Rx antenna ports with corresponding requirements, would be sufficient to verify the Rx performance. \nAdditionally, RAN5 discussed the testability of 2Rx antenna ports in 4Rx bands to ensure the UE is only tested with 2Rx antenna ports during the test. RAN5 has identified one option would be to connect 2 Rx antenna ports based on OEM declaration. \nActions: To RAN4 group: RAN5 request RAN4 to:\n1.\tConfirm RAN5 view that for requirements other than single carrier REFSENS, testing the UE with 4Rx antenna ports with corresponding requirements, would be sufficient to verify the Rx performance.\n2.\tConfirm whether connecting UE declared 2Rx antenna ports suffices to test 2Rx requirements on 4Rx bands","secretary_remarks":"","agenda_item_sort_order":286,"ainumber":"5.6","ainame":"\tOutgoing liaison statements for provisional approval","tdoc_agenda_sort_order":255301,"status":"approved","reservation_date":"2020-06-01 16:35:45","uploaded":"2020-06-10 14:56:21","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_NR_LTE-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG WG RAN4","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_87_Electronic\/Docs\/R5-202806.zip","group":"R5","meeting":"R5-ah-38102","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-202963","title":"LS on structure of NR CA reference sensitivity requirements in 38.101-1","source":"TSG WG RAN5","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS out","for":"Approval","abstract":"Release:\tRelease 15\nWork Item:\t5GS_NR_LTE-UEConTest\nIn recent years, RAN5 have spent considerably effort to add test coverage for the thousands of LTE CA configurations defined in 3GPP. The test point analysis and lower order fallback test optimization is required to be done per CA configuration which is slowing down the progress of certification.\nIn order to optimize this for NR, RAN5 have come up with a different approach for NR that is believed to greatly reduce this effort. This new approach is relying on some key properties of the RAN4 core requirements in TS 38.101-1, 7.3A that is new compared to LTE; the exceptions in 7.3A.4 includes only aggressor and victim band and are independent on bandwidth class. \nFrom this, RAN5 have optimized the standalone NR CA test cases and restructured them so that:\n\u2022\tTo verify sensitivity exceptions in TS 38.101-1 clause 7.3A it is sufficient to configure 2-3CC (only aggressor and victim)\n\u2022\tTo enable test of maximum number of CCs the UE is capable of, another test case is defined where only single carrier requirements are verified (test parameters chosen so that no exceptions apply)\nIn order for this approach to be successful in the long term, it is important for RAN5 to know if RAN4 intend to keep the current requirement structure where the requirements are not listed per CA configuration but only per exception.\nThis from a RAN5 point of view advantageous requirement structure is defined in clause 7.3A.4 (UL harmonic interference), but not fully in 7.3A.2.4 (SDL), 7.3A.5 (2UL intermodulation) and 7.3A.6 (Cross band isolation). In the latter clauses, the CA configuration is explicitly listed in the requirement. However, the requirements seem to be the same for a certain band combination regardless of bandwidth class.  \nActions: To RAN4 group: RAN5 requests RAN4 to:\n1.\tTo inform if the requirement structure in clause 7.3A.4 listing only aggressor and victim will be retained in future.\n2.\tTo consider the possibility of doing the same in 7.3A.5 and 7.3A.6\n3.\tTo consider the possibility of moving (some of) the SDL requirements in 7.3A.2.4 to 7.3 so they can be treated as single carrier requirement.","secretary_remarks":"","agenda_item_sort_order":286,"ainumber":"5.6","ainame":"\tOutgoing liaison statements for provisional approval","tdoc_agenda_sort_order":255300,"status":"approved","reservation_date":"2020-06-01 17:00:21","uploaded":"2020-06-10 14:56:28","revisionof":"R5-202804","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_NR_LTE-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"R5-202375","lsto":"TSG WG RAN4","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_87_Electronic\/Docs\/R5-202963.zip","group":"R5","meeting":"R5-ah-38102","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]