Description
The F1-C interface is a critical component of the 3GPP-defined disaggregated Next Generation Radio Access Network (NG-RAN) architecture introduced in 5G. It operates over a transport network, typically using IP, and connects the Central Unit (CU), which handles higher-layer protocols and centralized control, with one or more Distributed Units (DUs), which manage lower-layer protocols and the radio frequency. The interface is defined to be open and standardized, allowing for multi-vendor interoperability between CU and DU components.
The primary function of the F1-C is to carry the F1 Application Protocol (F1AP) signaling messages. These messages facilitate a wide range of control procedures essential for radio resource management. Key procedures include the establishment, modification, and release of UE contexts; the setup and management of data radio bearers (DRBs); handover preparation and execution; and the transfer of RRC messages transparently between the CU and the DU. The F1-C interface ensures that the CU, which houses the RRC and PDCP layers for the control plane, can effectively control the DU, which houses the RLC, MAC, and PHY layers.
From an architectural perspective, the F1-C is a logical point-to-point interface, though the physical connection traverses an IP network. It supports interface management functions, such as error indication and reset procedures, to maintain robustness. The separation of control (F1-C) and user plane (F1-U) traffic allows for independent scaling and optimization of network functions. This disaggregation is fundamental to Cloud RAN (C-RAN) and virtualized RAN (vRAN) deployments, enabling centralized processing pools and distributed radio units.
Purpose & Motivation
The F1-C interface was created to address the need for a flexible, scalable, and cost-effective Radio Access Network architecture in 5G. Traditional base stations (eNBs in 4G) were monolithic, integrating all protocol layers into a single physical unit, which limited deployment flexibility and innovation. The 5G NR specification introduced a functional split, separating the base station into a Central Unit (CU) and Distributed Unit (DU), to enable centralized processing, advanced coordination techniques, and efficient resource pooling.
The F1-C specifically solves the problem of control signaling between these separated entities. By providing a standardized control plane interface, it allows network operators to source CU and DU equipment from different vendors, fostering a competitive ecosystem and avoiding vendor lock-in. It also enables advanced RAN architectures like C-RAN, where multiple DUs can be connected to a centralized, possibly virtualized, CU pool. This centralization improves interference coordination, mobility management, and enables the implementation of sophisticated network slicing and QoS policies across a wider coverage area.
Historically, the lack of such an open internal interface in 4G eNBs made the RAN a closed system. The F1-C, along with the F1-U, is a cornerstone of the Open RAN (O-RAN) movement, which builds upon 3GPP's functional splits. It provides the necessary signaling conduit to realize the benefits of RAN disaggregation, including reduced capital and operational expenditures, increased deployment agility, and the ability to independently upgrade or scale control and user plane functions.
What changed in its specifications
The latest release-to-release comparison of specifications that define F1-C. Each summary describes the whole specification, not only this term.
Rel-19 adds Wireless Access Backhaul (WAB) architecture and node procedures to TS 38.401. It also adds multi-hop Layer-2 sidelink UE-to-Network relay with First, Intermediate and Last U2N Relay UE roles. Ambient IoT support is added, including A-IoT session contexts and AMF connectivity.
Full comparison in TS 38.401 →Technology family
RAN interfaces · Radio Access Network
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 4 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
F1-C is specified for the first time in Rel-15: the CU-CP to DU control plane interface, F1AP procedures over it, multiple TNLA handling, and security protection requirements.
- “The gNB-CU-CP is connected to the gNB-DU through the F1-C interface;” TS 38.401 v15.10.0
- “F1-C interface shall support confidentiality, integrity and replay protection.” TS 33.501 v15.20.0
- “This procedure shall be the first F1AP procedure triggered for the F1-C interface instance after a TNL association has become operational.” TS 38.473 v15.18.0
Rel-16 adds F1-C support for IAB: backhauling over IAB-donor-DU, an F1-C Transfer Path IE, an X2AP F1-C Traffic Transfer procedure via the MeNB, and DTLS mutual authentication on F1-C.
- “If the F1-C Transfer Path IE is included in UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, take it into account.” TS 38.473 v16.23.0
- “The purpose of the F1-C Traffic Transfer procedure is to deliver F1-C traffic to the MeNB so that it is then forwarded to the IAB-node” TS 36.423 v16.13.0
- “Mutual authentication shall be supported over the F1-C interface between the gNB-CU and the gNB-DU using DTLS and/or IKEv2.” TS 33.501 v16.20.0
Adds NR-DC support for IAB: an F1-C Transfer Path NRDC IE in UE CONTEXT SETUP REQUEST, and F1-C traffic delivered via the MgNB, whereas OLD covered only EN-DC/MeNB.
- “If the F1-C Transfer Path NRDC IE is included in UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, take it into account.” TS 38.473 v17.16.0
- “when the F1-C traffic is exchanged via the MgNB.” TS 38.401 v17.10.0
F1-C gained new roles in Rel-18: it carries information for identifying identical broadcast MBS sessions across gNB-DUs, and it is established, switched and redirected for mobile IAB-DUs.
- “gNB-DUs sharing the same physical cell resources receive via F1-C information to enable identifying broadcast MBS sessions providing identical content.” TS 38.401 v18.7.0
- “The MIAB F1 SETUP TRIGGERING message includes the gNB ID of the target F1-terminating IAB-donor-CU” TS 38.401 v18.7.0
- “is performed to redirect the mobile IAB-DU’s F1-C to the new path” TS 38.401 v18.7.0
Defining Specifications
3GPP specifications that define or reference F1-C, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 38.401 vj30 | NG-RAN Architecture Description | Rel-19 read |
| TS 38.470 vj20 | F1 Interface Specification for NG-RAN | Rel-19 read |