5G NAS Architecture and N1 Context
NAS is the non-access stratum signaling family used for logical UE-to-core control in 5G. It is the protocol layer that carries mobility-side and session-side meaning between the UE and the core, especially around registration, identity, authentication, security, service continuity, and PDU session control.
This page explains where NAS sits in the 5G control plane, what N1 means, how NAS relates to N2 and RRC in live procedures, how NAS appears across 3GPP and non-3GPP access, and how the NAS-MM and NAS-SM split helps organize the protocol before moving into procedure-level detail.
Quick facts
| Technology | 5G |
|---|---|
| Area / Protocol | NAS architecture and N1 context |
| Main relationship | Logical UE-to-core control signaling on N1 |
| Key split | NAS-MM for mobility-side control and NAS-SM for session-side control |
| Access scope | 3GPP access and non-3GPP access within the wider 5GS architecture view |
| Related topics | N1, N2, RRC, NGAP, AMF, SMF, registration, service request, PDU session control |
Contents
Overview
NAS should be understood first as a control-plane architecture concept, not only as a message set. It belongs to the UE-to-core signaling relationship and defines how the UE and the core exchange control meaning around mobility, identity, security, reachability, and session service.
That architecture view matters because NAS often appears inside wider end-to-end procedures that also involve radio-side control and access-core relay behavior. In practice, NAS rarely stands alone in traces even though its logical signaling relationship is distinct.
Where NAS fits
In 5GS architecture, NAS belongs to the control conversation between the UE and the core. The mobility-side anchor for that relationship is the AMF, while session-side control is read in relation to the SMF. NAS is therefore best understood as the control-layer meaning between the UE and core functions rather than as a pure access-network protocol.
| Item | Architecture meaning | Why it matters |
|---|---|---|
| UE | Origin and endpoint for NAS behavior on the device side. | NAS procedures begin with UE intent, state, identity, or response behavior. |
| AMF | Main mobility-side NAS anchor in the core. | Registration, reachability, identity, and security progression are centered here. |
| SMF | Session-side control function viewed through NAS session-management meaning. | PDU session procedures are easier to read when session-side control is separated from mobility-side control. |
| Access network | Path through which NAS often becomes visible in live 5G procedures. | Explains why NAS is often read together with RRC and NGAP even though its logical relationship is UE-to-core. |
N1 context
N1 is the logical relationship used for NAS signaling between the UE and the AMF. It is not simply a transport label. It is the architecture context that tells you where NAS belongs, how the signaling is described, and why NAS procedures are interpreted as UE-to-core control even when they are visible inside access-side traces.
| Context | Meaning | Trace reading note |
|---|---|---|
| N1 | Logical UE-to-AMF relationship for NAS signaling. | This is the main architectural home of NAS in 5G. |
| Logical rather than purely physical | N1 describes signaling meaning, not just one visible transport hop. | Explains why NAS is still treated as UE-to-core signaling when it appears through access-side relay. |
| Mobility-side anchor | The AMF is the key N1-side control anchor. | Most early NAS procedures should first be read against AMF-side control context. |
N1, N2, and RRC
A common source of confusion is that NAS is logically UE-to-core signaling, but in real access procedures it often appears together with RRC and NGAP. RRC governs radio-side control, NGAP governs access-to-core control signaling on N2, and NAS is carried through that wider procedure path when the UE and core exchange control information.
That is why a registration or service issue can begin in RRC setup, become visible in NGAP transport, and only then reach the NAS message that shows the final control meaning.
| Protocol or interface | Main role | How it relates to NAS |
|---|---|---|
| RRC | Radio-side control between UE and gNB. | Provides the access-side signaling environment in which NAS often becomes visible during entry or continuity procedures. |
| N2 / NGAP | Access-to-core control path between gNB and AMF. | Relays or coordinates access-core signaling around NAS progression. |
| N1 / NAS | Logical UE-to-core control relationship. | Carries the actual mobility-side and session-side control meaning. |
N2 Interface in 5G
Open the N2 reference when the NAS question has to be read together with NGAP relay, access-core signaling, or AMF-facing control transport.
5G RRC Protocol
Use the RRC protocol hub when the issue begins with radio-side control, signaling setup, or UE-to-gNB procedure context before NAS reaches the core cleanly.
3GPP and non-3GPP access
NAS is not limited to one access model. In the wider 5GS architecture view, NAS remains part of the UE-to-core control relationship across both 3GPP and non-3GPP access. That matters because the same core-side mobility and session-control logic may be encountered even when the access side differs.
| Access model | Context | Why it matters for NAS reading |
|---|---|---|
| 3GPP access | NAS commonly appears together with radio-side control and access-core signaling. | This is the path most readers first meet during registration, service request, and session setup traces. |
| Non-3GPP access | NAS still belongs to the wider UE-to-core control model even though access-side mechanics differ. | Helps avoid treating NAS as a purely radio-access protocol. |
NAS-MM and NAS-SM
One of the most useful architecture-level separations inside NAS is the split between NAS-MM (NAS Mobility Management) and NAS-SM (NAS Session Management). Without that split, many readers treat NAS as one large message family and lose the difference between mobility-side control and session-side control.
NAS-MM covers registration, identity, authentication, security, service continuity, deregistration, and related control status. NAS-SM covers PDU session establishment, modification, release, transport, and session status handling.
| Area | Main role | Typical questions |
|---|---|---|
| NAS-MM | Mobility-side control between UE and core. | Did the UE register, authenticate, establish NAS security, stay reachable, or return to service? |
| NAS-SM | Session-side control for data-session service. | Was the requested PDU session accepted, modified, released, or otherwise maintained correctly? |
Why this context matters
Most NAS confusion comes from mixing logical relationship, access-side visibility, and procedure ownership. If you first place NAS correctly in the architecture, it becomes much easier to decide whether a problem belongs mainly to radio entry, NGAP relay, mobility-side NAS control, or session-side NAS control.
References
- 3GPP TS 24.501, Non-Access-Stratum (NAS) protocol for the 5G System
- 3GPP TS 23.501, System architecture for the 5G System
- 3GPP TS 23.502, Procedures for the 5G System
- 3GPP TS 24.502, Access to the 5G Core Network and interworking procedures
FAQ
What is the main architectural role of NAS in 5G?
NAS is the UE-to-core control signaling family used for mobility-side and session-side control in the 5G system.
What is NAS in 5G?
NAS is the non-access stratum signaling family used for logical UE-to-core control in 5G, especially around mobility management, identity, security, service continuity, and session control.
What does N1 mean in 5G?
N1 is the logical signaling relationship used for NAS between the UE and the AMF. It defines the architectural context in which NAS is described and interpreted.
How is NAS different from NGAP or RRC?
NAS carries UE-to-core control meaning, NGAP carries access-to-core control signaling on N2, and RRC handles radio-side control between the UE and the gNB. They often appear in the same end-to-end procedure, but they belong to different protocol roles.
Why is NAS described on N1 if it appears in RRC and NGAP procedures?
Because N1 is the logical UE-to-AMF relationship for NAS. In live access procedures, NAS is often visible through wider radio-side and access-core signaling context, but its logical control meaning remains UE-to-core.
What is the difference between NAS-MM and NAS-SM?
NAS-MM covers mobility-side control such as registration, identity, authentication, security, and service continuity. NAS-SM covers session-side control such as PDU session establishment, modification, release, and related session status.
Should NAS always be read together with NGAP?
Not always, but often in 3GPP access traces. NAS should be read with NGAP when access-core relay behavior or N2 procedure context affects what the UE-to-core signaling is doing.