F1-C

F1 Control Plane Interface

Interface →
Introduced in Rel-15

F1-C is the control plane interface between a gNB-Central Unit and a gNB-Distributed Unit in a disaggregated 5G RAN, carrying signaling for context management, bearer setup, and mobility.

Category
Interface
Introduced
Rel-15
Where
Radio Access Network › NG-RAN (5G)
Specifications
2 specs
F1-C Description Purpose Related Classification Detected Changes Specifications

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.

Classification

Part ofF1AP
Specific typesF1AP
Related approachesF1-U

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (16 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 3 changes

In Release 15, the F1-C interface was introduced as the control plane link between the gNB-DU and the gNB-CU-Control Plane, which hosts RRC and the control part of PDCP. This release also added support for multiple Transport Network Layer Associations (TNLAs) on the F1-C interface for enhanced reliability and load distribution. Furthermore, initial support for energy saving mechanisms was introduced over the F1 interface.

  • CR to 38.401 on Multiple TNLAs for F1-C and E1 TS 38.401CR0063
  • Clarify the support for multiple TNLAs for F1-C TS 38.401CR0043
  • Energy Saving Support over F1 Interface TS 38.470CR0023
Rel-16 2 changes

In Release 16, the F1-C interface was enhanced with new positioning and trace capabilities. Specifically, it introduced support for positioning procedures over the F1AP protocol. Furthermore, the release added explicit support for the trace function across the F1 interface.

  • Positioning support over F1AP TS 38.470CR0061
  • Trace function Support over F1 Interface TS 38.470CR0040
Rel-17 3 changes

In Release 17, the F1-C interface was enhanced to introduce support for NR Sidelink Relay, enabling new device-to-device communication scenarios via the gNB. Additionally, corrections and clarifications were made to the definitions and procedures for Multicast F1-U Contexts and tunnels to ensure proper support for multicast MRB (Multicast Radio Bearer) services.

  • (Stage-2 F1AP CR) support for NR Sidelink Relay TS 38.470CR0085
  • Correction on F1-U tunnels for multicast MRB TS 38.401CR0258
  • Correction on definition of Multicast F1-U Context TS 38.401CR0263
Rel-18 7 changes

In Release 18, the F1-C interface was enhanced to support the operation of Network-Controlled Repeaters, as indicated by the dedicated Change Requests. Furthermore, the release introduced corrections and clarifications for multicast service (MBS) procedures, specifically addressing F1-U failure recovery and the general F1AP principles for multicast reception in the RRC_INACTIVE state.

  • Support of Network-Controlled Repeater TS 38.401CR0274
  • Correction on TS 38401 for Network Controlled Repeater TS 38.401CR0351
  • Correction of MBS F1-U failure Recovery - option 1 TS 38.401CR0392
  • Correction on general F1AP principles for multicast reception in RRC_INACTIVE TS 38.401CR0403
  • Missing Iuant interface reference in NR specification TS 38.401CR0422
  • Correction for name of AP ID over Xn interface TS 38.401CR0460

+ 1 more changes

Rel-19 1 change

In Release 19, the F1-C interface saw the introduction of support for AI/ML (Artificial Intelligence/Machine Learning) functions. This update is specifically noted in a Change Request focused on correcting the AI/ML F1-U stage 2 description, indicating the integration of AI/ML management capabilities into the NG-RAN architecture for F1 interfaces. These enhancements build upon the existing protocol structure defined between the gNB-CU-CP and the gNB-DU.

  • Correction on AIML F1-U stage2 TS 38.470CR0170

Explore further

Broader topics and technologies where F1-C plays a role.

Defining Specifications

3GPP specifications that define or reference F1-C, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 38.401 vj10 NG-RAN Architecture Specification Rel-19
TS 38.470 vj10 F1 Interface Introduction Rel-19