[{"name":"R5-234958","title":"Discussion on handling legacy NB-IoT test case for IoT NTN UE","source":"MediaTek Inc.","contact":"Daiwei Zhou","contact-id":72872,"tdoctype":"discussion","for":"Endorsement","abstract":"At RAN5 #99, legacy NB-IoT test case list applicable to NB-IoT NTN was discussed but not finally concluded, see details in [1] [2]. This discussion paper aims to complete the case review and furtherly update the adapted legacy test cases for a NB-IoT NTN UE.\n\n2.\tDiscussion\nBased on the discussion summary of [1] [2], some further considerations are taken to review the applicable legacy NB-IoT test case list. Test cases related to below feature or scenarios needs to be considered in the applicable test case list:\n1)\tAccess Class: as the NTN cell has a much larger coverage than TN cell, network operator may use AC to bar some UEs or for different service categories. The impacted cases include 22.4.4\/5\/8\/9.\n2)\tabnormal procedure: some abnormal procedure may happen in real network and impact the service experience, such as Attach reject or service request reject. The impacted cases include 22.5.1\/2\/3\/4\/5\/6\/9.\n\nThe detailed test case list that is applicable to NB-IoT NTN UE is attached in this discussion paper.\n3.\tProposal\/Way Forward\nProposal #1: Add a new table for legacy NB-IoT test cases applicable to UEs supporting NB-IoT over NTN. See R5-235082 [3] for details.\nProposal #2: For NB-IoT legacy test cases with test steps that are not applicable to UEs supporting NB-IoT over NTN add specific message contents for the test case to make it applicable. See R5-235078 [4] for details.","secretary_remarks":"","agenda_item_sort_order":839,"ainumber":"6.3.23.5","ainame":"Discussion Papers, Work Plan, TC lists","tdoc_agenda_sort_order":49580,"status":"revised","reservation_date":"2023-11-08 10:48:49","uploaded":"2023-08-12 05:21:21","revisionof":"","revisedto":"R5-235328","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"LTE_NBIOT_eMTC_NTN_plus_EPS-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__100_Toulouse\/Docs\/R5-234958.zip","group":"R5","meeting":"R5-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-234959","title":"Discussion on handling legacy eMTC test case for IoT NTN UE","source":"MediaTek Inc.","contact":"Daiwei Zhou","contact-id":72872,"tdoctype":"discussion","for":"Endorsement","abstract":"Internet of Things Non-Terrestrial Network (IoT NTN) was introduced in 3GPP Rel-17 to support NB-IoT and eMTC over satellite, re-using as much as possible legacy NB-IoT and eMTC features as defined in TS 36.763 [1] and TS 36.300 [2]:\n[TS 36.763]\n5.3\tIoT NTN features\nIt is assumed that all cellular IoT features specified up to Rel-16 are supported for IoT NTN.\nIt is assumed that both NB-IoT multi-carrier operation and NB-IoT single-carrier operation are supported as a baseline.\n\n[TS 36.300]\n23.21.1\tGeneral\nSupport for BL UEs, UEs in enhanced coverage and NB-IoT UEs over Non-Terrestrial Networks (see clause 4.12) is only applicable to E-UTRA connected to EPC. UEs not supporting NTN are barred from accessing an NTN cell.\nIn NTN, only BL UEs, UEs in enhanced coverage and NB-IoT UEs with GNSS capability are supported in this release of the specification.\n\u2026\nIn this release of the specification, NTN is only applicable to FDD system.\n\nAt RAN5 #99, legacy eMTC\/NB-IoT test case list applicable to IoT NTN was discussed but not finally concluded, see details in [3] [4]. This discussion paper aims to complete the eMTC case review and furtherly update the adapted legacy test cases for IoT NTN UE.\n2.\tDiscussion\nThis discussion paper proposes an overall solution for re-using the existing eMTC test cases, which are applicable to IoT NTN only UE, with method defined as below.\n2.1\tTS 36.523-1 Test cases\nHandle the applicable test cases, after scoping, as follows:\no\tFor a legacy eMTC TC that is not applicable to IoT NTN only UE fully:\n- no change\no\tFor a legacy eMTC TC that is applicable to IoT NTN only UE fully:\n- \tno change, or\n- \tadd a note around the test procedure to mention the difference for IoT NTN. One example is captured in CR R5-235079 [5], TC 9.2.1.1.22.\no\tFor a legacy eMTC TC that is applicable to IoT NTN only UE partially: \n- \tadd a exception \u2018NOT IoT NTN only\u2019 around the test steps not applicable to IoT NTN only UE. One example is captured in CR R5-235079 [5], TC 6.1.2.3.\n\nProposal #1: For eMTC legacy test cases are full or partially applicable to UEs supporting eMTC over NTN, update the test cases according to NTN requirements. See R5-235079 [5] for details.\n\n2.2\tTS 36.523-2 Case applicability\nIn TS 36.523-2, create a new clause and add all applicable legacy eMTC test cases which needs to be executed for IoT NTN only UE.\nFor IoT NTN only UE, it is not able to access TN networks and other RAT capabilities, e.g., pc_GERAN, pc_UTRA, pc_1xRTT, pc_HRPD and pc_eWLAN, shall be set to False, therefore inter-RAT test cases shall be excluded.\nAs NTN is only applicable to FDD duplex mode, the TDD capability, e.g., pc_eTDD shall be set to False, test cases with TDD mode, e.g., applicability condition includes \u201cand E-UTRA TDD\u201d shall be excluded. And NTN only applicability to Category M1 UE with FDD duplex mode, test cases not applicable to M1, e.g., applicability condition with \u201cNOT Category M1\u201d, shall be excluded.\nSimilarly, other features considered to be not applicable to IoT NTN includes: MFBI, (e)MBMS\/SC-PTM, ePDG, LWA\/LAA, CA\/DC, CoMP, ProSe, V2X and HST. The corresponding PICS shall be set to false for IoT NTN only UE.\n\nProposal #2: Add a new table for legacy eMTC test cases applicable to UEs supporting eMTC over NTN. See R5-235083 [6] for details.\n3.\tProposal\/Way Forward\nIn the contribution, we discuss the analysis of applicable legacy eMTC cases for IoT NTN with following proposals:\nProposal #1: For eMTC legacy test cases are full or partially applicable to UEs supporting eMTC over NTN, update the test cases according to NTN requirements. See R5-235079 [5] for details.\nProposal #2: Add a new table for legacy eMTC test cases applicable to UEs supporting eMTC over NTN. See R5-235083 [6] for details.","secretary_remarks":"","agenda_item_sort_order":839,"ainumber":"6.3.23.5","ainame":"Discussion Papers, Work Plan, TC lists","tdoc_agenda_sort_order":49590,"status":"noted","reservation_date":"2023-11-08 10:48:49","uploaded":"2023-08-12 07:27:43","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"LTE_NBIOT_eMTC_NTN_plus_EPS-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__100_Toulouse\/Docs\/R5-234959.zip","group":"R5","meeting":"R5-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-234960","title":"Discussion on handling SIB configuration for NGSO","source":"MediaTek Inc.","contact":"Daiwei Zhou","contact-id":72872,"tdoctype":"discussion","for":"Endorsement","abstract":"As defined in TS 36.300 [1] Clause 4.12, support of non-terrestrial network (NTN) typically includes GSO and NGSO satellites.\nE-UTRAN supports radio access over non-terrestrial networks for BL UEs, UEs in enhanced coverage and NB-IoT UEs. Support for non-terrestrial networks encompasses platforms that provide radio access through Geosynchronous orbits (GSO), Non-Geosynchronous Orbit (NGSO), which includes Low-Earth Orbit (LEO) and Medium Earth Orbit (MEO) or High Altitude Platform Systems (HAPS).\nAnd in TS 36.508 [2], System information blocks, especially SIB31 for eMTC and SIB31-NB for NB-IoT, have already specified for GSO. However, the SIBs for NGSO are still FFS in TS 36.508 [2] and the specific test cases.\n2.\tDiscussion\nThis discussion paper aims to provide a way to define the SIB configuration of NGSO satellite for IoT NTN.\n\nAs NGSO includes both LEO and MEO, considering the current industrial deployment and the characteristic of propagation channel, LEO should be the proper satellite platform to satisfy the requirements of IoT NTN use case. Therefore, in this discussion paper only LEO is discussed and MEO is not in the scope.\n\nIn TS 36.331 [3], the ephemeris within SIB31(-NB) is defined as below:\n[..]\norbitalParameters\nInstantaneous values of the satellite orbital parameters. The signalled values are only valid for the duration as defined by ul-SyncValidityDuration and epochTime.\nstateVectors\nInstantaneous values of the satellite state vectors. The signalled values are only valid for the duration as defined by  ul-SyncValidityDuration and epochTime.\n\nHowever, there is no clear requirement\/guideline on how to define ephemeris for GSO or NGSO, so the stateVectors IE should be applicable to both GSO and NGSO. Using stateVectors rather than orbitalParameters for NGSO could be feasible to align with current SIB configuration of GSO.\n\nProposal #1: With the implementation complexity of System simulator (SS) considered, stateVectors is proposed to be used for NGSO\/LEO.\n\nFor stateVectors IE, as the LEO moves fast, the satellite position and corresponding parameters, such as, common TA and Koffset, change frequently. So the SS needs to update the SIB-31 when needed.\n\nAs the UE position is stationary as defined in TS 36.508 [1] and the moving speed is usually known when the satellite height is fixed, a look-up table is proposed to be used for the SS to estimate the satellite position\/velocity and then to update the SIB31(-NB).\n\nBelow is an example of look-up table for LEO (600 km), T1 is the starting time of service available and T2 is the time the satellite flies away.\nWhen the SS needs to update the SIB31(-NB), the SS needs to search the timer offset and then find the exact position and velocity to generate the SIB31(-NB). Figure 1 illustrates how the SS estimate the ephemeris information. Detailed table are given in [4].\nProposal #2: A look-up table to be used to update the ephemeris information for LEO.\n3.\tProposal\/Way Forward\nIn the contribution, we discuss the analysis of applicable legacy eMTC and NB-IoT cases for IoT NTN with following proposals:\nProposal #1: With the implementation complexity of System simulator (SS) considered, stateVectors is proposed to be used for NGSO.\nProposal #2: A look-up table of position and velocity stored in SS to be used to update the ephemeris information for LEO.","secretary_remarks":"","agenda_item_sort_order":839,"ainumber":"6.3.23.5","ainame":"Discussion Papers, Work Plan, TC lists","tdoc_agenda_sort_order":49600,"status":"revised","reservation_date":"2023-11-08 10:48:49","uploaded":"2023-08-12 08:57:57","revisionof":"","revisedto":"R5-235329","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"LTE_NBIOT_eMTC_NTN_plus_EPS-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__100_Toulouse\/Docs\/R5-234960.zip","group":"R5","meeting":"R5-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-235119","title":"Applicability of legacy NB-IOT testcases to NTN GSO only UE","source":"Qualcomm Incorporated, Rohde & Schwarz, MediaTek","contact":"Bharadwaj Kumar Cheruvu","contact-id":68613,"tdoctype":"discussion","for":"Endorsement","abstract":"Discussion paper R5-233495 focused on NB-IOT NTN GSO scenario categorized two types of UEs (Type 1 UE \u2013 supporting NB-IOT legacy features and Release 17 NB-IOT NTN GSO scenario, Type 2 UE \u2013 supporting only NB-IOT NTN GSO scenario) and provided preliminary analysis of adapted legacy test cases to a Type 2 UE.\nKey points from discussion paper [3]:\n- Summary of agreed execution guidelines:\n - Type 1 UE (supporting both TN and NTN) \n- Release 17 NB-IoT test cases in NTN bands.\n- \tRelease 13 to 15 NB-IoT test cases in TN bands.\n - \tType 2 UE (supporting only NTN)\n -Release 17 NB-IoT test cases in NTN bands.\n -Adapted test cases (from Release 13 to 15) in NTN bands.\n\nThis discussion paper aims to complete the analysis and take further steps to conclude on the adapted legacy test case list for a Type 2 UE.\n2.\tDiscussion\n2.1\tAdapted legacy test cases for Type 2 UE\nAs mentioned in Proposal-1.1 of discussion paper [3], spreadsheet attached with this discussion paper includes the list of adapted legacy test cases considering typical NB-IOT NTN GSO deployments and industry needs.\nTest cases falling under the below listed categories are considered \u201cNot Applicable\u201d for a Type 2 UE.\na.\tAll non-approved (\u2018compliable\u2019, \u2018verifiable\u2019) test cases as per TTCN CR Agreement Status 2023-wk16.\n\nb.\tTest cases having corresponding NTN Release 17 variant (ex: t-reordering)\n\nc.\tAs NTN GSO cell area is expected to be huge, NTN UE may not perform PLMN changes and cell reselections. Hence, most of the Idle mode operation test cases (22.2.x) would be non-relevant. \n\nd.\tMajority of the test cases having additional applicabilities (Ex: S1-U, ROHC support, LAP etc) based on existing deployments.\n\ne.\tTest cases with negative scenarios (ex: TAU Reject, abnormal detach) not exercised in real deployments.\n\nIn addition to the test cases listed in [3] few more test cases listed below have been considered applicable for NB-IoT NTN GSO UE:\n1)\tAccess Class: as the NTN cell has a much larger coverage than TN cell, network operator may use AC to bar some UEs or for different service categories. The impacted cases include 22.4.4\/5\/8\/9. New system information combinations to be added in [8] and newly proposed test cases to be added in applicability list defined in [6].\n2)\tabnormal procedure: some abnormal procedure may happen in real network and impact the service experience, such as Attach reject or service request reject. The impacted cases include 22.5.1\/2\/3\/4\/6\/9. Newly proposed test cases to be added in applicability list defined in [6].\n\n2.2\tUE capability audit test case\nBased on the agreed execution guidelines, Type 1 UE (supporting both TN and NTN) lacks NTN coverage for UE Capability audit test case as the execution happens in TN bands.\n\n3.   Proposal\/Way Forward\n1.\tNew NTN system information combinations shall be defined in [4] for adapted legacy test cases. This is handled in [5] submitted in this meeting.\n\n2.\tChanges related to NTN test environment shall be added to identified adapted legacy test cases and CRs [7] [8] [9] are submitted in this meeting.\n\n3.\tAs RTT delays are huge for NTN environment, few L2 test cases of [1] needs additional test case specific updates to cater RTT delays. CR [10] has been submitted in this meeting.\n\n4.\tAll identified adapted legacy test cases shall be added in clause 5 of [2]. CR [6] has been submitted to [2] in this meeting.\n\n5.\tDefine new NTN UE Capability audit test case 22.4.13a. If agreed, this will be handled in RAN5#101.","secretary_remarks":"","agenda_item_sort_order":839,"ainumber":"6.3.23.5","ainame":"Discussion Papers, Work Plan, TC lists","tdoc_agenda_sort_order":51190,"status":"revised","reservation_date":"2023-11-08 15:08:19","uploaded":"2023-08-11 15:10:31","revisionof":"","revisedto":"R5-235327","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__100_Toulouse\/Docs\/R5-235119.zip","group":"R5","meeting":"R5-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-235327","title":"Applicability of legacy NB-IOT testcases to NTN GSO only UE","source":"Qualcomm Incorporated, Rohde & Schwarz, MediaTek","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":839,"ainumber":"6.3.23.5","ainame":"Discussion Papers, Work Plan, TC lists","tdoc_agenda_sort_order":51191,"status":"noted","reservation_date":"2023-03-09 09:40:14","uploaded":"2023-09-03 09:41:05","revisionof":"R5-235119","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__100_Toulouse\/Docs\/R5-235327.zip","group":"R5","meeting":"R5-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-235328","title":"Discussion on handling legacy NB-IoT test case for IoT NTN UE","source":"MediaTek Inc.","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":839,"ainumber":"6.3.23.5","ainame":"Discussion Papers, Work Plan, TC lists","tdoc_agenda_sort_order":49581,"status":"noted","reservation_date":"2023-03-09 09:40:14","uploaded":"2023-09-03 09:41:05","revisionof":"R5-234958","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"LTE_NBIOT_eMTC_NTN_plus_EPS-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__100_Toulouse\/Docs\/R5-235328.zip","group":"R5","meeting":"R5-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-235329","title":"Discussion on handling SIB configuration for NGSO","source":"MediaTek Inc.","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":839,"ainumber":"6.3.23.5","ainame":"Discussion Papers, Work Plan, TC lists","tdoc_agenda_sort_order":49601,"status":"noted","reservation_date":"2023-03-09 09:40:14","uploaded":"2023-09-03 09:41:05","revisionof":"R5-234960","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"LTE_NBIOT_eMTC_NTN_plus_EPS-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__100_Toulouse\/Docs\/R5-235329.zip","group":"R5","meeting":"R5-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]