Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Interface

F1-U

F1 User Plane Interface

Interface →

F1-U is the user plane interface between a gNB-Central Unit and a gNB-Distributed Unit that transports user data packets over GTP-U tunnels for flexible 5G RAN deployments.

Introduced
Rel-15
Where
Radio Access Network › NG-RAN (5G)
Specifications
2 specs
F1-U Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The F1-U interface is the user plane counterpart to the F1-C within the 3GPP disaggregated gNB architecture. It provides the data path for user traffic between the CU's user plane component (CU-UP) and the DU. The interface is designed to carry encapsulated user data packets using the GPRS Tunneling Protocol for the user plane (GTP-U) over a UDP/IP transport layer. This tunneling mechanism allows for the multiplexing of data flows from multiple UEs and bearers over a single F1-U association between a CU-UP and a DU.

Operationally, for each established Data Radio Bearer (DRB), one or more GTP-U tunnels are set up over the F1-U interface. The CU-UP, which houses the PDCP layer for the user plane, performs functions like header compression, ciphering, and integrity protection. It then forwards the processed PDCP Protocol Data Units (PDUs) to the DU via the appropriate GTP-U tunnel. The DU, responsible for the RLC, MAC, and PHY layers, receives these PDCP PDUs, segments them if necessary (at RLC), schedules them for transmission (at MAC), and finally sends them over the air interface to the User Equipment (UE). The reverse path is followed for uplink data.

The architecture of the F1-U is defined to be independent of the F1-C, allowing the user plane traffic to be routed over potentially different network paths for optimization. This separation is crucial for enabling high-throughput, low-latency data delivery. The interface supports data forwarding during handover procedures to minimize data loss. Furthermore, the F1-U's design aligns with network slicing requirements, as different QoS flows can be mapped to different DRBs and subsequently transported over the F1-U with appropriate prioritization within the transport network.

Purpose & Motivation

The F1-U interface was developed to facilitate the user plane separation mandated by the CU-DU split in 5G. In monolithic 4G eNBs, user data processing and radio transmission were tightly coupled within the same hardware, limiting deployment options. The F1-U enables the physical and logical separation of the user plane processing function (in the CU-UP) from the radio transmission/reception function (in the DU).

This separation solves several key problems. It allows network operators to centralize user plane processing in cost-effective data centers (CU pools), achieving statistical multiplexing gains and simplifying the implementation of advanced features like edge computing. The DUs can remain as simpler, potentially mass-produced radio units deployed at cell sites. This architecture reduces fronthaul bandwidth requirements compared to a more stringent split like CPRI, as the F1-U carries partially processed packet data rather than raw IQ samples.

The creation of the F1-U, alongside the F1-C, was motivated by the need for RAN virtualization and cloudification. By defining a standard packet-based user plane interface, 3GPP enabled the CU-UP to be implemented as a Virtual Network Function (VNF) or Cloud Native Network Function (CNF) on commercial off-the-shelf servers. This drives down costs, increases service agility, and paves the way for AI/ML-based optimization in the RAN. The F1-U is thus essential for realizing the economic and performance promises of 5G networks, including support for enhanced Mobile Broadband (eMBB) and Ultra-Reliable Low-Latency Communications (URLLC) services.

What changed in its specifications

The latest release-to-release comparison of specifications that define F1-U. Each summary describes the whole specification, not only this term.

TS 38.401Rel-18 → Rel-19

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

  1. Phase 1 A interface, Abis
  2. R99 Iu, Iu-BC, Iu-CS, Iu-PS, Iub, Iur, NBAP, Uu
  3. Rel-5 Iur-g
  4. Rel-8 S1, S1-MME, S1-U, S1AP, X2
  5. Rel-15 E1, E1AP, F1, F1-C, F1-U, F1AP, NG, NG-C, NG-U, NGAP, Xn, Xn-C, Xn-U

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 sources

Documented changes in 5 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.

Rel-15 introduced

F1-U is specified for the first time as the user plane interface between gNB-CU-UP and gNB-DU, including radio link outage/resume notifications and bearer context setup/release over F1-U.

  • “The gNB-CU-UP is connected to the gNB-DU through the F1-U interface;” TS 38.401 v15.10.0
  • “it may send a "Radio Link Resume" notification message as part of the DDDS PDU over the F1-U interface” TS 38.401 v15.10.0
  • “8.9.2 Bearer context setup over F1-U” TS 38.401 v15.10.0
Rel-16 1 CR

Rel-16 adds IAB support to F1-U: gNB-DU/CU update F1-U GTP tunnel UL/DL TNL addresses and BH mapping via IAB UP configuration update, with F1-U traffic backhauled over IAB-donor-DU.

  • “the gNB-DU shall replace the old TNL address with the new TNL address for all the maintained UL F1-U GTP tunnels” TS 38.473 v16.23.0
  • “The F1-U traffic between an IAB-node and IAB-donor-CU is backhauled via the IAB-donor-DU and the optional intermediate hop IAB-node(s).” TS 38.401 v16.12.0
  • Correction in F1-U on DSCP Derivation in IAB-donor node TS 38.474CR0008
Rel-17 specification text

Rel-17 extends F1-U for MBS: shared and UE-dedicated multicast F1-U tunnels, Multicast F1-U Context, and a Multicast Distribution Setup procedure to establish F1-U bearers for multicast sessions.

  • “The purpose of the Multicast Distribution Setup procedure is to establish F1-U bearers for the multicast MBS session.” TS 38.473 v17.16.0
  • “A shared F1-U tunnel is used between the gNB-CU and the gNB-DU forMRB with PTM transmission.” TS 38.401 v17.10.0
  • “A Multicast F1-U Context is a block of information in a gNB-DU to control the F1-U tunnels associated to the MRB Contexts” TS 38.401 v17.10.0
Rel-18 1 CR

F1-U gained new behaviour in Rel-18: the gNB-DU can trigger F1-U resource establishment for broadcast MBS, signal F1-U tunnel not established, and report shared F1-U path failure for recovery.

  • “The purpose of the Broadcast Transport Resource Request procedure is to request the gNB-CU to trigger the establishment of F1-U resources for the broadcast session.” TS 38.473 v18.11.0
  • “If the gNB-DU detects failure of a shared F1-U bearer of a broadcast MBS session it may send the F1AP Broadcast Transport Resource Request message” TS 38.401 v18.7.0
  • Correction of MBS F1-U failure Recovery - option 1 TS 38.401CR0392
Rel-19 1 CR

The F1-U user plane interface specification in 38.470 was corrected for the AI/ML-related F1-U stage 2 description.

  • Correction on AIML F1-U stage2 TS 38.470CR0170

Defining Specifications

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

SpecificationTitleRelease
TS 38.401 vj30 NG-RAN Architecture Description Rel-19 read
TS 38.470 vj20 F1 Interface Specification for NG-RAN Rel-19 read