OIR

Originating Identification presentation Restriction

Services →
Introduced in Rel-7

OIR is a supplementary service that allows a calling party to restrict the presentation of their identification, such as their phone number, to the called party.

Category
Services
Introduced
Rel-7
Where
Services › IMS
Specifications
44 specs
OIR Description Purpose Related Classification Detected Changes Specifications

Description

Originating Identification presentation Restriction (OIR) is a supplementary service standardized by 3GPP that provides the calling party with the ability to prevent their identification information (typically the Calling Party Number or SIP URI) from being presented to the called party. The service operates within the call control and session management layers of the network, intercepting and modifying the signaling messages that carry caller identification. When a user activates OIR (either per-call via a prefix or as a permanent subscription service), the network applies logic to either remove the identification from the outgoing signaling or mark it as 'presentation restricted'. This is enforced at the originating network's control nodes, such as the MSC (Mobile Switching Centre) in circuit-switched networks or the S-CSCF (Serving Call Session Control Function) in IMS (IP Multimedia Subsystem) networks. The service interacts with the HSS (Home Subscriber Server) or HLR (Home Location Register) to verify subscription data and service authorization. In the IMS architecture, OIR is implemented as an originating service within the S-CSCF, utilizing Initial Filter Criteria (iFC) to trigger the appropriate Application Server if needed for advanced logic. The restriction can be overridden in specific cases, such as emergency calls or calls to certain authorized numbers, as defined by network policy and regulatory requirements. The called party's network may also apply complementary services like Connected Line Identification Presentation (COLP) or generate privacy indicators based on the received restricted status.

Purpose & Motivation

OIR was created to address growing user privacy concerns, allowing individuals to control the disclosure of their personal contact information. Before such services, caller identification was typically always presented, which could lead to unwanted contact, harassment, or privacy breaches. The service solves the problem of involuntary information disclosure in telephony, giving subscribers autonomy over their identity. Its introduction was motivated by regulatory requirements in many regions mandating privacy options for telecommunications users. It also enables business applications, such as allowing employees to make business calls without revealing personal mobile numbers. The service provides a standardized mechanism across different network generations (circuit-switched and packet-switched/IMS), ensuring consistent privacy functionality as networks evolved.

Classification

Part ofCLIP
Related approachesCOLP

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (2 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-17 1 change

In Release 17, the primary new introduction for the OIR function was the configuration for Standalone Non-Public Networks (SNPN). This is specified to ensure the OIR service, which enables an originating party to withhold its identity, operates correctly within SNPN environments alongside the related OIP service.

  • SNPN configuration for OIP/OIR TS 24.417CR0002
Rel-19 1 change

In Release 19, the new work for the OIR function specifically defined its interaction with user RCD (Redirection Counter) information. This clarifies how the restriction of the originating party's identity is managed in scenarios involving call forwarding or deflection when RCD data is involved, ensuring consistent behavior across different supplementary services.

  • OIR interaction with user RCD information TS 24.607CR0059

Explore further

Broader topics and technologies where OIR plays a role.

Defining Specifications

3GPP specifications that define or reference OIR, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 22.173 vk00 IMS Multimedia Telephony Service Definition Rel-20
TS 22.273 v1700 IMS Multimedia Telephony with PSTN/ISDN Simulation Rel-7
TS 22.401 v1800 Videotelephony Service Requirements for NGN Rel-8
TS 24.173 vj00 Multimedia Telephony Service and Supplementary Services in IMS Rel-19
TS 24.186 vj60 IMS Data Channel applications Rel-19
TS 24.196 vj00 Enhanced Calling Name (eCNAM) Stage 3 Protocol Rel-19
TS 24.292 vj00 IMS Centralized Services (ICS) Protocol Rel-19
TS 24.404 v1700 Communication Diversion Services (CDIV) Rel-7
TS 24.405 v1700 Conference Service Protocol Description Rel-7
TS 24.406 v810 Message Waiting Indication (MWI) Protocol Rel-8
TS 24.407 v830 OIP and OIR Simulation Services Protocol Rel-8
TS 24.408 v1700 TIP/TIR Services Protocol Specification Rel-7
TS 24.410 v810 Protocol Description of HOLD Services Rel-8
TS 24.411 v1830 ACR and CB Service Protocol Specification Rel-8
TS 24.416 v1700 Malicious Call Identification Service Rel-7
TS 24.417 vj00 OIP/OIR Management Object Specification Rel-19
TS 24.429 v1700 Explicit Communication Transfer (ECT) Service Specification Rel-7
TS 24.447 v800 Advice Of Charge (AOC) Service Protocol Rel-8
TS 24.454 v840 Closed User Group (CUG) Protocol Specification Rel-8
TS 24.504 v8m0 Communication Diversion Services Stage 3 Rel-8
TS 24.505 v810 Protocol Description of the Conference Service Rel-8
TS 24.508 v820 TIP and TIR Service Protocol Description Rel-8
TS 24.516 v830 MCID Protocol Specification for NGN Rel-8
TS 24.529 v820 Explicit Communication Transfer (ECT) Simulation Service Rel-8
TS 24.604 vj00 Communications Diversion (CDIV) Protocol Spec Rel-19
TS 24.605 vj00 3GPP CONF Service Protocol Specification Rel-19
TS 24.606 vj00 MWI Service Protocol Description Rel-19
TS 24.607 vj10 OIP and OIR Supplementary Services Stage 3 Rel-19
TS 24.608 vj00 3GPP TS 24608: TIP/TIR Services Protocol Rel-19
TS 24.610 vj00 Communication Hold (HOLD) Service Protocol Rel-19
TS 24.611 vj00 Anonymous Communication Rejection & Barring Rel-19
TS 24.615 vj00 Communication Waiting (CW) Service Protocol Rel-19
TS 24.616 vj00 Malicious Call Identification (MCID) Protocol Rel-19
TS 24.629 vj00 Explicit Communication Transfer (ECT) Protocol Rel-19
TS 24.642 vj00 CCBS/CCNR/CCNL SIP Protocol Specification Rel-19
TS 24.647 vj00 Advice of Charge (AOC) service protocol Rel-19
TS 24.654 vj00 Closed User Group (CUG) supplementary service Rel-19
TS 29.163 vj00 Interworking between 3GPP IM CN and CS networks Rel-19
TS 29.165 vj10 Inter-IMS Network to Network Interface (NNI) Rel-19
TS 29.292 vj00 IMS Centralized Services (ICS) Interworking Rel-19
TS 29.364 vj10 IMS AS Service Data Descriptions Rel-19
TS 29.864 v801 Application Server Service Data Definition for IMS Telephony Rel-8
TS 32.275 vj00 MMTel Charging Specification Rel-19
TS 32.850 ve00 IMS Charging Correlation Methods Study Rel-14
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.