[{"name":"R5-195520","title":"Reply LS on MOP for UL MIMO","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"RAN4 thanks RAN5 for the LS on maximum output power for UL MIMO.  RAN4 agrees with the assessment from RAN5 that it may not be possible to test maximum output power for UL MIMO due to non-zero MPR specified for CP-OFDM waveforms.  RAN4 has considered several options to enable testing at maximum output power, but none were seen as practical, including the proposal from RAN5 that RAN4 change its MPR specification to define specific RB configurations for which the MPR allowance is decreased to 0 dB.  \nRAN4 instead suggests an alternative formulation where MOP for UL MIMO can be tested with a waveform chosen from those which are specified with the smallest MPR of 1.5 dB.  The lower test limit for MOP should then be reduced accordingly by the amount of specified MPR, namely, 1.5 dB.  The tolerance can be maintained at +2\/-3 dB. \nActions: RAN4 asks RAN5 to take the above information into consideration when defining test configurations and limits for maximum output power for UL MIMO.","secretary_remarks":"","agenda_item_sort_order":39,"ainumber":"5.2","ainame":"\tReview incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":55200,"status":"noted","reservation_date":"2019-07-17 08:24:15","uploaded":"2019-07-24 17:48:03","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_NR_LTE-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"R5-192509","lsto":"","Cc":"","lsoriginalls":"R4-1907116","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_84_Ljubljana\/Docs\/R5-195520.zip","group":"R5","meeting":"R5-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-195521","title":"Reply LS on SA Option 2 Core Requirement Dependencies","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"Response to:\tR5-192831 (R4-1902819)\nRelease:\tRelease 15 and forwards\nWork Item:\t5GS_NR_LTE-UEConTest\nRAN4 thanks RAN5 for raising the pending issues for SA Option 2 Core Requirement. \nIn RAN4 #91 meeting, consensus has been reached on the listed issue provided by RAN5 after the discussion on RF part. RAN4 has updated the pending issue list with attachment in the reply LS. \nActions: To: 3GPP TSG RAN WG5: RAN4 asks RAN5 to take the feedback into consideration for future work.","secretary_remarks":"","agenda_item_sort_order":39,"ainumber":"5.2","ainame":"\tReview incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":55210,"status":"noted","reservation_date":"2019-07-17 08:24:15","uploaded":"2019-07-24 17:48:03","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_NR_LTE-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"R5-192831 \/ R4-1902819","lsto":"","Cc":"","lsoriginalls":"R4-1907427","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_84_Ljubljana\/Docs\/R5-195521.zip","group":"R5","meeting":"R5-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-195522","title":"Reply LS on applicability of LTE anchor agnostic to specific RF test cases","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"Response to:\tR5-190730 from TSG RAN WG5\nWork Item:\t5GS_NR_LTE-UEConTest\nRAN4 thanks RAN5 for the LS on applicability of LTE anchor agnostic to specific RF test cases.  RAN4 agrees with the assessment from RAN5 that there may be some impact to the identified test cases of reference sensitivity and general spurious emissions for inter-band EN-DC that may not be fully captured by the anchor agnostic approach.  Therefore, RAN4 has modified its specification to include an additional requirement for inter-band EN-DC reference sensitivity and general spurious emissions with the condition that both E-UTRA and NR uplinks are simultaneously active.\nHowever, RAN4 feels that it is preferred to verify the requirement for only a single EN-DC configuration per NR band, rather than to verify for all supported EN-DC configurations considering the amount of test cases among other reasons.  The choice of configuration to verify is left to RAN5 or to the tester to decide.  Moreover, for the general spurious emissions requirement, RAN4 believes it is sufficient to verify emissions for only those frequencies where second or third order intermodulation products land rather than to verify all frequencies.\n2. Actions: RAN4 asks RAN5 to take the above information as well as the attached draft CR describing modifications to the core requirement into consideration when defining the reference sensitivity and general spurious emissions test cases for inter-band EN-DC.","secretary_remarks":"","agenda_item_sort_order":39,"ainumber":"5.2","ainame":"\tReview incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":55220,"status":"noted","reservation_date":"2019-07-17 08:24:15","uploaded":"2019-07-24 17:48:03","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_NR_LTE-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"R5-190730","lsto":"","Cc":"","lsoriginalls":"R4-1907491","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_84_Ljubljana\/Docs\/R5-195522.zip","group":"R5","meeting":"R5-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-195523","title":"LS on FR2 maxUplinkdutycycle","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"Release:\tRel-15\nWork Item:\tNR_newRAT-Core\nRAN4 has continued the discussion on maxUplinkDutyCycle-FR2 for FR2 UE capability after sending LS [1] earlier and made the following agreements:  \n-\tEvaluation period for UE capability maxUplinkDutyCycle-FR2 for is 1 seconds \n-\t15 % value should be allowed for UE capability maxUplinkDutyCycle-FR2 in addition to values what were in WF from plenary [2] i.e. possible declarable values are 15%, 20%, 25%, 30%, 40%, 50%, 60%, 70%, 80%, 90% and 100%\n-\tIf the field of UE capability maxUplinkDutyCycle-FR2 is present and the percentage of uplink symbols transmitted within any 1 s evaluation period is larger than maxUplinkDutyCycle-FR2, the UE follows the uplink scheduling and can apply P-MPRf,c\n-\tIf the field of UE capability maxUplinkDutyCycle-FR2 is absent, the compliance to electromagnetic power density exposure requirements are ensured by means of scaling down the power density or by other means.\n-\tmaxUplinkDutyCycle-FR2 is applicable for all power classes in FR2\nWith these agreements, RAN4 considers work for maxUplinkDutyCycle-FR2 to be completed\nActions: To RAN2 group: RAN4 respectfully asks RAN2 to accommodate agreements above in their work","secretary_remarks":"","agenda_item_sort_order":39,"ainumber":"5.2","ainame":"\tReview incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":55230,"status":"noted","reservation_date":"2019-07-17 08:24:15","uploaded":"2019-07-24 17:48:03","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"R4-1907458","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_84_Ljubljana\/Docs\/R5-195523.zip","group":"R5","meeting":"R5-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-195527","title":"Reply LS to \u2018LS on multi-band test cases for FR2 Ues","source":"GCF CAG","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"GCF CAG thanks 3GPP TSG RAN5 for their LS \u2018LS on multi-band test cases for FR2 UEs\u2019. CAG#59 discussed the assumption made by the 3GPP TSG's in definition of MB Relaxations.\nGCF is a member driven organisation and introduction of new bands for certification is based on member requirements, mainly Operator member deployment plans. GCF does not automatically  include  every band defined in 3GPP specs into the scope of certification. A test case to be mandatory for GCF certification in a band is dependent on\n\u2022\tBand specific work item is defined and activated\n\u2022\tTest case has been validated and is in \u2018Full Validation Status' (Cat A or B) due to work item activation in the valid CC version selected by device vendor for certification at the time of certification\nHence GCF certification scheme mandates testing only in bands that have band specific work item active  at the time of device certification. To mitigate the risks identified in the RAN5 LS and to bring transparency in GCF certifications, CAG#59 agreed attached Tdoc CAG-19-313r2, which requires devices being certified to declare the MB relaxation budget across all supported bands (both certified and not certified) with testing limited to certified bands.\nSpecific feedback on the questions asked in 3GPP RAN5 LS\n1. The approval of Tdoc CAG-19-313r2 requires the use of same relaxation even when GCF certification testing is split in multiple labs.\n2a. Testing is mandated in bands that have band specific work item active .\n2b. The declaration of MBp and MBs values in CC Annex F2( for all supported bands) as part of certification, assures ?MBP,n and ?MBS,n per band  satisfy the ?MBP (dB) and ?MBS (dB) according to Table 6.2.1.3-4 in TS 38.521-2. \n3. Validations are done per band basis for all bands included  in the scope of GCF certification and shall correctly account for UE vendor declared multi-band relaxation values.\nActions: GCF-CAG requests 3GPP RAN5 to take above feedback into consideration.","secretary_remarks":"","agenda_item_sort_order":39,"ainumber":"5.2","ainame":"\tReview incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":55270,"status":"noted","reservation_date":"2019-07-17 08:24:15","uploaded":"2019-08-19 14:21:36","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"CAG-19-310","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_84_Ljubljana\/Docs\/R5-195527.zip","group":"R5","meeting":"R5-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-196960","title":"Reply LS on 5G-NR FR2 Transmitter & Receiver Testability Issues","source":"ARIB","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Discussion","abstract":"3GPP-RAN Support WG (RSW) in Mobile Partnership Subcommittee of ARIB would like to thank 3GPP TSG RAN for their liaison statement on \u201c5G-NR FR2 Transmitter & Receiver Testability Issues\u201d [1] and appreciates every effort being made by TSG-RAN and relevant WGs on this matter. RSW of ARIB would like to provide the following information as a response to the LS and expects this information will help to work towards reasonable technical solutions in a sensible manner.\n1. RAN respectfully requests technical input to address 5G-NR FR2 Transmitter and Receiver Testability issues.\nRSW of ARIB has recognized the subject (FR2 testability issue), however has no useful solution in hand that could be provided to 3GPP. RSW expects 3GPP to have a reasonable solution and will continue to support and collaborate with TSG-RAN and the relevant WGs.\n2. RAN is seeking input on whether executing these tests with the mentioned relaxations is acceptable from regulatory point of view.\nRSW of ARIB would like to provide the following relevant information regarding \u2018Test limit\u2019 or \u2018Test condition\u2019 specified in [2],[3],[4] and [5] with \u2018Test tolerance\u2019 derived as the difference between the minimum requirements set in 3GPP and the test limits under the technical requirements. It should be noted that the way the technical requirements are defined is in line with the concepts of \u201cTest tolerance\u201d and \u201cTest limit\u201d as described in [6], [7] and [8].","secretary_remarks":"","agenda_item_sort_order":39,"ainumber":"5.2","ainame":"\tReview incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":696000,"status":"noted","reservation_date":"2019-09-03 11:42:45","uploaded":"2019-09-03 11:47:53","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_84_Ljubljana\/Docs\/R5-196960.zip","group":"R5","meeting":"R5-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-196966","title":"Reply LS to 3GPP RAN5 regarding MB relaxation (R5-195451)","source":"PTCRB PVG","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"PTCRB PVG thanks 3GPP RAN WG5 for the LS on MB relaxation. We understand that 3GPP RAN WG5 implemented the core requirements from 3GPP RAN WG4 on multi-band relaxation into a few FR2 single-band test cases with a set of assumptions on implementation, validation and execution of these test cases.\nThere are different \u2018multi-band relaxation\u2019 values being declared for UE implementation with identical band combinations supported. So, 3GPP RAN WG5 is suggesting that all supported bands are declared to prevent the misuse of the MB relaxation applied.\nRAN4 had agreed Relaxation to UEs that support multiple FR2 bands, minimum requirement for peak EIRP and EIRP spherical coverage. PTCRB PVG understand that RAN5 reflected this in TS 38.521-2 test cases 7.3.2 and 7.3.4 and sent an LS to GCF and PTCRB to inform us about the requirements and the assumptions made.\nWe reviewed the LS and would like to inform 3GPP RAN WG5 that PTCRB PVG will make it part of the PTCRB Primary Labs responsibility to ensure consistency in using the same MBR values for all FR2 band supported of the same devices. Also, this process will be incorporate into the relevant PTCRB PRDs.","secretary_remarks":"","agenda_item_sort_order":39,"ainumber":"5.2","ainame":"\tReview incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":696600,"status":"noted","reservation_date":"2019-09-03 11:42:46","uploaded":"2019-09-03 11:47:53","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"R5-195451","lsto":"","Cc":"","lsoriginalls":"PVG86_0273_19","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_84_Ljubljana\/Docs\/R5-196966.zip","group":"R5","meeting":"R5-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]