Description
The Forward Access Channel (FACH) is a fundamental downlink transport channel in the UMTS (WCDMA) Radio Access Network (UTRAN). It is a common channel, meaning it is not dedicated to a single user but can be received by multiple User Equipments (UEs) within a cell. The FACH is mapped onto the Secondary Common Control Physical Channel (S-CCPCH) in the physical layer. Its primary role is to carry control signaling from the network to UEs, particularly for procedures that do not warrant the establishment of a dedicated channel (DCH), such as during call setup, response to paging, or cell update procedures. It can also transport small amounts of user plane data, making it suitable for low-rate, bursty packet services.
Architecturally, the FACH is terminated at the Radio Network Controller (RNC). The RNC uses the FACH to communicate with UEs in the Cell_FACH state, one of the several Radio Resource Control (RRC) connection states. In this state, the UE is known to the network on a cell level but does not have a dedicated channel allocated. The FACH is transmitted over the entire cell or a specific sector and does not employ fast power control. Instead, it is typically transmitted at a fixed, relatively high power level to ensure it can be received by UEs at the cell edge, which impacts overall cell capacity if used extensively.
How it works involves addressing. Messages on the FACH contain a UE identifier (like U-RNTI or C-RNTI) so that multiple UEs listening to the same channel can discern which messages are intended for them. When a UE needs to send uplink data or signaling while in Cell_FACH state, it uses the Random Access Channel (RACH) in the uplink, creating a paired FACH/RACH combination for low-activity communication. The FACH plays a critical role in state transitions; for example, when data activity increases, the network may command the UE to transition to the Cell_DCH state using a message sent on the FACH itself. Its design represents a trade-off between signaling overhead, resource allocation efficiency, and UE battery consumption for low-activity devices.
Purpose & Motivation
The FACH was created as a core component of UMTS to efficiently manage radio resources for a large population of mobile devices with varying and often sporadic communication needs. In the circuit-switched dominated 2G world, dedicated channels were the norm for any active connection. For packet data and many signaling scenarios, maintaining a dedicated channel with fast power control for each UE is highly inefficient in terms of code and power resources. The FACH addresses this by providing a shared, always-available downlink path for control and small data bursts.
It solves the problem of how to keep a UE registered and reachable by the network without consuming dedicated resources. It enables the Cell_FACH state, which is a low-overhead but connected state, bridging the gap between idle mode (Cell_PCH, URA_PCH) and high-activity dedicated channel mode (Cell_DCH). This state machine is crucial for battery life optimization and network capacity management. The FACH allows the network to page UEs, deliver broadcast system information, and handle initial access procedures, forming the backbone of connection management in UMTS. Its support for small packet data was particularly important for early always-on mobile data services, allowing efficient transmission of keep-alive messages or small TCP acknowledgements without the latency of establishing a DCH.
Classification
Evolution Across Releases
Introduced as a foundational transport channel in the first UMTS release. Defined its mapping to S-CCPCH, its role in the RRC state machine (Cell_FACH state), and its use for carrying signaling and small data packets. Established the FACH/RACH pair as the primary method for low-activity communication.
Explore further
Broader topics and technologies where FACH plays a role.
Defining Specifications
3GPP specifications that define or reference FACH, 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 25.101 vj00 | UTRA FDD UE RF Requirements | Rel-19 |
| TS 25.171 vj00 | A-GPS Minimum Performance Requirements for UTRA FDD UE | Rel-19 |
| TS 25.202 vj00 | 7.68Mcps TDD Option Technical Specification | Rel-19 |
| TS 25.211 vj00 | UTRA FDD Layer 1: Transport & Physical Channels | Rel-19 |
| TS 25.212 vj00 | UTRA FDD Layer 1 Multiplexing & Channel Coding | Rel-19 |
| TS 25.214 vj00 | UTRA FDD Physical Layer Procedures | Rel-19 |
| TS 25.221 vj00 | UTRA TDD Physical Layer Specification | Rel-19 |
| TS 25.222 vj00 | UTRA TDD Multiplexing & Channel Coding | Rel-19 |
| TS 25.224 vj00 | UTRA TDD Physical Layer Procedures | Rel-19 |
| TS 25.225 vj00 | UTRA TDD Physical Layer Measurements | Rel-19 |
| TS 25.301 vj00 | UE-UTRAN Radio Interface Protocol Architecture | Rel-19 |
| TS 25.302 vj00 | UTRA Physical Layer Services | Rel-19 |
| TS 25.321 vj00 | MAC Protocol Specification for UTRAN | Rel-19 |
| TS 25.322 vj00 | RLC Protocol Specification | Rel-19 |
| TS 25.324 vj00 | Broadcast/Multicast Control Protocol | Rel-19 |
| TS 25.331 vj00 | UTRAN RRC Protocol Specification | Rel-19 |
| TS 25.401 vj00 | UTRAN Overall Architecture | Rel-19 |
| TS 25.402 vj00 | UTRAN Synchronisation Mechanisms | Rel-19 |
| TS 25.420 vj00 | Iur Interface Introduction for UTRAN | Rel-19 |
| TS 25.423 vj00 | UTRAN RNSAP Specification | Rel-19 |
| TS 25.424 vj00 | UTRAN Iur Interface Data Transport & Signalling | Rel-19 |
| TS 25.425 vj00 | UTRAN Iur Interface User Plane Protocols | Rel-19 |
| TS 25.430 vj00 | Introduction to Iub Interface Specifications | Rel-19 |
| TS 25.433 vj00 | Node B Application Part (NBAP) Protocol | Rel-19 |
| TS 25.434 vj00 | UTRAN Iub Interface Data Transport and Signalling | Rel-19 |
| TS 25.865 va00 | Distributed Antenna Enhancements for TDD | Rel-10 |
| TR 25.931 vj00 | UTRAN Signalling Procedures Examples | Rel-19 |
| TS 37.320 vj00 | Minimization of Drive Tests (MDT) Overview | Rel-19 |