Network Service Entity Identifier

Description

The Network Service Entity Identifier (NSEI) is a fundamental identifier within the GPRS and early 3G network architecture, defined in the Gb interface specifications. It uniquely identifies a Network Service Entity, which is a logical entity representing a BSS (Base Station Subsystem) or a group of BSSs from the perspective of the SGSN (Serving GPRS Support Node). The NSEI is used within the Network Service (NS) layer protocols, which are responsible for the transport of BSSGP (Base Station System GPRS Protocol) packets across the frame relay-based Gb interface. This layer manages virtual connections, known as Network Service Virtual Connections (NS-VCs), between the BSS and SGSN. The NSEI, along with the BVCI (BSSGP Virtual Connection Identifier), forms a two-tier addressing scheme that allows the SGSN to route packets to the correct cell within the correct BSS. The SGSN maintains a mapping of NSEIs to the underlying transport network addresses (e.g., Frame Relay DLCIs) and uses this information to establish and manage the NS-VCs. This mechanism is essential for the SGSN to manage multiple BSSs, handle mobility events like cell reselection, and ensure reliable data transfer for packet-switched services. The NSEI's role is confined to the Gb interface architecture and is a key component in the pre-S1 interface era of mobile packet data.

Purpose & Motivation

The NSEI was created to address the need for a scalable and efficient addressing mechanism for Base Station Subsystems within the GPRS network architecture introduced in 2.5G. Prior to GPRS, circuit-switched voice networks had different control mechanisms. The packet-switched nature of GPRS required a new interface (Gb) and protocol stack to handle data traffic. The primary problem was enabling a single SGSN to communicate with and manage a potentially large number of BSSs and their constituent cells. The NSEI provides a logical identifier that abstracts the physical transport details, allowing the SGSN to identify the source or destination BSS entity for any given data packet or control message. This abstraction simplifies network management, routing, and mobility procedures. It solved the limitation of having to manage direct physical connections to every BSS by introducing a logical layer (Network Service layer) that could multiplex traffic over shared virtual circuits, with the NSEI being the key to demultiplexing and directing traffic at the SGSN.

Key Features

• Uniquely identifies a Network Service Entity (BSS or BSS group) on the Gb interface.
• Forms the first part of a two-tier addressing scheme alongside the BVCI for precise cell identification.
• Used by the SGSN to map logical BSS entities to underlying Frame Relay virtual circuits (NS-VCs).
• Essential for routing BSSGP protocol data units between the BSS and SGSN.
• Supports network management functions like BSS context management and reset procedures.
• A foundational element of the GPRS Tunnelling Protocol (GTP) and packet data routing in 2.5G/3G networks.

Evolution Across Releases

Defining Specifications