FECN

Forward Explicit Congestion Notification

Core Network
Introduced in Rel-8
A congestion control mechanism used in Frame Relay networks, standardized by 3GPP for the Gb interface between the BSS and SGSN in 2G/GSM and GPRS networks. It is a bit in the Frame Relay header set by a congested network node to notify the receiving end of congestion in the forward direction.

Description

Forward Explicit Congestion Notification (FECN) is a flow control feature of the Frame Relay protocol, which was adopted as the layer 2 data link technology for the Gb interface in 2G/GSM and GPRS core networks. The Gb interface connects the Base Station System (BSS), comprising BTSs and BSCs, to the Serving GPRS Support Node (SGSN). FECN operates within the Frame Relay header of each frame. It is a single-bit field that can be set to '1' by any intermediate Frame Relay switch (or the network) experiencing congestion along the path from source to destination. When set, it explicitly signals to the frame's destination endpoint (e.g., the SGSN or BSS) that congestion was encountered in the forward direction of this particular virtual circuit.

Architecturally, the Gb interface uses Frame Relay Permanent Virtual Circuits (PVCs) to carry signaling and user data packets between the BSS and SGSN. Network elements like Frame Relay switches monitor buffer levels and link utilization. Upon detecting congestion—such as queue lengths exceeding a threshold—a switch sets the FECN bit in the header of frames passing through the congested resource. The receiving end (e.g., SGSN) processes this bit. According to 3GPP specifications, the primary reaction to a FECN indication is to potentially invoke higher-layer flow control mechanisms. For instance, the SGSN might reduce the window size for the BSSGP (BSS GPRS Protocol) or trigger LLC (Logical Link Control) flow control to throttle the source's data rate indirectly.

How it works is integral to the Frame Relay's lightweight approach to congestion management. Unlike TCP's implicit congestion detection via packet loss, FECN provides an explicit, early notification. When the destination receives a frame with FECN=1, it typically echoes this notification back to the original source using the Backward Explicit Congestion Notification (BECN) bit in frames traveling in the reverse direction. This informs the source (e.g., BSS) to slow its transmission rate. In the 3GPP Gb interface context, the SGSN, upon receiving FECN, may also use BSSGP or other GPRS-specific protocols to regulate traffic flow from the network towards the BSS and ultimately the mobile station. This helps prevent packet loss in the core network, maintaining quality of service for GPRS data services.

Purpose & Motivation

FECN exists to manage congestion in connection-oriented, packet-switched data networks like Frame Relay, which was chosen for the Gb interface due to its efficiency and suitability for bursty data traffic in 2.5G GPRS. The core problem it addresses is network resource contention without the overhead of per-connection acknowledgments or complex retransmission schemes. In early data services, preventing congestion collapse was critical for maintaining service availability. FECN provides a simple, explicit signal that congestion is occurring, allowing endpoints to react proactively before buffers overflow and packets are dropped.

The historical context is the evolution from circuit-switched GSM to packet-switched GPRS. The Gb interface needed a cost-effective, reliable layer 2 technology. Frame Relay, widely deployed in wide area networks, offered statistical multiplexing and committed information rates. However, its minimal error checking and lack of built-in congestion control required mechanisms like FECN/BECN. 3GPP standardized its use to ensure interoperable congestion management between BSS and SGSN equipment from different vendors. This was crucial for the commercial success of GPRS, as it allowed networks to handle increasing data traffic without degrading voice services sharing the same infrastructure.

FECN solves the limitation of implicit congestion control, which relies on packet loss as an indicator—a poor method for time-sensitive or loss-sensitive traffic. By providing an explicit notification, it enables faster and more precise traffic shaping. It allows the network to communicate its state directly, facilitating more stable operation and efficient use of the Gb interface bandwidth. While later 3GPP technologies (Iu-PS, S1-U) moved to IP-based transport, FECN remains a key part of the legacy GPRS/EDGE network architecture, ensuring backward compatibility and reliable operation for millions of 2G data devices still in use.

Key Features

  • Single-bit indicator in the Frame Relay header for explicit congestion signaling
  • Set by congested network nodes (Frame Relay switches) on the forward path
  • Used specifically on the Gb interface between BSS and SGSN in 2G/GPRS networks
  • Triggers flow control responses in higher-layer protocols like BSSGP or LLC
  • Works in conjunction with Backward Explicit Congestion Notification (BECN)
  • Provides early congestion avoidance to reduce packet loss in the core network

Evolution Across Releases

Rel-8 Initial

Specified the use of Frame Relay and the FECN mechanism for the Gb interface as part of the GSM/GPRS standards consolidation. Defined how the SGSN and BSS should interpret and react to FECN bits for congestion control, integrating it with the BSS GPRS Protocol (BSSGP) management procedures.

Defining Specifications

SpecificationTitle
TS 48.016 3GPP TR 48.016