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

Home / 5G / Protocols / NGAP / Identifiers and Logical Connections

NGAP Identifiers and Logical Connections

NGAP identifiers and logical connections define how one UE is tracked across UE-associated signaling on N2. They are the main anchors for reading per-UE procedures correctly, especially when access signaling, NAS transport, context setup, mobility, release, or reset handling all appear in the same trace.

Use it when you need to answer a practical trace question: which messages belong to the same UE, when AMF UE NGAP ID should appear, how RAN UE NGAP ID is reused across a live context, and what it means when a UE-associated logical NG-connection is released, reset, or no longer trusted.

Technology 5G
Area NGAP identifiers and UE correlation
Scope AMF UE NGAP ID, RAN UE NGAP ID, and UE-associated logical NG-connection handling
Main identifiers AMF UE NGAP ID and RAN UE NGAP ID
Main use UE correlation, procedure continuity, reset handling, and trace reading
Related pages NGAP Overview, Initial UE Message, Uplink NAS Transport, Initial Context Setup, NG Reset, UE Context Release

Contents

  1. Overview
  2. Why identifiers matter
  3. Main identifiers
  4. UE-associated logical NG-connection
  5. Identifier lifecycle
  6. Trace correlation workflow
  7. Procedure examples
  8. Troubleshooting
  9. Related pages
  10. References
  11. FAQ

Overview

NGAP has many procedures, but most live trace work starts with a simpler question: how do you prove that two messages belong to the same UE? The answer usually begins with RAN UE NGAP ID, AMF UE NGAP ID, and the presence or absence of a UE-associated logical NG-connection.

Identifier reading matters because message names alone are not enough. A trace may contain multiple UEs on the same SCTP association, overlapping procedures, partial resets, and release branches. Without correct identifier continuity, it is easy to merge the wrong messages or miss where a UE context was lost.

NG-RAN allocates RAN UE NGAP ID UE-associated logical NG-connection message correlation path AMF UE NGAP ID + RAN UE NGAP ID AMF allocates AMF UE NGAP ID

Why identifiers matter

NGAP is multiplexed across one interface and one transport association, but the signaling itself is often UE-specific. Identifiers are what separate one UE procedure from another and what let you follow continuity through setup, modification, handover, paging return, or release.

Trace problem What identifier reading solves Why it matters
Multiple UEs on one SCTP association Separates per-UE NGAP procedures cleanly. Prevents mixing messages from different UEs.
Early access entry Shows when only RAN-side identity is available. Explains why AMF UE NGAP ID may not appear yet.
Procedure overlap Preserves continuity across setup, NAS transport, and later control procedures. Keeps message timelines accurate.
Reset or release Shows where identifier validity stops. Prevents false assumptions after cleanup or recovery.

Main identifiers

The main practical identifier pair in UE-associated NGAP signaling is RAN UE NGAP ID plus AMF UE NGAP ID. One side allocates each value, and many later messages depend on the pair being read together.

Identifier Allocated by Typical reading use
RAN UE NGAP ID NG-RAN node Earliest UE anchor on the RAN side, often visible at initial access entry.
AMF UE NGAP ID AMF AMF-side UE anchor used once the core has accepted and identified the UE context.
AMF UE NGAP ID + RAN UE NGAP ID pair Both sides together Main correlation pair for most live UE-associated signaling after context establishment.

RAN UE NGAP ID

This is often the first useful UE identifier in NGAP. It appears when the NG-RAN side has created enough local context to send the first UE-associated signaling toward the AMF.

AMF UE NGAP ID

This appears after the AMF has accepted the UE context on its side. From that point onward, many procedures use the AMF UE NGAP ID and RAN UE NGAP ID pair as the stable per-UE correlation anchor.

Initial UE Message

-> RAN UE NGAP ID visible first

-> AMF allocates AMF UE NGAP ID

-> later UE-associated messages use both

Trace note: If a later UE-associated message carries only one side of the expected pair, do not assume the decode is complete. First check whether you are looking at an early entry message, a partial capture, or an abnormal branch.

UE-associated logical NG-connection

A UE-associated logical NG-connection is the per-UE signaling relationship on the NG interface. It is not the same thing as the SCTP association itself. One SCTP association can carry signaling for many UEs, while the logical NG-connection keeps the UE-specific procedure context separate.

Item What it means Why the distinction matters
SCTP association Transport relationship between NG-RAN and AMF. Can stay alive even while individual UE contexts are created or released.
UE-associated logical NG-connection UE-specific signaling context on that interface. Is what most UE-associated procedures actually depend on.
Non-UE-associated signaling Interface-level signaling without one UE context. Does not use the UE identifier pair in the same way.
One SCTP association on N2 UE A RAN UE NGAP ID AMF UE NGAP ID UE B RAN UE NGAP ID AMF UE NGAP ID UE C RAN UE NGAP ID AMF UE NGAP ID

Trace note: Reset and release behavior can target individual UE-associated logical NG-connections even when the transport association itself remains present.

