Description
The F1 Application Protocol (F1AP) is the core signaling protocol that enables control plane communication between the Central Unit (CU) and Distributed Unit (DU) of a disaggregated 5G gNB. It operates on top of Stream Control Transmission Protocol (SCTP) over IP, providing a reliable transport for its messages. F1AP defines a comprehensive set of Elementary Procedures (EPs), which are the fundamental units of interaction between the CU and DU. These procedures are categorized into Class 1 (requiring a response) and Class 2 (not requiring a response).
The protocol works through the exchange of F1AP messages, each carrying Information Elements (IEs) that contain the necessary parameters for a given procedure. Key functional areas covered by F1AP include: Interface Management (e.g., F1 setup, gNB-DU configuration update, error indication), UE Context Management (e.g., UE context setup, modification, and release), RRC Message Transfer (transparent conveyance of RRC messages between the CU's RRC layer and the UE via the DU), and Bearer Management (controlling the setup and modification of Data Radio Bearers). Furthermore, F1AP handles mobility procedures, such as handover preparation, and system information management, where the CU provides the SI messages to be broadcast by the DU.
From an architectural perspective, F1AP resides in the CU-CP (Control Plane) and the DU. Each F1AP message is associated with a specific UE context (for UE-associated signaling) or with the entire F1 interface (for non-UE-associated signaling). The protocol is designed to be efficient and scalable, supporting the management of thousands of UEs connected to a single DU. Its robust error handling and recovery mechanisms ensure the stability of the F1 interface, which is critical for maintaining service continuity in the RAN.
Purpose & Motivation
F1AP was created to provide a standardized, robust, and feature-rich signaling protocol for the new F1 interface introduced with the 5G CU-DU split. Prior to 5G, the internal communication within a base station was proprietary and vendor-specific, as the eNB was a monolithic entity. The disaggregation of the gNB into CU and DU necessitated an open, interoperable protocol to manage the complex coordination between these two network functions.
The protocol solves the fundamental problem of how a centralized control entity (the CU-CP) can command and manage a distributed radio unit (the DU) that handles the physical layer. It provides the necessary language for all control interactions, from bringing a UE into the network to managing its mobility and quality of service. Without F1AP, the CU and DU from different vendors would be unable to work together, defeating the purpose of an open interface.
Historically, the development of F1AP was influenced by the similar X2AP protocol used for inter-eNB communication in 4G, but it was designed from the ground up to address the specific needs of an *intra*-gNB interface with tighter integration and more comprehensive control. Its creation was motivated by the industry's push towards virtualization, cloudification, and Open RAN. F1AP is the enabling glue that makes the 3GPP-defined functional split practical, allowing operators to deploy flexible, scalable, and cost-effective RAN architectures while maintaining full control over radio resources and user sessions.
What changed in its specifications
The latest release-to-release comparison of specifications that define F1AP. 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 →Protocol Stack
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 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.
F1AP is specified for the first time in Rel-15 as the F1-C application protocol between gNB-CU and gNB-DU, with its services, elementary procedures and UE-associated signalling.
- “The present document specifies the 5G radio network layer signalling protocol for the F1 interface.” TS 38.473 v15.18.0
- “F1AP provides the signalling service between gNB-DU and the gNB-CU that is required to fulfil the F1AP functions described in clause 7.” TS 38.473 v15.18.0
- “F1AP shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax” TS 38.473 v15.18.0
F1AP gained new procedures and IEs in Rel-16, including conditional handover and PSCell change handling, positioning support over F1AP, and IAB-related signalling.
- “the gNB-DU shall replace the existing prepared conditional handover or conditional PSCell change identified by the Target gNB-DU UE F1AP ID IE” TS 38.473 v16.23.0
- Introduction of positioning support over F1AP TS 38.473CR0495
- “the gNB-DU shall consider that the gNB-CU is cancelling only the conditional handover or conditional PSCell change” TS 38.473 v16.23.0
F1AP gained MBS-associated signalling with MBS-associated logical F1-connections identified by gNB-CU/gNB-DU MBS F1AP IDs, plus new handling for conditional PSCell addition, CG-SDT and sidelink relay.
- “The MBS-associated logical F1-connection uses the identities GNB-CU MBS F1AP ID and GNB-DU MBS F1AP ID” TS 38.473 v17.16.0
- “If the Old CG-SDT Session Info IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, retrieve” TS 38.473 v17.16.0
- “If the Sidelink Relay Configuration IE is included in the INITIAL UL RRC MESSAGE TRANSFER, the gNB-CU shall, if supported, consider that the UE is a NR ProSe Layer-2 U2N Remote UE” TS 38.473 v17.16.0
F1AP procedures were extended in Rel-18, with added support for sub-1s location reporting periodicity, LTM cell release handling, conditional mobility (CPAC) replacement and cancellation, and A2X communication services.
- “If the LTM Cells To Be Released List IE is included in the UE CONTEXT RELEASE REQUEST message, the gNB-CU shall, if supported” TS 38.473 v18.11.0
- F1AP support for sub 1s location information reporting periodicity [Sub_1s_periodicity] TS 38.473CR1446
- A2X communication services support in F1AP TS 38.473CR1250
F1AP procedures were extended: ACCESS AND MOBILITY INDICATION now carries MRO for LTM information (BFR SSB Index, Target SSB Index, TA Information) that the gNB-DU may use for beam and timing advance optimisation.
- “If the ACCESS AND MOBILITY INDICATION message contains the BFR SSB Index IE within the MRO for LTM Information IE, the gNB-DU shall, if supported” TS 38.473 v19.4.0
- “the gNB-DU may take it into account for optimisation of Timing Advance related parameters or optimisation of target beam selection” TS 38.473 v19.4.0
- Abnormal conditions for F1AP gNB-CU Configuration Update TS 38.473CR1692
Defining Specifications
3GPP specifications that define or reference F1AP, 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 |