Description
Global Text Telephony (GTT) is a standardized service within the 3GPP framework designed to support real-time text (RTT) communication as an integral part of conversational multimedia services, such as IP Multimedia Subsystem (IMS)-based telephony. It operates by establishing a text media stream alongside or instead of a voice media stream within a session, allowing characters to be transmitted as they are typed, providing an immediate, conversational experience. The architecture leverages the existing IMS core and Packet-Switched (PS) bearers, with specific application servers and user equipment (UE) capabilities to negotiate, establish, and manage the text session. Key functional components include the GTT Application Server (GTT AS) within the IMS domain, which handles service logic, and the UE, which must support the necessary codecs and session control protocols like SIP and RTP for text transport.
Technically, GTT sessions are established using SIP INVITE methods with Session Description Protocol (SDP) offers that indicate support for text media lines, typically using codecs like the ITU-T T.140 text protocol encapsulated in RTP. The network ensures Quality of Service (QoS) for the text stream, often assigning it a dedicated bearer with appropriate QoS Class Identifier (QCI) values to guarantee low latency and reliable delivery, which is critical for real-time interaction. Interworking with legacy text telephony systems, such as Text over IP (ToIP) or traditional teletypewriter (TTY) services over circuit-switched networks, is a crucial aspect, managed via interworking functions (IWFs) that translate between different text transport formats and signaling protocols.
GTT's role in the network extends beyond basic accessibility; it is part of the Conversational Services enabler, ensuring that text is a first-class media type in multimedia telephony. This integration allows for combined voice and text sessions, where users can switch between or use both modalities simultaneously. The service is defined across multiple 3GPP specifications covering service requirements (22-series), architecture (23-series), codecs (26-series), and signaling (29-series), ensuring interoperability across different vendors and network deployments. Its implementation is mandatory for certain regulatory accessibility requirements in various regions, making it a critical component for network operators to achieve compliance and provide inclusive communication services.
Purpose & Motivation
GTT was created to address the need for standardized, real-time text communication within 3GPP networks, primarily to serve users with disabilities, such as those who are deaf, hard of hearing, or speech-impaired. Prior to its introduction, text communication in mobile networks was largely limited to non-real-time SMS or proprietary implementations of text telephony, which lacked interoperability and seamless integration with voice services. The motivation stemmed from regulatory pressures, like the US Twenty-First Century Communications and Video Accessibility Act (CVAA) and European accessibility directives, which mandated telecommunications services to be accessible to all users.
Historically, text telephony existed in the form of TTY devices over analog phone lines, but the transition to digital and packet-switched networks like GSM and UMTS created compatibility challenges. Early 3GPP releases had limited text support, often requiring fallback to circuit-switched data modes. GTT, introduced in Release 4 as part of the IMS evolution, provided a native IP-based solution that integrates text as a core media type within the conversational multimedia domain. This solved the limitations of fragmented, non-standardized approaches by defining a uniform architecture, signaling, and codec specifications, enabling real-time text to be delivered with the same reliability and quality expectations as voice.
The technology solves the problem of inclusive communication by ensuring text is not an afterthought but a fundamental service component. It allows network operators to deploy a single, future-proof system that supports both voice and text seamlessly, reducing complexity and cost compared to maintaining separate accessibility solutions. Furthermore, GTT facilitates emergency service access (e.g., text-to-911) and enhances communication in noisy environments, benefiting a broader user base beyond those with disabilities, thereby aligning with 3GPP's goal of universal service provision.
Key Features
- Real-time character-by-character transmission during conversational sessions
- Integration with IMS-based multimedia telephony (MMTel) architecture
- Support for simultaneous voice and text media streams within a single session
- Interworking with legacy TTY and circuit-switched text telephony systems
- Standardized use of ITU-T T.140 text protocol over RTP transport
- QoS management for low-latency text delivery via dedicated bearers
Evolution Across Releases
Introduced GTT as part of the initial IMS framework, defining the basic service requirements and architecture for real-time text in conversational services. It specified the use of T.140 codec over RTP and initial interworking considerations with existing text telephony.
Enhanced GTT integration with IMS Phase 2, improving SIP signaling procedures and support for combined voice and text sessions. Added clarifications on QoS handling for text streams within the PS domain.
Introduced further refinements to interworking functions (IWFs) for compatibility with legacy systems. Updated codec specifications and expanded service requirements for broader accessibility scenarios.
Focused on optimization of text transport efficiency and latency improvements. Enhanced support for emergency services text sessions, aligning with regulatory requirements for text-to-911 capabilities.
Integrated GTT more tightly with the Evolved Packet System (EPS) for LTE networks, ensuring text service continuity during mobility. Updated bearer management for text QoS in the E-UTRAN context.
Introduced the GTT Feature Environment (GTTFE) concept to better define network components. Enhanced security features for text sessions, including encryption and integrity protection where applicable.
Introduced support for GTT in 5G NR standalone deployments, with optimizations for ultra-reliable low-latency communication (URLLC) scenarios. Enhanced interworking with next-generation emergency services.
Continued refinements for GTT in 6G study items, focusing on holographic text communication and advanced human-machine interfaces. Enhanced security protocols for quantum-resistant text encryption.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 22.226 | 3GPP TS 22.226 |
| TS 23.066 | 3GPP TS 23.066 |
| TS 23.226 | 3GPP TS 23.226 |
| TS 23.334 | 3GPP TS 23.334 |
| TS 23.701 | 3GPP TS 23.701 |
| TS 26.110 | 3GPP TS 26.110 |
| TS 29.334 | 3GPP TS 29.334 |
| TS 32.102 | 3GPP TR 32.102 |
| TS 32.140 | 3GPP TR 32.140 |
| TS 32.141 | 3GPP TR 32.141 |