[{"name":"R5-260861","title":"Real Time Text implementation in 3GPP test specifications","source":"Apple Solutions","contact":"Deepak Sheoran","contact-id":104095,"tdoctype":"discussion","for":"Endorsement","abstract":"There are serveral Real Time Text(RTT) related test cases in [1] and [2]. During internal validation, we observed inconsistencies between current prose and their actual field deployment. \nCurrent RTT implementation has some limitations that result in undesirable signaling overhead and a suboptimal user experience for individuals relying on RTT as an accessibility feature. \nTo mitigate these inconsistencies, the following observations and proposals seek removal of mendatory QoS precondiotions for text media, introduction of new (PICS) to enable more flexible and user-centric control over RTT behavior during active calls.\nSimilar disscussion happened during CAG#85[6].\n2\tDiscussion\nObservation2.1\nFor all the normal MO\/MT call test cases involving RTT upgrade, there is a requirement for UE to support preconditions while upgrading the call to RTT. The strength tag is set to \u2018mandatory\u2019 for preconditions attributes related to QoS for text media.\nRTT has been commercially deployed in North America for years and is and is recently enabled in most EU countries (driven by the European Accessibility Act June 2025 mandate [3]), these mandatory preconditions are not enforced in any of these operational markets. \nNG.114\/IR.92 also mandate network to initiate dedicated QoS bearer for text media. It is not at the discretion of the UE.\nImpacted test cases:\n\u2022\tTS34.229-1, Test cases 17.19 & 17.20\n\u2022\tTS34.229-5, Test case 7.35\nProposal 2-1:\nTo match the functionality currently deployed in networks, it is proposed that the QoS \u2018Attributes for preconditions\u2019 realted to media=text be removed.\n\nObservation2.2\nThere are some emergency call test cases which require a user-initiated upgrade to add RTT via the MMI after an emergency call has been established.This induce extra signaling flow when user is already on an active emergency call.\nThis process introduces additional signaling overhead, which is undesirable in critical emergency scenarios where time is critical and RTT users need immediate, seamless call initiation. Therefore, it is proposed that the ability to add or remove RTT on an active emergency call should be an optional feature, controlled via PICS.\nImpacted test cases:\n\u2022\tTS34.229-1, Test case 19.1.8\n\u2022\tTS34.229-5, Test case 10.17\nProposal 2-2:\nIt is proposed to introduce a new PICS to define the applicability of adding and removing RTT during an emergency call.\n\nObservation2.3\nCurrent prose for MO calls assume the MTSI client supporting real-time text must offer a method to remove RTT once added to the call, however no such requirement exists in 26.114. \nProper handling of text removal or RTT downgrade by a remote party can be validated in the existing MT call RTT tests. \nAs no requirement exists to implement downgrade or removal of RTT within a session, this step should be removed or made optional based on the capability of the MTSI client.\nImpacted test cases:\n\u2022\tTS34.229-1, Test case 17.19\n\u2022\tTS34.229-5, Test case 7.35 &7.36\nProposal 2-3:\nIt is proposed to introduce a new PICS to define the applicability of removing RTT during a MO call.","secretary_remarks":"","agenda_item_sort_order":1268,"ainumber":"6.6.6.6","ainame":"Discussion Papers, Work Plan, TC lists","tdoc_agenda_sort_order":8610,"status":"revised","reservation_date":"2026-01-30 08:41:57","uploaded":"2026-01-31 03:32:51","revisionof":"","revisedto":"R5-261230","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-260861.zip","group":"R5","meeting":"R5-110","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-260963","title":"Discussion on Adding Further 5G RTT Test Cases","source":"Vodafone GmbH","contact":"Petra Rauer","contact-id":16070,"tdoctype":"discussion","for":"Endorsement","abstract":"The Real-Time Text (RTT)\u2013related test cases for 5G, as defined in [1], do not provide alignment with the existing 4G RTT test cases described in [2]. This gap may lead to incomplete coverage as networks evolve toward 5G-only deployments.\n2\tDiscussion\nObservation 2.1\nReference [1] currently does not define any Mobile-Terminated (MT) RTT test cases for 5G. As future UE implementations are expected to support 5G-only operation without fallback to 4G, the absence of MT test cases would result in missing conformance coverage for such devices.\nProposal 2-1\nIt is proposed to introduce MT related RTT test cases in alignment with the existing 4G approach, ensuring continuity, completeness, and forward compatibility for 5G only UEs","secretary_remarks":"","agenda_item_sort_order":1268,"ainumber":"6.6.6.6","ainame":"Discussion Papers, Work Plan, TC lists","tdoc_agenda_sort_order":9630,"status":"revised","reservation_date":"2026-01-30 13:06:40","uploaded":"2026-01-30 19:47:35","revisionof":"","revisedto":"R5-261163","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-260963.zip","group":"R5","meeting":"R5-110","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-261163","title":"Discussion on Adding Further 5G RTT Test Cases","source":"Vodafone GmbH","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":1268,"ainumber":"6.6.6.6","ainame":"Discussion Papers, Work Plan, TC lists","tdoc_agenda_sort_order":9631,"status":"noted","reservation_date":"2026-02-18 19:21:53","uploaded":"2026-02-18 19:31:04","revisionof":"R5-260963","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-261163.zip","group":"R5","meeting":"R5-110","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-261230","title":"Real Time Text implementation in 3GPP test specifications","source":"Apple Solutions","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":1268,"ainumber":"6.6.6.6","ainame":"Discussion Papers, Work Plan, TC lists","tdoc_agenda_sort_order":8611,"status":"noted","reservation_date":"2026-02-18 19:22:42","uploaded":"2026-02-18 19:31:13","revisionof":"R5-260861","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-261230.zip","group":"R5","meeting":"R5-110","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]