3GLTEInfo Text-based logo for the 3GLTEInfo telecom engineering reference platform. 3GLTE INFO TELECOM ENGINEERING REFERENCE
Menu

Home / 5G / Protocols / NGAP / NG Interface and Transport

NGAP NG Interface and Transport

From 3glteinfo telecom reference

NGAP signaling is carried on N2, the NG-C control-plane side of the NG interface between the NG-RAN node and the AMF. This transport view is important because many NGAP issues start before message content is even evaluated, usually in SCTP association state, stream usage, IP reachability, or interface-level transport behavior.

Use this page when you need the transport baseline behind NGAP: protocol stack, signaling bearer expectations, SCTP associations, stream separation, IP support, redundancy, and the transport checks that matter in trace analysis.

Technology 5G
Area NGAP transport on N2 / NG-C
Protocol stack NGAP over SCTP over IP
Scope Signaling transport between NG-RAN node and AMF
Key transport details In-sequence delivery, connection-break notification, PPID 60, destination port 38412, stream separation for UE-associated and non-UE-associated signaling
Related pages NGAP Overview, N2 Interface, Interface Management, Initial UE Message, NG Reset, N2 Handover

Contents

  1. Overview
  2. Where it fits
  3. Protocol stack
  4. Transport expectations
  5. Associations and streams
  6. IP and redundancy
  7. Procedure context
  8. Troubleshooting
  9. References
  10. FAQ

Overview

NGAP itself is the application protocol, but NGAP never appears alone in live operation. It sits on a defined signaling transport path that provides reliable delivery behavior, stream structure, and transport-level continuity between the NG-RAN node and the AMF.

If the signaling bearer is unstable, higher-layer NGAP procedures may appear incomplete, delayed, or missing. That is why NGAP transport belongs near the start of any serious N2 troubleshooting workflow.

Where it fits

The NG interface connects NG-RAN and 5GC. Its control-plane side is NG-C, commonly viewed in 5GS reference terminology as N2. NGAP is the signaling protocol on that control-plane path.

Item Meaning Why it matters
NG interface Overall access-to-core interface between NG-RAN and 5GC. Provides the parent context for both control-plane and user-plane sides.
NG-C / N2 Control-plane side between NG-RAN node and AMF. This is where NGAP signaling is transported.
NG-U / N3 User-plane side between NG-RAN node and UPF. Useful companion path, but it is not the NGAP transport bearer.
NG-RAN gNB / NG-RAN node AMF UPF NG-C / N2 NGAP signaling transport NG-U / N3 user-plane transport, not NGAP

Protocol stack

The NG-C signaling bearer uses NGAP at the application layer, SCTP at the transport layer, and IP underneath. This stack is one of the most important anchor points for understanding NGAP transport. 

NGAP
  ->
SCTP
  ->
IP
  ->
Data link layer
  ->
Physical layer
Layer Role Transport reading note
NGAP Application signaling between NG-RAN node and AMF. What you decode at message level.
SCTP Signaling transport with associations and streams. What you inspect when message sequencing or connectivity looks wrong.
IP Network-layer reachability for NG-C signaling. What you inspect when peer reachability or routing is unstable.
NGAP SCTP IP message procedures associations and streams reachability and routing

Transport expectations

The signaling transport is expected to provide in-sequence delivery of NGAP messages and to notify NGAP if the signaling connection breaks. Those two expectations are basic, but they explain many higher-layer symptoms.

Expected behavior Meaning Why it matters
In-sequence delivery NGAP messages must reach the receiving side in sequence on the signaling connection. Procedure pairing and state progression rely on clean message order.
Break notification NGAP must be informed when the signaling connection fails. Without this, the application layer may appear to wait for procedures that can never continue.
Reliable transfer The signaling bearer is intended for reliable transport of NGAP messages. Transport instability often shows up as missing outcomes, incomplete setup, or reset behavior.
Flow and congestion support The signaling transport supports signaling-network control behavior. Under load, this matters for overload handling and signaling stability.

Associations and streams

