[{"name":"R5-244289","title":"Discussion paper on early implementable features and corrections","source":"MediaTek Inc.","contact":"Daiwei Zhou","contact-id":72872,"tdoctype":"discussion","for":"Endorsement","abstract":"In TS 36.331 Annex G and TS 38.331 Annex C, there are tables containing the feature and correction CR lists which may be implemented by a UE of an earlier release than which the CR was approved in. And RAN5 refers to these tables to define the release requirement of the relative PICS and test case applicability. According to the ASN.1 definition, early implementation is doable for UE as defined in TS 36.331 Annex F and TS 38.331 Annex D._x000D_\n2.\tDiscussion_x000D_\nCurrently there are some circumstances as below:_x000D_\n1)\tNot every feature or correction CR in RAN2 has been clearly discussed whether it is early implementable in RAN2, e.g. contains \"Implementation of this CR from Rel-N will not cause interoperability issues\" on the CR coversheet and then adds them into the lists. Therefore, the list in TS 36.331 Annex G or TS 38.331 Annex C maybe incomplete. And it`s not feasible for RAN5 to request RAN2 to go back to clarify whether the features earlier than Rel-18 are early implementable._x000D_\n2)\tFrom UE perspective, some features are significant for security enhancement, e.g. UPIP (User plane integrity protection) is introduced in Rel-17 but UE may implement it since Rel-15 to enhance EN-DC security as EN-DC is based on Rel-15._x000D_\n3)\tSome features impact both NR and E-UTRA part, but UE may have different NR and E-UTRAN AS release. For example, RACS (UE Radio Capability Signaling Optimization) and RRC UL segmentation are Rel-16 features in both NR and E-UTRA core specification, and network may query nr, eutra-nr and\/or eutra capabilities from gNB or eNB side. If UE reports NR accessStratumRelease as Rel-16 and E-UTRA accessStratumRelease as Rel-15, and the UE supports RACS or UL segmentation in NR, that means it also needs to support these features in E-UTRA to ensure network having the same UE capabilities._x000D_\nConsidering above situations, in this discussion paper, it is proposed to allow features and corrections CRs, which are not in TS 36.331 Annex G nor TS 38.331 Annex C, being early implementable in RAN5 based on meeting CRs [1][2][3][4]._x000D_\n3.\tProposal_x000D_\nProposal:\tRAN5 to accept the handling of early implementable features and corrections based on meeting CR process.","secretary_remarks":"","agenda_item_sort_order":1152,"ainumber":"6.4.7","ainame":"Discussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":42890,"status":"noted","reservation_date":"2024-08-05 03:13:13","uploaded":"2024-08-09 11:04:39","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-244289.zip","group":"R5","meeting":"R5-104","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-244708","title":"Discussion to extend the scope for MBS Broadcast test case","source":"Huawei, HiSilicon, MCC TF160","contact":"Ya Zhao","contact-id":81385,"tdoctype":"discussion","for":"Endorsement","abstract":"Observation 1(From MCC TF160): SearchspaceMCCH\/ searchspaceMTCH are set to 1 (same as searchspace for CSS) in all MBS broadcast test case , so the scenario for SearchspaceMCCH\/ searchspaceMTCH set to zero is not tested._x000D_\nObservation 2(From HiSilicon): It is possible that PCell and SCell have different PLMN list (for example, PCell PLMN list is PLMN1, while SCell PLMN list is PLMN1 and PLMN2, and the MBS is broadcasted in PLMN2 ), so RAN2 add plmn-IdentityInfoList-r17 in SCellConfig to indicate the PLMN list for SCell. Plmn-IdentityInfoList-r17 absent scenario has been tested in the 14.1.1.4.x, but plmn-IdentityInfoList-r17 present scenario has not been tested in any MBS broadcast test case._x000D_\nProposal 1: Update the title\/TP and message content for one MBS Broadcast test case (i.e 38.523-1 14.1.1.2) to cover the searchspaceMCCH and searchspaceMTCH set to zero scenario._x000D_\nProposal 2: Update theTP\/test procedure and message content for MBS Broadcast CA test case (i.e 14.1.1.4) to cover the plmn-IdentityInfoList-r17 present scenario.","secretary_remarks":"","agenda_item_sort_order":1152,"ainumber":"6.4.7","ainame":"Discussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":47080,"status":"noted","reservation_date":"2024-08-08 07:47:23","uploaded":"2024-08-09 07:14:14","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17_Test"},{"winame":" NR_MBS_5MBS_5MBUSA-UEConTest"}],"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-244708.zip","group":"R5","meeting":"R5-104","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-244721","title":"Discussion to handle IMS for loop back test case","source":"Huawei, HiSilicon","contact":"Ya Zhao","contact-id":81385,"tdoctype":"discussion","for":"Endorsement","abstract":"Observation 1: When Test mode is activated, according to 36.509 5.3.2.3 IMS SIP message (e.g IMS REGISTER ) shall not be transmitted by UE\u2019s layer2. However the 36.509 does not forbid UE to establish PDU session for IMS. Therefore, normally UE will establish PDU session for IMS but IMS registration failure._x000D_\nObservation 2: UE test mode shall be activated before PDU session (DRB) establishment. Since PDU session always happened after test mode activation, it is impossible that UE firstly perform IMS registration and then activate test mode._x000D_\nObservation 3: For Voice centric UE, if IMS is not available (e.g UE or SS not support IMS, or UE IMS registration failure), UE shall disable N1 mode. That may cause nearly all the NR test case failure, theoretically. _x000D_\nObservation 4: For Data centric UE, UE shall not disable N1 mode because IMS is not available. However, as 38.509 does not limit the high layer behaviour after test mode activation, so there still may have some error case._x000D_\n2\tProposal_x000D_\nBased on the above discussion, if UE keep on enabling IMS for the loop back test case, the UE cannot transmit any IMS SIP message and IMS registration will be failure, which may also cause some other error case. The followings are proposed:_x000D_\nProposal 1: Add a Note in TS 38.508-1 to allow UE to set to Data Centric and\/or close IMS for the loop back test case.","secretary_remarks":"","agenda_item_sort_order":1152,"ainumber":"6.4.7","ainame":"Discussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":47210,"status":"revised","reservation_date":"2024-08-08 07:47:40","uploaded":"2024-08-09 09:08:36","revisionof":"","revisedto":"R5-245653","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"TEI15_Test"},{"winame":" 5GS_NR_LTE-UEConTest"}],"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-244721.zip","group":"R5","meeting":"R5-104","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-245210","title":"TS 38.523-1 Tracker status before RAN5-104","source":"Huawei, Hisilicon","contact":"zhaobing yang","contact-id":80062,"tdoctype":"other","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":1152,"ainumber":"6.4.7","ainame":"Discussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":52100,"status":"noted","reservation_date":"2024-08-09 09:43:11","uploaded":"2024-08-09 11:01:56","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-245210.zip","group":"R5","meeting":"R5-104","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-245466","title":"Introduction of New R16 IDC Test Case","source":"China Mobile","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Discussion","abstract":"Background of R16 IDC new test case_x000D_\nObservation 1.1: RAN2 introduced a NR IDC solution in R16 to inform network that UE is experiencing IDC problems that cannot be solved by itself. Basing on the IDC assistance information provided by the UE, the network may take some actions to help UE to fix the IDC problem._x000D_\nObservation 1.2: If UE is configured to provide IDC assistance information, and UE did not transmit a UEAssistanceInformation message, UE transmits UEAssistanceInformation message._x000D_\nObservation 1.3: If UE is configured to provide IDC assistance information, the UE transmits a UEAssistanceInformation message before, but the current IDC information is different from the one reported previously, UE transmits UEAssistanceInformation message_x000D_\n_x000D_\nWhy do we need to introduce R16 IDC new test case now?_x000D_\nObservation 2.1: The earliest NR IDC solutions were introduced by a TEI16 CR into TS 38.331 in R16, and it only focus on NR FDM solution._x000D_\nObservation 2.2: There was no R17 IDC WI._x000D_\nObservation 2.3: In R18 IDC WI, enhanced FDM solution was introduced to provide more information of affected frequencies, and also to support NR-DC scenarios. Besides, TDM solution was also introduced to handle which alternative non-interfered frequencies are not available._x000D_\nObservation 2.4: R18 \u201cNR_IDC_enh-UEConTest\u201d is the first IDC WI in RAN5. To ensure the integrity of the IDC related tests and further support R18 IDC solutions, it is necessary to introduce R16 IDC test case based on the IDC features introduced in R16 core spec_x000D_\n_x000D_\nIntroduction of R16 IDC new test case_x000D_\nObservation 3.1: R16 IDC test case is introduced by R5-244515 with two TPs. _x000D_\nTP1 is for the scenario that UE did not transmit a UEAssistanceInformation message before. _x000D_\nTP2 is for the scenario that UE already transmitted a UEAssistanceInformation message before, and UE transmits a UEAssistanceInformation message again when the current idc-Assistance information is different from the previous one._x000D_\nObservation 3.2: RAN2 introduced the R16 IDC solution into TS 38.331 via a TEI16 CR without any specific R2 WI .Proposal 1: RAN5 agrees to introduce the R16 IDC related TCs into TS 38.523-1 with TEI16_Test WIC to align with RAN2 core spec TS 38.331.","secretary_remarks":"","agenda_item_sort_order":1152,"ainumber":"6.4.7","ainame":"Discussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":546600,"status":"noted","reservation_date":"2024-09-02 14:52:06","uploaded":"2024-09-02 15:01:09","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-245466.zip","group":"R5","meeting":"R5-104","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-245488","title":"Discussion to split DAPS test case","source":"Huawei, HiSilicon","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Discussion","abstract":"Proposal 1: Add new PICS to split the capability based on BC and then split interFreqDAPS test case 7.1.3.4.4\/8.1.4.3.4\/8.1.4.3.5. _x000D_\n_x000D_\nFor 38.523-1, the original 7.1.3.4.4\/8.1.4.3.4\/8.1.4.3.5 change nothing except for the title (i.e add \/ Intraband non-contiguous in the test case title), test frequency configuration is still the same as other inter frequency test case. New interFreqDAPS test cases 7.1.3.4.4a\/ 8.1.4.3.4a\/ 8.1.4.3.5a are added, and the test frequency configuration is the same as the intra-band contiguous CA test cases._x000D_\nFor 38.523-2 and 38.508-2, add two PICS, one for intra-band contiguous BC and one for intra-band non-contiguous BC_x000D_\nIf UE supports inter-frequency DAPS handover only on intra-band non-contiguous BC, UE test 7.1.3.4.4\/8.1.4.3.4\/8.1.4.3.5._x000D_\nIf UE supports inter-frequency DAPS handover only on intra-band contiguous BC, UE test 7.1.3.4.4a\/8.1.4.3.4a\/8.1.4.3.5a._x000D_\nIf UE supports inter-frequency DAPS handover on both intra-band non-contiguous BC and intra-band contiguous BC, UE test 7.1.3.4.4a\/8.1.4.3.4a\/8.1.4.3.5a or 7.1.3.4.4\/8.1.4.3.4\/8.1.4.3.5.","secretary_remarks":"","agenda_item_sort_order":1152,"ainumber":"6.4.7","ainame":"Discussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":548800,"status":"noted","reservation_date":"2024-09-02 14:52:23","uploaded":"2024-09-02 15:01:09","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"TEI16_Test"},{"winame":" NR_Mob_enh-UEConTest"}],"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-245488.zip","group":"R5","meeting":"R5-104","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-245653","title":"Discussion to handle IMS for loop back test case","source":"Huawei, HiSilicon","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":1152,"ainumber":"6.4.7","ainame":"Discussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":47211,"status":"noted","reservation_date":"2024-09-03 07:30:38","uploaded":"2024-09-03 07:31:08","revisionof":"R5-244721","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"TEI15_Test"},{"winame":" 5GS_NR_LTE-UEConTest"}],"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-245653.zip","group":"R5","meeting":"R5-104","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]