[{"name":"R5-253742","title":"New WID on UE Conformance - Introduction of another IoT-NTN S-band (MSS band 2000-2020 MHz UL and 2180-2200 MHz DL)","source":"MediaTek Inc., China Telecom, EchoStar","contact":"Daiwei Zhou","contact-id":72872,"tdoctype":"WID new","for":"Endorsement","abstract":"In Rel-17, there is already a S-band defined for IoT NTN (1980-2010 MHz in UL, and 2170-2200 MHz in DL). However, there is some deviation in how MSS S-band is allocated in region 2 versus in all other regions. Per ITU, the Region 2 MSS S-Band had been allocated to UL 1980-2025 MHz and DL 2160-2200 MHz.\nIn the case of North America region (US, Canada, Mexico) the MSS band is allocated to UL 2000 MHz -2020 MHz and DL 2180 MHz -2200 MHz which is not exactly aligned to n256\/B256 definition, i.e., UL 1980 MHz \u2013 2010 MHz, DL 2170 MHz \u2013 2200 MHz. For consistency across North America and Region 2 as a whole, it is beneficial to have a common range of UL 2000 MHz -2020 MHz and DL 2180 MHz -2200 MHz as a separate 3GPP NTN band.\nThe aim of this spectrum WID is to add support for a new FDD E-UTRA IoT-NTN band with the 2000-2020 MHz UL and 2180-2200 MHz DL. This FDD band 252 is Release-independent from Rel-17 for the IoT NTN UE.\nThe Rel-19 WI IoT_NTN_FDD_S_band has been 100% completed for both Core and Perf parts at RAN#108 meeting (Jun. 2025). According to the requirements of  IoT NTN bands, it is justified now to start the work on the corresponding UE conformance test specifications for band 252 for IoT NTN operation in 3GPP RAN WG5.\n4\tObjective\n4.1\tObjective of SI or Core part WI or Testing part WI\nThe objective of this work item is to define the UE conformance requirements corresponding to IoT_NTN_FDD_S_band, by analysing the test case impact, applicability and test environment, and updating the relevant conformance specifications. This work item will cover Signalling, RF, Demod and RRM conformance test specifications for FDD IoT NTN band 252.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":37420,"status":"revised","reservation_date":"2025-08-01 08:25:35","uploaded":"2025-08-15 02:45:35","revisionof":"","revisedto":"R5-254908","release":"Rel-19","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__108_Bangalore\/Docs\/R5-253742.zip","group":"R5","meeting":"R5-108","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-253960","title":"New WID on UE Conformance - Channel raster enhancement","source":"China Telecom, Huawei","contact":"Lei GAO","contact-id":107221,"tdoctype":"WID new","for":"Endorsement","abstract":"3GPP TSG RAN WG4 has completed the work item on channel raster enhancement, which defined new channel raster with 10kHz granularity for NR FR1, called enhanced channel raster, and introduce new UE capability to indicate whether the UE supports the requirements for UE channel bandwidths located on the enhanced channel raster of a band. 3GPP TSG RAN WG5 needs to introduce the relevant conformance testing into RAN5 specifications. \n4\tObjective\n4.1\tObjective of SI or Core part WI or Testing part WI\nThe objective of the present work item is to define the corresponding conformance requirements, the test cases, applicability, test environment and update the relevant conformance specifications for enhanced channel raster requirements introduced by RAN4.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":39600,"status":"revised","reservation_date":"2025-08-11 06:55:48","uploaded":"2025-08-15 06:10:11","revisionof":"","revisedto":"R5-254909","release":"Rel-18","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__108_Bangalore\/Docs\/R5-253960.zip","group":"R5","meeting":"R5-108","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-254043","title":"UE Conformance - core and perf requirements for IoT NTN TDD mode","source":"Iridium Satellite LLC","contact":"Andjela Ilic Savoia","contact-id":106171,"tdoctype":"WID new","for":"Endorsement","abstract":"As the Core of the WI below is near completion, there is a need for conformance requirements.\n(Relevant RAN1 led WI: RP-243293: introduction of IoT-NTN TDD mode)\n\nThe IoT NTN TDD mode will extend the deployment of NB-IoT NTN worldwide, by enabling the service from the existing, in-orbit Non-Geostationary Satellite Orbit (NGSO) system. This includes providing connectivity to polar regions.\nThe completion level of the 3GPP RAN1-lead Rel-19 work item on IoT NTN TDD mode has achieved 76% for core part at RP#108 (Jun-2025). The Target Completion Date of the core part is September 2025, and the Target Completion Date of the performance part is March 2026. To fulfil the strong demand for IoT NTN deployments, there is a need to introduce an associated RAN5 work item to enable UE RF\/RRM conformance testing for Rel-19 IoT NTN TDD mode core and performance requirements for NTN.\n4\tObjective\n4.1\tObjective of SI or Core part WI or Testing part WI\nThe objective of this work item is to define the UE RF\/RRM\/Protocol conformance testing requirements for Rel-19 IoT NTN TDD mode, to enable global NB-IoT NTN service coverage.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":40430,"status":"revised","reservation_date":"2025-08-11 18:50:31","uploaded":"2025-08-15 17:02:24","revisionof":"","revisedto":"R5-254914","release":"Rel-19","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__108_Bangalore\/Docs\/R5-254043.zip","group":"R5","meeting":"R5-108","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-254130","title":"New WID on UE Conformance -Low-power wake-up signal and receiver for NR","source":"vivo, Apple","contact":"Ruixin Wang","contact-id":104883,"tdoctype":"WID new","for":"Endorsement","abstract":"5G systems are designed and developed targeting for both mobile telephone and vertical use cases. Besides latency, reliability, and availability, UE energy efficiency is also critical to 5G. Currently, 5G devices may have to be recharged per week or day, depending on individual\u2019s usage time. In general, 5G devices consume tens of milliwatts in RRC idle\/inactive state and hundreds of milliwatts in RRC connected state. Designs to prolong battery life is a necessity for improving energy efficiency as well as for better user experience. \nEnergy efficiency is even more critical for UEs without a continuous energy source, e.g., UEs using small rechargeable and single coin cell batteries. Among vertical use cases, sensors and actuators are deployed extensively for monitoring, measuring, charging, etc. Generally, their batteries are not rechargeable and expected to last at least few years as described in TR38.875. Wearables include smart watches, rings, eHealth related devices, and medical monitoring devices. With typical battery capacity, it is challenging to sustain up to 1-2 weeks as required. \nStudy item for \"Study on low-power wake up signal and receiver for NR\" is completed in Rel-18.\nBased on the SI outcome, Rel-19 Work Item Low-power wake-up signal and receiver for NR (LP-WUS\/WUR) was approved to introduce new requirements fo LP-WUS\/WUR.\nUnder the Rel-19 parent WI, RAN4 has specified below requirements in the Core part:\n\u2022\tUE low-power wake-up receiver RF requirements, e.g. bandwidth, REFSENS, Max Input level, ACS and ASCS, Blocking, Spurious response, Intermodulation, Spurious emissions requirements and DL reference measurement channels. \n\u2022\tThe necessary RRM requirements.\n\u2022\tThe UE demodulation performance and test cases for LP-WUS\/WUR.\nThe overall completion level for the Core part of NR_LPWUS is 90% at the RAN#108 in June 2025 and the target completion date of Core part is September 2025. The corresponding UE conformance specifications are now required to be implemented in RAN5.\n4\tObjective\n4.1\tObjective of SI or Core part WI or Testing part WI\nThe objective of this work item is to define the UE conformance requirements corresponding to the WID Low-power wake-up signal and receiver for NR. This work item will cover RF, RRM and demodulation conformance test specifications.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":41300,"status":"revised","reservation_date":"2025-08-13 02:49:47","uploaded":"2025-08-15 06:16:36","revisionof":"","revisedto":"R5-254910","release":"Rel-19","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__108_Bangalore\/Docs\/R5-254130.zip","group":"R5","meeting":"R5-108","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-254199","title":"New WID on UE Conformance - Enhanced requirements and conductive test methodology for NR NTN and IoT NTN","source":"Xiaomi, China Unicom, Samsung","contact":"Sunlin Zhu","contact-id":108237,"tdoctype":"WID new","for":"Endorsement","abstract":"From RAN#103, a new Rel-19 RAN4 work item Enhanced requirements and conductive test methodology for NR NTN and IoT NTN was carried out, this WI targets at the UE Conformance on enhanced requirements and test methodology for NR-NTN (Non-Terrestrial Networks) and IoT-NTN (NB-IoT and eMTC based NTN) in NR-NTN frequency range 1 (FR1-NTN) and frequency range for LTE bands. The following working areas are included. \n\u2022\tHigh power UE (HPUE) for NTN:\nTo address NTN uplink limitations by elevating UE Tx power beyond Rel-18's, aligning with TN high-power standards to enhance coverage\/throughput for critical scenarios (e.g., disaster response, automotive) under feasible regulatory.\nSpecify high power UE (HPUE) for NR-NTN (Non-Terrestrial Networks) and IoT-NTN (NB-IoT and eMTC based NTN) in FR1-NTN bands and the corresponding LTE NTN bands for the single uplink (UL) carrier scenario.\n\n\u2022\tNTN testing for Non-Geostationary Orbit (NGSO):\nIn Rel-18 the UE test coverage issue was identified in RAN5 for non-geostationary orbit (NGSO) when approaching the end of Rel-18, and correspondingly the solution was provided in RP-232682, where the UE supporting NGSO will be verified for frequency and timing compensation performance under the channel model with fixed Doppler shift or fixed delay shift which are randomly selected before the test. A new channel model with time-varying Doppler\/delay shifts is needed to validate UE compensation under real-world mobility, ensuring robust NGSO service performance.\n\n\u2022\tLess than 5MHz for NR-NTN:\nTo enable more efficient deployment of the FR1 NTN bands where parts of the spectrum for satellite use is limited. This feature built on the work done in the Rel-18, i.e., WI of NR support for dedicated spectrum less than 5 MHz for FR1, as much as possible by extending support for NTN.\nFor this work item in RAN4, the overall completion level for core part has reached 88% and performance part has reached to 40% after RP#108 (Sep 2024) and expected complete at the RP#109 meeting. Therefore, it is justified to introduce the conformance testing for Enhanced requirements and conductive test methodology for NR NTN and IoT NTN into RAN5 specifications.\n4\tObjective\nThe objective of this work item is to enable UE conformance testing for the Rel-18 NTN enhancements WI which includes analysing the requirements, creation of corresponding test cases by defining the test environment, special conformance testing function, test procedure, message contents, MU\/TT analysis, associated PICS, applicability and updating the relevant conformance specifications. \nThe conformance testing aspects for this WI would consist of below areas:\n?\tUE RF test cases for HPUE requirements for NR NTN, HPUE requirements for IoT NTN, NTN testing NGSO channel model and NR IoT NTN less than 5MHz\n?\tUE DEMOD test cases for NTN testing NGSO channel model and NR IoT NTN less than 5MHz\n?\tRRM test cases for NTN testing NGSO channel model and NR IoT NTN less than 5MHz","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":41990,"status":"revised","reservation_date":"2025-08-14 07:50:41","uploaded":"2025-08-15 05:56:31","revisionof":"","revisedto":"R5-254911","release":"Rel-19","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__108_Bangalore\/Docs\/R5-254199.zip","group":"R5","meeting":"R5-108","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-254337","title":"New WID on UE Conformance \u2013 Additional NR bands for NR features in Rel-19","source":"ZTE Corporation, Huawei, China Telecom","contact":"Zhifeng Ma","contact-id":61569,"tdoctype":"WID new","for":"Endorsement","abstract":"3GPP TSG RAN WG4 has created the Rel-19 WID for additional NR bands for NR features. The WID is to support a number of NR features for the band specific requirements. Following requirements are introduced into the tables of core specifications where the band specific requirements are specified:\n\u2022\tNR feature: UL-MIMO for a single band\no\tThe introduction of NR bands with UL-MIMO happened in Rel-16 WI NR_RF_FR1 and in Rel-17 WI NR_bands_UL_MIMO_PC3_R17 for PC1.5\/2\/3. The work continued in Rel-18 WI NR_bands_UL_MIMO_R18 for PC1.5\/2\/3\/5.\no\tThe Rel-19 basket WI is setup to introduce further NR bands with UL-MIMO for PC5, PC3, PC2 and PC1.5 UE power class.\no\tNote: PC1.5\/2\/3\/5 means the power class 1.5\/2\/3\/5, where the corresponding maximum output power are defined in Table 6.2.1-1 and Table 6.2F.1-1 in TS 38.101-1, respectively.\n\u2022\tNR features: 4Rx and 8Rx\no\tTo provide higher throughput and better coverage, the 4Rx UE requirements had been introduced based on the operator and market\u2019s demand in the previous releases from Rel-15 to Rel-18.\no\tSimilar to 4Rx, the bands supporting 8Rx are added to RAN4 specification based on operators\u2019 demands. In Rel-18, CPE\/FWA\/vehicle\/industrial devices are applied to 8Rx in terms of the WID NR_ENDC_RF_FR1_enh2.\no\tThe Rel-19 basket WI is created to include the corresponding 4Rx and 8Rx requirements for NR FR1 bands (<2.6GHz) in the RAN4 specifications.\nThe RAN4 WID was completed with 75% completion level in last RAN plenary. It\u2019s time for 3GPP TSG RAN5 to start working on the corresponding conformance testing part to meet the industry interest.\n4\tObjective\n4.1\tObjective of SI or Core part WI or Testing part WI\nThe objective of this work item is to develop RF test cases for Rel-19 additional NR bands for NR features covered by the RAN4 work items.\n.. In the conformance test WI, example bands would be selected from the above list based on the industry interest to complete the new RF test cases.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":43370,"status":"revised","reservation_date":"2025-08-14 14:49:41","uploaded":"2025-08-15 14:37:49","revisionof":"","revisedto":"R5-254912","release":"Rel-19","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__108_Bangalore\/Docs\/R5-254337.zip","group":"R5","meeting":"R5-108","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-254431","title":"New WID on UE Conformance \u2013 FR1 TRP (Total Radiated Power), TRS (Total Radiated Sensitivity) and MIMO OTA (Over the Air) testing enhancement Phase 3","source":"Apple Inc, Vivo","contact":"Ashwin Mohan","contact-id":102945,"tdoctype":"WID new","for":"Endorsement","abstract":"RAN5 has completed definition of Rel-18 conformance test cases for NR FR1 TRP TRS and NR MIMO OTA. In Rel-19, further enhancements for TRP TRS requirements as well as for NR MIMO OTA and corresponding verification methodologies are introduced:\nTRP and TRS enhancements\nAddressing TRP and TRS requirements for smartphones, conformance test requirements need to be defined for additional NR bands for which core requirements have been defined. This will also include the introduction of conformance test requirements for smartphones supporting UL-MIMO.\nIn the field of OTA performance verification, there exists significant interest from the industry concerning XR (Extended Reality) and NTN (Non-Terrestrial Network) devices. Regarding phantom definitions for XR device testing, it has been acknowledged in 3GPP that there might be a challenge to reuse the current head and hand phantom used for handheld UE testing for XR devices and an enhanced phantom or a new design is necessary for OTA measurement. Preliminary OTA conformance test method aspects for XR and NTN may be informatively included in the annexes of the test specifications for this release; performance requirements are not in scope. \nMIMO OTA enhancements\nIn Rel-17, NR MIMO OTA WI specified the test methodology for FR1, and corresponding requirements were defined for bands n41 and n78. As we move to Rel-18, the NR MIMO OTA WI enhancement specified requirements for more FR1 bands, specifically n1, n5, and n28 with the test methodology defined in Rel-17.\nHowever, the current FR1 MIMO test methodology considering static channel conditions, limits the ability to verify UE MIMO performance only under stationary channel models where parameters such as AoD and AoA remains fixed. Consequently, the existing FR1 MIMO OTA test system cannot adequately verify UE performance in realistic dynamic channel conditions. Therefore, it is essential to study dynamic channel models and develop corresponding channel validation solution in Rel-19 to create more realistic FR1 MIMO OTA test scenarios.\nFurthermore, addressing MIMO OTA with dynamic channel model requirements, additional NR FR1 band requirements need to be defined based on operators\u2019 requests, considering the current Rel-17 and Rel-18 FR1 MPAC static test methodology as a starting point.\n4\tObjective\n4.1\tObjective of SI or Core part WI or Testing part WI\nThe objective of this Work Item is to enable UE conformance testing for the corresponding Rel-19 NR FR1 TRP TRS and MIMO OTA Enhancements Phase 3 Work Items listed under clause 2.2. RAN5 conformance test procedures will be created to verify test requirements as per the scope being covered in the core and performance parts of the Rel-19 Work item namely:\n(1)\tEnhancements of test methodology \n\u2022\tAddition of test methodology for Handheld UEs with 2Tx (non-coherent UL MIMO)  \n\u2022\tIncorporate informatively within Annex of TS 38.561, any  test method, metric or other details related to for radiated performance testing of FR1 NTN devices (including NR NTN and IoT NTN) or XR devices. Performance Requirements are not within the scope of this Release.\n\u2022\tStudy and develop FR1 dynamic MIMO OTA test methodology with the following aspects\no\tFree Space measurement condition is the baseline \no\tDevelop preliminary MU and TT for the FR1 MIMO OTA with dynamic channel models, capturing the outcome as an informative in the correspondent TS 38.551 annexes.\n(2)\tDefine conformance tests containing test requirements for NR FR1 SISO SA TRP and TRS (OTA) and NR MIMO OTA for the following:\n\u2022\tSpecify TRP and TRS conformance requirements:\no\tSpecify FR1 TRP and TRS test requirements for smartphones for the NR bands listed below: ...","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":44310,"status":"revised","reservation_date":"2025-08-14 21:51:12","uploaded":"2025-08-26 06:01:04","revisionof":"","revisedto":"R5-254913","release":"Rel-19","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__108_Bangalore\/Docs\/R5-254431.zip","group":"R5","meeting":"R5-108","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-254453","title":"New WID on UE Conformance - Evolution of NR duplex operation: Sub-band full duplex (SBFD)","source":"Huawei, HiSilicon, CMCC","contact":"Yaping Zhang","contact-id":85042,"tdoctype":"WID new","for":"Endorsement","abstract":"TDD is widely used in commercial NR deployments. In TDD, the time domain resource is split between downlink and uplink. Allocation of a limited time duration for the uplink in TDD would result in reduced coverage, increased latency and reduced capacity. As a possible enhancement on this limitation of the conventional TDD operation, the feasibility of allowing the simultaneous existence of downlink and uplink, a.k.a. full duplex, or more specifically, subband non-overlapping full duplex (SBFD) at the gNB side within a conventional TDD band has been studied in Rel-18. During the study in Rel-18 SI, the applicable and relevant deployment scenarios were identified for SBFD and dynamic\/flexible TDD, respectively. For SBFD, the specification impacts, performance evaluation results, implementation feasibility and impact on RF requirements are summarized in TR 38.858.\nAccording to the conclusion in the TR 38.858, 3GPP created the Rel-19 WID Evolution of NR duplex operation: Sub-band full duplex (SBFD) to specify SBFD operation at the gNB side within a TDD carrier, gNB-to-gNB CLI handling schemes and UE-to-UE CLI handling schemes for SBFD operation, and RF requirements for SBFD operation at gNB.  Specifically, the core part of this work item covers the following aspects:\n?\tSpecify semi-static indication of time location and frequency domain location of SBFD subbands to UEs in RRC_CONNECTED mode\n?\tSpecify SBFD operation to support random access in SBFD symbols by UEs in RRC_CONNECTED mode and RRC_IDLE\/INACTIVE mode\n?\tSpecify UE transmission, reception and measurement behavior and procedures in SBFD symbols and\/or non-SBFD symbols for SBFD aware UE\n?\tSpecify enhancements for CLI handling, including UL resource muting for PUSCH and L1 based UE-to-UE CLI measurement and reporting based on existing CSI framework\nThe core part of this work item has completed 93% in RAN#108 (2025-06) and is expected to be 100% completed in RAN#109 (2025-09). Therefore, it\u2019s time for 3GPP TSG RAN WG5 to start working on the corresponding conformance testing part to meet the industry interest.\n4\tObjective\n4.1\tObjective of SI or Core part WI or Testing part WI\nThe objective of the present work item is to provide conformance testing for Rel-19 Evolution of NR duplex operation: Sub-band full duplex (SBFD) to reflect the relevant core and performance requirements.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":44530,"status":"revised","reservation_date":"2025-08-15 01:50:28","uploaded":"2025-08-15 08:46:41","revisionof":"","revisedto":"R5-254915","release":"Rel-19","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__108_Bangalore\/Docs\/R5-254453.zip","group":"R5","meeting":"R5-108","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-254673","title":"New WID on UE Conformance - Multi-carrier enhancements for NR Phase 3","source":"Lenovo, Motorola Mobility","contact":"Abdul Rasheed Mohammed","contact-id":29230,"tdoctype":"WID new","for":"Information","abstract":"Multi-carrier operation is very important for 5G commercial networks by aggregating various spectrum resources for providing high data rate and low latency communication. Co-scheduled carriers with different SCSs have high commercial needs for operators, e.g., 3.5GHz TDD + Sub-3GHz FDD, FR1 + FR2, etc.\n\nRAN1 in Rel-18 introduced two new DCI formats 0_3 and 1_3. DCI formats 0_3 or 1_3 can schedule up to 4 cells with a single PUSCH or PDSCH per scheduled cell. In Rel-17, for FR2 with high SCS, multi-PDSCH\/PUSCH scheduling was introduced, i.e., up to 8 PUSCHs or PDSCHs on a single serving cell could be scheduled by a single DCI format 0_1 or 1_1, in order to save UE power consumption and reduce PDCCH overhead. Rel-19 Multi-carrier enhancements for NR proposes to combine multi-cell scheduling and multi-PDSCH\/PUSCH scheduling  to fully exploit the gain of power saving and PDCCH overhead reduction so that one DCI format 0_3 or 1_3 can schedule multiple cells with one or multiple PUSCHs\/PDSCHs per scheduled cell. This is especially useful when scheduling cell in FR1 with a lower SCS schedules multiple cells in FR2 with higher SCS.\n\nThe \u201cCore part: Multi-carrier enhancements for NR Phase 3\u201d WI is targeted to be completed in RP#109 (Sep 25). It\u2019s a proper time for RAN5 to initiate an associated conformance work item to enable UE protocol conformance testing of new features for multi carrier enhancements added in Rel-19.\n\n4\tObjective\n4.1\tObjective of SI or Core part WI or Testing part WI\nThe objective of this work item is to define the corresponding UE protocol conformance requirements,  applicability, test environment, and update the relevant conformance specifications for the multi-cell PUSCH\/PDSCH scheduling with a single DCI with one or multiple PUSCHs\/PDSCHs per scheduled cell by the single DCI  format 0_3 or 1_3.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":46730,"status":"revised","reservation_date":"2025-08-15 11:30:50","uploaded":"2025-08-15 13:58:55","revisionof":"","revisedto":"R5-254916","release":"Rel-19","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__108_Bangalore\/Docs\/R5-254673.zip","group":"R5","meeting":"R5-108","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-254913","title":"New WID on UE Conformance \u2013 FR1 TRP (Total Radiated Power), TRS (Total Radiated Sensitivity) and MIMO OTA (Over the Air) testing enhancement Phase 3","source":"Apple Inc, Vivo","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"WID new","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":44311,"status":"noted","reservation_date":"2025-09-04 11:28:03","uploaded":"2025-09-04 11:31:05","revisionof":"R5-254431","revisedto":"","release":"Rel-19","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__108_Bangalore\/Docs\/R5-254913.zip","group":"R5","meeting":"R5-108","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-254914","title":"UE Conformance - core and perf requirements for IoT NTN TDD mode","source":"Iridium Satellite LLC","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"WID new","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":40431,"status":"noted","reservation_date":"2025-09-04 11:28:03","uploaded":"2025-09-04 11:31:05","revisionof":"R5-254043","revisedto":"","release":"Rel-19","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__108_Bangalore\/Docs\/R5-254914.zip","group":"R5","meeting":"R5-108","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-254916","title":"New WID on UE Conformance - Multi-carrier enhancements for NR Phase 3","source":"Lenovo, Motorola Mobility","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"WID new","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":46731,"status":"noted","reservation_date":"2025-09-04 11:28:03","uploaded":"2025-09-04 11:31:05","revisionof":"R5-254673","revisedto":"","release":"Rel-19","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__108_Bangalore\/Docs\/R5-254916.zip","group":"R5","meeting":"R5-108","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]