BGCF

Breakout Gateway Control Function

Core Network →
Introduced in Rel-2 Also in: Core Network, Management

BGCF is the IMS call session control function that selects the network for routing SIP sessions to the PSTN or CS domain and chooses the appropriate breakout point, such as an MGCF.

Category
Core Network
Introduced
Rel-2
Where
Services › Codecs
Also touches
2 segments
Specifications
32 specs
BGCF Description Purpose Related Classification Detected Changes Specifications

Description

The Breakout Gateway Control Function (BGCF) is a critical component within the IP Multimedia Subsystem (IMS) architecture, specifically within the Call Session Control Function (CSCF) layer. Its primary role is to make routing decisions for SIP sessions that need to be terminated in a circuit-switched (CS) network, such as the Public Switched Telephone Network (PSTN) or a legacy cellular network (e.g., 2G/3G). When a SIP session initiated within the IMS is destined for a user or service in the CS domain, the Serving-CSCF (S-CSCF) forwards the session signaling to the BGCF. The BGCF then analyzes the session request, typically based on the dialed number (E.164), to decide where the session should 'break out' from the IMS packet core into the CS domain.

Architecturally, the BGCF is a SIP server that implements specific routing logic. It does not handle media but purely makes signaling decisions. Upon receiving a SIP INVITE request, the BGCF evaluates the destination. If the breakout point is determined to be within its own network, the BGCF selects an appropriate Media Gateway Control Function (MGCF) within its domain and forwards the SIP signaling to it. The MGCF is then responsible for interworking the SIP signaling with the ISUP/BICC signaling used in the CS network and controlling the Media Gateway (MGW) for media conversion. If the breakout is best handled in another network, the BGCF's role is to select a peer BGCF in that external network and forward the SIP session to it, delegating the final breakout decision.

Key components of the BGCF's functionality include its routing logic database and its interfaces. It interfaces with the S-CSCF via the Mr reference point (using SIP) and with other BGCFs via the Mi reference point (also SIP). Its internal decision-making can be based on configured routing tables, number analysis, operator policies, or interactions with other network elements like a Transport Stratum for ENUM/DNS queries to resolve telephone numbers to SIP URIs or routing numbers. The BGCF's selection process ensures optimal routing, load distribution among MGCFs, and adherence to commercial agreements between network operators for inter-network breakout.

In the broader IMS architecture, the BGCF's role is pivotal for seamless service continuity. It enables the IMS, which is an all-IP service delivery platform, to connect with the vast installed base of legacy telephony users and services. Without the BGCF, IMS-originated calls could not reach PSTN numbers, severely limiting its utility. Its operation is transparent to the end-user but is a fundamental enabler for the 'fixed-mobile convergence' vision of IMS, allowing service providers to offer unified communication services across packet and circuit-switched boundaries.

Purpose & Motivation

The BGCF was created to solve a fundamental problem in the transition from circuit-switched to packet-switched telephony networks. As 3GPP defined the IMS in Release 5 to deliver multimedia services over IP, a mechanism was needed to interconnect this new IP-based signaling domain (SIP) with the existing global PSTN and legacy mobile CS cores, which used signaling protocols like ISUP. The primary problem was determining *where* and *how* to perform this protocol interworking and media conversion in a scalable, efficient, and policy-controlled manner.

Historically, in pure CS networks, calls were routed through switches based on hierarchical number plans. In the IMS, routing is based on SIP URIs and IP addresses. The BGCF provides the intelligence to bridge these two worlds. It addresses the limitation of having a single, fixed breakout point, which could create bottlenecks or suboptimal routing (e.g., tromboning calls back to a home network). By making a dynamic selection, the BGCF allows for breakout closer to the destination, reducing latency and transport costs. It also enables network operators to implement sophisticated routing policies, such as selecting breakout points based on time of day, least-cost routing, or failover scenarios.

