BSS GPRS Protocol Virtual Connection Identifier

Description

The BSS GPRS Protocol Virtual Connection Identifier (BVCI) is a fundamental element within the Gb interface architecture, which connects the GSM/EDGE Radio Access Network (GERAN) to the GPRS core network. It operates within the BSS GPRS Protocol (BSSGP), a layer 3 protocol defined in 3GPP TS 48.016. The BVCI serves as a local identifier at the Gb interface, uniquely marking a virtual connection between a specific BSS and an SGSN. This virtual connection is essentially a logical path used to transport GPRS signaling and user data packets associated with mobile stations (MS) currently served by that BSS.

Architecturally, the BVCI works in conjunction with other identifiers like the Network Service Access Point Identifier (NSAPI) and the Temporary Logical Link Identity (TLLI). While the TLLI identifies a specific MS at the radio interface (Um) and the LLC layer, and the NSAPI identifies a specific PDP context for that MS, the BVCI provides the routing context at the Gb interface. A single BVCI is established per BSS for a given SGSN, but it carries multiplexed traffic for all MSs and their PDP contexts active in the cells controlled by that BSS. The BSSGP layer uses the BVCI to correctly route downlink packets from the SGSN to the correct BSS and, subsequently, to the correct cell and MS. Conversely, uplink packets from the BSS to the SGSN are also tagged with the BVCI.

The key components involved are the BSS (comprising BTSs and BSC) and the SGSN. The BVCI is assigned during the Gb interface initialization or BSS configuration. It is not signaled over the radio interface to the MS; it is purely a network-side identifier for Gb interface management. Its role is to abstract the physical Gb link (often Frame Relay or IP-based) into logical connections, allowing a single physical interface to handle traffic for thousands of mobile users efficiently. This multiplexing capability is vital for scalability and resource optimization in the access network.

In operation, when an SGSN has downlink data for an MS, it uses the BVCI associated with the BSS serving that MS's current cell. The BSSGP PDU containing the data includes the BVCI. The BSS receives this PDU, examines the BVCI to confirm it's destined for itself, and then uses the accompanying TLLI and other information to route the data to the correct radio resource (e.g., a specific PDTCH). This separation of concerns—routing at the Gb interface via BVCI and routing at the radio interface via TLLI—simplifies network design and enhances reliability.

Purpose & Motivation

BVCI was created to solve the fundamental problem of efficiently managing and routing packet-switched data traffic over the existing circuit-switched oriented GSM infrastructure when GPRS was introduced. Prior to GPRS, GSM networks were designed primarily for voice calls, with dedicated physical channels (TCH) assigned per call on the A-interface. This model was inefficient for bursty, intermittent data traffic. The introduction of packet-switching required a method to multiplex many users' data sessions over shared network resources.

The BVCI addresses this by providing a logical multiplexing identifier at the critical junction between the radio access network (BSS) and the packet core (SGSN). Without such an identifier, the network would need to establish a separate physical or permanent virtual circuit (in a Frame Relay context) for each MS or PDP context, which would be prohibitively complex and resource-intensive. The BVCI allows a single, managed virtual connection (representing the aggregate traffic for all GPRS users in a BSS area) to exist on the Gb interface. This dramatically reduces signaling overhead and simplifies network configuration and management.

Historically, its creation was motivated by the need for a scalable, cost-effective migration path to mobile data within the 3GPP Release 99 framework. It enabled the reuse of existing BSS infrastructure with minimal hardware changes while introducing the packet-switched core. The BVCI, as part of the BSSGP protocol, was a key enabler for the 'always-on' connectivity model of GPRS, allowing the network to manage user state and data routing without maintaining dedicated end-to-end circuits.

Key Features

• Uniquely identifies a virtual connection between a specific BSS and an SGSN on the Gb interface
• Enables multiplexing of all GPRS user plane and control plane traffic for a BSS over a single logical path
• Works in conjunction with TLLI and NSAPI for end-to-end packet routing from SGSN to the mobile device
• A network-side identifier not exposed to the User Equipment (UE), simplifying mobile device operation
• Essential for the BSSGP protocol's routing function, directing downlink packets to the correct BSS
• Supports scalability by abstracting the physical layer, allowing many users to share access network resources

Evolution Across Releases

Defining Specifications