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

Glossary term · Protocol

NAS

Non-Access Stratum

Protocol →

NAS is the protocol layer between a device and the core network that independently manages mobility, sessions, and subscriber identity to establish and maintain connectivity.

Introduced
R99
Where
Radio Access Network › UTRAN (3G)
Specifications
67 specs
Also in
Security, Services, Core Network
NAS Description Purpose What changed Neighbours Detected Changes Specifications

Description

The Non-Access Stratum (NAS) is a key protocol layer in the control plane of 3GPP systems, operating directly between the User Equipment (UE) and the Core Network's control nodes—specifically the Mobility Management Entity (MME) in 4G EPC and the Access and Mobility Management Function (AMF) in 5G Core. It sits above the Access Stratum (AS), which handles radio-specific signaling between the UE and the radio access network (e.g., eNB, gNB). This stratification allows NAS procedures to be largely independent of the specific radio technology (e.g., LTE, NR, non-3GPP access), enabling core network services to be delivered consistently across heterogeneous access networks. The NAS protocol is responsible for the most critical control signaling related to the UE's registration and reachability within the network.

NAS functionality is divided into two primary protocol entities: the Mobility Management (MM) entity and the Session Management (SM) entity. In EPS (4G), these are the EPS Mobility Management (EMM) and EPS Session Management (ESM) protocols. In 5GS, they are the 5G Mobility Management (5GMM) and 5G Session Management (5GSM) protocols. The MM entity handles procedures such as attach/detach, tracking area update, authentication, and security mode control. It manages the UE's registration state and ensures the network can locate and page the UE. The SM entity handles the establishment, modification, and release of Packet Data Unit (PDU) sessions or bearers, which are the data pipelines for user traffic. It negotiates quality of service (QoS) parameters and manages the lifecycle of these data contexts.

NAS messages are carried transparently by the Access Stratum. When a UE sends a NAS message (e.g., an Attach Request), it is encapsulated by the AS protocols (RRC in LTE/NR) and transported to the base station (eNB/gNB). The base station extracts the NAS message and forwards it to the appropriate core network node via the S1-AP or NG-AP interface without interpreting its content. This ensures a clear separation of concerns: the RAN handles radio resource management, while the CN handles subscriber and session management. NAS signaling is always integrity protected and, for sensitive messages, ciphered using keys established during authentication and key agreement (AKA). This end-to-end security between the UE and the core network is a cornerstone of 3GPP system security.

Over successive releases, NAS has evolved to support an increasing array of services and network architectures. It introduced support for emergency calls, power saving features like Power Saving Mode (PSM) and extended idle mode DRX, and enhanced coverage for IoT devices (CE mode). With 5G, the NAS protocol was redesigned to be more modular and forward-compatible, supporting network slicing, alternative authentication methods, and seamless interworking between 3GPP and non-3GPP (e.g., Wi-Fi) access. The NAS layer is therefore not just a connectivity enabler but a flexible framework that adapts to new service requirements and network paradigms defined across 3GPP releases.

Purpose & Motivation

The Non-Access Stratum was created to establish a clear, standardized, and access-agnostic signaling protocol between the mobile device and the core network. Prior to its formal definition in 3GPP, early cellular systems had more monolithic and technology-dependent control signaling. The stratification into Access Stratum and Non-Access Stratum, a concept solidified with GSM and fully realized in UMTS, was a pivotal architectural decision. It separated radio-specific control functions (handled in the AS by the RAN) from subscriber and connection management functions (handled in the NAS by the CN). This separation solved critical problems of network evolution and multi-vendor interoperability.

A primary motivation was to enable core network services to evolve independently from the radio interface. A network operator could upgrade its core network to support new services (e.g., IMS-based voice) without requiring changes to every base station, as long as the AS could transparently transport the new NAS messages. Conversely, new radio technologies (e.g., moving from GSM to UMTS to LTE) could be introduced without fundamentally altering the core network procedures for authenticating a user or establishing a data session. This greatly reduced complexity and cost for network modernization. It also facilitated seamless mobility and service continuity when a device moved between different radio access technologies (inter-RAT mobility), as the NAS context could be preserved and transferred between core network nodes.

Furthermore, NAS provides a secure, trusted endpoint for subscriber management. By terminating in the core network, it allows for centralized authentication, authorization, and key management. The security context established via NAS protocols (like AKA) is used to protect both NAS signaling itself and the user plane data. This architecture addresses the limitation of having critical security functions distributed or dependent on the potentially less-trusted radio access network. In summary, NAS exists to provide a stable, secure, and future-proof control plane foundation that decouples service logic from access technology, enabling the scalable and flexible mobile networks we have today.

