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

Glossary term · Protocol

NG-AP

NG Application Protocol

Protocol →

NG-AP is the control plane protocol between the 5G gNB and the AMF, managing procedures like UE context, paging, and handovers over the NG interface for 5G signaling and mobility.

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

Description

The NG Application Protocol (NG-AP) is a critical control plane protocol defined by 3GPP for the 5G System (5GS). It operates over the NG interface, specifically the N2 reference point, which connects the Next Generation Radio Access Network (NG-RAN) to the 5G Core Network (5GC). NG-AP is responsible for all signaling interactions between the gNB (or ng-eNB) and the Access and Mobility Management Function (AMF). It is a key enabler for the service-based architecture of 5G, facilitating the decoupling of the control and user planes.

NG-AP works by exchanging structured messages, known as Elementary Procedures (EPs), between the RAN and the core network. These procedures are categorized into Class 1 (requiring a response) and Class 2 (not requiring a response). Key procedures include the Initial UE Message, which establishes the first signaling connection for a user equipment (UE); the UE Context Management procedures for setup, modification, and release; and the Handover Preparation and Resource Allocation procedures for seamless mobility. The protocol also handles Paging, UE Capability Info Indication, and the setup of NG interfaces themselves.

Architecturally, NG-AP is carried over Stream Control Transmission Protocol (SCTP) to ensure reliable, message-oriented transport. It is a peer-to-peer protocol where the gNB and AMF are the logical endpoints. Its design supports network slicing by allowing the RAN to be aware of and route traffic to the appropriate network slice instance via the associated AMF. NG-AP's role is central to session management, mobility management, and the overall orchestration of UE connections within the 5G network, providing the foundational signaling layer that makes advanced 5G features possible.

Purpose & Motivation

NG-AP was created as part of the 5G architecture in 3GPP Release 15 to provide a new, flexible, and service-based signaling protocol between the RAN and the core network. It addresses the limitations of previous protocols like S1-AP (used in 4G LTE between eNB and MME), which were not designed for the cloud-native, service-based, and slice-aware architecture of 5G. The primary motivation was to support new 5G requirements, including enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC), which demand more agile and efficient control plane signaling.

The protocol solves the problem of rigid, point-to-point signaling by enabling a more decoupled and scalable interaction model. It allows a single gNB to connect to multiple AMFs, supporting advanced features like network slicing and AMF redundancy. Furthermore, NG-AP is designed to be forward-compatible, with a modular structure that can accommodate new procedures and parameters in future releases without breaking existing functionality. Its creation was motivated by the need for a protocol that could handle the increased complexity and diversity of 5G services, from high-speed data to critical IoT communications, while operating in a virtualized and software-defined network environment.

What changed in its specifications

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

TS 38.305Rel-18 → Rel-19

Rel-19 adds enhanced NR topology support to TS 38.305, including WAB-gNB, updated definitions and gNB-to-LMF information transfer. It also includes two further related items.

Full comparison in TS 38.305 →

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
  • NG-AP counterpart in another generation: S1AP
    “The application layer signalling protocol is referred to as NGAP (NG Application Protocol).” TS 38.410

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 3 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

TS 38.413 first specifies the NG Application Protocol as the radio network layer signalling protocol supporting the functions of the NG interface through defined signalling procedures.

  • “The present document specifies the radio network layer signalling protocol for the NG interface.” TS 38.413 v15.13.0
  • “The NG Application Protocol (NGAP) supports the functions of the NG interface by signalling procedures defined in this document.” TS 38.413 v15.13.0
Rel-16 1 CR

NG-AP gained new NB-IoT related procedures over the NG interface between the gNB and the AMF in Rel-16.

  • “Introduction of NB-IoT related NG-AP procedures” TS 38.413 v16.18.0
  • Introduction of NB-IoT related NG-AP procedures TS 38.413CR0156
Rel-17 1 CR

NG-AP gained support for 5G ProSe authorization in Rel-17, adding ProSe authorization handling to the NG interface signalling between gNB and AMF.

Defining Specifications

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

SpecificationTitleRelease
TS 38.305 vj30 NG-RAN UE Positioning Stage 2 Rel-19 read