[{"name":"R5-223914","title":"Reply LS on V2X PC5 link for unicast communication with null security algorithm","source":"TSG WG CT1","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"CT1 thanks RAN5 for their LS on V2X PC5 link for unicast communication with null security algorithms.\nCT1 has reviewed the content of the LS and relevant specifications and would like to indicate that according to CT1 specification the use of null security protection algorithm (i.e., in 5GS NEA0 and NIA0) are in fact security protection algorithms used for integrity protecting and ciphering of the PC5 messages. However, when applied they cannot provide any integrity protection or ciphering for the PC5 messages. Therefore if the null security protection algorithms, i.e. integrity protection and ciphering using null security protection, are activated as a result of successful security control mode procedure, the PC5 messages are transmitted unprotected.\nCT1 has updated their specification TS 24.587 to clarify the use of null and non-null security protection algorithms in order to avoid any misunderstanding (see attached file).\nActions: To 3GPP RAN WG5: \tCT1 asks RAN5 to take the above information into account in their discussion about formal conformance testing of the null security algorithms for V2X.","secretary_remarks":"LS R5-206259 on failing initial registration without Retry-After header field from RAN5","agenda_item_sort_order":4,"ainumber":"3","ainame":"Incoming Liaison Statements","tdoc_agenda_sort_order":39140,"status":"noted","reservation_date":"2022-07-01 15:10:21","uploaded":"2022-07-07 13:50:08","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"C1-223325\/ R5-222035","lsto":"TSG RAN WG5","Cc":"TSG WG SA3, TSG WG RAN2","lsoriginalls":"C1-223972","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_96_Electronic\/Docs\/R5-223914.zip","group":"R5","meeting":"R5-96-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-223915","title":"Reply LS on configuration of p-MaxEUTRA and p-NR-FR1","source":"TSG WG RAN1","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"RAN1 thanks RAN4 and RAN5 for the LS\u2019s on configuration of p-MaxEUTRA and p-NR-FR1. Regarding the question raised in the RAN5 LS, RAN1 provides further answer as follows:\nFor the case where either p-MaxEUTRA or p-NR-FR1 is not configured for EN-DC, no new UE behavior for uplink power control will be specified in RAN1. With recognition of RAN2 LS R1-1905937, if default value is introduced, it is expected to be introduced in a way that is transparent to RAN1 specification\nActions: To: RAN5: RAN1 asks RAN5 to take the above answer into account.","secretary_remarks":"LS R5-206259 on failing initial registration without Retry-After header field from RAN5","agenda_item_sort_order":4,"ainumber":"3","ainame":"Incoming Liaison Statements","tdoc_agenda_sort_order":39150,"status":"noted","reservation_date":"2022-07-01 15:10:21","uploaded":"2022-07-07 13:50:08","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"R1-2203038\/R4-2206567","lsto":"TSG RAN WG5","Cc":"TSG WG RAN2, TSG WG RAN4","lsoriginalls":"R1-2205465","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_96_Electronic\/Docs\/R5-223915.zip","group":"R5","meeting":"R5-96-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-223916","title":"Reply LS on configuration of p-MaxEUTRA and p-NR-FR1","source":"TSG WG RAN2","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"RAN2 thanks RAN5 for the LS on configuration of p-MaxEUTRA and p-NR-FR1. RAN2 has discussed the question below in the LS:\nACTION: RAN5 kindly request RAN2 feedback on whether the RAN2 specifications require that the IEs p-MaxEUTRA and p-NR-FR1 are always configured by the network when UE works in EN-DC connectivity mode and also consider updating the core specification to clarify the same.\nRAN2 would like to confirm that in RAN2 specifications both p-MaxEUTRA and p-NR-FR1 are optional fields for configuration when UE works in EN-DC connectivity mode. There is also no default value specified for these two IEs in case these two IEs are not configured. However, from RAN2 perspective, most of the network deployments configure p-MaxEUTRA and p-NR-FR1 fields when the UE is configured with EN-DC.\n\nAction: To RAN5: \tRAN2 asks RAN5 to take the above into account.","secretary_remarks":"LS R5-206259 on failing initial registration without Retry-After header field from RAN5","agenda_item_sort_order":4,"ainumber":"3","ainame":"Incoming Liaison Statements","tdoc_agenda_sort_order":39160,"status":"noted","reservation_date":"2022-07-01 15:10:21","uploaded":"2022-07-07 13:50:08","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"R5-217995","lsto":"TSG RAN WG5","Cc":"TSG WG RAN1, TSG WG RAN4","lsoriginalls":"R2-2206422","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_96_Electronic\/Docs\/R5-223916.zip","group":"R5","meeting":"R5-96-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-223917","title":"LS to RAN5 on measurement of phase continuity requirements for DMRS bundling","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Action","abstract":"RAN4 has introduced the UE RF requirements for the phase continuity requirement for DMRS bundling in both FR1 and FR2 and has agreed attached CRs for FR1 and FR2. DMRS bundling improves the UL coverage and despite the core requirements apply for DFT-S-OFDM and CP-OFDM RAN4 has concluded that testing should be done only for DFT-S-OFDM.\nRAN4 has below questions regarding the testing aspect of this requirement:\nQuestions on Common Frequency Offset and its handing (within one bundling time):\nRAN4 has agreed that there will be no change to the 0.1ppm UE frequency error requirement for the DMRS bundling feature, and have agreed that the Test Equipment would estimate the signal slot-by-slot and perform Frequency Error Correction on a slot-by-slot basis, as is currently done for other transmission signal quality requirements. However, RAN4 is not clear on the level of accuracy of frequency error correction by the TE and have the following questions.\nQ1-1: What would be the impact of the residual frequency error after CFO correction by TE on the testability of the phase offset measurement for UE complying with +\/- 0.1 ppm frequency error requirement, particularly for the upper range of FR2-1 and lowest allowed SCS?\nQ1-2: Can Frequency error be corrected in such way that it has minimal or no impact on measurement uncertainty for phase discontinuity requirements? If answer is yes, in which options below could achieve this:\n1.\tCFO correction in each slot should be applied taking into account a slot starting from a reference time slot (e.g slot 0 or any slot p-1) to measured time slot (slot p) to enable a continuous correction to avoid any potential phase step introduced by CFO correction.\n2.\tCFO in each slot is corrected with its individual frequency error\nQ1-3: Does RAN5 see any other testing issue apart from issues raised by RAN4 above?\nRAN1 specification has defined some the phase consistency violating \u201cevents\u201d defined in TS 38.214 and these events may happen outside the bundling time window but not within the bundling window. Therefore, sufficient time between any repeated bundles should be allowed for UE to perform such \u201cevent\u201d. \nQuestions on improving test accuracy by repeated testing\nQ2-1: The requirement of phase continuity requirement is applied within one DMRS bundling configuration, would the measurement uncertainty be improved as the result of repeating the test over several bundles and if so, what would be the recommended number of bundles and should it be dependent on the subcarrier spacing?\nQ2-2: In case multiple bundles will be tested, what is Ran5 view on how the test results in terms of phase offset from individual bundles be used to improve the test reliability and reduce measurement uncertainty (e.g., maximum over all bundles or RMS average over all bundles or others method)?\nRAN4 asks RAN5 to provide answers on the above questions.\nActions: To RAN WG5: RAN4 ask RAN5 to provide answers to RAN4.","secretary_remarks":"","agenda_item_sort_order":4,"ainumber":"3","ainame":"Incoming Liaison Statements","tdoc_agenda_sort_order":39170,"status":"noted","reservation_date":"2022-07-01 15:10:21","uploaded":"2022-07-07 13:50:08","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"NR_cov_enh"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG WG RAN5","Cc":"","lsoriginalls":"R4-2210550","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_96_Electronic\/Docs\/R5-223917.zip","group":"R5","meeting":"R5-96-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-223919","title":"Reply LS on SCell dropping in FR2 RF UL-CA tests","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"RAN4 thanks RAN5 on informing the development of a conformance-only test function to test FR2 RF UL-CA conformance tests which includes the usage of a parameter that defines the power back-off needed to be applied to the PCell to potentially avoid SCell drop in FR2 UL-CA conformance test cases.\nRegarding RAN5\u2019s request to RAN4 for the responses to the following questions:\na)\tWhether RAN4 sees a need to define within TS 38.101-2, the aforementioned power backoff parameter which will be used by conformance-only test function?\nb)\tWhether RAN4 can share guidance on any impact on absolute and relative power tolerance accuracy that needs to be factored because of usage of such a conformance-only test function to apply power limits\/back-off?\nRAN4 had discussed and concluded with the following responses:\nResponse to Question a): RAN4 sees no need to define within TS 38.101-2 the power back-off parameter which will be used by conformance-only test function.\nResponse to Question b): RAN4 concludes that there is no impact on absolute and relative power tolerance accuracy that needs to be factored because of usage of the conformance-only test function to apply power back-off.\nActions: To: RAN5 RAN4 asks RAN5 to take the above RAN4 responses into consideration.","secretary_remarks":"","agenda_item_sort_order":4,"ainumber":"3","ainame":"Incoming Liaison Statements","tdoc_agenda_sort_order":39190,"status":"noted","reservation_date":"2022-07-01 15:10:21","uploaded":"2022-07-07 13:50:08","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"R5-221617","lsto":"TSG WG RAN5","Cc":"","lsoriginalls":"R4-2210812","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_96_Electronic\/Docs\/R5-223919.zip","group":"R5","meeting":"R5-96-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-223920","title":"Reply LS on FR2 UE relative power control tolerance requirements","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"RAN4 thanks RAN5 for clarifying the motivation for combining the 2 tables of FR2 relative power tolerance. It\u2019s understood by RAN4 that current requirements are not testable for quite a few scenarios due to the start and target power values can\u2019t be both within the same power range in conformance testing. RAN4 has discussed this issue and made the following response.\nThe FR2 relative power tolerance is an important RF requirement for the coordination between UE and network. Current way of defining FR2 relative power tolerance is based on comprehensive analysis and discussion, and was introduced since Rel-15. It\u2019s not optimal choice to update the requirements at this time stage.\nOn the other hand, it\u2019s also important to make sure the corresponding test case is specified by RAN5. A test method that only verifies the requirements as they stand today could be employed for UEs: If the start and target power lever are not within the same power range, apply the worse tolerance in the test verdict.\nActions: To RAN5: RAN4 asks RAN5 to take into account the above information in the conformance testing work.","secretary_remarks":"","agenda_item_sort_order":4,"ainumber":"3","ainame":"Incoming Liaison Statements","tdoc_agenda_sort_order":39200,"status":"noted","reservation_date":"2022-07-01 15:10:21","uploaded":"2022-07-07 13:50:08","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"R5-218231","lsto":"TSG WG RAN5","Cc":"","lsoriginalls":"R4-2210814","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_96_Electronic\/Docs\/R5-223920.zip","group":"R5","meeting":"R5-96-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-223921","title":"Further Reply LS on configuration of p-MaxEUTRA and p-NR-FR1","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"At RAN4 meeting #102-e RAN4 had indicated in a reply LS (R4-2206567) to RAN5 that it is up to RAN1 to confirm whether the network leaving p-MaxEUTRA or p-NR-FR1 unconfigured is a valid configuration.  RAN4 further indicated that it would further discuss whether \u201cinfinity\u201d could be used as a default value if these two parameters are not configured and whether and how to capture into the specification.\nRAN4 would like to kindly inform RAN5 that it has agreed to a evaluate the parameters p-MaxEUTRA and p-NR-FR1 as  infinity only in the configured maximum power calculation in the case these two parameters are not configured by the network.  RAN4 has agreed to modify the 38.101-3 specification accordingly (please see attached CR). This change has no RAN1 or RAN2 impact.\nActions: To: TSG RAN WG1, TSG RAN WG2, TSG RAN WG5: RAN4 requests RAN1, RAN2, and RAN5 to take the above into consideration.","secretary_remarks":"","agenda_item_sort_order":4,"ainumber":"3","ainame":"Incoming Liaison Statements","tdoc_agenda_sort_order":39210,"status":"noted","reservation_date":"2022-07-01 15:10:21","uploaded":"2022-07-07 13:50:08","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"R5-217995","lsto":"TSG WG RAN5","Cc":"TSG WG RAN1, TSG WG RAN2","lsoriginalls":"R4-2210815","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_96_Electronic\/Docs\/R5-223921.zip","group":"R5","meeting":"R5-96-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-223922","title":"Reply LS on Additional RF requirements for NS_03U, NS_05U and NS_43U","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"RAN4 thanks RAN5 for the LS on additional requirements for NS_03U, NS_05U, and NS_43U.  Indeed, RAN4 agrees with RAN5 that the 38.101-1 specification is not fully clear on the requirements imposed by the signaling of the above-mentioned NS values.  RAN4 would like to inform RAN5 that the intent of the NS value NS_xxU is to apply the requirements of NS_xx in addition to the requirement on UTRA ACLR.  For example, as listed in Table 6.2.3.1-1 of 38.101-1 (snippet shown below), the requirement for NS_05U is specified in clauses 6.5.3.3.4 and 6.5.2.4.2. \nClause 6.5.3.3.4 contains the same requirements as applicable for NS_05, but clause 6.5.2.4.2 contains additionally a specification for UTRA ACLR intended to be signaled in deployments where UTRA may be present in the same frequency range.  \nRAN4 has agreed on corrections to the specification to indicate clearly that the requirements in clause 6.5.3.3.4 apply to both NS_05 and NS_05U.  The same correction is made for NS_03U and NS_43U.\nAction: To TSG WG5: RAN4 requests RAN5 to take the above into consideration in their further work.","secretary_remarks":"","agenda_item_sort_order":4,"ainumber":"3","ainame":"Incoming Liaison Statements","tdoc_agenda_sort_order":39220,"status":"noted","reservation_date":"2022-07-01 15:10:21","uploaded":"2022-07-07 13:50:08","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_NR_LTE-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"R4-2207624 \/ R5-221613","lsto":"TSG WG RAN5","Cc":"","lsoriginalls":"R4-2211129","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_96_Electronic\/Docs\/R5-223922.zip","group":"R5","meeting":"R5-96-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-223923","title":"Reply LS on V2X PC5 link for unicast communication with null security algorithm","source":"TSG WG SA3","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"SA3 thanks RAN5 for their LS on V2X PC5 link for unicast communication with null security algorithms.\nSA3 has reviewed the content of the LS and relevant specification and would like to provide clarification on the usage of the NULL security algorithms. \nThe wording of \u201cno security\u201d is misleading in the current specification of TS 33.536, i.e. the NULL security algorithms for encryption and integrity are still security algorithms, but without any protection of the content of the messages. Put in another way, the selection of NULL algorithms means that the PC5 messages are considered protected for the purposes of being allowed to be sent or received (even if in effect there is no protection of the messages).\nFurthermore SA3 would like to confirm that the key establishment procedures in clause 5.3.3.1.3 of TS 33.536 can be skipped if the receiving UE chooses NULL PC5 integrity protection algorithm for the PC5 signalling integrity protection.\n2\tActions: To 3GPP RAN WG5 group: \tSA3 asks RAN5 to take the above information into account in their discussion about formal conformance testing of the null security algorithms for V2X.","secretary_remarks":"","agenda_item_sort_order":4,"ainumber":"3","ainame":"Incoming Liaison Statements","tdoc_agenda_sort_order":39230,"status":"noted","reservation_date":"2022-07-01 15:10:21","uploaded":"2022-09-06 07:01:21","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S3-221317\/ R5-222035","lsto":"TSG WG RAN5","Cc":"TSG WG CT1, TSG WG RAN2","lsoriginalls":"S3-221590","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_96_Electronic\/Docs\/R5-223923.zip","group":"R5","meeting":"R5-96-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]