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.
Key Features
- Common downlink transport channel for multiple UEs
- Mapped to the S-CCPCH physical channel
- Supports UEs in Cell_FACH RRC state
- Carries both control plane signaling and small user data packets
- Operates without fast (closed-loop) power control
- Uses UE-specific identifiers for message addressing
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.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 25.101 | 3GPP TS 25.101 |
| TS 25.171 | 3GPP TS 25.171 |
| TS 25.202 | 3GPP TS 25.202 |
| TS 25.211 | 3GPP TS 25.211 |
| TS 25.212 | 3GPP TS 25.212 |
| TS 25.214 | 3GPP TS 25.214 |
| TS 25.221 | 3GPP TS 25.221 |
| TS 25.222 | 3GPP TS 25.222 |
| TS 25.224 | 3GPP TS 25.224 |
| TS 25.225 | 3GPP TS 25.225 |
| TS 25.301 | 3GPP TS 25.301 |
| TS 25.302 | 3GPP TS 25.302 |
| TS 25.321 | 3GPP TS 25.321 |
| TS 25.322 | 3GPP TS 25.322 |
| TS 25.324 | 3GPP TS 25.324 |
| TS 25.331 | 3GPP TS 25.331 |
| TS 25.401 | 3GPP TS 25.401 |
| TS 25.402 | 3GPP TS 25.402 |
| TS 25.420 | 3GPP TS 25.420 |
| TS 25.423 | 3GPP TS 25.423 |
| TS 25.424 | 3GPP TS 25.424 |
| TS 25.425 | 3GPP TS 25.425 |
| TS 25.430 | 3GPP TS 25.430 |
| TS 25.433 | 3GPP TS 25.433 |
| TS 25.434 | 3GPP TS 25.434 |
| TS 25.865 | 3GPP TS 25.865 |
| TS 25.931 | 3GPP TS 25.931 |
| TS 37.320 | 3GPP TR 37.320 |