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

Glossary term · Core Network

NSR

Network Status Request

Core Network →

NSR is a signaling procedure used to request the operational status or availability of a network entity or service.

Introduced
Rel-10
Where
Radio Access Network
Specifications
3 specs
NSR Description Purpose What changed Neighbours Specifications

Description

Network Status Request (NSR) is a core network signaling procedure defined in 3GPP specifications. It is a generic mechanism where one network entity sends a request to another to ascertain its current operational status, availability, or specific capability information. This procedure is crucial for maintaining network awareness and enabling intelligent routing, load balancing, and failover decisions. The request is typically carried over standard signaling protocols like Diameter or MAP (Mobile Application Part), depending on the network domain and release.

In operation, an NSR message contains identifiers for the requesting and target nodes, along with parameters specifying the type of status information required. The target entity processes the request and returns a Network Status Response containing the queried data. This data can include simple binary availability (e.g., reachable/unreachable), more detailed load information (e.g., current CPU utilization, session count), or specific service support indicators. The procedure is often used by network elements like Serving GPRS Support Nodes (SGSN), Mobility Management Entities (MME), or Home Subscriber Servers (HSS) to determine the best peer for routing signaling messages or to verify the health of a network path before initiating a transaction.

The NSR mechanism supports both proactive and reactive status checking. Proactively, network elements can periodically poll peers to build a dynamic map of network health. Reactively, an element can send an NSR when it needs to select a peer for a new procedure, such as routing a location update request. This enhances network reliability and efficiency by preventing attempts to communicate with failed or overloaded nodes, thereby reducing signaling failures and improving overall service reliability. Its implementation is foundational for features like network redundancy and graceful shutdown procedures.

Purpose & Motivation

The NSR procedure was created to address the need for dynamic network state awareness in increasingly complex and distributed mobile core networks. Early circuit-switched networks had relatively static configurations, but with the evolution to packet-switched and all-IP cores in 2.5G (GPRS) and 3G, networks became more dynamic with elements that could fail, become congested, or be taken out of service for maintenance. Without a standardized status query mechanism, networks relied on static routing or failure detection through timeouts, which was inefficient and led to poor user experience during outages.

NSR solves this by providing a direct, low-overhead method for network elements to interrogate each other's state. This enables intelligent network behavior, such as load sharing across multiple instances of a network function or automatic rerouting around a failure. It is a key enabler for high availability and efficient resource utilization. The procedure's standardization across releases ensures interoperability between network elements from different vendors, which is critical for the multi-vendor ecosystems common in telecom networks.

What changed in its specifications

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

TS 29.153Rel-13 → Rel-14

Added Diameter load control procedures over Ns point and defined Load AVP. Updated Command-Code values references for base protocol updates and backward compatibility.

Full comparison in TS 29.153 →

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-10 Initial

Introduced the Network Status Request procedure as a standardized mechanism. Defined its basic message format and use cases for core network elements to query each other's operational status, primarily within the Evolved Packet Core (EPC) and for interworking with legacy GSM/UMTS core networks.

Defining Specifications

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

SpecificationTitleRelease
TS 29.153 vj00 Ns Reference Point Protocol between SCEF and RCAF Rel-19 read
TS 45.860 vb50 Precoded EGPRS2 Downlink Study Rel-11 read
TS 45.871 ve00 MIMO for GSM/EDGE Downlink Study Rel-14 read