Identifier lifecycle

Identifier reading becomes much easier if you think in lifecycle stages: first appearance, stable paired use, possible mobility updates, and final release or reset. That lifecycle tells you when reuse is plausible and when continuity should stop.

Stage Typical identifier state What to expect
Access entry RAN UE NGAP ID appears first. Early messages may not yet carry AMF UE NGAP ID.
Context established AMF UE NGAP ID and RAN UE NGAP ID pair is available. Most later UE-associated control messages should correlate with both.
Procedure continuation Identifier pair remains stable across setup, modification, and many transport steps. Unexpected change often signals a branch change, reset, or trace-merge problem.
Release or reset UE-associated logical NG-connection is removed or invalidated. Do not expect later continuation with the old context unless a new access branch begins. 
Initial UE Message
        -> RAN UE NGAP ID
                -> AMF UE NGAP ID assigned
                        -> paired UE-associated signaling
                                -> release or reset
                                        -> old correlation ends

Trace correlation workflow

A practical NGAP trace workflow is to start with the earliest visible UE identifier, confirm whether the procedure is UE-associated or non-UE-associated, then rebuild continuity message by message until release, reset, or a new access branch changes the context.

  1. Check whether the message is UE-associated or non-UE-associated.
  2. Look for RAN UE NGAP ID first, especially in early access messages.
  3. Add AMF UE NGAP ID once the AMF-side context exists.
  4. Confirm that later messages keep the same identifier pair.
  5. Stop continuity at release, reset, or other explicit context cleanup points.
Workflow step Main check Common mistake
Classify signaling UE-associated or non-UE-associated? Trying to use UE IDs on Paging or other interface-level signaling.
Anchor early entry Which RAN UE NGAP ID starts the branch? Waiting for AMF UE NGAP ID too early.
Build the pair When does AMF UE NGAP ID become available? Merging messages before AMF-side context is confirmed.
Validate continuity Does the same pair persist? Ignoring reset, release, or handover context changes.

Procedure examples

Identifier behavior is easiest to understand in real procedures. Some messages show the first appearance of the RAN-side identifier, some show the stable paired form, and some mark the end of the UE-associated logical NG-connection.

Procedure or message Identifier reading value Open next
Initial UE Message Best first example for early UE entry and initial RAN-side correlation. Initial UE Message
Uplink NAS Transport Shows continued UE-associated signaling after entry. Uplink NAS Transport
Initial Context Setup Request Strong example of the stable AMF UE NGAP ID and RAN UE NGAP ID pair. Initial Context Setup Request
Path Switch Request Useful for seeing identifier continuity across mobility-related change. Path Switch Request
UE Context Release Command Marks intentional teardown of the live UE-associated NG context. UE Context Release Command
NG Reset Important for full or partial clearing of UE-associated logical NG-connections. NG Reset

Troubleshooting

Many confusing NGAP problems are actually correlation problems. When the UE identifier timeline is wrong, the rest of the interpretation usually goes wrong with it.

Symptom Likely issue What to verify
Later UE-associated message cannot be matched cleanly AMF UE NGAP ID or RAN UE NGAP ID continuity was lost. Rebuild the timeline from Initial UE Message or the last confirmed paired message.
Same transport association appears healthy but one UE branch disappears UE-associated logical NG-connection was released or partially reset. Check UE Context Release and NG Reset messages around the discontinuity.
Paging appears without usable UE identifier pair The signaling is non-UE-associated. Do not force UE-associated correlation rules onto non-UE-associated messages.
Identifier suddenly changes in the middle of a branch Wrong trace merge, mobility branch change, reset, or new access entry. Check procedure transition, handover context, and any explicit cleanup before assuming continuity.

Trace note: If the identifier pair looks inconsistent, verify the procedure class and message direction before blaming content. A response may belong to a different branch, or the real failure may have started at reset or release.

References

  • 3GPP TS 38.413, NG Application Protocol (NGAP)
  • 3GPP TS 38.412, NGAP signaling transport
  • 3GPP TS 38.410, NG-RAN architecture description
  • 3GPP TS 23.501, System architecture for the 5G System
  • 3GPP TS 23.502, Procedures for the 5G System

FAQ

Which identifier should I look for first in early NGAP access signaling?

Start with RAN UE NGAP ID. It is often the first stable UE-specific anchor visible before the AMF allocates AMF UE NGAP ID.

Do all NGAP messages use AMF UE NGAP ID and RAN UE NGAP ID?

No. UE-associated procedures depend on them most, but non-UE-associated procedures such as paging or some interface-management signaling do not use the same per-UE identifier model.

What usually marks the end of a UE-associated logical NG-connection?

Release and reset behavior are the main boundaries. After explicit cleanup, later messages should not be read as a continuation of the old UE-associated context unless a new branch clearly re-establishes it.

Why is identifier pairing important during troubleshooting?

Because many NGAP failures look like message or procedure problems when the real issue is simply that the wrong messages were correlated together.