What changed in its specifications

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

TR 21.905Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 21.905 →
TS 23.236Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 23.236: 1 clause changed, with no change attributed to a release feature.

Full comparison in TS 23.236 →

Protocol Stack

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (35 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 14 changes
  • Enabling 3GPP PS data off in roaming-NAS MO TS 24.368CR0033
  • Coding of AN-parameters in EAP 5G-NAS message TS 24.502CR0005
  • TCP protocol as inner transport layer protocol for NAS signaling TS 24.502CR0040
  • AMF congestion when receiving NAS message TS 24.502CR0051
  • Introduction of Authentication procedure and NAS security context handling for 5G test cases TS 31.121CR0306
  • Triggering UE capability info retrieval using DL NAS TRANSPORT (Stage 2) TS 36.300CR1160

+ 8 more changes

Rel-16 7 changes
  • NAS configuration for restriction on access to RLOS TS 24.368CR0046
  • EAP-5G handling and transport of NAS messages for wireline access TS 24.502CR0110
  • Introduction of TCs to allow testing NAS security context storage in multiple registration TS 31.121CR0519
  • 5GSM cause #27 and #70 for NAS MO SM_RetryWaitTime TS 24.368CR0043
  • Error in EAP-Response/5G-NAS message coding TS 24.502CR0066
  • NAS handling error of nas-Container for security key derivation TS 36.331CR4099

+ 1 more changes

Rel-17 5 changes
  • Introduce a new 31.121 TC for NAS configuration “No E-UTRA Disabling In 5GS” TS 31.121CR0555
  • Support for mapping complete security capabilities from NAS [UE_Sec_Caps] TS 36.413CR1835
  • Introduce "PLMNs not allowed to operate at the present UE location" in table AS/NAS functional division TS 36.304CR0853
  • Correction on UE behavior for NAS-based busy indication in RRC_INACTIVE TS 36.331CR4822
  • Correcting NAS transport between 5G RG and W-AGF to accommodate latest BBF developments TS 24.502CR0200
Rel-18 5 changes
  • NAS configuration MO for using SENSE TS 24.368CR0065
  • NAS protocol supports LCS PRU messages TS 24.571CR0017
  • NAS transport for RSPP TS 24.571CR0047
  • Updates to NAS Configuration MO for SENSE TS 24.368CR0066
  • Correction to NAS signalling transport for downlink SLPP messages TS 24.571CR0064
Rel-19 4 changes
  • NAS MO Lower Selection-priority for PLMN Selection TS 24.368CR0087
  • Extra IAB information in stage 2 related to Downlink NAS transport and to UE CONTEXT MODIFICATION REQUEST TS 33.127CR0255
  • Adding NAS configuration parameter Satellite_Disabling_Allowed_for_EMM_cause_#15 TS 24.368CR0077
  • Corrections to the UL NAS TRANSPORT and DL NAS TRANSPORT messages TS 24.571CR0093

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 23.110 vj00 Access Stratum Services Specification Rel-19 read
TS 23.236 vj00 Intra Domain Connection of RAN Nodes to Multiple CN Nodes Rel-19 read
TS 23.851 v610 Network Sharing Architecture for 3G Systems Rel-6 read
TR 23.923 v300 Mobile IP+ Feasibility Study for UMTS/GPRS R99 read
TR 23.979 vj00 PoC over 3GPP Systems Architectural Requirements Rel-19 read
TS 24.171 vj00 NAS Protocol for LCS in E-UTRAN Rel-19 read
TS 24.206 v750 Voice Call Continuity Between CS and IMS Rel-7 read
TS 24.292 vj00 IMS Centralized Services (ICS) Protocol Rel-19 read
TS 24.368 vk00 NAS Configuration Management Object Rel-20 read
TS 24.502 vk00 Non-3GPP Access Network Discovery and Selection Rel-20 read
TS 24.543 vk10 SEAL Data Delivery Management Protocol Rel-20 read
TS 24.558 vk00 Edge Application Enabler Server APIs Stage 3 Rel-20 read
TS 24.571 vj50 5G NAS Location Services (LCS) Rel-19 read
TS 25.301 vj00 UE-UTRAN Radio Interface Protocol Architecture Rel-19 read
TS 25.304 vj10 UE Idle Mode Procedures Rel-19 read
TS 25.305 vj00 UTRAN UE Positioning Stage 2 Rel-19 read
TS 25.323 vj00 Packet Data Convergence Protocol (PDCP) Specification Rel-19 read
TS 25.324 vj00 Broadcast/Multicast Control Protocol Rel-19 read
TS 25.331 vj01 UTRAN Radio Resource Control Protocol Rel-19 read
TS 25.367 vj00 Home NodeB Mobility Procedures Rel-19 read
TS 25.401 vj00 UTRAN Overall Architecture Rel-19 read
TS 25.410 vj00 Iu Interface Introduction for UTRAN Rel-19 read
TS 25.413 vj00 Radio Access Network Application Part (RANAP) Rel-19 read
TS 25.415 vj00 Iu Interface User Plane Protocol Rel-19 read
TS 25.423 vj00 UTRAN RNSAP Specification Rel-19 read
TS 25.824 v800 HSPA Evolution for 1.28Mcps TDD Study Rel-8 read
TR 25.912 vj00 Evolved UTRA and UTRAN Technical Report Rel-19 read
TS 25.913 v900 Evolved UTRA and UTRAN Requirements Rel-9 read
TR 25.931 vj00 UTRAN Signalling Procedures Examples Rel-19 read
TS 26.247 vj10 Transparent End-to-End Packet-switched Streaming Rel-19 read
TS 26.802 vk00 5G Media Streaming Multicast Enhancements Rel-20 read
TS 26.891 vg00 Media Distribution Services in 5G System Rel-16 read
TS 29.273 vj20 EPS AAA Reference Points and Procedures Rel-19 read
TS 29.292 vj00 IMS Centralized Services (ICS) Interworking Rel-19 read
TS 29.503 vk10 UDM Service Based Interface Rel-20 read
TS 31.121 vj00 UICC Application Test Specification Rel-19 read
TS 32.808 v800 Common Profile Storage Framework for User Data Rel-8 read
TS 33.127 vj80 Lawful Interception Architecture Rel-19 read
TS 33.401 vj20 EPS Security Architecture Rel-19 read
TS 33.501 vk30 5G Security Architecture Rel-20 read
TS 33.820 v830 H(e)NB Security Threats and Countermeasures Rel-8 read
TS 33.821 v900 LTE/SAE Security Threat Analysis and Countermeasures Rel-9 read
TS 33.835 vg10 Study on authentication and key management for apps Rel-16 read
TR 33.841 vg10 Security aspects; Study on 256-bit algorithms for 5G Rel-16 read
TS 33.856 vg10 Security for 5G to 3G Voice Continuity Rel-16 read
TS 33.859 vb10 UTRAN Key Hierarchy Enhancement Study Rel-11 read
TS 33.938 vj30 5G Standalone Cryptographic Inventory Rel-19 read
TS 36.300 vj20 E-UTRAN Radio Interface Protocol Architecture Rel-19 read
TS 36.302 vj00 E-UTRA Physical Layer Services Rel-19 read
TS 36.304 vj30 LTE UE Idle Mode Procedures Rel-19 read
TS 36.331 vj40 E-UTRA Radio Resource Control (RRC) Protocol Rel-19 read
TS 36.401 vj00 E-UTRAN Overall Architecture Description Rel-19 read
TS 36.413 vj20 S1 Application Protocol (S1AP) for E-UTRAN Rel-19 read
TS 36.444 vj00 M3AP Protocol Specification for M3 Interface Rel-19 read
TS 36.938 v900 E-UTRAN to 3GPP2/Mobile WiMAX Mobility Rel-9 read
TR 36.976 vj00 LTE-based 5G Terrestrial Broadcast Overview Rel-19 read
TS 38.304 vj30 NR UE Idle and Inactive State Procedures Rel-19 read
TS 38.401 vj30 NG-RAN Architecture Description Rel-19 read
TR 38.882 vi00 Technical Report on UE Location Service Rel-18 read
TS 43.051 vj00 GERAN Stage 2 Service Description Rel-19 read
TS 43.318 vj00 Generic Access Network (GAN) Stage 2 Rel-19 read
TR 43.901 vj00 Generic Access to A/Gb Interface Feasibility Study Rel-19 read
TR 43.902 vj00 GAN Enhancements Feasibility Study Rel-19 read
TS 44.060 vj00 GERAN RLC/MAC Protocol Specification Rel-19 read
TS 44.160 vg00 GERAN Iu Mode RLC/MAC Protocol Specification Rel-16 read
TS 44.318 vj00 Generic Access Network (GAN) Interface Procedures Rel-19 read