Description
Terminating Identification presentation Restriction (TIR) is a supplementary service defined by 3GPP that enables the calling party to prevent the presentation of their identity to the called (terminating) user. It is the counterpart to Terminating Identification Presentation (TIP) and is part of the Calling Line Identification Restriction (CLIR) family of services. TIR is specified in numerous 3GPP technical specifications, including 22.173 (IMS Multimedia Telephony), 24.604 (Communication Diversion), and 24.615 (Communication Waiting). The service operates in both circuit-switched (CS) and IP Multimedia Subsystem (IMS) networks, providing a mechanism for users to maintain privacy when making calls.
In IMS, TIR is implemented through the use of SIP headers and parameters. When a calling party invokes TIR, the originating network sets the presentation indicator in the SIP INVITE request to "restricted" or omits the calling party's identity from the P-Asserted-Identity header. The terminating network, upon receiving the request, checks the presentation indicator and, if restricted, does not present the calling party's identity to the called user. Instead, the called user may see an anonymous indication or no identity information at all. The service is controlled by the calling party's subscription profile, which is stored in the Home Subscriber Server (HSS) and enforced by the Serving-Call Session Control Function (S-CSCF).
TIR can be invoked on a per-call basis or as a permanent subscription setting. The calling party can activate TIR by dialing a specific prefix (e.g., *67 in many networks) or by configuring their user equipment (UE) to always restrict identity presentation. The network then applies the restriction according to the user's preferences and any overriding network policies. For example, emergency calls may override TIR to ensure that the emergency services receive the calling party's identity, as required by regulations in many countries.
The service interacts closely with TIP. When TIR is invoked, the terminating network receives a restricted identity, and TIP will not display the actual calling party's information. However, the terminating network may still receive the calling party's identity for billing or lawful interception purposes, but it is not presented to the user. TIR also works in conjunction with Originating Identification Restriction (OIR), which restricts the presentation of the calling party's identity to the called party in the originating network. Together, these services provide a comprehensive privacy framework.
TIR is standardized across multiple 3GPP releases, ensuring interoperability between different vendors and networks. The specifications 22.173 and 24.604 provide the core requirements and procedures for TIR, while other specs like 24.615 and 24.629 address specific scenarios. The service is essential for users who wish to keep their phone numbers private, such as celebrities, public figures, or individuals concerned about privacy. It also supports regulatory requirements for privacy in many jurisdictions. Overall, TIR is a critical supplementary service that balances the need for caller identification with the user's right to privacy.
Purpose & Motivation
TIR was created to address the privacy concerns of calling parties who do not want their identity revealed to the called party. Before TIR, the calling party's number was always presented to the terminating user, which could lead to unwanted return calls, harassment, or loss of privacy. TIR provides a mechanism for users to control the presentation of their identity, giving them the ability to make calls anonymously when desired. This is particularly important for individuals who need to protect their personal information, such as victims of harassment or public figures.
Historically, TIR evolved from the Calling Line Identification Restriction (CLIR) service in traditional circuit-switched networks. As networks migrated to IMS and VoIP, TIR was adapted to work with SIP-based signaling, ensuring continuity of service across different access technologies. The service also had to accommodate regulatory requirements, such as the need to present the calling party's identity to emergency services even when TIR is invoked. This led to the development of override mechanisms that allow authorized entities to bypass TIR under specific circumstances.
One of the key motivations for TIR was to provide users with a sense of control over their personal information. By allowing users to restrict identity presentation, TIR helps build trust in telecommunication services and encourages users to make calls without fear of their number being misused. Additionally, TIR supports compliance with privacy laws and regulations, such as the General Data Protection Regulation (GDPR) in the European Union, which mandates the protection of personal data. TIR is therefore not only a technical feature but also a legal and ethical necessity in modern telecommunications.
What changed in its specifications
The latest release-to-release comparison of specifications that define TIR. Each summary describes the whole specification, not only this term.
Rel-19 brings only minor changes to TS 22.173: 1 clause changed, with no change attributed to a release feature.
Full comparison in TS 22.173 →Rel-17 restricts ongoing MMTEL voice and video handovers from non-3GPP access to 3GPP only.
Full comparison in TS 24.173 →Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (1 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Defining Specifications
3GPP specifications that define or reference TIR, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.173 vl00 | IMS Multimedia Telephony Service | Rel-21 read |
| TS 22.273 v710 | IMS Multimedia Telephony with PSTN/ISDN Simulation | Rel-7 read |
| TS 22.401 v800 | Videotelephony over TISPAN NGN Requirements | Rel-8 read |
| TS 24.173 vj00 | Multimedia Telephony Service and Supplementary Services in IMS | Rel-19 read |
| TS 24.186 vk10 | IMS Data Channel and AR Communication | Rel-20 read |
| TS 24.196 vj00 | Enhanced Calling Name (eCNAM) Stage 3 Protocol | Rel-19 read |
| TS 24.292 vj00 | IMS Centralized Services (ICS) Protocol | Rel-19 read |
| TS 24.404 v750 | Communication Diversion Services Stage 3 | Rel-7 read |
| TS 24.405 v700 | Conference Service Protocol Description | Rel-7 read |
| TS 24.406 v810 | Message Waiting Indication (MWI) Protocol | Rel-8 read |
| TS 24.408 v700 | TIP/TIR Services Protocol Specification | Rel-7 read |
| TS 24.410 v810 | Protocol Description of HOLD Services | Rel-8 read |
| TS 24.411 v830 | 3GPP TS 24411 v830: Anonymous Communication Rejection and Communication Barring | Rel-8 read |
| TS 24.416 v700 | Malicious Call Identification Service | Rel-7 read |
| TS 24.429 v700 | Explicit Communication Transfer (ECT) Service Specification | Rel-7 read |
| TS 24.447 v800 | Advice Of Charge (AOC) Service Protocol | Rel-8 read |
| TS 24.454 v840 | Closed User Group (CUG) Protocol Specification | Rel-8 read |
| TS 24.504 v8m0 | Communication Diversion (CDIV) Protocol Specification | Rel-8 read |
| TS 24.505 v810 | Protocol Description of the Conference Service | Rel-8 read |
| TS 24.508 v820 | TIP and TIR Service Protocol Description | Rel-8 read |
| TS 24.516 v830 | MCID Protocol Specification for NGN | Rel-8 read |
| TS 24.529 v820 | Explicit Communication Transfer (ECT) Simulation Service | Rel-8 read |
| TS 24.604 vj00 | Communications Diversion (CDIV) Protocol Spec | Rel-19 read |
| TS 24.605 vj00 | 3GPP CONF Service Protocol Specification | Rel-19 read |
| TS 24.606 vj00 | MWI Service Protocol Description | Rel-19 read |
| TS 24.608 vj00 | 3GPP TS 24608: TIP/TIR Services Protocol | Rel-19 read |
| TS 24.610 vj00 | Communication Hold (HOLD) Service Protocol | Rel-19 read |
| TS 24.611 vj00 | Anonymous Communication Rejection & Barring | Rel-19 read |
| TS 24.615 vj00 | Communication Waiting (CW) Service Protocol | Rel-19 read |
| TS 24.616 vj00 | Malicious Call Identification (MCID) Protocol | Rel-19 read |
| TS 24.629 vj00 | Explicit Communication Transfer (ECT) Protocol | Rel-19 read |
| TS 24.642 vj00 | CCBS/CCNR/CCNL SIP Protocol Specification | Rel-19 read |
| TS 24.647 vj00 | Advice of Charge (AOC) service protocol | Rel-19 read |
| TS 24.654 vj00 | Closed User Group (CUG) supplementary service | Rel-19 read |
| TS 29.163 vj00 | Interworking between 3GPP IM CN and CS networks | Rel-19 read |
| TS 29.165 vk00 | Inter-IMS Network-to-Network Interface (II-NNI) | Rel-20 read |
| TS 29.292 vj00 | IMS Centralized Services (ICS) Interworking | Rel-19 read |
| TS 29.364 vj10 | IMS AS Service Data Descriptions | Rel-19 read |
| TS 29.864 v801 | Application Server Service Data Definition for IMS Telephony | Rel-8 read |
| TS 32.260 vk10 | IMS Charging Management | Rel-20 read |
| TS 32.275 vj00 | MMTel Charging Specification | Rel-19 read |
| TS 32.850 ve00 | IMS Charging Correlation Methods Study | Rel-14 read |
| TS 37.355 vj30 | LTE Positioning Protocol (LPP) | Rel-19 read |
| TR 38.857 vh00 | Study on NR Positioning Enhancements | Rel-17 read |