Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Core Network

ATCF

Access Transfer Control Function

Core Network →

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.

Introduced
Rel-10
Where
Core Network › Evolved Packet Core
Specifications
14 specs
Also in
Services, Management
ATCF Description Purpose What changed Family Neighbours 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.

What changed in its specifications

The latest release-to-release comparison of specifications that define ATCF. Each summary describes the whole specification, not only this term.

TS 23.237Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 23.237: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 23.237 →
TS 23.334Rel-17 → Rel-18

Rel-18 adds IVAS codec handling clauses, references to IVAS specifications, a definition, and modifies EVS max-red parameter selection.

Full comparison in TS 23.334 →

Technology family

Voice service evolution · Services › IMS

  1. R96 CS voice
  2. Rel-8 1xCSFB, CSFB, ICS, SRVCC
  3. Rel-9 VoLTE
  4. Rel-10 SRVCC enhanced with ATCF
  5. Rel-11 CS to PS SRVCC, vSRVCC
  6. Rel-12 DRVCC
  7. Rel-15 Emergency Services Fallback, EPS fallback, VoNR
  8. Rel-16 5G-SRVCC
  • ATCF builds on SRVCC
    “When (5G-)SRVCC enhanced with ATCF is used, an Access Transfer Control Function (ATCF) and an Access Transfer Gateway (ATGW) may be used in the serving network (visited if roaming).” TS 23.237

IMS functions · Services › IMS

  1. R99 OSA-SCS
  2. Rel-5 AS, BGCF, CSCF, I-CSCF, IM-MGW, IM-SSF, MGCF, MRFC, MRFP, P-CSCF, S-CSCF
  3. Rel-6 IBCF, IMS-ALG, TrGW
  4. Rel-7 E-CSCF, IMS-AGW
  5. Rel-8 MRB, SCC AS
  6. Rel-9 EATF
  7. Rel-10 ATCF, ATGW
  • ATCF used together with ATGW
    “The Access Transfer Gateway (ATGW) is controlled by the ATCF” TS 23.237
  • ATCF used together with SCC AS
    “IMS Service Continuity requires a Service Centralization and Continuity (SCC) AS, which is an Application Server as described in TS 23.228 [4], and a UE with SC capabilities. When (5G-)SRVCC enhanced with ATCF is used, an Access Transfer Control Function (ATCF) and an Access Transfer Gateway (ATGW) may be used in the serving network” TS 23.237
  • ATCF coexists with P-CSCF
    “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
  • ATCF coexists with IBCF
    “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 sources

Documented changes in 6 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.

Rel-10 introduced

The ATCF is specified for the first time as an IMS node that anchors sessions, allocates the STN-SR, and acts as proxy or UA to support SRVCC enhanced with ATCF.

  • “a routable STN-SR pointing to the ATCF shall be provided to the MME before SRVCC procedure is triggered.” TS 23.237 v10.13.0
  • “An ATCF shall support both the ATCF (proxy) role and the ATCF (UA) role.” TS 24.229 v10.29.0
  • “The ATCF/ATGW functions may be supported by the IMS-ALG/IMS-AGW when SRVCC enhanced with ATCF is used.” TS 23.334 v10.5.0
Rel-11 1 CR

SRVCC enhanced with ATCF was extended: the ATCF gained an ATCF management URI, video media anchoring, priority handling of access transfer, and SCC AS informing it of UE SRVCC capability.

  • “Additionally to the STN-SR, the ATCF allocates an ATCF management URI that can be used by SCC AS to address the ATCF directly.” TS 23.237 v11.11.0
  • “ATCF may provide priority handling if the Access Transfer message contains priority indication.” TS 23.237 v11.11.0
  • Correction of Access Transfer Information handling for ATCF TS 23.237CR0370
Rel-12 1 CR

ATCF behaviour changed: new image-size negotiation (a=imageattr) procedures for the IMS-ALG (ATCF) and IMS-AGW (ATGW), plus a correction preventing the ATCF's STN-SR from being overwritten on registration.

  • “The IMS-ALG (ATCF) and the IMS-AGW (ATGW) may support a media-level SDP image attribute "a=imageattr" defined in IETF RFC 6236 [24]” TS 23.334 v12.13.0
  • Correction to avoid the ATCF's STN-SR to be overwritten when a registration over I2 or non-3GPP access occurs TS 23.237CR0448
  • “The list of image sizes per payload type supported by the IMS-AGW (ATGW) shall be preconfigured in the IMS-ALG (ATCF).” TS 23.334 v12.13.0
Rel-13 specification text

Charging specification for ATCF extended: ICID correlation with Related ICID, Access Transfer Type/Inter-UE Transfer and Access Transfer Information reporting by AS and ATCF, and OneChargingSession preserving the original ICID in the ATCF CDR.

  • “when OneChargingSession is applied in the SCC AS and the ATCF, the ICID of the original access leg is preserved in the AS/ATCF CDR” TS 32.260 v13.9.0
  • “the Access Network Information, Additional Access Network Information and Cellular Network Information shall be provided by the AS and ATCF together with transfer parameters” TS 32.260 v13.9.0
  • “in offline and online charging of the AS and in offline charging of the ATCF the Access Transfer Type parameter provides information on the used access technologies” TS 32.260 v13.9.0
Rel-14 specification text

ATCF now takes the MSC Supported Codec List into account during SRVCC, selects the codec for the MSC-IMS interface, and initiates transcoding or codec-mode modification signalling towards the remote end.

  • “ATCF takes the MSC Preferred Codec List (indicated by MSC Server in the Initiation of Session Transfer as defined in TS 23.216 [10]) into account” TS 23.237 v14.2.0
  • “The ATCF compares the IMS Selected Codec with the Codecs of the MSC Supported Codec List” TS 23.237 v14.2.0
  • “it is up to the ATCF to initiate a SIP REINVITE to modify the IMS Selected Codec towards the remote end” TS 23.237 v14.2.0
Rel-16 specification text

ATCF is now also included in the session control plane, and STN-SR now also indicates the ATCF, when 5G-SRVCC is used, not only for (v)SRVCC enhanced with ATCF.

  • “When (v)SRVCC enhanced with ATCF is used or when 5G-SRVCC is used, the ATCF is included in the session control plane” TS 23.237 v16.4.0
  • “routing number indicating the SCC-AS or the ATCF if SRVCC enhanced with ATCF or if 5G-SRVCC is used” TS 23.237 v16.4.0

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 read
TS 23.334 vj00 IMS-ALG to IMS-AGW Interface (Iq) Stage 2 Rel-19 read
TS 24.229 vk10 IMS SIP/SDP Call Control Protocol Rel-20 read
TS 24.802 vc10 II-NNI Traversal Scenario Determination Rel-12 read
TS 26.114 vk11 IMS Multimedia Telephony Client Rel-20 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.238 vj00 H.248 Profile for IBCF-TrGW Interface Rel-19 read
TS 29.334 vj00 IMS-ALG to IMS-AGW Interface Protocol Rel-19 read
TS 29.806 vc10 P-CSCF Restoration Analysis & Solutions Rel-12 read
TR 29.949 vj00 VoLTE IMS Roaming Architecture & Procedures Rel-19 read
TS 32.250 vj00 Circuit Switched Offline Charging Rel-19 read
TS 32.260 vk10 IMS Charging Management Rel-20 read
TS 32.850 ve00 IMS Charging Correlation Methods Study Rel-14 read