[{"name":"R5-260228","title":"New WID on UE Conformance \u2013 NR MIMO Phase 5","source":"China Telecom","contact":"Lei GAO","contact-id":107221,"tdoctype":"WID new","for":"Endorsement","abstract":"Justification\nIn the parent WI: NR MIMO Phase 5, the following new features are introduced, and corresponding UE Core and Performance requirements are specified:\n\u2022\tUE-initiated\/event-driven beam management for reducing overhead and\/or latency, targeting FR2 and sTRP with intra- and inter-cell beam management.\n\u2022\tUp to 128 CSI-RS ports, targeting FR1\n\u2022\tUE inter-TRP time misalignment and frequency\/phase offset measurement and reporting, targeting FR1, both FDD and TDD\n\u2022\tNon-coherent UL codebook to facilitate 3-antenna-port codebook-based transmissions, enhancement(s) to enable 3T6R SRS antenna switching, as well as UE capability signaling for 3T3R antenna switching and 3-antenna-port non-codebook-based transmissions\n\u2022\tEnhancement for asymmetric DL sTRP\/UL mTRP deployment scenarios.\nIn RAN#110, the parent WI has been 100% completed in the Core part and 80% completed in the Performance part. With the Perf part is targeting March 2026, it is time for RAN5 to start the corresponding UE conformance testing work.\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 Rel-19 NR MIMO Phase 5 WI which includes analysing the test case impact, applicability, test environment, and updating the relevant conformance specifications. \nThe conformance testing aspects for this WI would consist of RF, RRM and Demod area.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":2280,"status":"revised","reservation_date":"2026-01-27 02:55:42","uploaded":"2026-01-30 06:45:35","revisionof":"","revisedto":"R5-261117","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__110_Gothenburg\/Docs\/R5-260228.zip","group":"R5","meeting":"R5-110","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-260252","title":"New WID on UE Conformance - Identifying non-3GPP Devices Connecting behind a UE or 5G-RG","source":"China Telecom","contact":"JING ZHAO","contact-id":85327,"tdoctype":"WID new","for":"Endorsement","abstract":"Justification\nBy enhancing the 5G System to support the identification of device-specific identities, operators can enable differentiated treatment for devices that are not natively part of the operator\u2019s 3GPP network. This capability allows the network to adapt configurations and offer services based on the specific characteristics and requirements of individual devices, which may differ from those associated with the subscription identifier used to establish the connection.\nThe Rel-19 work item CT1 aspects of Identifying non-3GPP Devices Connecting behind a UE or 5G-RG specifies the stage-3 core network procedures and protocols to identify non-3GPP devices connected behind a UE or a 5G-RG. This includes, for example, the introduction of non-3GPP device connection information IE during the PDU Session Modification procedure, thereby enabling differentiated QoS treatment, policy control, and management for such devices.\nThe core part of the 3GPP Rel-19 CT1 aspects of Identifying non-3GPP Devices Connecting behind a UE or 5G-RG work item has reached 100% completion as of September 2025.Therefore, it is timely for RAN5 to introduce an associated RAN5 work item to enable UE conformance testing for the new features.\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 protocol conformance requirements to cover the new Rel-19 UIA_ARC capabilities to further extend the scenarios that UIA_ARC can be supported and bring better performance.\n\nNOTE 1:Due to the early stages of deployment,non-3GPP Devices Connecting behind a 5G-RG is outside the scope of this Conformance WI.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":2520,"status":"revised","reservation_date":"2026-01-27 06:15:42","uploaded":"2026-01-27 07:02:03","revisionof":"","revisedto":"R5-261118","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__110_Gothenburg\/Docs\/R5-260252.zip","group":"R5","meeting":"R5-110","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-260539","title":"New WID on UE Conformance - Simultaneous RxTx band combinations for NR CA\/DC, NR SUL and LTE\/NR DC in Rel-19","source":"Huawei, China Telecom, CMCC","contact":"Yaping Zhang","contact-id":85042,"tdoctype":"WID new","for":"Endorsement","abstract":"Justification\nSimultaneous Rx\/Tx capability for inter-band CA, SUL and EN-DC band combinations were introduced from Rel-15. According to the description of the capability, it is conditional mandatory and the condition is described in the field, i.e. indicated in the RAN4 spec which combinations should mandatorily support simultaneous Rx\/Tx. For the combinations which have no such indication, the capability is optional, i.e. for UE supporting simultaneous Rx\/Tx, the capability should be reported, otherwise, the capability is absent or not reported. Since the capability is important for network scheduling, it should be reported accurately. \nRAN4 have introduced Rel-19 work items to further study simultaneous Rx\/Tx issues including:\n1.\tIntroducing the general principle of simultaneous Rx\/Tx capability for inter-band CA, SUL and EN-DC band combinations, and removing the unnecessary Notes for simultaneous Rx-Tx applied to band combinations for NR CA\/DC, NR SUL and LTE\/NR DC.\n2.\tFor band combination CA_n40A-n41A, new MSD requirements are defined when n41 spectrum is restricted to 2515-2675MHz.\n3.\tFor band combination CA_n5A-n8A, the UL CA operation is supported and the MSD requirements are defined based on simultaneous Rx-Tx analysis.\nThe core part of this work item has 100% completed in RAN#110 (2025-12). 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 Simultaneous RxTx band combinations for NR CA\/DC, NR SUL and LTE\/NR DC to reflect the relevant core RF requirements.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":5390,"status":"revised","reservation_date":"2026-01-29 09:36:01","uploaded":"2026-01-30 12:16:32","revisionof":"","revisedto":"R5-261119","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__110_Gothenburg\/Docs\/R5-260539.zip","group":"R5","meeting":"R5-110","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-260671","title":"New WID on UE Conformance Test Aspects - Further RRM enhancement for NR and MR-DC","source":"Apple, Huawei, China Telecom","contact":"Xinrong Wang","contact-id":102059,"tdoctype":"WID new","for":"Endorsement","abstract":"Justification\nRAN4 introduced a Rel-17 work item for NR RRM Further Enhancements for which both the Core and Performance parts have been 100% complete as of RAN#97e (September 2022). The RAN5 Rel-16 NR RRM Enhancements WI is targeted to be finished as of RAN#111 (March 2026). To meet the industry expectations in time, there is a need for RAN5 to start a work item to deliver conformance test cases for NR RRM Further Enhancements.\n4\tObjective\n4.1\tObjective of SI or Core part WI or Testing part WI\nThe objective of this RAN5 WI is to enable UE conformance testing for the Rel-17 RRM further enhancements related requirements for the sub-topics indicated below. RAN5 conformance test procedures will be created to verify test requirements as per the scope being covered in RAN4.\nThe focus will be to specify test requirements for the following:\n(1)\tSRS antenna port switching\no\tSpecify RRM requirement for SRS antenna port switching, e.g.\n-\tInterruption requirement\n-\tPotential impact on other RRM requirements\n(2)\tHO with PSCell\no\tDetermine the scenarios for HO with PSCell for which RRM requirements are to be specified\n-\tfrom NR SA to EN-DC\n-\tfrom EN-DC to EN-DC\n-\tfrom NE-DC to NE-DC\n-\tfrom NR-DC to NR-DC\no\tStudy the UE behavior for HO with PSCell\n-\tExisting requirements for HO and PSCell addition as baseline\n-\tTimeline and interaction between HO and PSCell addition\no\t Specify RRM requirements for HO with PSCell based on agreed UE behavior\n(3)\tPUCCH SCell activation\/deactivation\no\tSpecify SCell Activation Delay Requirement for Deactivated PUCCH SCell (including valid TA and invalid TA)\no\tSpecify SCell Activation Delay Requirement for Deactivated PUCCH SCell with Multiple SCells (including valid TA and invalid TA)\no\tSpecify SCell Deactivation Delay Requirement for Activated PUCCH SCell\no\tSpecify SCell Deactivation Delay Requirement for Activated PUCCH SCell with Multiple SCells.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":6710,"status":"revised","reservation_date":"2026-01-29 18:34:15","uploaded":"2026-01-30 18:45:11","revisionof":"","revisedto":"R5-261120","release":"Rel-17","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__110_Gothenburg\/Docs\/R5-260671.zip","group":"R5","meeting":"R5-110","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-260672","title":"New WID on UE Conformance Test Aspects - Even further RRM enhancement for NR and MR-DC","source":"Apple, China Telecom, Huawei","contact":"Xinrong Wang","contact-id":102059,"tdoctype":"WID new","for":"Endorsement","abstract":"Justification\nRAN4 introduced a Rel-18 work item for NR RRM Even Further Enhancements for which both the Core and Performance parts have been 100% complete as of RAN#104 (June 2024). The RAN5 Rel-16 NR RRM Enhancements WI is targeted to be finished as of RAN#111 (March 2026). To meet the industry expectations in time, there is a need for RAN5 to start a work item to deliver conformance test cases for Even Further NR RRM Enhancements \n4\tObjective\n4.1\tObjective of SI or Core part WI or Testing part WI\nThe objective of this RAN5 WI is to enable UE conformance testing for the Rel-18 RRM enhancements related requirements for the sub-topics indicated below. RAN5 conformance test procedures will be created to verify test requirements as per the scope being covered in RAN4.\nThe focus will be to specify test requirements for the following:\n\u2022\tFR2 SCell activation delay reduction\no\tIdentify cases where FR2 SCell activation delay can be reduced (e.g., unknown target cell cases), and specify reduced delay requirements for such cases, including but not limited to\n?\tStudy and, if feasible, enhance cell detection for unknown SCell and time\/frequency tracking\n?\tStudy and, if feasible, enhance L1-RSRP measurement delay reduction on target SCell\n?\tNote: Subject to RAN4\u2019s agreement, the technical solutions can be extended to other general RRM requirements if applicable.\no\tSpecify if needed, reference signal enhancement and\/or signaling enhancement for the UE to meet the enhanced delay requirements\no\tNote: the technical solutions can be extended to FR1, when applicable\n\u2022\tDefine RRM requirements for FR1-FR1 NR-DC scenarios\no\tRRM requirements include the number of serving carriers, PSCell addition\/release delay requirement, PSCell change and conditional PSCell change delay, scheduling availability, and CSSF. Other Rel-15 requirements are not precluded and are subject to WI stage discussion.\no\tFor R16 and R17 features, RRM requirements for FR1-FR1 NR-DC including HO with PSCell, SCG activation\/deactivation and CPAC.\n?\t Note: no other R16\/17 features are considered","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":6720,"status":"withdrawn","reservation_date":"2026-01-29 18:34:15","uploaded":"2026-01-30 18:45:11","revisionof":"","revisedto":"","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__110_Gothenburg\/Docs\/R5-260672.zip","group":"R5","meeting":"R5-110","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-260859","title":"New WID on UE Conformance - NR mobility enhancements Phase 4 plus SA3 aspects","source":"Apple, China Telecom, Motorola Mobility","contact":"Deepak Sheoran","contact-id":104095,"tdoctype":"WID new","for":"Endorsement","abstract":"Justification\nLayer 1\/Layer 2 Triggered mobility (LTM) was introduced in Rel-18 and could offer improvements in handover latency and interruption time compared to Layer 3 based mobility. However, Rel-18 LTM had several limitations compared to Layer 3 mobility. The Rel-19 core work item aimed to remove a number of these limitations.\nLTM operation is only supported for mobility between cells of the same gNB (same CU). Depending on the network deployment this may significantly limit the opportunities to use LTM. By enabling LTM operation between inter-CU cells, the network will be able to gain the benefits of LTM for a far greater number of handovers.\nL1 measurements for Rel-18 LTM procedures are limited to SSB measurements. Expanding L1 measurements to include CSI-RS can address this limitation and can be expected to enable greater throughput on the target cell immediately after cell switch.\nLayer 3 mobility has evolved over several releases. Conditional handover (CHO) and other conditional mobility procedures (CPAC, SCPAC) were developed to achieve high robustness by enabling the procedure to be executed without necessitating a signalling exchange with source cell beforehand. LTM as introduced in Rel-18 offers short interruption time but not with the same level of robustness as the conditional L3 mobility procedures. In Rel-19 enhancements, Support of conditional Intra-CU LTM was also added to address this limitation.\nThe core part has been completed 100% in RP#109 (Sept 2025) while the Performance part will be completed 100% in RP#111(March 2026). Therefore, it\u2019s a proper time for RAN5 to initiate the corresponding conformance work item to enable this new feature for UE protocol conformance testing.\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 conformance requirements, applicability, and update the relevant conformance specifications for Rel-19 NR mobility enhancements Phase 4 WI, 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":8590,"status":"revised","reservation_date":"2026-01-30 08:37:28","uploaded":"2026-01-31 03:44:16","revisionof":"","revisedto":"R5-261121","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__110_Gothenburg\/Docs\/R5-260859.zip","group":"R5","meeting":"R5-110","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-260860","title":"New WID on UE Conformance - Multi-Access(ATSSS_Ph4)","source":"Apple, China Telecom","contact":"Deepak Sheoran","contact-id":104095,"tdoctype":"WID new","for":"Endorsement","abstract":"Justification\nRel-19 SA2 was working on Multi-Access (MASSS) which covers support for phase 4 of Access Traffic Steering, Switching and Splitting feature (ATSSS_Ph4). The ATSSS_Ph4, involves specifying how the MPQUIC steering functionality defined in Rel-18 as part of phase 3 of Access Traffic Steering, Switching and Splitting feature (ATSSS_Ph3) is extended to be able to steer, switch, and split the IP traffic and the Ethernet traffic. Furthermore, a new SA2 work item (MASSS) \"Multi-Access (ATSSS_Ph4)\" was approved at SA#104.\nConsidering the above, impacts on protocols and interfaces under CT WGs' responsibilities were foreseen. The CT WGs needed to carry out stage-3 work in Rel-19 to satisfy the normative requirements arising out of stage-2 work.\nThe completion level of the core part of Rel-19 MASSS work item in CT WGs\u2019 achieved 100% in June 2025, and the Rel-18 ATSSS phase 3 related testing specifications will be completed in March 2026. It is therefore appropriate for 3GPP RAN5 to introduce a corresponding conformance work item to enable UE protocol conformance testing for the Rel-19 MASSS feature.\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 UE protocol conformance requirements, applicability, test environment for the Rel-19 MASSS feature which introduced new steering modes and MPQUIC functionalities.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":8600,"status":"revised","reservation_date":"2026-01-30 08:39:13","uploaded":"2026-01-31 03:44:16","revisionof":"","revisedto":"R5-261122","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__110_Gothenburg\/Docs\/R5-260860.zip","group":"R5","meeting":"R5-110","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-260953","title":"New WID on UE Conformance - Protocol enhancements for Mission Critical Services (MCPTT, MCVideo, MCData) for Rel-18","source":"Ericsson, FirstNet, AT&T, Element, Samsung","contact":"Calle Hagenfeldt","contact-id":38975,"tdoctype":"WID new","for":"Endorsement","abstract":"Justification\nThe demand and need for Mission Critical Services (MCS) on 3GPP-compliant networks is growing. As a result, the need to enhance MCS functionality is also growing. 3GPP has answered this demand with enhancements to core specifications for MCS. MCS includes Mission Critical Push To Talk (MCPTT), Mission Critical Video (MCVideo), and Mission Critical Data (MCData). RAN5 has completed the UE conformance tests for MCS for Release 17. RAN5 needs to address developing test specifications that relate to Release 18 MCPTT, MCVideo and MCData requirements for both LTE and 5G.\n4\tObjective\nThe objective of this work item is to provide UE conformance test specifications for the Rel-18 core requirements for MCPTT, MCVideo and MCData, including:\n\u2022\tProtocol enhancements for Mission Critical Services\n\u2022\tCT aspects of Enhanced Mission Critical Push-to-talk architecture phase 4\n\u2022\tCT aspects of Gateway UE function for Mission Critical Communication","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":9530,"status":"withdrawn","reservation_date":"2026-01-30 12:59:31","uploaded":"2026-01-30 15:09:23","revisionof":"","revisedto":"","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__110_Gothenburg\/Docs\/R5-260953.zip","group":"R5","meeting":"R5-110","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-260954","title":"New WID on UE Conformance - Mission Critical ad hoc group communications and MCS system interconnection and migration","source":"Ericsson, FirstNet, AT&T, Element, Samsung","contact":"Calle Hagenfeldt","contact-id":38975,"tdoctype":"WID new","for":"Endorsement","abstract":"Justification\nMany public safety organizations and Railway organizations have expressed interest in having a support for Ad hoc group communication feature. Ad hoc group communication enables authorized users to combine a random set of MCX Service Users into a group and enable communication. Ad hoc group is used for single communication and it does not persist when the communication is terminated. This non-persistent characteristic of an ad hoc group makes it different from the existing user regroup functionality.\nIn addition, interconnection and migration between mission critical systems are necessary to provide inter-system communication for purposes such as operational support and mutual aid between mission critical systems in different security domains operated by different mission critical organizations.\nThe stage 3 work for this functionality is completed in the core groups in Release 18. Therefore, it is appropriate for RAN5 to initiate a corresponding work item to enable UE protocol conformance testing of ad hoc group communication and interconnection and migration between mission critical systems, for all mission critical services.\n4\tObjective\nThe objective of this work item is to define the corresponding UE protocol conformance requirements, applicability, test environment for Rel-18 Mission Critical ad hoc group communications and interconnection and migration between mission critical systems for all mission critical services (MCPTT, MCVideo and MCData).","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":9540,"status":"withdrawn","reservation_date":"2026-01-30 12:59:31","uploaded":"2026-01-30 15:09:23","revisionof":"","revisedto":"","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__110_Gothenburg\/Docs\/R5-260954.zip","group":"R5","meeting":"R5-110","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-260955","title":"New WID on UE Conformance - Mission Critical Services over 5MBS","source":"Ericsson, FirstNet, AT&T, Element, Samsung","contact":"Calle Hagenfeldt","contact-id":38975,"tdoctype":"WID new","for":"Endorsement","abstract":"Justification\n3PP has developed the 5G System (5GS) specifications, beginning in Release 15. Further specification work has been done in Release 16 and Release 17. In order to make MC Services available over 5GS, Stage 2 has organised the corresponding normative work as follows:\n-\tFocus area 1: On-network - unicast communication for Mission Critical Services;\n-\tFocus area 2: On-network \u2013 multicast and broadcast communications for Mission Critical Services;\n-\tFocus area 3: Off-network communication and On-network communication of Mission Critical Services (encompassing UE-to-network relay support);\nNormative work for focus area 1 was completed in WI Mission Critical Services over 5GS both in stage-2 and stage-3 in Release 17. Normative work for focus area 2 is also completed, in Release 18. The Rel-18 \u201cCT1 aspects of Mission Critical Services over 5MBS\u201d stage-3 core Work Item was completed in CT#102 (Dec 23) so RAN5 can initiate a corresponding work item to enable UE protocol conformance testing of Mission Critical Services over 5MBS for all mission critical services.\n4\tObjective\nThe objective of this work item is to define the corresponding UE protocol conformance requirements, applicability, test environment for Rel-18 on-network multicast and broadcast transport capabilities for Mission Critical Services over 5GS for all mission critical services (MCPTT, MCVideo and MCData).","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":9550,"status":"revised","reservation_date":"2026-01-30 12:59:31","uploaded":"2026-01-30 15:09:23","revisionof":"","revisedto":"R5-261125","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__110_Gothenburg\/Docs\/R5-260955.zip","group":"R5","meeting":"R5-110","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-261072","title":"New WID on UE Conformance - Low NR band carrier aggregation via switching","source":"Apple, Telus, CATT","contact":"Ashwin Mohan","contact-id":102945,"tdoctype":"WID new","for":"Endorsement","abstract":"Justification\nOperator interest for aggregating low band spectrum has always been high during the entire history of the carrier aggregation feature, spanning LTE and NR specifications.  Considering the practicalities of handset RF front end architectures available in the market today, the operators have requested 3GPP to consider specifying a solution based on a switching scheme which can potentially accommodate the related limitations.\n3GPP TSG RAN WG4 has created Rel-19 work item to enable the following solution:\n-\tDevice needs to support switching: when the SCell operation is triggered, UE needs to switch to the SCell, and during the operation period there is no simultaneous Tx\/Rx between the PCell and the SCell\n-\tDevice switches back to the PCell after the SCell operation is finished\nRequirements for above aspects are introduced under the RAN4 WI for which the core part has been 100% completed and the Performance part has been 50% completed at RAN#110 (December 2025). It is therefore appropriate 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 this work item is to define the conformance testing aspects for the Rel-19 NR Low band carrier aggregation via switching requirements including RF, RRM and Protocol areas. The below aspects or requirement will be covered in the newly added conformance test cases:\n-\tSpecify UE conformance test requirements that cover switching between case 1 and case 2 below. This incorporates any defined switching gaps and corresponding physical layer procedures as well as switching delay and time mask for carrier switching.\n-\tCase 1: Tx\/Rx on FDD carrier 1 and no Rx on SDL carrier 2\n-\tCase 2: Rx on SDL carrier 2 and no Tx\/Rx on FDD carrier 1\n-\tThe test requirements added within this WI cover the following band combinations, as defined in the core specifications: CA_n5A-n29A, CA_n12A-n29A, CA_n14A-n29A, CA_n28A-n67A, CA_n29A-n71A, with additional band combinations to be handled as per core specification updates.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":10720,"status":"revised","reservation_date":"2026-01-30 21:32:04","uploaded":"2026-01-31 08:38:56","revisionof":"","revisedto":"R5-261126","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__110_Gothenburg\/Docs\/R5-261072.zip","group":"R5","meeting":"R5-110","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]