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.
What changed in its specifications
The latest release-to-release comparison of specifications that define IBCF. Each summary describes the whole specification, not only this term.
Rel-19 TS 23.228 adds SBI service operations for IMS data channels, event subscription, and user information, plus HSS lookup of the serving IMS AS. It adds PS Data Off handling for IMS Data Channel services and Multimedia Priority Service for Messaging.
Full comparison in TS 23.228 →Rel-17 restricts ongoing MMTEL voice and video handovers from non-3GPP access to 3GPP only.
Full comparison in TS 24.173 →Technology family
IMS functions · Services › IMS
- R99 OSA-SCS
- Rel-5 AS, BGCF, CSCF, I-CSCF, IM-MGW, IM-SSF, MGCF, MRFC, MRFP, P-CSCF, S-CSCF
- Rel-6 IBCF, IMS-ALG, TrGW
- Rel-7 E-CSCF, IMS-AGW
- Rel-8 MRB, SCC AS
- Rel-9 EATF
- Rel-10 ATCF, ATGW
- IBCF used together with TrGW
“The IBCF providing IMS-ALG functions would be supported by TrGW functions using the Ix interface (see subclause I.2 of 3GPP TS 23.228 [7])” TS 23.218
- IBCF coexists with ATCF
“The ATCF may be co-located with one of the existing functional entities within the serving network (i.e. P-CSCF or IBCF).” TS 23.237
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 14 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
IBCF (acting as IMS-ALG) first appears in TS 24.229 in Rel-6, with text covering SDP handling for the IBCF.
- “SDP referencing error for IBCF (IMS-ALG)” TS 24.229 v6.30.0
The IBCF is defined for the first time, acting as entry and exit point with border control functions (topology hiding, screening, IMS-ALG) and with SIP procedures for REGISTER, INVITE and subsequent requests.
- “In case border control concepts are to be applied in an IMS network, the IBCF acts as an entry point for this network” TS 23.228 v7.16.0
- “The IBCF may act both as an entry point and as an exit point for a network.” TS 24.229 v7.34.0
- “IBCF Interconnection Border Control Function” TS 23.228 v7.16.0
Rel-8 gave the IBCF a role in voice transcoding: it may insert codecs into SIP offers, check SDP to determine transcoding need, and work with the TrGW.
- “The IBCF shall add codecs to the offer such that in the terminating UE codec selection process, priority shall be given to the codecs inserted by the originating UE” TS 23.228 v8.12.0
- “The IBCF/TrGw provides the necessary function for codec transcoding, when required by interworking agreement and session information” TS 23.228 v8.12.0
- “The Mx reference point allows S‑CSCF/I‑CSCF/P‑CSCF/MSC Server enhanced for ICS or MSC Server enhanced for SRVCC to communicate with an IBCF” TS 23.228 v8.12.0
IBCF gained new requirements in Rel-9: it can reject requests per local policy, apply transcoding with the TrGW over Ix, and retain SUBSCRIBE dialog state.
Compared with Rel-7: intermediate versions are not available, so this change may date from any release since Rel-7.
- “the IBCF may reject the SIP request based on local policy by sending an appropriate SIP 4xx response.” TS 24.229 v9.31.0
- “The Ix reference point allows the IBCF to control the TrGW.” TS 23.228 v9.4.0
- “If the IBCF is configured per local policy to use proactive transcoding, the IBCF shall add codecs to the offer” TS 23.228 v9.4.0
IBCF procedures were extended in Rel-10: it routes enterprise emergency calls to E-CSCF, inserts Resource-Priority headers, handles ECN and ICE SDP, and supports ATCF/ATGW with TrGW selection.
- “An IBCF can also route emergency calls received from an enterprise network (peering-based business trunking) to an E-CSCF.” TS 24.229 v10.29.0
- “the IBCF shall insert the temporarily authorised Resource-Priority header field with appropriate namespace and priority value in the INVITE request.” TS 24.229 v10.29.0
- “If the IBCF supports the ATCF functionality (see subclause 6.1.4), the IBCF shall select a TRGW which supports the ATGW functionality.” TS 29.162 v10.7.0
IBCF gained new Rel-11 requirements: MPS priority handling towards the TrGW over H.248, OMR application, S-CSCF restoration support, and emergency-call routing and Resource-Priority handling.
- “The IBCF shall send the Priority information for a context to the TrGW to enable the priority treatment described below related to the TrGW.” TS 29.162 v11.2.0
- “The IBCF shall apply OMR as specified in 3GPP TS 29.079 [11D]” TS 24.229 v11.31.0
- “the IBCF supports S-CSCF restoration procedures;” TS 24.229 v11.31.0
IBCF behaviour was extended in Rel-12: it now selects alternative P-CSCFs for PCRF-based restoration, uses the RFC 7549 'iotl' parameter, adds premium-rate tel URI parameters, and supports CVO and media security with the TrGW.
- “When the user is roaming, the IBCF selects an alternative P-CSCF and forwards the IMSI of the terminating user in a Restoration-Info header field.” TS 24.229 v12.27.0
- “the IBCF shall, based on local policy, add the "premium-rate" tel URI parameter specified in subclause 7.2A.17” TS 24.229 v12.27.0
- “the IBCF shall include an "extended RTP header for CVO" information element when seizing resources in the TrGW” TS 29.162 v12.7.0
IBCF behaviour was extended in Rel-13: topology hiding now covers Path and Service-Route headers, new feature-capability indicator g.3gpp.thig-path, RFC 7549 traffic leg support, and SDP bandwidth/capability negotiation handling toward the TrGW.
- “The IBCF shall apply network topology hiding to all header fields which reveal topology information, such as Via, Route, Record-Route, Service-Route, and Path.” TS 24.229 v13.23.0
- “in a roaming scenario, the visited network IBCF supports topology hiding of a Path header field.” TS 24.229 v13.23.0
- “the IBCF shall include appropriate bandwidth information in new or existing "a=bw-info" attribute lines(s).” TS 29.162 v13.3.0
IBCF procedures were extended in Rel-14, adding logging of SIP requests that carry a "logme" parameter, IPv4/IPv6 interworking on a 488 response, and P-Early-Media based through-connect control of early media.
- “The IBCF shall log all SIP requests and responses that contain a "logme" header field parameter in the SIP Session-ID header field” TS 24.229 v14.21.0
- “the IBCF may, by performing the IP version interworking, acquire an IPv4 address or use an existing IPv4 address” TS 24.229 v14.21.0
- “If the IBCF uses the em-param(s) of the P-Early-Media header field for the through-connect control of early media” TS 29.162 v14.2.0
IBCF gained new roles in Rel-15: invoking an AS over the Ms reference point to sign and verify caller identity and attestation, and adding gateway attestation information.
- “the IBCF sends a signingRequest, specified in annex V, over the Ms reference point.” TS 24.229 v15.20.0
- “the IBCF, if configured through policies, invokes an AS for signature verification.” TS 23.228 v15.5.0
- Gateway attestation procedure for the IBCF TS 24.229CR6090
IBCF and TrGW interworking requirements were extended in TS 29.162 to optionally support "DBI" signalling, applying the procedures of TS 23.334.
- “The IBCF and the TrGW may support the "DBI" signalling as defined in 3GPP TS 26.114 [36].” TS 29.162 v16.0.0
- “If the IBCF and the TrGW support the "DBI" signalling, they shall apply the requirements and procedures specified in 3GPP TS 23.334 [43]” TS 29.162 v16.0.0
- Update IBCF and TrGW interworking requirements for DBI support TS 29.162CR0159
IBCF procedures were extended in Rel-17: it verifies and signs Resource-Priority/Priority information via Ms using PASSporT, populates verstat and Reason headers, and supports ICE per RFC 8445.
- “When receiving a re-INVITE request containing the Resource-Priority header field, the IBCF sends a signingRequest, over the Ms reference point” TS 24.229 v17.19.0
- “This subclause describes procedures of an IBCF to support ICE as defined in RFC 8445 [289] and RFC 8839 [290].” TS 24.229 v17.19.0
- Add IBCF Ms procedures to support verification failures TS 24.229CR6560
IBCF behaviour changed: it may now populate a Reason header per Identity verification error with STIR cause and failing PASSporT, and may support IVAS transcoding with the TrGW.
- “the IBCF may populate for each reported Identity header field verification error a Reason header field in the next provisional or final response” TS 24.229 v18.11.0
- “The IBCF and the TrGW may support transcoding to and from the IVAS speech and audio codec.” TS 29.162 v18.1.0
The IBCF gained procedures for Rich Call Data: verifying RCD Identity header fields, requesting RCD signing over Ms via signingRequest, removing the rcd-np parameter, and rejecting calls when verification fails.
- “based on the policy, the IBCF may reject the initial INVITE request or MESSAGE request with suitable 4xx or 5xx or 6xx response code.” TS 24.229 v19.7.0
- “the IBCF sends a signingRequest, over the Ms reference point, as specified in annex V, for the RCD info.” TS 24.229 v19.7.0
- “the IBCF, if configured through policies, invokes an AS for signature verification as per Annex AF.” TS 23.228 v19.8.0
Defining Specifications
3GPP specifications that define or reference IBCF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.228 vk10 | IP Multimedia Core Network Subsystem | Rel-20 read |
| TS 23.417 v700 | IMS Core Component for NGN Architecture | Rel-7 read |
| TS 23.517 v800 | IMS Core Architecture for TISPAN NGN | Rel-8 read |
| TS 23.849 vb00 | IMS Roaming Resource Control Study | Rel-11 read |
| TS 24.173 vj00 | Multimedia Telephony Service and Supplementary Services in IMS | Rel-19 read |
| TS 24.229 vk10 | IMS SIP/SDP Call Control Protocol | Rel-20 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.407 v830 | OIP and OIR Simulation Services 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.416 v700 | Malicious Call Identification Service | Rel-7 read |
| TS 24.428 v720 | Common Basic Communication Procedures | Rel-7 read |
| TS 24.429 v700 | Explicit Communication Transfer (ECT) Service Specification | Rel-7 read |
| TS 24.454 v840 | Closed User Group (CUG) 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.523 vj00 | NGCN-NGN Interconnection Scenarios | Rel-19 read |
| TS 24.528 v830 | Common Basic Communication Procedures for IMS Services | Rel-8 read |
| TS 24.529 v820 | Explicit Communication Transfer (ECT) Simulation Service | Rel-8 read |
| TS 24.607 vj10 | OIP and OIR Supplementary Services Stage 3 | Rel-19 read |
| TS 24.608 vj00 | 3GPP TS 24608: TIP/TIR Services Protocol | Rel-19 read |
| TS 24.802 vc10 | II-NNI Traversal Scenario Determination | Rel-12 read |
| TR 26.919 vj00 | Study on 5G Conversational Media Handling | Rel-19 read |
| TR 26.924 vj00 | MTSI QoS Improvement Study | Rel-19 read |
| TR 26.930 vj00 | WebRTC Enhancements for Immersive RTC over 5G | Rel-19 read |
| TS 29.162 vj00 | IMS-IP Network Interworking | Rel-19 read |
| TS 29.165 vk00 | Inter-IMS Network-to-Network Interface (II-NNI) | Rel-20 read |
| TS 29.235 vj00 | SIP-I CS Core Network Interworking | Rel-19 read |
| TS 29.238 vj00 | H.248 Profile for IBCF-TrGW Interface | Rel-19 read |
| TS 29.421 v810 | IMS Interworking with External IP Networks | Rel-8 read |
| TS 29.806 vc10 | P-CSCF Restoration Analysis & Solutions | Rel-12 read |
| TS 29.865 v800 | Inter-IMS Network to Network Interface (II-NNI) | Rel-8 read |
| TR 29.949 vj00 | VoLTE IMS Roaming Architecture & Procedures | Rel-19 read |
| TS 32.102 vj00 | Telecom Management Physical Architecture Framework | Rel-19 read |
| TS 32.240 vk10 | 3GPP Charging Architecture and Principles | Rel-20 read |
| TS 32.260 vk10 | IMS Charging Management | Rel-20 read |
| TS 32.280 vj00 | Advice of Charge (AoC) Framework | Rel-19 read |
| TS 32.409 vj00 | IMS Performance Management Measurements | Rel-19 read |
| TS 33.107 vj00 | Lawful Interception Architecture & Functions | Rel-19 read |
| TS 33.108 vj00 | LI Handover Interface Specification | Rel-19 read |
| TS 33.127 vj80 | Lawful Interception Architecture | Rel-19 read |
| TS 33.203 vk00 | IMS Security Features and Mechanisms | Rel-20 read |
| TS 33.790 vj10 | Security for Next-Gen Real-Time Communication Phase 2 | Rel-19 read |