Description
Error Correction Mode (ECM) is a protocol mechanism designed to ensure the accurate transmission of facsimile (fax) data over digital mobile networks, as defined in 3GPP specifications. It operates during a fax session by breaking the transmitted page data into smaller blocks, typically of 256 or 64 octets, depending on the implementation. Each data block is accompanied by a Frame Check Sequence (FCS) for error detection. The receiving fax terminal checks the FCS upon receipt; if an error is detected, it signals the transmitting terminal to retransmit that specific block. This process continues until all blocks are received correctly or a maximum retry limit is reached, after which the session may be terminated. ECM is implemented within the T.30 protocol framework for fax over ISDN, adapted for mobile networks through 3GPP's support for fax services over circuit-switched and later packet-switched domains.
Architecturally, ECM functions at the application layer for fax services, interfacing with lower-layer transport protocols provided by the mobile network. In early 3GPP releases (e.g., Rel-5), fax services were primarily supported over circuit-switched connections, such as in GSM or UMTS CS data calls. The network provides a transparent data bearer, and ECM operates end-to-end between the fax terminals, independent of the radio access technology. Key components include the fax terminal's ECM capability negotiation during the T.30 training phase, the block segmentation and reassembly logic, and the retransmission control mechanism. The role of ECM is to mitigate errors introduced by radio channel impairments, network interferences, or handovers, which are common in mobile environments, thereby preventing corrupted fax outputs.
In operation, ECM adds overhead due to block headers and retransmissions, which can increase transmission time but ensures data fidelity. It is particularly important for mobile fax because wireless links are more prone to errors compared to fixed-line connections. 3GPP specifications reference ECM in the context of fax interworking, ensuring compatibility with ITU-T T.30 standards. While fax usage has declined, ECM remains a defined feature for legacy service support and regulatory requirements in some regions. Its inclusion in multiple 3GPP releases underscores the need for reliable real-time communication services over evolving network technologies.
Purpose & Motivation
ECM was created to address the challenge of transmitting facsimile documents reliably over error-prone mobile radio channels. In early mobile networks (e.g., GSM), fax was a critical business service, but radio interference, fading, and handovers could corrupt data, leading to unreadable fax pages. Without error correction, fax transmissions over mobile links were often unreliable, limiting the adoption of mobile fax services. ECM solves this by implementing a robust error detection and retransmission scheme, ensuring document integrity similar to fixed-line fax.
The historical context stems from the ITU-T T.30 standard for fax over PSTN/ISDN, which included ECM for error control. 3GPP adopted and adapted this for mobile networks to maintain interoperability with existing fax machines and networks. Prior approaches, like basic fax modes without ECM, suffered from high error rates in mobile environments, causing frequent failed transmissions or garbled outputs. ECM provided a standardized method to mitigate these issues, enabling viable mobile fax services as part of 3GPP's circuit-switched data offerings.
ECM's motivation also lies in supporting legacy services during the transition to digital mobile systems, ensuring backward compatibility. It addressed the limitations of previous mobile data services that lacked application-layer error correction for real-time fax. By incorporating ECM, 3GPP facilitated reliable fax over 2G, 3G, and beyond, meeting regulatory and business needs for document transmission in sectors like healthcare and law, where fax remained entrenched.
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (352 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-5, normative work from Rel-15.
In Release 15, corrections were made to the ECM function to clarify Power Saving Mode (PRA) reporting procedures specifically when the UE is in the ECM-IDLE state. Additionally, corrections were introduced to address timer inconsistencies within the EMM and to rectify the handling of network policy indications for LTE call redirection to GERAN.
- Service Gap Control feature cleanup and corrections TS 24.301CR3010
- Secondary RAT related data usage reporting corrections TS 23.401CR3327
- Correction on the update of RAN in subscription change TS 23.401CR3342
- Corrections to secondary RAT usage data reporting TS 23.401CR3362
- Correction to Enhanced Coverage restriction TS 23.401CR3372
- Clarification on PRA reporting in ECM-IDLE state TS 23.401CR3381
+ 93 more changes
In Release 16, the ECM function saw corrections and clarifications focused on improving interworking and specific NAS procedures. These included corrections to the TAU (Tracking Area Update) procedure for 5GC interworking and to the establishment of secure exchange of NAS messages for attach. Additionally, corrections were made to UE handling for specific EMM (EPS Mobility Management) causes and to parameters in the registration request message.
- Corrections to Dual Connectivity with NR feature TS 23.401CR3475
- Correction on the number of PDN types stored per APN in the subscription data TS 23.401CR3518
- Correction on support of RACS TS 23.401CR3519
- Some corrections and clarifications on RACS procedure TS 23.401CR3537
- Corrections of PLMN assigned Capability signalling TS 23.401CR3520
- Correction on UCMF event notification for PLMN assigned ID(s) TS 23.401CR3593
+ 74 more changes
In Release 17, the ECM function saw specific corrections to improve reliability and clarity. These included a correction to the UE retry restriction mechanism for specific ESM causes (#50, #51, #57, #58, #61) and a correction to the handling of the service request attempt counter's reset conditions. Additionally, a definitional correction was made for the IMC (IP Multimedia Core network subsystem) regarding terminals accessing IMS via a Standalone Non-Public Network (SNPN).
- Correction of IMC definition for terminals accessing IMS via SNPN TS 21.905CR0122
- Terminologies Correction TS 23.401CR3654
- Correction to MME handling EPS bearer QoS TS 23.401CR3670
- Correction for Restriction of use of Enhanced Coverage TS 23.401CR3681
- Paging priority correction for MPS TS 23.401CR3689
- Correction on MUSIM Paging Cause feature TS 23.401CR3692
+ 48 more changes
In Release 18, the ECM function saw corrections primarily focused on EPS mobility management timers and state handling. Specific updates included refined handling for the T3402 timer when set to zero, corrections to the start condition for the T3440 timer during re-registration indications, and adjustments to configurable attach and TAU retry procedures for certain lower-layer failures. Additionally, corrections were made to the calculation of the mobile reachable timer based on user plane activity.
- MPS when access to EPC is WLAN correction TS 23.401CR3731
- Corrections on Estimated Maximum Wait Time for Discontinuous Coverage for Satellite Access TS 23.401CR3771
- Correction to condition to trigger TAU for local release of PDN connection TS 24.301CR3769
- Correction on capability indication of N1 mode TS 24.301CR3801
- Correction on WUS handling in EPS TS 24.301CR3802
- Correction on setting of UE status IE TS 24.301CR3803
+ 42 more changes
In Release 19, the ECM function saw specific corrections and clarifications related to EPS mobility management and satellite operations. These included corrections for handling the list of PLMNs not allowed at the UE's location, the EPS update result in TAU procedures, and the discontinuous coverage maximum time offset in EPS. Additionally, terminology and procedural corrections were made for Store and Forward Satellite Operation support and for RAT utilization control mechanisms within EPS.
- User data related corrections in data transport TS 24.301CR4446
- Terminology correction and clarification for Store and Forward Satellite Operation TS 23.401CR3849
- Corrections for S&F Support and operation TS 23.401CR3919
- Correction on the cause reason TS 24.301CR4092
- Correction for handling list of PLMNs not allowed to operate at the present UE location TS 24.301CR4085
- Correction on term 4G-GUTI TS 24.301CR4180
+ 65 more changes
Explore further
Broader topics and technologies where ECM plays a role.
Defining Specifications
3GPP specifications that define or reference ECM, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TS 23.401 vj50 | Evolved Packet System (EPS) Stage 2 Description | Rel-19 |
| TS 24.301 vj60 | NAS protocol for Evolved Packet System | Rel-19 |
| TS 24.801 v810 | CT1 SAE NAS Aspects for EPC | Rel-8 |
| TS 33.401 vj10 | EPS Security Architecture | Rel-19 |
| TS 36.300 vj00 | E-UTRAN Radio Interface Protocol Architecture Overview | Rel-19 |
| TS 36.401 vj00 | E-UTRAN Overall Architecture Description | Rel-19 |
| TS 36.420 vj00 | X2 Interface Introduction for E-UTRAN | Rel-19 |