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.
What changed in its specifications
The latest release-to-release comparison of specifications that define BGCF. 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-19 adds Rich Call Data support to TS 24.229, including the DC-Info header, rcd-np Call-Info parameter, and RCD info retrieval and verification across originating, terminating, IBCF and AS behaviour. It also adds MPS for Messaging, eCall alignment with EN 17184:2024 (test eCall and updated-MSD transfer), and satellite identifiers in P-Access-Network-Info.
Full comparison in TS 24.229 →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
- BGCF used together with MGCF
“If the routing determination is such that the breakout is to occur in the same network in which the BGCF is located, then the BGCF shall select a MGCF that will be responsible for the interworking with the PSTN/CS Domain.” TS 23.228
- BGCF used together with E-CSCF
“The E‑CSCF is the IMS network entity, which is responsible to route the request to an emergency centre/PSAP via or BGCF, IBCF or IP multimedia network based on location information” TS 23.167
- BGCF used together with S-CSCF
“This reference point allows the Serving CSCF to forward the session signalling to the Breakout Gateway Control Function for the purpose of interworking to the circuit switched networks.” TS 23.002
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 11 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.
The BGCF is specified for the first time in Rel-5: it selects the network for PSTN/CS breakout and forwards session requests to an MGCF or to a BGCF in another network.
- “The Breakout Gateway control function (BGCF) selects the network in which PSTN/CS Domain breakout is to occur.” TS 23.228 v5.15.0
- “When the BGCF receives an INVITE request, the BGCF shall forward the request either to an MGCF within its own network, or to another network containing an MGCF.” TS 24.229 v5.26.0
- “5.6 Procedures at the BGCF” TS 24.229 v5.26.0
In Rel-6 the BGCF gained new behaviour: it can act as a UA, may require session refresh via RFC 4028, and takes part in IMS offline charging via Rf with its own BGCF CDR.
- “if the BGCF inserts its own Record-Route header, the BGCF may require the periodic refreshment of the session to avoid hung states in the BGCF” TS 24.229 v6.30.0
- “the BGCF sends an Accounting-Request with Accounting-Record-Type indicating START_RECORD to record start of a user session” TS 32.260 v6.8.0
- “the BGCF can act as a UA when providing server functionality to return a final response” TS 24.229 v6.30.0
BGCF behaviour was revised: 24.229 gains a common BGCF procedures subclause and generalised request forwarding, 23.228 BGCF selects next hop and transit contact point, and 32.260 corrects BGCF charging records.
- “When the BGCF receives a request, the BGCF shall forward the request:” TS 24.229 v7.34.0
- “the Breakout Gateway Control Function (BGCF) may be provisioned as the contact point within an operator's network for transit IMS scenarios” TS 23.228 v7.16.0
- “Corrections to BGCF state during PSTN and IMS intiated session establishment and releases” TS 32.260 v7.7.0
BGCF gained the ability to retrieve number portability data when selecting an MGCF, may serve as contact point for transit IMS scenarios, and handles preferred circuit carrier parameters.
- “per operator policy, the BGCF can retrieve NP data as part of the procedures to select an MGCF for PSTN connection” TS 23.228 v8.12.0
- “the Breakout Gateway Control Function (BGCF) may be provisioned as the contact point within an operator's network for transit IMS scenarios” TS 23.228 v8.12.0
- “The BGCF needs to consider, and can insert, the preferred circuit carrier” TS 23.228 v8.12.0
BGCF procedures in TS 24.229 gained number portability data retrieval, carrier routeing with the "cic" parameter, local-number handling and overlap signalling routing to the same next hop.
Compared with Rel-7: intermediate versions are not available, so this change may date from any release since Rel-7.
- “The BGCF may support retrieval of NP data as part of the procedures to determine where to route the request.” TS 24.229 v9.31.0
- “the BGCF shall include the "cic" tel-URI parameter in the Request-URI identifying the preassigned carrier” TS 24.229 v9.31.0
- “the BGCF shall route such INVITE request received during a certain period of time to the same next hop.” TS 24.229 v9.31.0
BGCF gained procedures for deciding on loopback routeing for roaming (RAVEL) based on the Feature-Caps "+g.3gpp.home-visited" parameter, and the BGCF CDR gained a loopback indicator.
- “the BGCF shall decide based on local policy whether to perform loopback routeing for this request.” TS 24.229 v11.31.0
- “If local policy requires access to BGCF routing data to make the loopback decision for a particular originating INVITE request, then the loopback decision should be performed in the BGCF.” TS 23.228 v11.11.0
- “Introduction of Loopback indicator in BGCF CDR for RAVEL” TS 32.260 v11.19.0
BGCF procedures were extended in Rel-12: it can indicate the traffic leg by adding an "iotl" URI parameter, and it now has an II-NNI traversal scenario.
- “the BGCF if required by local policy, append an "iotl" URI parameter with a value set to "homeA-visitedA" to the URI in the Route header field” TS 24.229 v12.27.0
- “Adding II-NNI traversal scenario by BGCF” TS 24.229 v12.27.0
- “the BGCF supports indicating the traffic leg as specified in RFC 7549 [225]” TS 24.229 v12.27.0
BGCF procedures in TS 24.229 changed: for subsequent requests after loopback routeing it must replace orig-ioi in P-Charging-Vector, and charging header insertion rules were split by header.
- “When the BGCF receives a subsequent request whose initial request applied loopback routeing, the BGCF shall:” TS 24.229 v13.23.0
- “The BGCF shall insert a type 1 "orig-ioi" header field parameter into the P-Charging-Vector header field” TS 24.229 v13.23.0
- Correction for Access Network Information in BGCF CDR – align with TS 32.260 TS 32.298CR0582
BGCF procedures in 24.229 gained new requirements: logging SIP requests with the "logme" parameter, inserting Response-Source "bgcf" in failure responses, and adding fe-addr to P-Charging-Vector.
- “The BGCF 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 BGCF shall add an "fe-addr" element of the "fe-identifier" header field parameter of the P-Charging-Vector header field” TS 24.229 v14.21.0
- Charging Completeness: Procedures at the BGCF TS 24.229CR5877
The BGCF charging description was corrected: on SIP 200 OK the BGCF now sends a Charging Data Request[Event] to create a BGCF CDR, instead of recording session and media start.
- “Upon reception of the SIP 200 OK message, the BGCF sends an Charging Data Request[Event] to create a BGCF CDR.” TS 32.260 v16.3.0
- Correction of BGCF CDR description TS 32.260CR0397
Adds a requirement that, if priority is supported, priority treatment is adjusted according to the most recently received authorized Resource-Priority header field or backwards indication value.
- “the MGCF shall adjust the priority treatment of transactions or dialogs according to the most recently received authorized Resource-Priority header field or backwards indication value” TS 24.229 v17.19.0
Defining Specifications
3GPP specifications that define or reference BGCF, 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.806 v700 | Voice Call Continuity between CS and IMS | Rel-7 read |
| TS 23.815 v500 | IMS Charging Implications | Rel-5 read |
| TS 24.228 v590 | IP Multimedia Call Control Signaling Flows | Rel-5 read |
| TS 24.229 vk10 | IMS SIP/SDP Call Control Protocol | Rel-20 read |
| TS 24.407 v830 | OIP and OIR Simulation Services Protocol | Rel-8 read |
| TS 24.416 v700 | Malicious Call Identification Service | 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.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.524 vj00 | Hosted Enterprise Services Architecture | Rel-19 read |
| TS 24.529 v820 | Explicit Communication Transfer (ECT) Simulation Service | Rel-8 read |
| TS 24.802 vc10 | II-NNI Traversal Scenario Determination | Rel-12 read |
| TR 26.944 vj00 | QoE, ESQoS and SQoS metrics for 3G multimedia services | Rel-19 read |
| TS 28.702 vj00 | Core Network NRM IRP Information Service | Rel-19 read |
| TS 28.705 vj00 | IMS NRM IRP Information Service | Rel-19 read |
| TS 29.162 vj00 | IMS-IP Network Interworking | Rel-19 read |
| TS 29.163 vj00 | Interworking between 3GPP IM CN and CS networks | 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.421 v810 | IMS Interworking with External IP Networks | 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.272 vj00 | Charging for Push-to-Talk over Cellular (PoC) | Rel-19 read |
| TS 32.409 vj00 | IMS Performance Management Measurements | Rel-19 read |
| TS 32.422 vk30 | Trace, MDT and UE Measurement Control | Rel-20 read |
| TS 32.632 vb00 | Core Network Resources NRM | Rel-11 read |
| TS 32.732 vb00 | IMS Network Resource Model Information Service | Rel-11 read |