IBCF

Interconnection Border Control Functions

Core Network →
Introduced in Rel-7 Also in: Core Network

IBCF is a core IMS network element that acts as a secure gateway for SIP signaling between different operator networks, providing topology hiding, protocol interworking, and security for inter-domain communication.

Category
Core Network
Introduced
Rel-7
Where
Services › Codecs
Also touches
1 segments
Specifications
45 specs
IBCF Description Purpose Related Classification Detected Changes Specifications

Description

The Interconnection Border Control Function (IBCF) is a critical functional entity within the 3GPP IP Multimedia Subsystem (IMS) architecture, specifically designed to handle the border between an operator's IMS network and external networks. Its primary role is to process Session Initiation Protocol (SIP) and Session Description Protocol (SDP) signaling for multimedia sessions (like voice, video) that traverse network boundaries. Located at the network edge, the IBCF serves as the first point of contact for incoming signaling from other networks and the last point for outgoing signaling, enforcing the operator's interconnection policies.

Architecturally, the IBCF resides within the IMS Core and interfaces internally with the Serving-Call Session Control Function (S-CSCF) and the Breakout Gateway Control Function (BGCF). Externally, it connects to other networks via the IBCF-Interconnection Border Control Function (IBCF) interface (Ic) or to non-IMS networks like the Public Switched Telephone Network (PSTN) via the IBCF-TrGW (Transition Gateway) interface (Ic). A key component often associated with the IBCF is the Transition Gateway (TrGW), which handles the media plane. The IBCF controls the TrGW for functions like Network Address/Port Translation (NAPT) and IPv4/IPv6 interworking.

The IBCF performs several vital functions. First, it provides topology hiding by removing or obfuscating internal network information (like node names and IP addresses) from SIP messages before they leave the home network, enhancing security. Second, it performs protocol interworking, which may involve translating between different SIP profiles (e.g., IMS SIP versus SIP-I for PSTN) or between IPv4 and IPv6. Third, it acts as a Session Border Controller (SBC) for the signaling plane, providing access control, policing SIP traffic rates, and validating SIP message formats. Fourth, it authorizes the establishment of media bearers by controlling the associated TrGW. Finally, it can generate charging data records (CDRs) for inter-domain sessions. By centralizing these border functions, the IBCF simplifies network architecture, improves security, and ensures reliable inter-operator service delivery.

Purpose & Motivation

The IBCF was created to address the fundamental challenges of securely and reliably interconnecting IMS-based networks, both with other IMS networks and with legacy circuit-switched networks. Prior to IMS, inter-operator connectivity for voice was largely handled by circuit-switched gateways (like GMSC) with relatively simple, non-IP signaling. The shift to an all-IP, SIP-based core for multimedia services introduced new complexities: exposure of internal network topology via SIP headers, security threats from untrusted IP networks, the need for IP version interworking, and the requirement for sophisticated session and media policy control at the border.

The IBCF solves these problems by acting as a standardized, secure gateway. It protects the operator's internal network infrastructure from external threats and prevents information leakage. It enables seamless service delivery between operators using potentially different IMS implementations or SIP profiles. Furthermore, as networks transitioned from IPv4 to IPv6, the IBCF's interworking function became essential for maintaining connectivity. Its introduction in Release 7 alongside the full IMS architecture was pivotal for making IMS a viable technology for commercial, multi-operator service offerings like Voice over LTE (VoLTE) and Rich Communication Services (RCS), ensuring that the promise of interoperable, IP-based multimedia could be realized across administrative and technological boundaries.

Classification

Part ofCSCF
Related approachesBGCF

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-16 1 change

In Release 16, the IBCF's capabilities were updated to support DBI (Dynamic Business Trunking Interconnection), requiring updated interworking requirements between the IBCF and the TrGW. This enhancement is part of providing support for business trunking in static mode, which is clarified as a function of either an IBCF or a P-CSCF.

  • Update IBCF and TrGW interworking requirements for DBI support TS 29.162CR0159
Rel-17 2 changes

In Release 17, the IBCF's capabilities were enhanced to support the signing of Resource-Priority related information for Multimedia Priority Service (MPS) by invoking an Application Server when configured by operator policy. Furthermore, the specification clarified architectural routing by removing the IBCF as an alternate option for handling non-local identities in the Visited Public Land Mobile Network (VPLMN).

  • IBCF RPH signing for MPS TS 29.165CR1030
  • IMS: Removing IBCF from the alternate option for non-local ID in the VPLMN TS 33.127CR0122

Explore further

Broader topics and technologies where IBCF plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.228 vj50 IMS Stage-2 Service Description Rel-19
TS 23.417 v1700 IMS Core Component for NGN Architecture Rel-7
TS 23.517 v1800 IMS Core Component for NGN Architecture Rel-8
TS 23.849 vb00 Study on IMS Roaming Media Optimization Rel-11
TS 24.173 vj00 Multimedia Telephony Service and Supplementary Services in IMS Rel-19
TS 24.229 vj50 IMS call control protocol based on SIP and SDP Rel-19
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.416 v1700 Malicious Call Identification Service Rel-7
TS 24.428 v1700 Common Basic Communication Procedures Rel-7
TS 24.429 v1700 Explicit Communication Transfer (ECT) Service Specification Rel-7
TS 24.454 v840 Closed User Group (CUG) Protocol Specification 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.523 vj00 NGCN-NGN Interconnection Scenarios Rel-19
TS 24.528 v830 Common Basic Communication Procedures for IMS Services Rel-8
TS 24.529 v820 Explicit Communication Transfer (ECT) Simulation Service Rel-8
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.802 vc10 IMS II-NNI Traversal Scenario Determination Study Rel-12
TR 26.919 vj00 Study on 5G Conversational Media Handling Rel-19
TR 26.924 vj00 MTSI QoS Improvement Study Rel-19
TR 26.930 vj00 WebRTC Enhancements for Immersive RTC over 5G Rel-19
TS 29.162 vj00 IMS-IP Network Interworking Rel-19
TS 29.165 vj10 Inter-IMS Network to Network Interface (NNI) Rel-19
TS 29.235 vj00 SIP-I CS Core Network Interworking Rel-19
TS 29.238 vj00 H.248 Profile for IBCF-TrGW Interface Rel-19
TS 29.421 v810 IMS Interworking with External IP Networks Rel-8
TS 29.806 vc10 P-CSCF Restoration Analysis & Solutions Rel-12
TS 29.865 v1800 Inter-IMS Network to Network Interface Rel-8
TR 29.949 vj00 VoLTE IMS Roaming Architecture & Procedures Rel-19
TS 32.102 vj00 Telecom Management Physical Architecture Framework Rel-19
TS 32.240 vj40 Charging Management Architecture & Principles Rel-19
TS 32.260 vj10 IMS Charging Management Rel-19
TS 32.280 vj00 Advice of Charge (AoC) Framework Rel-19
TS 32.409 vj00 IMS Performance Management Measurements Rel-19
TS 33.107 vj00 Lawful Interception Architecture & Functions Rel-19
TS 33.108 vj00 LI Handover Interface Specification Rel-19
TS 33.127 vj50 Lawful Interception Architecture and Functions Rel-19
TS 33.203 vj10 IMS Security Specification Rel-19
TS 33.790 vj10 Security for Next-Gen Real-Time Communication Phase 2 Rel-19
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.