[{"name":"R5-235986","title":"On frequencyInfo for NR SL RSRP measurements","source":"TSG WG RAN2","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"RAN2 received from RAN5 one LS R5-233768\/R2-2307050 on frequencyInfo for NR SL RSRP measurements. RAN2 understands that, without field description in TS 38.331, the exact meaning of frequencyInfoSL-r16 in IE SL-MeasObject-r16 can be unclear, and this ambiguity can lead to unpredictable UE behaviour during testing. \nRAN2 understands that the field frequencyInfoSL-r16 should be the indication of the carrier, on which SL-RSRP measurement is performed, RAN2 respectfully asks RAN1 to confirm that the below field description for frequencyInfoSL in IE SL-MeasObjectList is acceptable:\n \"It indicates the lowest usable subcarrier on this carrier, determined according to sl-AbsoluteFrequencyPointA in IE SL-FreqConfig\/SL-FreqConfigCommon and offsetToCarrier in IE SCS-SpecificCarrier configured for sl-SCS-SpecificCarrierList in IE SL-FreqConfig\/SL-FreqConfigCommon. See TS 38.211 [16], clause 4.4.2.\"\nActions: To RAN1 \nRAN2 asks RAN1 to feedback whether the above field description of frequencyInfoSL in IE SL-MeasObjectList in TS 38.331 is acceptable.","secretary_remarks":"LS R5-206259 on failing initial registration without Retry-After header field from RAN5","agenda_item_sort_order":6,"ainumber":"3","ainame":"\tIncoming Liaison Statements","tdoc_agenda_sort_order":59860,"status":"noted","reservation_date":"2023-09-19 16:18:24","uploaded":"2023-10-03 09:15:36","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"NR_RF_FR1-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__101_Chicago\/Docs\/R5-235986.zip","group":"R5","meeting":"R5-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-235993","title":"Response LS on frequencyInfo for NR SL RSRP measurements","source":"TSG WG RAN1","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"RAN1 thanks RAN2 for triggering the discussion on the field description for the parameter frequencyInfoSL in IE SL-MeasObjectList to indicate the carrier on which SL-RSRP measurement is performed. \nRAN1 have discussed this subject matter, and recommend the the following changes to the frequencyInfoSL field description:\n\u2022\tClarify that the carrier being indicated is to be used for SL RSRP measurement.\n\u2022\tUpdate the reference provided in TS 38.211 from clause 4.4.2 to 8.2.5.\nBased on the aforementioned changes, the field description has been updated as follows:\n\"It indicates the lowest usable subcarrier on this carrier where SL RSRP is measured, determined according to sl-AbsoluteFrequencyPointA in IE SL-FreqConfig\/SL-FreqConfigCommon and offsetToCarrier in IE SCS-SpecificCarrier configured for sl-SCS-SpecificCarrierList in IE SL-FreqConfig\/SL-FreqConfigCommon. See TS 38.211 [16], clause 8.2.5.\"\nActions: To RAN2\nRAN1 requests RAN2 to take above response into account when adding the field description for the parameter frequencyInfoSL.","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"3","ainame":"\tIncoming Liaison Statements","tdoc_agenda_sort_order":59930,"status":"noted","reservation_date":"2023-09-19 16:18:25","uploaded":"2023-10-24 04:52:11","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_V2X_NRSL-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__101_Chicago\/Docs\/R5-235993.zip","group":"R5","meeting":"R5-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-236042","title":"Reply LS on CG-SDT RRM test procedure","source":"TSG WG RAN4","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"RAN4 thanks RAN5 for the information in LS R5-235340. \nIn RAN4#108-bis, RAN4 reached following agreements on modification of the CG-SDT RRM test.\no\tSplit CG-SDT test for positive check and negative check \n?\tTest 1 verifies the positive check to ensure that CG-SDT transmission is performed,\n?\tTest 2 verifies the negative check to ensure that CG-SDT transmission is not performed.\n?\tTest 2 is executed only when Test 1 is passed.\no\tIn Test#1, the original time points are reused with removing T5 and deducting W1 from T4\no\tIn Test#2, the time points are repeated from Test#1 with removing time point TH\no\tUpdate RedCap CG-SDT RRM test accordingly with NR CG-SDT test case\nThe draftCR for updating the test case in A.6.2.1 and A.7.2.1.1 is endorsed in R4-2317398.\nRAN4 respectfully asks RAN5 to take the above information into account.\nActions: To RAN5: RAN4 asks RAN5 to take the above information into account.","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"3","ainame":"\tIncoming Liaison Statements","tdoc_agenda_sort_order":60420,"status":"noted","reservation_date":"2023-10-24 05:05:56","uploaded":"2023-10-24 05:31:23","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"NR_SmallData_INACTIVE-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__101_Chicago\/Docs\/R5-236042.zip","group":"R5","meeting":"R5-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]