Network Resource Identifier

Description

The Network Resource Identifier (NRI) is a specific field within the structure of the Temporary Mobile Subscriber Identity (TMSI) and its derivatives like the P-TMSI in GPRS/UMTS. The TMSI is a temporary identifier assigned by the network to a mobile subscriber to protect the permanent International Mobile Subscriber Identity (IMSI) from eavesdropping. The NRI is a subset of bits within the TMSI value that is used for routing purposes within a pool of core network nodes. In circuit-switched (CS) domains, it routes to the correct Mobile Switching Center (MSC), and in packet-switched (PS) domains, it routes to the correct Serving GPRS Support Node (SGSN).

Architecturally, the concept is used in a Network Resource Identifier (NRI) pool area. This is a geographical area served by a group (pool) of MSCs or SGSNs. When a UE registers with the network, the core network node (e.g., an MSC from the pool) assigns a TMSI that contains an NRI value corresponding to that specific node. The structure of the TMSI, including the length and position of the NRI field, is configured by the network operator. For example, an operator might designate the 10 most significant bits of the TMSI as the NRI. The remaining bits are used as a local identifier unique within that node.

How it works is central to mobility and session management. When a UE sends a signaling message (e.g., a Location Update Request or a Service Request) and includes its TMSI, the Radio Access Network (RAN) node (BSC in GSM, RNC in UMTS, or eNodeB in LTE) examines the NRI field. The RAN is configured with a mapping table that associates each possible NRI value with a specific core network node (MSC or SGSN) from the pool. The RAN uses this NRI to route the initial message directly to the correct core node without broadcasting the request to all nodes in the pool. This mechanism is known as NRI-based routing. It allows the UE to be efficiently managed by the same core node as it moves within the pool area, supporting features like MSC/SGSN pooling for load sharing and redundancy. If a UE roams into an area where the NRI is not recognized (e.g., outside its home pool area), the RAN uses default routing procedures, often leading to a reallocation of a new TMSI with a local NRI.

Purpose & Motivation

The NRI was created to solve the problem of efficient and scalable routing of mobile subscriber signaling within a shared radio access network connected to multiple core network nodes. In early GSM deployments, a BSC was typically connected to a single MSC. As networks grew, operators deployed pools of MSCs or SGSNs to increase capacity and provide redundancy (MSC/SGSN Pool). Without the NRI mechanism, the RAN would have no way of knowing which MSC in the pool was serving a particular UE when it initiated contact, potentially requiring inefficient broadcast queries or forcing static, inflexible associations between radio cells and core nodes.

The NRI addresses this by embedding routing information directly into the temporary subscriber identifier. This allows for stateless routing at the RAN: the RAN simply extracts the NRI bits from the TMSI and forwards the message to the corresponding node. This enables true load balancing and redundancy within a pool. If one MSC fails, another MSC in the pool can take over its traffic, and UEs can be redistributed by assigning new TMSIs with different NRIs. It decouples the radio topology from the core network topology, providing significant operational flexibility.

Historically, its introduction (conceptually from R99 onwards for UMTS/GPRS) was a key enabler for core network pooling, which improves network resilience, simplifies network planning (no need for MSC border areas), and enhances resource utilization. It solved the limitations of earlier, more rigid architectures and remains a foundational concept for mobility management in 2G, 3G, and 4G networks, even as 5G introduces different mechanisms like the 5G-GUTI and service-based architecture.

Key Features

• A configurable bit field within the TMSI/P-TMSI structure
• Enables RAN (BSC/RNC/eNodeB) to route initial UE messages to the correct MSC or SGSN in a pool
• Supports MSC Pool and SGSN Pool architectures for load balancing and redundancy
• Defines a Network Resource Identifier (NRI) pool area for seamless mobility
• Allows dynamic reassignment of UEs between core nodes within the pool
• Protects subscriber privacy by being part of the temporary identifier (TMSI)

Evolution Across Releases

Defining Specifications