[{"name":"R5-205037","title":"LS on 5G NR Over The Air test methodologies and performance requirements","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"RAN4 thanks NGMN for their LS R4-2009502 [1] on 5G NR OTA test methodologies and performance requirements. \nRAN4 has been working on NR OTA test methodologies and performance requirements for NR devices on FR1 and FR2, both NSA and SA. The status is summarized:\n-\tNR MIMO OTA test methodologies and performance requirements related SI\/WIs:\no\tThe Rel-16 SI: Study on radiated metrics and test methodology for the verification of multi-antenna reception performance of NR UEs was focused on developing test methodologies of NR MIMO OTA, for FR1 and FR2, in both cases of SA and NSA mode [2]. The SI was closed in RAN#88e meeting with 100% completion level [3]. The outcome of this SI is captured in the published 3GPP TR38.827 v16.0.0 [4].\no\tThe new Rel-17 WI: WI on Multiple Input Multiple Output (MIMO) Over-the-Air (OTA) performance requirements for NR UEs was approved in RAN RAN#88e meeting [5]. This WI will focus on specifying the minimum performance requirements for NR MIMO OTA, both FR1 and FR2. The outcome of NR MIMO OTA WI will be captured in the 3GPP TS 38.151. \n\n-\tNR SISO OTA test methodologies and performance requirements related SI\/WIs is separated into two parts:\no\tAll the FR2 UE RF [6][7], RRM [8] and Demodulation requirements [9] are verified by OTA approach. Considering the Maximum Output Power (MOP) and Reference Sensitivity (REFSENS) tested under OTA condition were always taken as SISO OTA performance, so the status of FR2 MOP and REFSENS (subset of the 3GPP FR2 UE RF test cases) is also presented here: \n?\tThe Rel-15 SI: Study on test methods for New Radio was focused on defining the over the air (OTA) testing methodology for UE RF, UE RRM, and UE demodulation requirements [10]; This SI was closed in RAN#82 meeting with 100% completion level [11]. The outcome of this SI is captured in the published 3GPP TR 38.810 v16.5.0 [12].\n?\tThe related FR2 MOP and REFSENS requirements are specified in 3GPP TS 38.101-2 [6] and 3GPP TS 38.101-3 [7]; \n?\tA Rel-17 SI: Study on enhanced test methods for FR2 was approved to enhance the FR2 UE RF test methodology [13]. The outcome of this SI will be captured in 3GPP TR 38.884 [14].\no\tUntil now, there is no FR1 SISO OTA test methodology and performance requirements developed in 3GPP RAN4 group. Whether RAN4 will specify NR SISO OTA performance requirement and test methodology in Rel-17 timeline is under discussion. \n\n-\tPotential distinction between different frequency bands belonging to same Frequency Range: \no\tRAN4 will only specify FR1 4x4 MIMO OTA requirement for 4Rx antenna bands (e.g. Band n41, n77, n78 and n79) [5]. \no\tFrom test methodology perspective, the potential MU assessment of FR1 MPAC MIMO OTA system for FR1 low frequency (410MHz<f=3GHz) and FR1 high frequency (3GHz <f=7.125GHz) could be different. \no\tThe FR2 MOP and REFSENS requirements defined in 3GPP TS 38.101-2 and 3GPP TS 38.101-3 for n257, n258 and n261, is different from band n260 and n259. \no\tA Multiband relaxation framework was agreed to introduce a per-band relaxation for FR2 MOP and REFSENS [15], due to UE supporting for multi-band operation.\n\n-\tPotential roadmap and further future work plan:\no\tThe MIMO OTA requirements for FR1 and FR2 is planned to finalize in TSG#94 meeting, December 2021 [5]. Detailed work plan of this WI is under discussion in RAN4 [16].\no\tThe test methods enhancement of FR2 UE RF is planned to finalize in RAN#89e meeting, September 2020 [17]. \n\n\tActions: To NGMN: \tRAN4 asks NGMN to take the above status of 5G NR OTA test methodologies and performance requirements in RAN4 into consideration in their future work.","secretary_remarks":"","agenda_item_sort_order":5,"ainumber":"3","ainame":"\tIncoming Liaison Statements","tdoc_agenda_sort_order":50370,"status":"noted","reservation_date":"2020-10-08 12:47:56","uploaded":"2020-10-08 13:30:03","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"NR_MIMO_OTA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"LS R4-2009502 on 5G NR Over The Air test methodologies and performance requirements from NGMN","lsto":"","Cc":"","lsoriginalls":"R4-2012708","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_89_Electronic\/Docs\/R5-205037.zip","group":"R5","meeting":"R5-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-205039","title":"LS Announcing the publication of GSMA TS.48 Generic eUICC Test Profile for Device Testing version 3.0","source":"GSMA TSG eSIMTP","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"GSMA TSG is pleased to announce the publication of V3.0 of the TS.48 \u2018Generic eUICC Test Profile for Device Testing\u2019 which defines an eSIM test profile for use in testing product with System Simulators, typically for use when testing a device with a non-removable eSIM to ensure  compliance to 3GPP specifications..\n2\tTS.48 V3.0 Overview\n\nTS.48 V3.0 takes account of feedback that we received, and ensures this specification is now compliant to 3GPP TS 31.102 Release 15 v15.9.0, specifically noting the EF-NSI is not compatible with this release.\nA download of a reference ASN.1 files and a Excel file detailing the test profile definition is available on GitHub, \nhttps:\/\/github.com\/GSMATerminals\/Generic-eUICC-Test-Profile-for-Device-Testing-Public\nThere are four reference ASN.1 Files are available:\nSAIP 2.3 with BER-TLV\nSAIP 2.3 without BER-TLV\nSAIP 2.1 with BER-TLV\nSAIP 2.1 without BER-TLV\n(SAIP = SIMAlliance Interoperable Profile)\n\n\tAction\nThe basis for the Generic Test Profile is to enable continued use of existing process and procedures, validated test cases and test platforms in GCF and PTCRB when certifying device with a non-removable eUICC. It also removes the need for specific device hardware or modified hardware by an OEM testing 3GPP compliance in devices supporting eSIM.\nGSMA requests GCF and PTCRB to note the coming publication of TS.48 v3.0, and make appropriate references and guidance in their process and procedure documentation to encourage use of the TS.48 Generic Test Profile when testing 3GPP device compliance.","secretary_remarks":"","agenda_item_sort_order":5,"ainumber":"3","ainame":"\tIncoming Liaison Statements","tdoc_agenda_sort_order":50390,"status":"noted","reservation_date":"2020-10-08 12:47:56","uploaded":"2020-10-08 13:30:03","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"TSG LS announcing the release of TS.48 V3","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_89_Electronic\/Docs\/R5-205039.zip","group":"R5","meeting":"R5-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-205040","title":"LS on MCS group document subscription procedures","source":"TSG WG CT1","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"Overall description\nCT1 thanks RAN5 for their LS on MCS group document subscription procedures.\nCT1 has not put any restrictions on the number of subscriptions a group management client (GMC) may create, either to a single group management server (GMS) or to multiple GMSs. The client may choose to use a single subscription to a given GMS, or multiple. A GMS must be prepared to handle multiple subscriptions from a single GMC. This appears to support your second interpretation. Given that, we also wish to reply to your additional questions:\na)\tMay the GMC create up to as many dialogs as the number of group documents and <GKTPs> elements it wants to get notifications for?\nAnswer: Yes, though it is doubtful that a client implementation would choose that approach, it is permitted.\nb)\tMay the set of documents for different dialogs overlap?\nAnswer: Yes, though it may not be an efficient client implementation to do so, it is permitted.\nc)\tShall the CSK be the same for all dialogs or may the CSK be per dialog?\nAnswer: The client uses the CSK that it has at the time the dialog is created. If the CSK is changed between the creation of two dialogs, the two dialogs will use different CSKs. If the CSK is not changed between the creation of two dialogs, the two dialogs will use the same CSK.\nActions To RAN5 3GPP TSG CT WG1 asks RAN5 to take the answers above into consideration in their work.","secretary_remarks":"","agenda_item_sort_order":5,"ainumber":"3","ainame":"\tIncoming Liaison Statements","tdoc_agenda_sort_order":50400,"status":"noted","reservation_date":"2020-10-08 12:47:56","uploaded":"2020-10-26 15:24:33","revisionof":"","revisedto":"","release":"Rel-13","crspec":"","crspecversion":"","workitem":[{"winame":"MCPTT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"R5-204383","lsto":"","Cc":"","lsoriginalls":"C1-206108","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_89_Electronic\/Docs\/R5-205040.zip","group":"R5","meeting":"R5-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-205041","title":"Reply LS on two consecutive invalid challenges","source":"TSG WG CT1","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"Overall description\nCT1 thanks RAN5 for their LS on two consecutive invalid challenges. CT1 would like to provide the following answer to RAN5\u2019s question:\nIn the scenario described by RAN5, the UE shall send another REGISTER request after the second invalid challenge. In CT1#126e meeting, CT1 agreed to remove the ambiguous text in CR C1-206450- clarification on number of retry attempts when receiving invalid challenges. The UE may send another initial REGISTER request after the next invalid 401 challenge response upon a UE implementation specific time, but is not required to. The network shall respond with a 403 (Forbidden) response if the authentication attempt is to be abandoned. Consequently, the expected sequence should be as follows:\n1)\tThe UE sends an unprotected REGISTER\n2)\tThe UE gets an invalid 401 response\n3)\tThe UE sends another unprotected REGISTER \n4)\tThe UE gets an invalid 401 response \n5)\tThe UE sends another unprotected REGISTER \n6)\tThe UE gets an invalid 401 response \n7)\tThe UE may send another initial REGISTER request upon a UE implementation specific time, but is not required to\nActions To TSG RAN WG5: TSG CT WG1 asks RAN5 group to take the above response into account.","secretary_remarks":"","agenda_item_sort_order":5,"ainumber":"3","ainame":"\tIncoming Liaison Statements","tdoc_agenda_sort_order":50410,"status":"noted","reservation_date":"2020-10-08 12:47:56","uploaded":"2020-10-26 15:24:33","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"R5-204362","lsto":"","Cc":"","lsoriginalls":"C1-206661","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_89_Electronic\/Docs\/R5-205041.zip","group":"R5","meeting":"R5-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-206276","title":"LS on nominal channel spacing calculation for two carriers at band n41 with 40MHz and 80MHz channel bandwidths","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"RAN4 recognized that the nominal channel spacing for two carriers in band n41 with 40MHz and 80MHz channel bandwidths in TS 38.508 is not aligned with the nominal channel spacing definition in TS 38.101-1. RAN4 would like to clarify whether the specific parameter used in the calculation was misunderstood by RAN5 Following table compares parameters for the nominal channel space calculation. [..]\nAccording to the calculation in the table, RAN4 would like to ask RAN5 following questions:\nQuestion 1: Is that correct understanding that the nominal channel spacing for two carriers in band n41 with 40MHz and 80MHz channel bandwidths calculated as 59.94MHz in TS 38.508 is because of incorrectly selected \u00b5=1 for Gbchannel(i) ? \nActions: to: 3GPP TSG RAN WG5: RAN4 asks RAN5 feedback on the above questions.","secretary_remarks":"","agenda_item_sort_order":5,"ainumber":"3","ainame":"\tIncoming Liaison Statements","tdoc_agenda_sort_order":627600,"status":"noted","reservation_date":"2020-11-22 12:48:33","uploaded":"2020-11-22 12:51:21","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"R4-2016779","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_89_Electronic\/Docs\/R5-206276.zip","group":"R5","meeting":"R5-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-206277","title":"Reply LS on structure of NR CA reference sensitivity requirements in 38.101-1","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"Response to:\tLS R5-202804 on structure of NR CA reference sensitivity requirements in 38.101-1 from RAN5.\nRAN4 thanks RAN5 LS on structure of NR CA reference sensitivity requirements in 38.101-1. RAN4 has discussed the structure of NR CA reference sensitivity requirements and achieved the following agreement:\n1)\tThe requirement structure in both clause 7.3A.4 and 7.3A.6 listing only aggressor and victim will be retained in future.\n2)\tBand combination specific manner will be used to specify IMD exception requirements in clause 7.3A.5 instead of NR CA configurations.\n3)\tRAN4 accept RAN5\u2019s suggestion that the SDL band REFSENS requirements will be moved to 7.3.\nAction to TSG RAN WG5: \tRAN4 asks RAN5 to take account the above RAN4 agreements in the future.","secretary_remarks":"","agenda_item_sort_order":5,"ainumber":"3","ainame":"\tIncoming Liaison Statements","tdoc_agenda_sort_order":627700,"status":"noted","reservation_date":"2020-11-22 12:48:33","uploaded":"2020-11-22 12:51:21","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"R4-2016784","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_89_Electronic\/Docs\/R5-206277.zip","group":"R5","meeting":"R5-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-206278","title":"LS on Rel-16 RAN4 Clarification for UE Antenna Connector Interpretation","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"In TS 38.101-1, the transmitter and receiver characteristics are specified at the UE antenna connector. However, it is observed that in V2X devices, external components such as cables and compensator modules may be used to connect the UE antenna connector to a vehicle mounted antenna connector. A V2X integration block diagram, with an example set of components external to the UE, is illustrated in Figure1. To ensure alignment on interpretation of TS 38.101-1 between RAN4 and 5GAA, RAN4 would like to inform 5GAA that for V2X applications, the transmitter and receiver characteristics are specified at the UE antenna connector, as illustrated in Figure 1, excluding any external components. \n Actions: To 5GAA: RAN4 asks 5GAA to take the above clarification into consideration when designing V2X Tx and Rx conformance test and test procedure. An identical LS (R4-2011710) was sent to RAN5 and RAN5 has an action to take this into account in RAN5 conformance test specifications","secretary_remarks":"","agenda_item_sort_order":5,"ainumber":"3","ainame":"\tIncoming Liaison Statements","tdoc_agenda_sort_order":627800,"status":"noted","reservation_date":"2020-11-22 12:48:33","uploaded":"2020-11-22 12:51:21","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_V2X_NRSL-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"R4-2017811","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_89_Electronic\/Docs\/R5-206278.zip","group":"R5","meeting":"R5-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]