ATCF

Access Transfer Control Function

Core Network →
Introduced in Rel-10 Also in: Services

ATCF is a 3GPP network element that anchors a call in the IMS to manage seamless access transfer between different networks, such as circuit-switched and packet-switched domains.

Category
Core Network
Introduced
Rel-10
Where
Core Network › Evolved Packet Core
Also touches
1 segments
Specifications
14 specs
ATCF Description Purpose Related Classification Detected Changes Specifications

Description

The Access Transfer Control Function (ATCF) is a critical component in 3GPP's IP Multimedia Subsystem (IMS) architecture, specifically designed to facilitate Voice Call Continuity (VCC) and Single Radio Voice Call Continuity (SRVCC) operations. Functionally positioned as a Session Border Controller (SBC) within the IMS core, the ATCF serves as an anchor point for media and signaling during active voice sessions. When a user equipment (UE) initiates or receives a voice call, the ATCF becomes the fixed point in the IMS network that handles all subsequent access transfers, ensuring that the remote party remains unaware of any underlying network changes.

Architecturally, the ATCF consists of two main components: the Access Transfer Control Function itself and the Access Transfer Gateway (ATGW). The ATCF handles the signaling plane, managing SIP session control and coordinating with other IMS elements like the Serving-Call Session Control Function (S-CSCF) and the Access Transfer Signaling Function (ATSF). The ATGW operates in the media plane, anchoring the media path and performing necessary media interworking functions. This separation allows for efficient handling of both control and user plane operations during complex handover scenarios.

During operation, the ATCF implements several key procedures. When a UE registers with the IMS network, the S-CSCF identifies the need for SRVCC capability and selects an appropriate ATCF. The ATCF then inserts itself into the signaling path and establishes the ATGW in the media path. During an active voice call, if the UE detects deteriorating LTE coverage and needs to handover to a 2G/3G circuit-switched network, the ATCF coordinates with the Mobility Management Entity (MME) and Mobile Switching Center (MSC) to execute the SRVCC procedure. It manages the session transfer, updates the remote party's media path to point to the ATGW, and ensures no media interruption occurs during the transition.

The ATCF interfaces with numerous network elements through standardized reference points. Key interfaces include the Mw interface with the S-CSCF for SIP signaling, the I2 interface with the MSC Server for SRVCC coordination, and internal interfaces between the ATCF and ATGW components. It also interacts with the Policy and Charging Rules Function (PCRF) for quality of service management and with the Home Subscriber Server (HSS) for subscriber data. This comprehensive integration enables the ATCF to maintain session continuity while preserving security, charging, and policy enforcement across different access technologies.

Purpose & Motivation

The ATCF was created to address the critical challenge of maintaining voice call continuity during handovers between different radio access technologies, particularly as operators began deploying LTE networks alongside existing 2G and 3G infrastructure. Before SRVCC and ATCF were standardized, voice calls on LTE (using VoLTE) would simply drop when users moved out of LTE coverage areas, creating a poor user experience and limiting operator ability to migrate voice services to packet-switched networks. The ATCF provides the necessary anchoring function to enable seamless transitions without call drops.

Historically, the development of ATCF was motivated by the industry's transition to all-IP networks and the need to maintain voice service quality during this migration. Early LTE deployments lacked circuit-switched fallback capabilities, making voice services unreliable in areas with patchy LTE coverage. The ATCF, introduced in 3GPP Release 10 as part of the enhanced SRVCC (eSRVCC) solution, solved this by providing a stable anchor point in the IMS core that could manage the complex signaling and media path updates required during access transfers.

The ATCF addresses several limitations of previous approaches. Initial SRVCC implementations in Release 8 had longer interruption times during handovers because they required signaling all the way back to the remote party's network. The ATCF localizes this signaling by anchoring the session closer to the user, significantly reducing handover interruption times from potentially hundreds of milliseconds to under 300 milliseconds. This improvement made SRVCC practically viable for maintaining voice quality during network transitions, enabling operators to confidently deploy VoLTE services while leveraging their existing circuit-switched networks for coverage.

Classification

Part ofCSCF
Related approachesSRVCCIMSATGW

Detected Changes Across Releases

from 3GPP Change Requests

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

Studied in Rel-10, normative work from Rel-15.

Rel-15 1 change

In Release 15, the ATCF's functionality was extended to support the SRVCC session transfer of an IMS emergency session during the early dialogue phase. This specifically enables PS to CS access transfer for emergency calls while the UE is in the pre-alerting state, where it can receive early media. The enhancement ensures service continuity for IMS emergency sessions from the initial call setup phase.

  • PS to CS SRVCC for IMS emergency session in early dialogue phase TS 23.237CR0504
Rel-16 5 changes

In Release 16, the ATCF-related enhancements primarily focused on supporting emergency call continuity into and within 5G systems. This included the formal introduction of 5G SRVCC procedures and enabling SRVCC for IMS emergency sessions transferred to EPS. Furthermore, the release introduced support for multiple EATF instances to handle emergency SRVCC scenarios.

  • Introduction of support of multiple EATF instances in Emergency SRVCC procedures TS 23.237CR0509
  • Completing introducing of 5G SRVCC TS 23.237CR0510
  • Corrections on ATCF TS 23.237CR0514
  • Enabling SRVCC for emergency call transferred to EPS TS 23.237CR0512
  • P-CSCF restoration in 5GS TS 29.165CR0995

Explore further

Broader topics and technologies where ATCF plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.237 vj00 IMS Service Continuity (ISC) Stage 2 Rel-19
TS 23.334 vj00 IMS-ALG to IMS-AGW Interface (Iq) Stage 2 Rel-19
TS 24.229 vj50 IMS call control protocol based on SIP and SDP Rel-19
TS 24.802 vc10 IMS II-NNI Traversal Scenario Determination Study Rel-12
TS 26.114 vj10 IMS Multimedia Telephony Media Handling 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.238 vj00 H.248 Profile for IBCF-TrGW Interface Rel-19
TS 29.334 vj00 IMS-ALG to IMS-AGW Interface Protocol Rel-19
TS 29.806 vc10 P-CSCF Restoration Analysis & Solutions Rel-12
TR 29.949 vj00 VoLTE IMS Roaming Architecture & Procedures Rel-19
TS 32.250 vj00 Circuit Switched Offline Charging Rel-19
TS 32.260 vj10 IMS Charging Management Rel-19
TS 32.850 ve00 IMS Charging Correlation Methods Study Rel-14