NSLPI

NAS Signalling Low Priority Indication

Core Network →
Introduced in Rel-12

NSLPI is a NAS-level indication set by the UE to signal that a NAS signalling request is of low priority, which the network uses for congestion control to prioritize critical procedures.

Category
Core Network
Introduced
Rel-12
Where
User Equipment
Specifications
1 specs
NSLPI Description Purpose Related Classification Specifications

Description

The NAS Signalling Low Priority Indication (NSLPI) is a parameter within the Non-Access Stratum (NAS) protocol, used in EPS (Evolved Packet System) and 5GS. It is included in certain NAS request messages, such as ATTACH REQUEST, TRACKING AREA UPDATE REQUEST, and SERVICE REQUEST, sent from the User Equipment (UE) to the core network's Mobility Management Entity (MME) in 4G or Access and Mobility Management Function (AMF) in 5G. The NSLPI is a single-bit flag that, when set, informs the network that the associated signalling procedure can be treated as lower priority. The core network node (MME/AMF) uses this indication as a key input for its congestion and overload control mechanisms. For example, if the MME is experiencing high load, it may reject or delay the processing of requests marked with NSLPI, while continuing to accept high-priority requests. The UE is mandated to set the NSLPI for certain automated, non-user-initiated procedures, such as periodic tracking area updates or signalling related to delay-tolerant services. The mechanism works in conjunction with other NAS-level features like the Attach with IMSI and the Extended Wait Timer. When a low-priority request is rejected due to congestion, the network typically provides a back-off timer (e.g., T3346) to the UE, preventing it from immediately reattempting the procedure and thus alleviating the signalling storm. This end-to-end, application-layer congestion control is a crucial tool for maintaining network stability during peak loads or failure scenarios.

Purpose & Motivation

The NSLPI was introduced to address the problem of control plane signalling storms and core network overload, which became more pronounced with the proliferation of M2M and IoT devices. Early cellular networks were designed primarily for human-centric communication, where signalling is relatively infrequent and user-initiated. The advent of millions of IoT devices performing automated, periodic registration and reporting created the risk of massive, synchronized signalling traffic that could overwhelm the MME. This could degrade service for all users, including those making emergency calls. The NSLPI provides a standardized way for UEs—especially those configured for delay-tolerant or low-priority services—to identify their signalling as non-critical. This allows the network to implement intelligent overload control, prioritizing essential human traffic and critical machine communication. It solves the limitation of networks treating all signalling requests equally, which made them vulnerable to congestion collapse from massive IoT deployments. The feature is a cornerstone of 3GPP's Machine-Type Communication (MTC) enhancements, enabling scalable support for a vast number of devices without compromising network reliability.

Classification

Part ofNAS
Related approachesMTC

Evolution Across Releases

Rel-12 Initial

Introduced as part of the MTC and network overload control enhancements. The NSLPI was defined in the NAS protocol specifications (TS 24.301) and associated core network procedures (TS 23.401) to allow UEs to indicate low-priority signalling, enabling the MME to apply specific congestion control measures for such requests.

Explore further

Broader topics and technologies where NSLPI plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 27.007 vj40 AT Command Set for UE Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.