[{"name":"R5-244046","title":"LS Out on including MCPTT, MCVideo and MCData Server Conformance Testing in 3GPP Conformance Test Specifications","source":"TSG CT","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"3GPP TSG CT discussed a discussion paper CP-241289 on the need to include MCPTT, MCVideo and MCData Server Test Cases in the June CT#104 meeting. _x000D_\nTSG CT has been flagged by RAN5 meeting minutes below and its request to the TSGs_x000D_\n\u201cRAN5 guidance to the proponents of MCS Server Conformance Testing is to seek TSG approval first and then RAN5 ToR can be updated to extend the scope and responsibility. With TSG approval, RAN5 can take up the work but it will be restricted to MCS Server conformance testing only. RAN5 has no intention to take up either server side and\/or network interface conformance testing\u201d_x000D_\n3GPP TSG CT supports this RAN5 initiative with the scope as described in RAN5 meeting minutes. _x000D_\nActions: To RAN: 3GPP TSG CT asks RAN to take into consideration CT\u2019s conclusion that CT is supportive of RAN5\u2019s initiative to include Mission Critical Services server conformance testing in 3GPP conformance test specifications with the scope as identified in its meeting minutes above.","secretary_remarks":"LS R5-206259 on failing initial registration without Retry-After header field from RAN5","agenda_item_sort_order":5,"ainumber":"3","ainame":"\tIncoming Liaison Statements","tdoc_agenda_sort_order":40460,"status":"noted","reservation_date":"2024-06-25 13:00:19","uploaded":"2024-06-25 13:00:54","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__104_Maastricht\/Docs\/R5-244046.zip","group":"R5","meeting":"R5-104","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-244047","title":"LS on Rel-18 NR MIMO OTA progress","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 Rel-18 NR_MIMO_OTA_enh WI in 3GPP RAN4. _x000D_\nBased on the agreed scope and objectives in the WID [1], the Rel-18 NR_MIMO_OTA_enh WI further enhanced NR MIMO OTA test methodologies based on the outcome of Rel-17 NR_MIMO_OTA WI in TS 38.151, and specified more MIMO OTA performance requirements for FR1 bands and FR2 bands as well as the recommended test tolerance (TT). The outcome of this WI impacted TS 38.151, and the measurements of MIMO OTA were captured in a new internal technical report TR 38.761.  \nThe core part WI has been completed in RAN#102, Dec. 2023. As described in the WI summary [2], the main outcomes of the core part WI are summarized as below:...\n\u2022\tFR1 MIMO OTA test methodology enhancement:_x000D_\n-\tSpecified necessary enhancements of the FR1 MIMO OTA test methodology for tablet device types in free space, with the 20-cm quiet zone and the 16-probe MPAC system unchanged_x000D_\n-\tDecided Test time reduction method for FR1 MIMO OTA_x000D_\n?\tFor bands < 1GHz, the test parameter Minimum Number of Slots per Stream can be reduced to 10k for FR1 MIMO OTA measurement campaign and conformance testing for 15kHz SCS_x000D_\n-\tRefined FR1 channel model validation pass\/fail limits_x000D_\n?\tPass\/fail criteria of power validation is defined as \u00b1 1.5 dB_x000D_\n\u2022\tFR2 MIMO OTA test methodology enhancement:_x000D_\n-\tDefined the framework for FR2 MIMO OTA requirement development_x000D_\n?\tPure measurement approach was adopted for the FR2 requirement definition_x000D_\n-\tRefined FR2 channel model validation pass\/fail limits based on practical measurement results_x000D_\n?\tPass\/fail criteria of power validation is defined as \u00b1 1.5 dB_x000D_\nFor the performance part WI, RAN4 has finalized MIMO OTA performance requirements work for FR1 bands and FR2 bands based on the approved framework and time plan in [3] and [4]. Key working procedures and outcomes in Rel-18 are summarized below: ...\n\u2022\tFR1 MIMO OTA performance requirements work:_x000D_\n-\tRAN4 performed a successful FR1 MIMO OTA lab alignment at band n28, all the participated 6 labs are well aligned based on the measurement results of 3 performance alignment devices (PADs)_x000D_\n?\tThe reference value of each PAD is derived from the linear average approach (in dBm) based on measurement results from all labs (no outliers identified)_x000D_\n?\tThe pass\/fail limit (the max deviation between individual results and the reference value) is defined as 0.75*MU, i.e., +\/- 1.96 dB for band n28_x000D_\n-\tRAN4 conducted a performance measurement campaign to collect TRMS measurement data from aligned labs_x000D_\n?\tA \u201cpartial anonymous\u201d approach is adopted in Rel-18 to collect UE model information for the measurement campaign, which is to check the representative of 3GPP MIMO OTA data pool. The disclosure of exact device models is done only between each test lab to the Neutral Party, by using the same template [5]._x000D_\n-\tRAN4 defined FR1 MIMO OTA performance requirements based on per-band data-driven approach with CDF analysis of all the valid measurement results from the Rel-18 performance measurement campaign._x000D_\n....\n2\tActions_x000D_\nTo 3GPP RAN5, CTIA MOSG, CCSA TC9 WG1: _x000D_\nACTION: \t3GPP RAN4 respectfully asks 3GPP RAN5, CTIA MOSG, and CCSA TC9 WG1 to take the above information into account.","secretary_remarks":"LS R5-206259 on failing initial registration without Retry-After header field from RAN5","agenda_item_sort_order":5,"ainumber":"3","ainame":"\tIncoming Liaison Statements","tdoc_agenda_sort_order":40470,"status":"noted","reservation_date":"2024-06-25 13:00:19","uploaded":"2024-06-25 13:00:54","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_MIMO_OTA_enh"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5__104_Maastricht\/Docs\/R5-244047.zip","group":"R5","meeting":"R5-104","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-244050","title":"TS.48 updates to cover IoT eUICC and request for defining AT commands for eUICC profile management","source":"GSMA TSG","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"GSMA PRD TS.48 v5.0 defines a Generic Test Profile for M2M and Consumer Device conformance testing. GSMA TSG plans on releasing TS.48 v6.0 to cover IoT Device in scope by referencing GSMA PRD SGP.31 v1.2 and GSMA PRD SGP.32 v1.1 recently published on 26th Apr. 2024._x000D_\nIn line with this extension, GSMA TSG recognises that there is no standard AT commands to perform eUICC profile management operations (such as enable or disable) for testing various types of devices including those with constrained user interfaces. Detailed changes and observations could be found in the attached CR (TSG55_014 TS.48 v5.0 CR1006 v01). For instance, an eUICC (test) profile can be disabled and enabled in case when a 3GPP conformance test requires SIM removal and (new) SIM insertion, respectively._x000D_\nStandardising AT commands for eUICC profile management will ensure continued use of 3GPP test specifications (see also GSMA PRD TS.48 Annex E) by device manufacturers and third party test labs for testing all categories of devices as per the existing test platforms defined by GCF and\/or PTCRB._x000D_\n2\tAction_x000D_\nGSMA TSG kindly requests 3GPP CT WG1 to define and allow standard AT commands to support profile management operations that can be used for 3GPP device conformance testing.","secretary_remarks":"LS R5-206259 on failing initial registration without Retry-After header field from RAN5","agenda_item_sort_order":5,"ainumber":"3","ainame":"\tIncoming Liaison Statements","tdoc_agenda_sort_order":40500,"status":"noted","reservation_date":"2024-06-25 13:00:19","uploaded":"2024-06-25 13:00:54","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__104_Maastricht\/Docs\/R5-244050.zip","group":"R5","meeting":"R5-104","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-244051","title":"LS on Avoiding Cross-TSG TEI","source":"TSG RAN","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"TSG RAN has had an approved TEI handling procedure since March 2021 (RAN#91e). The latest approved version is RP-240858 (attached). The main purpose of this procedure is to improve transparency and traceability of TEI work._x000D_\nIn line with previous inter-TSG agreement, it is not possible to trigger work in RAN WGs via TEI CRs coming from TSG SA\/CT or SA\/CT WGs. The same applies for the reverse direction._x000D_\nHowever, on several occasions in the recent past, RAN WGs received LSs from a WG of another TSG, with a request to introduce changes, based on an attached TEIxx CR._x000D_\nPlease note that if SA (WGs) or CT (WGs) need RAN (WGs) to undertake work, a SA (WGs) or CT (WGs) Work Item with a Work Item Description (that is not only TEIxx) is required._x000D_\nPlease note that MCC has given guidance that the receiving RAN groups should then use_x000D_\neither _x000D_\n\u2022\tthe same SA\/CT WI code that was in the incoming LS_x000D_\nor _x000D_\n\u2022\tthe SA\/CT WI code and a RAN WI code related to that._x000D_\n_x000D_\nActions: To TSG CT, CT WG1, CT WG3, CT WG4, CT WG6, TSG SA, SA WG1, SA WG2, SA WG3, SA WG4, SA WG5, SA WG6 groups_x000D_\nACTION: \tTSG RAN asks TSG CT (WGs) and TSG SA (WGs) to use an appropriate SA (WGs) or CT (WGs) WI code other than \"TEIxx\" when asking RAN (WGs) to undertake any necessary work required","secretary_remarks":"","agenda_item_sort_order":5,"ainumber":"3","ainame":"\tIncoming Liaison Statements","tdoc_agenda_sort_order":40510,"status":"noted","reservation_date":"2024-06-25 13:00:19","uploaded":"2024-07-15 10:18:20","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__104_Maastricht\/Docs\/R5-244051.zip","group":"R5","meeting":"R5-104","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]