[{"name":"R5-260261","title":"RAN5 PRD12 version 6.13","source":"MCC TF160","contact":"Olivier Genoud","contact-id":58316,"tdoctype":"other","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":20,"ainumber":"4.5.4","ainame":"Other open issues from joint sessions - original A.I. retained","tdoc_agenda_sort_order":2610,"status":"approved","reservation_date":"2026-01-27 07:55:59","uploaded":"2026-01-29 18:06:25","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__110_Gothenburg\/Docs\/R5-260261.zip","group":"R5","meeting":"R5-110","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-260483","title":"Discussion of A-IoT Device Conformance Testing","source":"CMCC, Huawei, Keysight, China Unicom","contact":"Dan Song","contact-id":86282,"tdoctype":"discussion","for":"Endorsement","abstract":"AI 5.3.38.5, 4.2.1\nThe Conformance test WI of Rel-19 A-IoT was approved in RAN#110 meeting. The scope consists of conformance testing of core requirements for A-IoT device from RAN(RAN1, RAN2, RAN4), CT1 and SA3 WGs.\nAfter RAN#110@Dec 2025, a few issues were identified for this WI, including expected new specification, RF and SIG parts. \nWP for this WI needs to be endorsed for facilitating the WI progress.\nThis document will discuss the identified issues above.\n\nIssue 1: Whether to keep a New external TR for MU\/TT\/TPs Analysis \nObservation 1: There are 2 solutions to fix the issue 1\nSolution 1.1: To add MU\/TT\/TPs for A-IoT test cases into existing NR TR 38.903\/38.905, and to remove \u201cNew external TR\u201d from the revised WID.\nSolution 1.2: To keep a New external TR for MU\/TT\/TPs for A-IoT test cases as it is in the revised WID, and the MU\/TT\/TPs for all the A-IoT related test cases to be covered in the New external TR. \nProposal 1: To endorse Solution 1.2. Considering both \u201cUE\u201d and \u201cdevice\u201d will be involved in Rel-20 A-IoT, and the \u201cUE\u201d in the title of NR TR 38.903 might be misunderstood as only MU\/TT\/TPs for \u201cUE\u201d being covered in the TR. An individual TR is needed to cover the MU\/TT\/TPs for all the A-IoT related test cases, including both \u201cUE\u201d and \u201cdevice\u201d. \n\nIssue 2: OTA Anechoic chamber method  \nTest antenna with two linear orthogonal polarizations supports both CW and Reader, namely CW and Reader share the same antenna with CW and Reader using both polarizations\u201d (See cl. 8.4.1 in TS 38.191)\nObservation 2: The statement of cl. 8.4.1 in TS 38.191 will require further clarifications\nNot clear whether CW and reader will be:\nin orthogonal polarizations\nSimultaneously in time\nNot clear whether CW in the same direction is the most common case in actual deployment (it could be the worst case for the reader but not for the device). RAN5 needs to find the worst case for device but not the reader since reader conformance testing is out of RAN5 scope.\nProposal 2: To seek clarification on the issue above from RAN4 by sending LS to RAN4. \n\nIssue 3: SIG part - D2R transmission  \nIssue 3: SIG part - R2D transmission  \nIssue 3: SIG part - Security procedure  \nIssue 3: SIG part - Procedures not controllable  \nProposal 3: RAN5 to discuss the potential solutions to the SIG issues list in the table above and list them as Action Points for monitoring.\nProposal 4: RAN5 to endorse the pre-RAN5#110 WP in R5-260506 at RAN5#110 for Rel-19 A-IoT conformance testing WI, including RF, RRM and SIG parts.","secretary_remarks":"","agenda_item_sort_order":20,"ainumber":"4.5.4","ainame":"Other open issues from joint sessions - original A.I. retained","tdoc_agenda_sort_order":4830,"status":"noted","reservation_date":"2026-01-29 03:36:41","uploaded":"2026-01-30 11:11:44","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"Ambient_IoT_Solutions_plus_CT1_SA3-ConTest"}],"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-260483.zip","group":"R5","meeting":"R5-110","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-260502","title":"Way forward on how to handle Option4 (NE-DC) test cases","source":"CMCC","contact":"Dan Song","contact-id":86282,"tdoctype":"discussion","for":"Endorsement","abstract":"Observation: RAN5 kicked off the work of Option4 (NE-DC) at RAN5#92e. As of now, 23 out of 30 FR1 Option4 test cases are completed. NE-DC deployment plan was stopped due to lack of enough industry interests\/support, and further test development work in RAN5 is put on hold now.\nThe unspecified NE-DC test cases numbers are still reserved in TS 38.523-1 Tracker spreadsheet.\nAt TF160, the unspecified NE-DC test cases are still in the test case TTCN status list.\nAt every TSG RAN Plenary, the following statement is still in the RAN5 status report: \u201con hold\u201d\nProposal: RAN5 to stop NE-DC conformance test development and close Rel-15 NE-DC WP at RAN5#110.","secretary_remarks":"","agenda_item_sort_order":20,"ainumber":"4.5.4","ainame":"Other open issues from joint sessions - original A.I. retained","tdoc_agenda_sort_order":5020,"status":"noted","reservation_date":"2026-01-29 03:36:47","uploaded":"2026-01-30 08:42:04","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__110_Gothenburg\/Docs\/R5-260502.zip","group":"R5","meeting":"R5-110","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-260642","title":"Discussion on Modernization of RRM specification converted using Markdown","source":"Nokia, Ericsson, China Telecom","contact":"Siddharth Das","contact-id":99463,"tdoctype":"discussion","for":"Discussion","abstract":"For four generations, 3GPP specifications have been developed using Microsoft Word, guidelines outlined in TR 21.801 to maintain a consistent format across working groups. Microsoft Word does offer valuable features such as WYSIWYG (What You See Is What You Get) editing and highly functional change tracking, which is an integral part of the Change Request (CR) process, clearly identifying the parts in each CR that are approved to change the specifications according to 3GPP decisions.\nHowever, several limitations have become increasingly apparent with the docx file format, raising the question of whether this remains the best tool for the job after four generations of use. Due to this, TSG has approved the study in [1] on new proposals and evaluation of the new formats.\nAlso, In RAN5#109, the following way forward was agreed and shared on the reflector (3GPP_TSG_RAN_WG5_6G_SPEC_MODERN@LIST.ETSI.ORG) for 6G spec modernization & RAN5 aspects:\n...\nWe plan to address the first two points, which are explained in detail in the following sections:\n\u2022\tCreate RAN5 dedicated playground on the 3GPP Forge focusing on .md format\n\u2022\tCreate a complete representative test case\nIn this document, we summarize the how Pandoc variant of Markdown can be used to address the pain points highlighted in section 4.2 of [2] from the RAN5 perspective. To support elements which are specific to 3GPP, some extensions to Markdown have been prototyped. These extensions are written in a language called Lua (https:\/\/www.lua.org\/), for which an interpreter is built directly into Pandoc, the tool used to convert from Markdown to HTML.\n We also provide a preview of specifications converted from Markdown to HTML and PDF hosted online in section 3.\nObservation 1: Microsoft Word suffers from significant performance degradation when handling multiple specifications, leading to navigational delays and other shortcomings highlighted in clause 4.2 of [2].\nObservation 2: Markdown supports equations, complex tables, and precise indentation that meet official specification requirements. This makes it a key format for 3GPP specifications.\nProposal 1: Companies shall conduct trials and feasibility studies by contributing to existing test cases using Markdown and Git.\nProposal 2: Companies to demonstrate that the complexities of RAN5 specifications can be achieved using their suggested preferred formats.","secretary_remarks":"","agenda_item_sort_order":20,"ainumber":"4.5.4","ainame":"Other open issues from joint sessions - original A.I. retained","tdoc_agenda_sort_order":6420,"status":"revised","reservation_date":"2026-01-29 14:36:15","uploaded":"2026-01-30 09:23:22","revisionof":"","revisedto":"R5-261169","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-260642.zip","group":"R5","meeting":"R5-110","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-260970","title":"Modernization of Specification Format and Procedures for 6G - Status Update","source":"Ericsson","contact":"Kuba Kolodziej","contact-id":76956,"tdoctype":"discussion","for":"Information","abstract":"Discussion paper on the topic of future of the specification handling in 3GPP.\nDuring TSG#108 meetings, a new Study Item (SI) was approved for \u201cModernization of Specification Format and Procedures for 6G\u201d, along with an agreed Way of Working. The SI has the following objectives:\n\u2022\tObjective 1: Assessment of existing specification formats and working methods, and requirements for any improvements.\no\tAdvantages of current tools\no\tShortcomings, pain-points, and potential benefits\no\tRequirements Identification\n\u2022\tObjective 2+3: (After TSG#109): Taking into account the outcome of objective 1, consider new formats, including but not necessarily limited to plain text format such as Markdown or LaTeX, or another format; consider use of Git and ETSI FORGE database to store specifications and manage version control. Other alternatives are not precluded.\n2\t6GSM progress\nAn extension of six months beyond TSG #111 (March 2026) is currently proposed, with a clear preference from many companies for an extension rather than concluding in March 2026. A 6-month extension was considered more reasonable than a 3-month one, given PCG timing. ..\n2.2\tStatus after Conference Call #5\nFor Objective 2, the formats under consideration include:\n\u2022\tOpenDocument\n\u2022\tAsciiDoc\n\u2022\tMarkdown\n\u2022\tMultiple formats for a single specification with Markdown as baseline\n\u2022\tLaTeX\n\u2022\tDOCX with restrictions\n\u2022\tMultiple formats for a single specification with Word as baseline\nFor Objective 3, discussions focused on modernizing 3GPP workflows for CRs, TSs, and TRs. Topics included the use of version control via 3GPP Forge (self-hosted GitLab), concepts such as protected branches, CR handling approaches inspired by OneM2M and GitFlow-like workflows, and options for improving publication and transparency. These discussions explored how such workflows could enable more structured, secure, and traceable handling of CRs, including support for parallel edits, controlled approvals, frozen release corrections, and increased automation in specification publication.\n...\n3 RAN5 Considerations and Next Steps\n.. Many proposals for 6G documentation now include the use of GIT\/forge platforms, either partially or for all documentation (multiformat approaches). It is therefore essential to assess new procedures required for managing documentation on the forge server. Within RAN5, there is already an initiative under the 5G documentation context to implement storage of .JSON tables on the forge server. ..\nThe following list was is the outcome of the discussion held at the RAN5#109 meeting and outlines key points for further investigation by RAN5, specifically regarding Objectives 2 and 3 of the 6G SM Study:\n\u2022\tEstablish a RAN5-dedicated playground on the 3GPP Forge, with a focus on .md format usage\n\u2022\tDevelop a comprehensive representative test case\n\u2022\tAddress management of large RF tables within the current RAN5 repository\n\u2022\tExplore the handling of substantial tables with call flow for signalling test cases, represented in .md format\n\u2022\tConsider cross-referencing functions, which\u2014although applicable to all groups\u2014are especially prominent in RAN5 specifications\n\u2022\tInvestigate machine-readable applicability specifications, including export functionality to CSV\n\u2022\tExamine PRD21 aspects","secretary_remarks":"","agenda_item_sort_order":20,"ainumber":"4.5.4","ainame":"Other open issues from joint sessions - original A.I. retained","tdoc_agenda_sort_order":9700,"status":"noted","reservation_date":"2026-01-30 14:39:28","uploaded":"2026-01-30 15:57:28","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__110_Gothenburg\/Docs\/R5-260970.zip","group":"R5","meeting":"R5-110","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-261103","title":"discussion on FR2-NTN requirements","source":"QUALCOMM JAPAN LLC.","contact":"Vijay Balasubramanian","contact-id":84569,"tdoctype":"discussion","for":"Endorsement","abstract":"The Rel18 NR NTN Enhancements plusCT1 aspects conformance work item (NR_NTN_enh_plus_CT-UEConTest) was introduced to define the test case to verify both FR1-NTN and FR2-NTN requirements. For verifying the FR2-NTN performance requirements, the testability of VSAT NTN UEs at frequency above 10 GHz is still open in RAN4. \nThis paper discusses the wayforward to proceed with the Rel18 NR-NTN enhancements WI NR_NTN_enh_plus_CT-UEConTest.\n2.\tDiscussion\nAs per the latest Rel18 NR-NTN Enhancements work plan [2], majority of the FR1-NTN test cases are completed. The Remaining FR1-NTN test cases are expected to be completed by the end of this meeting. The WP also defines FR2-NTN test cases spanning RF, Demod, RRM and Protocol areas. Protocol test cases have already been defined in the RAN5 spec since there is no issue with testability of the FR2-NTN VSAT devices.\nBut for RF, Demod and RRM performance areas, resolving the VSAT testability is critical before defining the test environment, test procedure for FR-NTN requirements. The WID already has a note highlighting the pending discussions on the testability of VSAT NTN UEs at frequencies above 10GHz.\nAfter several discussions at the plenary meeting, a Rel 20 WI was introduced in RAN4 to discuss the testability aspects of FR2-NTN VSAT UE 60cm x 60cm. The testability of FR2-NTN VSAT UE is part of the core part work item scope whose projected completion is March 2027.\nThere is atleast 1 year until RAN4 concludes on the testability and for RAN5 to start working on the MU analysis. \nAdditionally industry interest for FR2-NTN VSAT 60cm x 60cm UE is not clear.\nIn our view, RAN5 has few options\nOption1: Given the lack of clarity on the industry interest for FR2-NTN VSAT 60cm x 60cm UE and the one year time gap until RAN4 concludes on the testability, RAN5 closes the WI removing the pending FR2-NTN aspects from the objective.\nOption2: Keep the RAN5 WI open and continue adding the test case structure, environment, test procedure for the FR2-NTN test cases and wait for RAN4 core part to be completed before working on the MU\/TT analysis, pending industry interest.\n3.\tConclusion\nProposal1: Go with option1","secretary_remarks":"","agenda_item_sort_order":20,"ainumber":"4.5.4","ainame":"Other open issues from joint sessions - original A.I. retained","tdoc_agenda_sort_order":11030,"status":"noted","reservation_date":"2026-01-30 21:59:25","uploaded":"2026-02-12 16:11:08","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"NR_NTN_enh_plus_CT-UEConTest"}],"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-261103.zip","group":"R5","meeting":"R5-110","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-261169","title":"Discussion on Modernization of RRM specification converted using Markdown","source":"Nokia, Ericsson, China Telecom","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":20,"ainumber":"4.5.4","ainame":"Other open issues from joint sessions - original A.I. retained","tdoc_agenda_sort_order":6421,"status":"noted","reservation_date":"2026-02-18 19:21:56","uploaded":"2026-02-18 19:31:04","revisionof":"R5-260642","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__110_Gothenburg\/Docs\/R5-261169.zip","group":"R5","meeting":"R5-110","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]