5G NGAP Overview
From 3glteinfo telecom reference
NGAP is the application protocol used on the N2 interface, also viewed as the NG-C control-plane side of the NG interface. It carries signaling between the NG-RAN node and the AMF for UE context control, NAS transport, paging, mobility, and interface-level management.
This page explains what NGAP is, how the specification organizes its services and elementary procedures, how to think about UE-associated versus non-UE-associated signaling, and which deeper pages or message references to open next.
Quick facts
| Technology | 5G |
|---|---|
| Area / Protocol | NGAP on N2 / NG-C |
| Direction / scope | gNB (or NG-RAN node) to AMF control-plane signaling |
| Main use | NAS transport, UE context control, paging, mobility, interface management, PDU session resource coordination |
| Related topics | N2, NG interface, Initial UE Message, Initial Context Setup, Paging, Handover, UE Context Release, RRC, NAS |
NBAP Topics
NG Interface and Transport | Procedure Model and Message Structure | Identifiers and Logical Connections | Interface Management | NGAP Messages | Initial Registration | N2 Handover | NGAP Troubleshooting
Contents
Overview
NGAP is the control-plane application protocol between the NG-RAN node and the AMF. In practical protocol analysis, it is the protocol you inspect when a 5G problem crosses the RAN-to-core boundary: registration entry, paging reachability, UE context creation or release, PDU session resource coordination, and core-involved mobility.
NGAP should be read together with the transport, architecture, and procedure context around the NG interface. The relevant specifications are grouped in the references section at the end of the page.
NGAP reference map
Use this page as the top-level map. Start with transport and procedure mechanics, then move into identifiers, interface management, message pages, or troubleshooting depending on whether you are learning the protocol, decoding a trace, or isolating a failure.
Core NGAP Topics
- NG Interface and Transport Start here for N2, NG-C, SCTP transport expectations, stream usage, and signaling transport assumptions.
- Procedure Model and Message Structure Deep dive into NGAP elementary procedures, initiating versus outcome messages, and ASN.1 PDU structure.
- Identifiers and Logical Connections Use this page for AMF UE NGAP ID, RAN UE NGAP ID, UE-associated signaling, and correlation rules.
- Interface Management Open this for setup, reset, error indication, overload, and configuration-management signaling.
Procedure family map
- Interface management NG Setup, Reset, Error Indication, Overload Start, and configuration-related control at the interface level.
- UE context management Initial UE Message, Initial Context Setup, UE Context Release, and the broader per-UE state lifecycle.
- PDU session resource management Resource setup, modify, release, and notify procedures used around user-plane establishment and updates.
- Paging and NAS transport NAS message carriage, paging trigger support, and downlink or uplink access-side continuation.
- Mobility and handover Handover Required, Handover Request, Path Switch, and AMF-involved mobility coordination.
- Warning, location, trace, and positioning support Operationally less common, but part of the broader NGAP family map and important in specialized deployments.
Messages and troubleshooting
- 5G Initial UE Message Best first NGAP message to open when tracing registration entry from RRC into AMF signaling.
- 5G Initial Context Setup Request Open this for UE context creation and access-side setup continuation.
- 5G Paging Read NGAP paging together with NAS reachability and RRC paging behavior.
- 5G UE Context Release Command Useful when studying context teardown and abnormal release handling.
- 5G PDU Session Resource Setup Request High-value message for user-plane establishment and QoS signaling context.
- 5G NGAP Troubleshooting Use this path when the issue begins with an operational symptom instead of a named message.
Position on N2 and NG-C
UE -> NAS messages originate or terminate at the UE
RRC -> carries early access-side radio control between UE and gNB
NGAP -> carries gNB to AMF control signaling on N2 / NG-C
AMF -> handles access and mobility control in the 5G CoreNGAP does not replace RRC or NAS. Instead, it bridges the NG-RAN and AMF side of the system. In many procedures, the user-visible event starts in RRC or NAS, but the network coordination step that follows is visible in NGAP.
| Layer or interface | Role relative to NGAP | Typical example |
|---|---|---|
| RRC | Radio-side control between UE and gNB | RRC Setup Complete reaches the gNB before the gNB sends Initial UE Message over NGAP. |
| NAS | UE-to-core signaling payload | Registration Request may be transported through NGAP NAS transport procedures. |
| N2 / NG-C | Transport boundary where NGAP operates | Paging, UE context setup, or handover coordination between gNB and AMF. |
| N3 / NG-U | User-plane companion, not NGAP | PDU session user traffic uses N3, while NGAP coordinates related control actions on N2. |
NGAP services
The NGAP specification divides signaling services into two broad groups. This distinction is operationally useful because it tells you whether the procedure is scoped to the full interface instance or tied to one UE context.
| Service group | Meaning | Typical examples | Why it matters in traces |
|---|---|---|---|
| Non-UE-associated services | Related to the whole NG interface instance between the NG-RAN node and the AMF. | NG Setup, NG Reset, overload-related control, configuration updates. | These procedures usually appear even when no specific UE context exists yet. |
| UE-associated services | Related to one UE and maintained over a UE-associated signaling connection. | Initial UE Message, Initial Context Setup, Paging, PDU Session Resource Setup, UE Context Release. | These procedures depend on correct UE identity correlation and per-UE state management. |
Trace note: When a trace looks broken before UE identity correlation is stable, first check whether the failing procedure is really UE-associated. That often narrows the issue quickly.
Procedure model
NGAP is organized as elementary procedures. A practical first split is between Class 1 and Class 2 procedures. Class 1 procedures have an initiating message and may define successful and unsuccessful outcome messages. Class 2 procedures are one-way procedures with no explicit outcome message.
| Procedure class | Pattern | What to expect in logs |
|---|---|---|
| Class 1 | Initiating message, then successful or unsuccessful outcome when defined by the procedure. | Look for the request and then correlate the expected response or failure path. |
| Class 2 | Initiating message only, without a formal success or failure outcome message. | You usually infer procedure success from subsequent protocol progression, not a paired NGAP response. |
Class 1 pattern
Initiating message
-> Successful outcome
or
Initiating message
-> Unsuccessful outcomeThis is the most important pattern for message pairing and timeout analysis. If the expected outcome never appears, you usually investigate transport break, peer rejection, internal processing failure, or a trace gap.
Class 2 pattern
Initiating message
-> no explicit outcome
-> check later procedure stepsThese procedures are easy to misread as incomplete if you expect an acknowledge message. Always verify the procedure class before assuming a missing response.
Procedure family map
The protocol becomes easier to navigate if you group elementary procedures into operational families rather than reading them as one long spec chapter list.
| Family | What it covers | Open next |
|---|---|---|
| Interface management | Setup, reset, overload, configuration updates, and interface-wide error handling. | Interface Management |
| UE context management | Creation, maintenance, and release of UE-related NGAP state between gNB and AMF. | NGAP Messages |
| PDU session resource procedures | Access-side coordination for session resource setup, modify, notify, and release. | PDU Session Resource Setup Request |
| Mobility and handover | Core-involved mobility preparation, execution support, and path-switch-related signaling. | N2 Handover |
| Paging and NAS transport | Procedures that carry NAS payloads or trigger UE reachability on the access side. | Paging |
| Specialized support families | Warning message transmission, trace, location, positioning, and other deployment-specific functions. | Message library |
interface management
-> setup / reset / overload / config
UE context management
-> initial access / context create / context release
session resource procedures
-> setup / modify / release
mobility procedures
-> handover preparation / execution support / path switch
adjacent support
-> paging / NAS transport / warning / trace / locationMessage structure and IEs
NGAP messages are specified through procedure-oriented message definitions plus IE tables and ASN.1 structure. For practical use, the key habit is to separate three things clearly: the elementary procedure, the exact message within that procedure, and the IEs that make the message actionable.
| Decode layer | Question to ask | Example |
|---|---|---|
| Procedure | Which elementary procedure is running? | Initial Context Setup or UE Context Release. |
| Message role | Is this initiating, successful outcome, or unsuccessful outcome? | Initial Context Setup Request versus Failure versus Response. |
| IE content | Which fields explain the behavior or failure? | Cause, AMF UE NGAP ID, RAN UE NGAP ID, NAS-PDU, PDU session resource lists. |
Trace note: In NGAP troubleshooting, the message name alone is rarely enough. The procedure stage and the cause-related or identity-related IEs usually explain the failure.
Identifiers and logical connections
A large share of NGAP trace analysis is really identity correlation. UE-associated signaling depends on the correct handling of UE identifiers and the UE-associated logical NG-connection concept. If these references are broken or mismatched, the rest of the procedure often becomes unreadable.
| Identifier or concept | Meaning | Why it matters |
|---|---|---|
| AMF UE NGAP ID | AMF-side UE identifier in NGAP context. | Used to correlate the AMF view of the UE across NGAP signaling. |
| RAN UE NGAP ID | NG-RAN-side UE identifier in NGAP context. | Used to correlate the RAN view of the UE and match later signaling correctly. |
| UE-associated logical NG-connection | Per-UE signaling relationship used for UE-associated NGAP procedures. | Explains whether the procedure has UE-scoped context or is still interface-level only. |
| Cause IE and related context IEs | Failure explanation and procedural context. | Often the shortest route from a failed response to the real fault domain. |
RRC / NAS event
-> gNB creates or reuses RAN UE NGAP ID
-> AMF allocates or reuses AMF UE NGAP ID
-> UE-associated NGAP signaling proceeds
-> later messages correlate both IDsUse Identifiers and Logical Connections for the dedicated reference view.
Call-flow relevance
NGAP is best learned in procedures, not only in isolated message pages. In real logs, NGAP often appears as the coordination layer between the access procedure already underway in the RAN and the control-plane decision taken by the AMF.
Registration entry
UE -> RRC Setup Complete with NAS
gNB -> Initial UE Message
AMF -> Downlink NAS Transport / Initial Context Setup path
gNB -> access-side continuationThis is the most common learning path because it shows how RRC, NAS, and NGAP fit together during early 5G access.
Paging
core reachability event
-> NGAP Paging
-> gNB maps toward RRC paging behavior
-> UE re-enters service pathN2 handover
source gNB / AMF coordination
-> handover preparation messages
-> target-side context preparation
-> path switch or release continuationTroubleshooting
| Symptom | NGAP angle to inspect | Why it matters |
|---|---|---|
| Registration stalls after access | Initial UE Message, Downlink NAS Transport, Initial Context Setup | NGAP is often where the RAN-to-AMF handoff of control context becomes visible. |
| Paging not reaching the UE | Paging message presence, UE context state, downstream RRC continuity | The failure may sit in NGAP reachability signaling rather than only in radio paging behavior. |
| UE context released unexpectedly | UE Context Release Request, Command, Complete, and Cause IE | Cause handling and ownership of the release step are critical for root-cause analysis. |
| Handover fails with AMF involvement | Handover Required, Handover Request, failure outcome, path switch continuation | NGAP pinpoints whether the break happened before execution, at target preparation, or during switchback logic. |
| PDU session resources do not come up | PDU Session Resource Setup or Modify message content and outcome | These procedures often expose whether the issue is control signaling, transport setup, or QoS context mismatch. |
The dedicated NGAP troubleshooting page should be the next stop when you already know the symptom and need a debug workflow rather than a protocol overview.
References
- 3GPP TS 38.413 - NG-RAN; NG Application Protocol (NGAP)
- 3GPP TS 38.410 - NG-RAN; NG general aspects and principles
- 3GPP TS 38.412 - NG signaling transport
- 3GPP TS 23.501 - System architecture for the 5G System
- 3GPP TS 23.502 - Procedures for the 5G System
FAQ
What is NGAP in 5G?
NGAP is the application protocol used between the NG-RAN node and the AMF on N2. It is one of the main control-plane protocols inspected in 5G access, paging, mobility, and session-related procedures.
Is NGAP the same as N2?
No. N2 is the control-plane reference point between NG-RAN and AMF. NGAP is the main application protocol that runs over that interface.
Why does NGAP matter so much in troubleshooting?
Because many real failures happen at the RAN-to-core control boundary. NGAP often shows whether the issue is interface-level, UE-context-level, paging-related, mobility-related, or session-resource-related.
What is the fastest way to read an NGAP trace?
Identify the procedure family first, then confirm whether the message belongs to a Class 1 or Class 2 procedure, then inspect the identity IEs and cause-related fields.
Which NGAP messages should be learned first?
Initial UE Message, Initial Context Setup Request, Paging, UE Context Release Command, and PDU Session Resource Setup Request are high-value starting points because they appear in common access and service flows.
SEO
SEO title: 5G NGAP Overview
SEO description: Complete NGAP reference covering N2 placement, UE-associated and non-UE-associated services, procedure classes, message structure, troubleshooting angles, and related NGAP procedures or messages.