SCTP is not just a transport label in the stack. For NGAP, association and stream usage are operationally important. The transport baseline includes support for a single SCTP association per NG-RAN node and AMF pair, while configurations with multiple SCTP endpoints should also be supported.

Transport item Specification direction Practical reading note
Single SCTP association Shall be supported per NG-RAN node and AMF pair. This is the baseline deployment assumption.
Multiple SCTP endpoints or associations Should be supported. Useful for scaling, resilience, or signaling-type separation.
Non-UE-associated stream pair A single pair shall be reserved on at least one SCTP association. Keeps interface-level procedures separate from per-UE traffic.
UE-associated stream pairs At least one pair shall be reserved, and more than one should be reserved. Important for scaling many simultaneous UE-related procedures.
Per-UE signaling continuity One SCTP association and one SCTP stream are used for a UE-associated signaling relationship. Useful when checking whether a trace unexpectedly changes transport context mid-procedure. 
non-UE-associated procedures
        -> reserved stream pair

UE-associated procedures
        -> one of the UE-associated stream pairs
        -> per-UE continuity on one association and one stream

Trace note: If NG Setup or Reset behavior looks mixed into UE-specific troubleshooting, check first whether you are reading a non-UE-associated transport path or a UE-associated one.

IP and redundancy

The NG-C signaling bearer uses IP transport under SCTP. The specification supports IPv6 and or IPv4. It also defines point-to-point transmission for NGAP delivery and allows redundancy mechanisms such as SCTP multihoming.

Item Value or rule Why it matters
IP support IPv6 and or IPv4 shall be supported. Useful when validating deployment compatibility and address-family selection.
Transmission mode Point-to-point delivery for NGAP messages. Clarifies the signaling model at the IP layer.
PPID NGAP uses SCTP Payload Protocol Identifier 60. Useful for deep transport inspection.
Destination port NGAP uses SCTP destination port 38412 as the baseline assigned value. A fast check when SCTP setup looks wrong.
Redundancy SCTP multihoming may be used for transport network redundancy. Important when transport stability differs across paths or endpoints.

Procedure context

Transport details matter most when you connect them to real NGAP procedures. The content of a message may be correct, but the procedure can still fail if the signaling bearer is not healthy.

Interface setup

IP reachability
        -> SCTP association up
        -> NG Setup Request
        -> NG Setup Response or Failure

Registration entry

RRC setup complete with NAS
        -> gNB sends Initial UE Message
        -> NGAP continues over UE-associated stream
        -> AMF response path follows

Handover and session procedures

existing signaling connectivity
        -> mobility or session resource procedure
        -> outcome depends on both transport continuity and message content

Troubleshooting

Symptom Transport angle to inspect Next check
NG Setup does not complete IP reachability, SCTP association establishment, port usage Check whether the SCTP association is up before reading NGAP message content.
NGAP message missing its expected continuation Association break or stream continuity issue Check signaling-connection state and whether NGAP was notified of the break.
UE-related procedures fail intermittently UE-associated stream usage or transport path instability Check whether the same UE-associated signaling remains on the expected association and stream.
Interface-level procedures look mixed with UE procedures Non-UE-associated versus UE-associated stream separation Confirm the transport context before assuming a message-sequencing issue.
Signaling is unstable under load Congestion, redundancy behavior, multiple endpoint use Check overload, SCTP path status, and whether redundancy behavior is configured as intended.

References

FAQ

What transport does NGAP use?

NGAP uses SCTP over IP on the N2 or NG-C control-plane path between the NG-RAN node and the AMF.

Why is SCTP important for NGAP?

Because SCTP provides the association and stream behavior that the signaling transport relies on for ordered delivery, signaling separation, and redundancy support.

What port does NGAP use?

The baseline SCTP destination port assigned for NGAP is 38412.

Does NGAP transport support IPv4 and IPv6?

Yes. The NG-C signaling transport supports IPv6 and or IPv4.

How are non-UE-associated and UE-associated procedures separated?

SCTP stream pairs are reserved so that interface-level procedures and UE-related procedures can be kept distinct in transport usage.

Related Content