Furthermore, the BGCF supports the decomposition of network functions advocated by IMS. Separating the routing decision (BGCF) from the protocol interworking and media control (MGCF) allows for independent scaling and evolution of these functions. This modularity was a key motivation in IMS design, providing flexibility for network operators to deploy and manage resources efficiently. The BGCF, therefore, exists not just as a gateway, but as a strategic routing node that enables the economic and technical viability of deploying IMS alongside—and eventually replacing—legacy telephony infrastructure.

Classification

Part ofCSCF
Specific typesI-BGF
Related approachesMGCF

Detected Changes Across Releases

from 3GPP Change Requests

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

Studied in Rel-2, normative work from Rel-16.

Rel-16 6 changes

In Release 16, the BGCF function itself was not the primary focus of new capabilities. The enhancements centered on improving related IMS core network functions, specifically through corrections to the BGCF's Charging Data Record (CDR) description to ensure accurate documentation. Furthermore, the release introduced updates for network function discovery and registration, such as allowing the SMF to perform P-CSCF discovery using the NRF, which indirectly supports more efficient routing and interconnection scenarios involving the BGCF.

  • eIMS P-CSCF use of NRF TS 23.228CR1199
  • Allowing SMF to perform P-CSCF Discovery using NRF TS 23.228CR1202
  • Update P-CSCF Registration with NRF TS 23.228CR1219
  • Corrections to S-CSCF discovery during RLOS IMS registration TS 23.228CR1228
  • Correction of BGCF CDR description TS 32.260CR0397
  • P-CSCF restoration in 5GS TS 29.165CR0995
Rel-17 1 change

In Release 17, the BGCF's role was enhanced to support the charging architecture for Local Breakout, as defined in the Roaming Architecture for Voice over IMS with Local Breakout. This update ensures that when a session is routed using a Tel URI in a non-international format under this architecture, the appropriate charging procedures can be applied. The change integrates the BGCF more concretely into the policy and charging control framework for these specific breakout scenarios.

  • Charging architecture for Local Breakout TS 32.240CR0439
Rel-19 1 change

In Release 19, the BGCF function saw specific updates to clarify its role in routing sessions for satellite-based communications. The enhancements provided clarification on the P-CSCF's behavior for UE-Satellite-UE communication scenarios, which involve the BGCF via the Mk reference point to another BGCF. This ensures proper session routing and border control when the IBCF acts as the network entry point.

  • Clarification of P-CSCF Behavior for UE-Satellite-UE Communication TS 23.228CR1685

Explore further

Broader topics and technologies where BGCF plays a role.

Defining Specifications

3GPP specifications that define or reference BGCF, 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.806 v1700 Voice Call Continuity between CS and IMS Rel-7
TS 23.815 v1500 IMS Charging Implications Rel-5
TS 24.228 v1500 IP Multimedia Call Control Signaling Flows Rel-5
TS 24.229 vj50 IMS call control protocol based on SIP and SDP Rel-19
TS 24.407 v830 OIP and OIR Simulation Services Protocol Rel-8
TS 24.416 v1700 Malicious Call Identification Service 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.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.524 vj00 Hosted Enterprise Services Architecture Rel-19
TS 24.529 v820 Explicit Communication Transfer (ECT) Simulation Service Rel-8
TS 24.802 vc10 IMS II-NNI Traversal Scenario Determination Study Rel-12
TR 26.944 vj00 QoE, ESQoS and SQoS metrics for 3G multimedia services Rel-19
TS 28.702 vj00 Core Network NRM IRP Information Service Rel-19
TS 28.705 vj00 IMS NRM IRP Information Service Rel-19
TS 29.162 vj00 IMS-IP Network Interworking 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.235 vj00 SIP-I CS Core Network Interworking Rel-19
TS 29.421 v810 IMS Interworking with External IP Networks 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.272 vj00 Charging for Push-to-Talk over Cellular (PoC) Rel-19
TS 32.409 vj00 IMS Performance Management Measurements Rel-19
TS 32.422 vk00 Telecom Management: Trace Control & Configuration Rel-20
TS 32.632 vb00 Core Network Resources IRP: Network Resource Model Rel-11
TS 32.732 vb00 IMS Network Resource Model IRP: Information Service Rel-11