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

Glossary term · Services

ECT

Explicit Communication Transfer

Services →

ECT is a supplementary service in 3GPP networks that allows a user to explicitly transfer an ongoing communication, such as a voice call, to a third party in a controlled and signaled manner.

Introduced
Rel-5
Where
Services › Codecs
Specifications
43 specs
ECT Description Purpose What changed Neighbours Detected Changes Specifications

Description

Explicit Communication Transfer (ECT) is a standardized supplementary service within the 3GPP framework that enables a served user (User A) to transfer an established communication (typically a speech call) to another party (User C). The process is 'explicit' because it involves active user invocation and in-call signaling, rather than an automatic or pre-defined diversion. Architecturally, ECT relies on the call control and session management functions in the core network, specifically in the MSC server for CS calls or the IMS core for IP-based calls. The key components involved are the transferring user's terminal, the network's service control logic, and the target user's terminal. The service operates through a defined procedure: User A, engaged in a call with User B, may place B on hold, establish a new call or consultation call to User C, and then explicitly issue a transfer request. The network then connects User B and User C directly, releasing User A from the connection. ECT can be implemented as a 'blind transfer' (immediate transfer without consultation) or a 'consultative transfer' (consultation with the third party first). Its role is to provide advanced call handling capabilities, facilitating features like call forwarding on busy or no answer in a more dynamic, user-controlled manner. The service is detailed across numerous 3GPP specifications covering CS core (TS 24.083) and IMS (TS 24.604), defining the protocols (like ISUP, SIP) and timers required for interoperable implementation.

Purpose & Motivation

ECT was developed to address the need for flexible, user-initiated call management beyond basic call forwarding settings configured in advance. Prior to its standardization, call transfer capabilities were often proprietary or limited to specific PBX systems, hindering interoperability across different network operators and terminal types. The creation of ECT provided a uniform, network-controlled mechanism that works across multi-vendor, multi-operator environments. It solved the problem of efficiently redirecting calls in professional and personal contexts—for example, transferring a customer call to a specialist or redirecting a call to a mobile phone when leaving an office. The historical context includes its definition in early GSM standards and its subsequent evolution into the IP Multimedia Subsystem (IMS), ensuring service continuity as networks migrated to all-IP architectures. ECT addresses limitations of implicit or network-centric transfers by giving the transferring user explicit control over the process.

What changed in its specifications

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

TR 21.905Rel-17 → Rel-18

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

Full comparison in TR 21.905 →
TS 22.173Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 22.173: 1 clause changed, with no change attributed to a release feature.

Full comparison in TS 22.173 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 1 change
  • Interaction between ECT and "Enhanced calling name" service TS 24.629CR0038
Rel-18 1 change
  • MPS priority for ECT supplementary service TS 24.629CR0040
Rel-19 1 change
  • ECT corrections: AS serving the transferee and blind call flow TS 24.186CR0067

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 22.173 vl00 IMS Multimedia Telephony Service Rel-21 read
TS 22.273 v710 IMS Multimedia Telephony with PSTN/ISDN Simulation Rel-7 read
TS 22.401 v800 Videotelephony over TISPAN NGN Requirements Rel-8 read
TS 23.806 v700 Voice Call Continuity between CS and IMS Rel-7 read
TS 24.173 vj00 Multimedia Telephony Service and Supplementary Services in IMS Rel-19 read
TS 24.186 vk10 IMS Data Channel and AR Communication Rel-20 read
TS 24.196 vj00 Enhanced Calling Name (eCNAM) Stage 3 Protocol Rel-19 read
TS 24.292 vj00 IMS Centralized Services (ICS) Protocol Rel-19 read
TS 24.315 vj00 Operator Determined Barring (ODB) for IMS Rel-19 read
TS 24.404 v750 Communication Diversion Services Stage 3 Rel-7 read
TS 24.405 v700 Conference Service Protocol Description Rel-7 read
TS 24.406 v810 Message Waiting Indication (MWI) Protocol Rel-8 read
TS 24.410 v810 Protocol Description of HOLD Services Rel-8 read
TS 24.411 v830 3GPP TS 24411 v830: Anonymous Communication Rejection and Communication Barring 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.447 v800 Advice Of Charge (AOC) Service Protocol Rel-8 read
TS 24.454 v840 Closed User Group (CUG) Protocol Specification Rel-8 read
TS 24.504 v8m0 Communication Diversion (CDIV) Protocol Specification Rel-8 read
TS 24.505 v810 Protocol Description of the Conference Service Rel-8 read
TS 24.516 v830 MCID Protocol Specification for NGN Rel-8 read
TS 24.529 v820 Explicit Communication Transfer (ECT) Simulation Service Rel-8 read
TS 24.604 vj00 Communications Diversion (CDIV) Protocol Spec Rel-19 read
TS 24.605 vj00 3GPP CONF Service Protocol Specification Rel-19 read
TS 24.606 vj00 MWI Service Protocol Description Rel-19 read
TS 24.610 vj00 Communication Hold (HOLD) Service Protocol Rel-19 read
TS 24.611 vj00 Anonymous Communication Rejection & Barring Rel-19 read
TS 24.616 vj00 Malicious Call Identification (MCID) Protocol Rel-19 read
TS 24.629 vj00 Explicit Communication Transfer (ECT) Protocol Rel-19 read
TS 24.642 vj00 CCBS/CCNR/CCNL SIP Protocol Specification Rel-19 read
TS 24.647 vj00 Advice of Charge (AOC) service protocol Rel-19 read
TS 24.654 vj00 Closed User Group (CUG) supplementary service Rel-19 read
TS 26.114 vk11 IMS Multimedia Telephony Client Rel-20 read
TS 26.804 vk10 5G Media Delivery Architecture Extensions Rel-20 read
TS 29.165 vk00 Inter-IMS Network-to-Network Interface (II-NNI) Rel-20 read
TS 29.292 vj00 IMS Centralized Services (ICS) Interworking Rel-19 read
TS 29.364 vj10 IMS AS Service Data Descriptions Rel-19 read
TS 29.864 v801 Application Server Service Data Definition for IMS Telephony Rel-8 read
TS 32.275 vj00 MMTel Charging Specification Rel-19 read
TS 32.850 ve00 IMS Charging Correlation Methods Study Rel-14 read
TS 33.107 vj00 Lawful Interception Architecture & Functions Rel-19 read
TS 36.750 ve10 Study on enhancement of VoLTE Rel-14 read