Description
Terminating Identification Presentation (TIP) is a supplementary service defined by 3GPP that allows the identity of the calling party to be presented to the called (terminating) user. It is part of the family of Calling Line Identification (CLI) services and is specified in a wide range of technical specifications, including 22.173 (IMS Multimedia Telephony), 24.604 (Communication Diversion), and 24.615 (Communication Waiting). TIP operates within the IP Multimedia Subsystem (IMS) and also in circuit-switched networks, providing the terminating user with the calling party's number or SIP URI. The service is typically offered alongside Terminating Identification Restriction (TIR), which allows the calling party to prevent the presentation of their identity.
Architecturally, TIP is implemented through the use of the P-Asserted-Identity and From headers in SIP messages within the IMS. When a call is initiated, the originating network inserts the calling party's identity into the SIP INVITE request. The terminating network, upon receiving the request, verifies the identity and presents it to the called user equipment (UE). The presentation may be subject to authorization checks, such as whether the calling party has subscribed to the service and whether any restrictions apply. In circuit-switched networks, the calling party's number is delivered via the Calling Party Number (CPN) information element in the setup message.
The service is controlled by the terminating user's subscription profile, which is stored in the Home Subscriber Server (HSS) and enforced by the Serving-Call Session Control Function (S-CSCF) in IMS or the Mobile Switching Center (MSC) in CS networks. The TIP service can be activated or deactivated by the user, and its behavior can be influenced by the calling party's TIR settings. For example, if the calling party has invoked TIR, the terminating network may receive an anonymous identity or a presentation indicator set to "restricted," in which case TIP will not display the actual identity.
TIP is closely related to other supplementary services such as Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR). While OIP presents the calling party's identity to the called party, OIR allows the calling party to restrict the presentation of their identity. TIP works in conjunction with these services to provide a comprehensive identity management framework. The service is also applicable to emergency calls, where the calling party's identity may be presented to the emergency services regardless of any restriction settings.
In terms of implementation, TIP relies on the SIP protocol for session establishment and the DIAMETER protocol for authentication, authorization, and accounting (AAA) functions. The service is standardized across multiple releases of 3GPP, ensuring interoperability between different vendors and networks. The specifications 22.173 and 24.604 provide the core requirements and procedures for TIP, while other specs like 24.615 and 24.629 address specific scenarios such as communication waiting and explicit communication transfer. Overall, TIP enhances the user experience by providing essential caller information, enabling call screening, and supporting regulatory requirements for emergency services.
Purpose & Motivation
TIP was created to provide users with the ability to identify incoming callers before answering, a feature that has become fundamental in modern telephony. Before TIP, users had no way of knowing who was calling, which could lead to unwanted calls or missed important communications. The service addresses the need for call screening, allowing users to make informed decisions about whether to answer a call. It also supports regulatory requirements in some regions where emergency services must receive the calling party's identity.
Historically, TIP evolved from the Calling Line Identification Presentation (CLIP) service in traditional circuit-switched networks. As networks migrated to IMS and VoIP, TIP was adapted to work with SIP-based signaling, ensuring continuity of service across different access technologies. The service also had to accommodate privacy concerns, leading to the development of TIR as a complementary service. TIP's design ensures that it can be offered alongside other supplementary services without conflicts, and it is flexible enough to be customized based on user preferences and network policies.
One of the key motivations for TIP was to enable advanced telephony features such as call logs, missed call notifications, and integration with address books. By presenting the calling party's identity, TIP allows user devices to match the incoming number with stored contacts, enhancing the overall communication experience. Additionally, TIP plays a role in fraud prevention by allowing users to verify the authenticity of incoming calls, although additional mechanisms like STIR/SHAKEN are needed for full protection.
What changed in its specifications
The latest release-to-release comparison of specifications that define TIP. 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 TIP, 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 22.519 vj00 | NGN Business Communication Requirements | Rel-19 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.828 va00 | Study on 3GPP-TMF NRM/SID Alignment | Rel-10 read |
| TS 32.829 va00 | Fault Management Alignment Study | Rel-10 read |
| TS 32.831 va00 | 3GPP-TMF PM Alignment Study | Rel-10 read |
| TS 32.850 ve00 | IMS Charging Correlation Methods Study | Rel-14 read |