Description
The Emergency Access Transfer Function (EATF) is a critical functional entity within the IP Multimedia Subsystem (IMS) for emergency services. Its primary role is to manage and facilitate the transfer of an ongoing emergency session (e.g., an IMS emergency call) from one access network to another, or between different domains within the core network, while maintaining the session's emergency context and connection to the appropriate Public Safety Answering Point (PSAP). The EATF acts as an anchor point for the emergency session. When a User Equipment (UE) with an active emergency call initiates a handover—for instance, moving from LTE to Wi-Fi, or between 3GPP and non-3GPP access—the EATF ensures the signaling and media paths are re-established without dropping the call.
Architecturally, the EATF interacts with several IMS core functions. It typically interfaces with the Proxy-Call Session Control Function (P-CSCF), which is the first contact point for the UE in IMS, and the Serving-Call Session Control Function (S-CSCF), which handles session control. During an emergency session establishment, the P-CSCF may identify the call as an emergency and involve the EATF. The EATF then inserts itself into the signaling path, often becoming a back-to-back user agent (B2BUA). This allows it to maintain control over both legs of the call: one leg towards the UE and the other towards the PSAP. It manages the session descriptors and can hold multiple alternative media addresses for the UE.
How it works involves continuous monitoring and proactive management. The EATF is aware of the UE's access capabilities and registration status. When a handover condition is detected or initiated (e.g., via network or UE indications), the EATF coordinates the transfer. It may use mechanisms like the Session Initiation Protocol (SIP) re-INVITE or REFER methods to update the session parameters on the PSAP side while the UE re-establishes connectivity via the new access. This process is designed to be seamless, minimizing interruption to the emergency communication. The EATF also plays a role in emergency call back; if a PSAP needs to call back a UE that initiated an emergency session, the EATF can assist in routing the callback to the UE's current location and access type.
Purpose & Motivation
The EATF was introduced to solve a critical problem in IMS-based emergency services: maintaining emergency call continuity during access mobility. Prior to its standardization, emergency calls established over one type of access (e.g., LTE) would likely drop if the user moved to another coverage area using a different technology (e.g., Wi-Fi or a legacy circuit-switched network). This was unacceptable for life-critical communications. The evolution towards all-IP networks and the increasing support for voice over non-3GPP access (like Wi-Fi) created a complex mobility landscape that traditional emergency service architectures could not handle.
Its creation in 3GPP Release 9 was motivated by regulatory requirements for reliable emergency services and the industry's move to IMS as the sole platform for voice and communication services. The EATF addresses the limitations of previous, access-specific emergency solutions by providing a centralized, access-agnostic function within the IMS core. It ensures that the emergency service context (like the PSAP connection and call priority) is preserved across network boundaries. This is essential not only for user mobility but also for network resilience scenarios, such as transferring emergency sessions during a core network node failure or when a UE's primary radio access deteriorates.
What changed in its specifications
The latest release-to-release comparison of specifications that define EATF. Each summary describes the whole specification, not only this term.
Rel-18 adds signal level Enhanced Network Selection, covering emergency-session and eCall-over-IMS behaviour for UEs in limited service state, tied to the ims-EmergencySupport broadcast bit. The overview lists only this one feature, so no further items can be named from the provided material.
Full comparison in TS 23.167 →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 →Technology family
IMS functions · Services › IMS
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 7 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 EATF is defined for the first time in Rel-9 as an IMS function that anchors emergency sessions as a B2BUA and performs PS-to-CS access transfer via E-STN-SR.
- “The Emergency Access Transfer Function (EATF) provides IMS-based mechanisms for enabling service continuity of IMS emergency sessions.” TS 23.237 v9.10.0
- “the EATF shall store the SIP INVITE request until the session is terminated, anchor the session and act as specified for a routeing B2BUA” TS 24.237 v9.20.0
- “the EATF sends an Accounting-Request with Accounting-Record-Type indicating START_RECORD to record start of an EATF CDR” TS 32.260 v9.20.0
For emergency sessions the EATF, rather than the SCC AS, handles source access leg release and the SIP 503 BYE handling, with an operator-specific timer before releasing the source leg.
- “For emergency sessions, the UE and the EATF shall initiate the Session Release procedure when the switch to the Target Access Leg is complete.” TS 23.237 v10.13.0
- “after an operator specific timer has expired, the EATF shall release the source access leg” TS 24.237 v10.20.0
For EATF charging, an alternative OneChargingSession case is added where the EATF sends an INTERIM_RECORD to update the existing EATF CDR for the IMS session instead of starting a new CDR.
- “Alternatively, when “OneChargingSession”, the EATF sends an Accounting-Request with Accounting-Record-Type indicating INTERIM_RECORD to record modification of EATF CDR” TS 32.260 v11.19.0
EATF procedures and requirements were modified: the EATF's access-transfer handling in 24.237 was revised, and 24.229 profile tables now list EATF with updated support conditions, including a new eP-CSCF in its trust domain.
- “When the EATF receives SIP re-INVITE request(s) from the SC UE containing the Reason header field with the protocol value "SIP"” TS 24.237 v12.14.0
- “Upon release of old access leg, the EATF sends an Charging Data Request[Stop] to record stop of the EATF CDR for old access leg Call-ID #1.” TS 32.260 v12.13.0
- “IBCF (IMS-ALG), ISC gateway function (IMS-ALG), EATF, ATCF (UA), MSC server enhanced for DRVCC using SIP interface.” TS 24.229 v12.27.0
The EATF gained new behaviour in Rel-14: PS to CS DRVCC for emergency sessions via E-STN-DR, plus SRVCC support for eCall over IMS.
- “the EATF supports PS to CS DRVCC for emergency session;” TS 24.237 v14.7.0
- “When supporting PS to CS DRVCC for IMS emergency, the EATF provides the following functions:” TS 23.237 v14.2.0
- Support for SRVCC of eCall over IMS at the EATF TS 24.237CR1259
EATF now supports PS to CS SRVCC for originating emergency sessions in alerting and pre-alerting phase, inserting the g.3gpp.ps2cs-srvcc-orig-pre-alerting feature-capability indicator in the 200 OK response.
- “the EATF shall insert a Feature-Caps header field as described in RFC 6809 [60] with the g.3gpp.ps2cs-srvcc-orig-pre-alerting feature-capability indicator” TS 24.237 v15.6.0
- “the EATF supports the PS to CS SRVCC for originating emergency sessions in alerting phase according to operator policy” TS 24.237 v15.6.0
Emergency SRVCC procedures were extended to support multiple EATF instances, with I-CSCF forking INVITEs to each EATF and each EATF checking for a matching transferable session.
- “The I-CSCF creates multiple INVITE transactions: one INVITE per configured EATF instance.” TS 23.237 v16.4.0
- “Each EATF instance checks whether the equipment identifier matches with any transferable session:” TS 23.237 v16.4.0
- Introduction of support of multiple EATF instances in Emergency SRVCC procedures TS 23.237CR0509
Defining Specifications
3GPP specifications that define or reference EATF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.167 vk10 | IMS Emergency Services | Rel-20 read |
| TS 23.237 vj00 | IMS Service Continuity (ISC) Stage 2 | Rel-19 read |
| TS 24.229 vk10 | IMS SIP/SDP Call Control Protocol | Rel-20 read |
| TS 24.237 vj00 | IMS Service Continuity Protocol Details | Rel-19 read |
| TR 29.949 vj00 | VoLTE IMS Roaming Architecture & Procedures | 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 |