[{"name":"R5-225918","title":"LS on work towards two new recommendations \"\"Generic unwanted emission characteristics of base stations\/mobile stations using the terrestrial radio interfaces of IMT-2020\"\"","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"Response to:\tLS R4-2119596 on work towards two new recommendations \"Generic unwanted emission characteristics of base stations\/mobile stations using the terrestrial radio interfaces of IMT-2020\" from ITU-R Working Party 5D\nIn the LS from ITU-R WP5D in R4-2119596, the group \u201ckindly invite the Proponents of IMT-2020 to provide relevant materials for these new Recommendations consistent with the Recommendation ITU-R M.2150\u201d. This LS gives a response for 3GPP 5G-RIT concerning Generic unwanted emission characteristics of base stations using the terrestrial radio interfaces of IMT-2020 including information on the requirement reference point (e.g. power at antenna connector or TRP).\nAttached to the LS is a proposed Annex for Generic unwanted emission characteristics of base stations for 3GPP 5G-RIT. The following 3GPP specifications are used as reference:\n\u2022\tOperating bands (1): 3GPP TS 38.104 V17.6.0 (2022-06), \u201c3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Base Station (BS) radio transmission and reception (Release 17)\u201d\n\u2022\tConducted requirements (3): 3GPP TS 38.141-1 V17.6.0 (2022-06), \u201c3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Base Station (BS) conformance testing Part 1: Conducted conformance testing (Release 17)\u201d.\n\u2022\tRadiated requirements (4): 3GPP TS 38.141-2 V17.6.0 (2022-06), \u201c3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Base Station (BS) conformance testing Part 2: Radiated conformance testing (Release 17)\u201d.)\u201d\n2\tActions: To TSG RAN: RAN WG4 asks TSG RAN to take the above information and the attached Annex for Generic unwanted emission characteristics into account when drafting the LS response to ITU R WP5D.","secretary_remarks":"","agenda_item_sort_order":4,"ainumber":"3","ainame":"\tIncoming Liaison Statements","tdoc_agenda_sort_order":59180,"status":"noted","reservation_date":"2022-06-10 05:38:31","uploaded":"2022-10-06 15:01:20","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"R4-2119596","lsto":"TSG RAN","Cc":"TSG WG RAN5","lsoriginalls":"R4-2214737","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_97_Toulouse\/Docs\/R5-225918.zip","group":"R5","meeting":"R5-97","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-225921","title":"WF on NR MIMO OTA","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"This LS is to provide information on the technical progress of NR MIMO OTA WI in 3GPP RAN4. \nBased on the outcome of the Rel-16 SI TR38.827, RAN4 has finalized the core part of Rel-17 NR MIMO OTA WI in RAN#96e, the outcome is captured in TS38.151 v17.1.0. For performance part, RAN4 has finalized the Figure of Merits (FoM) definition, performance requirements of FR1 TRMS for n41 and n78 bands [1].\nSome main progresses are summarized as follows:\n1.\tFigure of Merits (FoM) for NR MIMO OTA performance requirements:\n-\tFor FR1 MIMO OTA:\n-\tThe average Total Radiated Multi-antenna Sensitivity (TRMS) of free space data mode portrait (FS DMP), free space data mode landscape (FSDML), and free space data mode screen up (FS DMSU), is the FoM of FR1 MIMO OTA requirement. \n-\t70% of the maximum theoretical throughput (TP) is the outage for FR1 MIMO OTA. The EUT shall meet 70%TP in 11 of total 12 azimuthal orientations and meet 90%TP in 10 of 12 azimuthal orientations.\n-\tFor FR2 MIMO OTA:\n-\tThe MIMO Average Spherical Coverage (MASC) is the FoM of FR2 MIMO OTA requirement. The MASC is determined by the averaging of the best 18 sensitivity values among the 36 test points for power class 3 UE.\n-\tIf the number of test points where the UE can meet 70% maximum throughput outage even under maximum downlink power condition is less than [18], then UE fails the test.\n2.\tTest parameters:\n-\tThe maximum downlink RS EPRE for FR1 is defined as -80dBm\/15kHz (or equivalent -77dBm\/30kHz), and [-79.1dBm\/120kHz] for FR2.\n-\t10MHz BW for FR1 FDD, 40MHz BW for FR1 TDD, 100MHz for FR2 TDD. \n3.\tChannel models:\n-\tUmi CDL-C and Uma CDL-C for 2x2 and 4x4 FR1 \n-\tUmi CDL-C for FR2\n4.\tChannel model validation:\n-\tReference values and pass\/fail limits for FR1 and FR2 channel model validation are specified.\n-\tFor the detailed agreements for channel model validation, please refer to the approved WFs [1-3].\n5.\tPreliminary measurement uncertainty (MU) assessment and recommended test tolerance (TT) values:\n-\tRAN4 approved the preliminary MU budget in R4-2200968 [4] and R4-2210937 [5] for FR1 MPAC system and FR2 3D-MPAC system, respectively.\n-\tRAN4 recommended TT values for FR1 TRMS as 0.6* the preliminary MU budget, i.e., 1.8dB for n41 and 2dB for n78. \n-\tConsidering the relationship between test requirements and TT, although final TT will be decided by RAN5, it is suggested not to change the TT values for FR1 MIMO OTA TRMS in RAN5.\n6.\tFR1 MIMO OTA lab alignment activity:\n-\tRAN4 performed a successful FR1 MIMO OTA lab alignment activity [6], 6 volunteered labs including CAICT, CMCC&BUPT, Huawei, MediaTek, Xiaomi, and Apple are confirmed as aligned labs.\n7.\tPerformance test campaign\n-\tAn FR1 MIMO OTA performance test campaign has been performed based on the agreed framework [7] to collect measurement results from aligned labs by anonymous approach [8]. The TRMS requirements are derived from the collected results. \n-\tThe minimum number of devices for defining requirements for each band is agreed as 15. In the performance test campaign, 27 data and 24 data have been collected for n41 and n78 bands, respectively.\n8.\tFR1 TRMS minimum requirements\n-\tFR1 TRMS minimum performance requirements for NR handheld UEs operating on SA mode in free space and the primary mechanical mode are defined as below: [..]\n2\tActions: To 3GPP RAN5, CTIA MOSG and CCSA TC9 WG1: 3GPP RAN4 asks 3GPP RAN5, CTIA MOSG, and CCSA TC9 WG1 to take the above information into account.","secretary_remarks":"","agenda_item_sort_order":4,"ainumber":"3","ainame":"\tIncoming Liaison Statements","tdoc_agenda_sort_order":59210,"status":"noted","reservation_date":"2022-06-10 05:38:31","uploaded":"2022-10-06 15:01:20","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"NR_MIMO_OTA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG WG RAN4","Cc":"TSG WG RAN5, CTIA MOSG, CCSA TC9 WG1","lsoriginalls":"R4-2215136","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_97_Toulouse\/Docs\/R5-225921.zip","group":"R5","meeting":"R5-97","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-225923","title":"LS on the feasibility of testing UE initiated SDT data transmission in RRC_INACTIVE","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Action","abstract":"During the RAN4#104bis meeting, RAN4 has made agreements regarding RRM test procedures for CG-SDT TA validation. As part of these agreements, it has been identified that there is a need for multiple CG-SDT procedures following each other during a test.\nWith the current RAN4 understanding of test mode B from 38.509, that would have to be implemented as outlined in Figure 1.\nFigure 1: Test procedure for multiple CG-SDT procedures \u2013 current understanding.\n\nSince re-entering RRC connected mode could increase testing time, it would be a clear benefit if the test would not have to re-enter connected mode multiple time during a test, such that the test could be implemented as outlined in Figure 2 and figure 3. In these figures at least 2 SDT transmissions can be triggered by the test equipment with control of the transmission time using a single or multiple test mode command. Options could include configuring periodic triggering of SDT messages with a single test mode command as in figure 2 or multiple test mode commands as in Figure 3. Regarding those options, RAN4 has the following questions:\n1.\tCan TE send Data packets to UE in RRC_INACTIVE for multiple SDT sessions requiring TA validation? Either configured multiple Data packets or one SDT session after another SDT session?\n2.\tShould the timer T_delay_modeB be explicitly included in RAN4 RRM test design?\n3.\tIf yes, how to set the timer T_delay_modeB for the second SDT transmission? Will it be automatically set when data arrival at UE? Or this should be set by TE explicitly each time after its expiry?\nFigure 2: Test procedure for multiple CG-SDT procedures - without entering connected mode between CG-SDT procedures.\nFigure 3: Test procedure for multiple CG-SDT procedures - without entering connected mode between CG-SDT procedures.\nThe options in Figure 1, Figure 2 and Figure 3 were identified as potential candidates for the testing of SDT, however RAN4 tends to prefer the options in Figure 2 or Figure 3 or other options that can avoid the need for UE to re-enter RRC connected mode, since it results in reduced testing time. \n2. Actions: To: RAN WG5: RAN4 asks RAN5 to provide feedback on whether a test mode can trigger 2 or more CG-SDT transmissions in RRC inactive with independently controlled timing without need for going to RRC connected in between transmissions.","secretary_remarks":"","agenda_item_sort_order":4,"ainumber":"3","ainame":"\tIncoming Liaison Statements","tdoc_agenda_sort_order":59230,"status":"noted","reservation_date":"2022-06-10 05:38:31","uploaded":"2022-10-25 10:32:27","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"NR_SmallData_INACTIVE-Perf"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"R4-2217242","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_97_Toulouse\/Docs\/R5-225923.zip","group":"R5","meeting":"R5-97","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-225924","title":"LS on 3GPP NR TRP TRS OTA requirements","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"3GPP RAN4 would like to inform the above standardization and certification bodies on the finalization of the definition of Rel-17 NR FR1 TRP TRS OTA requirements. \nIn RAN#97-e meeting, September 2022, 3GPP successfully concluded the Rel-17 Work Item on NR_FR1_TRP_TRS with the following key outcome. \nRAN4 has specified the OTA requirements and permitted test method for FR1 TRP TRS in published Technical Specification 38.161 v17.0.0 [1].\n?\tIn Rel-17, the TRP and TRS minimum requirements are defined as an average of Hand Left and Hand Right (Browsing mode) for bands n41 and n78, for NR standalone (SA) operation mode. The TRP and TRS minimum requirements are applicable for Power Class 2 handheld devices wider than 72mm and narrower than or equal to 92 mm.\n?\tThe following actions were performed in RAN4 to conclude the TRP TRS requirement work:\n1.\tRAN4 performed a successful FR1 TRP TRS Lab alignment activity, all the participated 8 labs (ISO 17025 accredited labs) are well aligned based on Round-Robin test of reference devices with anechoic chamber test system.\n?\tFinal pass\/fail limits for Rel-17 FR1 TRP TRS lab alignment activity was defined as 1.2dB for TRP and 1.5dB for TRS\n?\tThe lab alignment results were summarized in [2] \n2.\tRAN4 performed a performance test campaign to collect measurement results from aligned test labs based on agreed working procedure [3].\n3.\tThe TRP TRS minimum requirements are defined based on per-band Data driven approach with CDF analysis of all the collected measurement results. All the measured raw data of performance campaign was summarized in [4]. \n?\tThe recommended Test Tolerance from RAN4 to RAN5 are 1.1 dB for TRP, and 1.4 dB for TRS (computed as 0.62 * MU) for n41 and n78, CBW 100 MHz.\nMeanwhile, 3GPP also approved a new Work Item as NR_FR1_TRP_TRS_enh in Rel-18 [5], targets enhanced FR1 OTA test methodologies and more requirements for FR1 TRP and TRS, current high-level working scope can be summarized as (the Rel-18 scope might be further updated in 3GPP):\n?\tThe reference anechoic chamber test methodology to support new features e.g., Tx Diversity, one-layer UL MIMO, FR1 RedCap, and Carrier Aggregation. Reverberation chamber test methodology as an alternative is also considered.   \n?\tTRP TRS requirements for more NR bands with UE configured by 1Tx and 2Tx are considered.\n3GPP RAN4 respectfully asks all the standardization and certification bodies to take into consideration the above NR TRP TRS OTA requirements and test methodologies in their work.\n2\tActions: To all the OTA standardization and certification bodies: 3GPP RAN4 asks all the standardization and certification bodies to take into consideration the above NR TRP TRS OTA requirements and test methodologies in their work.","secretary_remarks":"","agenda_item_sort_order":4,"ainumber":"3","ainame":"\tIncoming Liaison Statements","tdoc_agenda_sort_order":59240,"status":"noted","reservation_date":"2022-06-10 05:38:31","uploaded":"2022-10-25 10:32:27","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"NR_FR1_TRP_TRS_enh"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"R4-2217457","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_97_Toulouse\/Docs\/R5-225924.zip","group":"R5","meeting":"R5-97","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-226537","title":"LS to 3GPP CT1 to review mandate of the implementation of Manual Network selection mode for Wearable form factors","source":"GCF CAG","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"Document CAG-22-253 was presented and discussed during the CAG#73 meeting.  The discussion raised important points about the risks related to maintaining the status-quo of the mandates of certain radio features that may either not be practical to implement in certain form factors such as Wearables or, due to the evolution of use cases, are no longer useful.\nMaintaining such mandates on OEMs forces the implementation of the features simply for the sake of certification and not for use by the end user or product stakeholders (eg. network operators) when commercialized.\nToday cellular connected watches wholly depend on Automatic Network selection for correct operation.  Connected watches can make use of call forking or \u201cOneNumber\u201d service, this service works great for customers who are on their HPLMN or a VPLMN that supports the feature.  However the feature works poorly in the case of a VPLMN that cannot support the feature.  Therefore Automatic network selection is critical to ensure the best user experience and manual network selection could result in the user disabling unintentionally their voice service.\nThere should be a mechanism available for OEMs of these types of devices to allow them not to certify this feature and therefore leave it disabled.\nGCF CAG thanks the 3GPP groups and looks forward to further fruitful collaboration.\nActions: GCF CAG kindly requests that 3GPP CT1 review the necessity for the mandate of the implementation of Manual Network selection mode and explore ways of making the feature optional.","secretary_remarks":"","agenda_item_sort_order":4,"ainumber":"3","ainame":"\tIncoming Liaison Statements","tdoc_agenda_sort_order":65370,"status":"noted","reservation_date":"2022-02-11 17:02:36","uploaded":"2022-11-02 17:04:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"CAG-22-321","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_97_Toulouse\/Docs\/R5-226537.zip","group":"R5","meeting":"R5-97","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]