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.
Key Features
- Selects the network and node for IMS-to-CS/PSTN session breakout
- Makes routing decisions based on destination number analysis and operator policy
- Forwards sessions to an MGCF in the same network or a peer BGCF in another network
- Interfaces with S-CSCF (Mr) and other BGCFs (Mi) using SIP
- Enables optimal routing to reduce latency and interconnect costs
- Supports load distribution and redundancy among multiple MGCFs
Evolution Across Releases
Introduced as a core IMS function in 3GPP Release 5. The initial architecture defined the BGCF's role in selecting the breakout point for SIP sessions destined to the CS domain. It specified the Mr interface to the S-CSCF and the Mi interface to other BGCFs, establishing its position as the routing decision point before reaching the MGCF for protocol interworking.
Defining Specifications
| Specification | Title |
|---|---|
| TS 23.228 | 3GPP TS 23.228 |
| TS 23.806 | 3GPP TS 23.806 |
| TS 23.815 | 3GPP TS 23.815 |
| TS 24.228 | 3GPP TS 24.228 |
| TS 24.229 | 3GPP TS 24.229 |
| TS 24.407 | 3GPP TS 24.407 |
| TS 24.416 | 3GPP TS 24.416 |
| TS 24.429 | 3GPP TS 24.429 |
| TS 24.454 | 3GPP TS 24.454 |
| TS 24.508 | 3GPP TS 24.508 |
| TS 24.516 | 3GPP TS 24.516 |
| TS 24.523 | 3GPP TS 24.523 |
| TS 24.524 | 3GPP TS 24.524 |
| TS 24.529 | 3GPP TS 24.529 |
| TS 24.802 | 3GPP TS 24.802 |
| TS 26.944 | 3GPP TS 26.944 |
| TS 28.702 | 3GPP TS 28.702 |
| TS 28.705 | 3GPP TS 28.705 |
| TS 29.162 | 3GPP TS 29.162 |
| TS 29.163 | 3GPP TS 29.163 |
| TS 29.165 | 3GPP TS 29.165 |
| TS 29.235 | 3GPP TS 29.235 |
| TS 29.421 | 3GPP TS 29.421 |
| TS 29.949 | 3GPP TS 29.949 |
| TS 32.102 | 3GPP TR 32.102 |
| TS 32.240 | 3GPP TR 32.240 |
| TS 32.260 | 3GPP TR 32.260 |
| TS 32.272 | 3GPP TR 32.272 |
| TS 32.409 | 3GPP TR 32.409 |
| TS 32.422 | 3GPP TR 32.422 |
| TS 32.632 | 3GPP TR 32.632 |
| TS 32.732 | 3GPP TR 32.732 |