BSS GPRS Protocol Virtual Connection

Description

The BSS GPRS Protocol Virtual Connection (BVC) is a fundamental concept in the GPRS architecture that establishes logical connectivity between the Base Station System (BSS) and the Serving GPRS Support Node (SGSN) via the Gb interface. Each BVC represents a virtual point-to-point connection that carries BSSGP (Base Station System GPRS Protocol) messages, which include both signaling information and user data packets. The BVC operates at the network layer, providing an abstraction that separates the logical connection management from the underlying physical transport layer, which typically uses Frame Relay or IP-based protocols.

Architecturally, each BVC corresponds to a specific routing area within the BSS coverage area. When a mobile station attaches to the GPRS network, it is associated with a particular BVC based on its current location. The BSS maintains BVC contexts that include information about the routing area, cell identifiers, and associated mobile stations. The SGSN similarly maintains BVC contexts to track the logical connections to various BSS elements. This two-ended context management enables coordinated packet routing and mobility handling as users move between cells.

From a protocol perspective, BVC operates within the BSSGP layer, which sits above the Network Service (NS) layer in the Gb interface protocol stack. The NS layer provides the physical transport, while BSSGP (and by extension BVC) handles logical connection management, flow control, and quality of service parameters. Each BVC is identified by a unique BVC identifier (BVCI) that allows both BSS and SGSN to distinguish between different logical connections. The BVCI is used in all BSSGP messages to ensure proper routing to the correct logical endpoint.

The BVC mechanism supports several critical functions in GPRS networks. First, it enables efficient packet routing by providing logical paths for downlink data from SGSN to BSS and uplink data from BSS to SGSN. Second, it supports mobility management by allowing the SGSN to track which BVC (and thus which routing area) a mobile station is currently using. Third, it facilitates flow control through BSSGP flow control messages that manage the data rate on each BVC independently. Fourth, it supports cell broadcast services by providing logical channels for broadcast message distribution to multiple cells.

In operation, BVC establishment occurs during BSS initialization or when new routing areas are configured. The BSS sends BVC-RESET messages to the SGSN to establish or reset BVC contexts. Once established, the BVC remains active until explicitly reset or until network reconfiguration occurs. The BVC management includes error handling mechanisms where BVC-FLUSH messages can clear buffered data in case of errors, and BVC-BLOCK/UNBLOCK messages can temporarily suspend and resume BVC operation for maintenance purposes.

Purpose & Motivation

The BVC concept was developed to address the fundamental challenge of connecting circuit-switched oriented Base Station Systems (BSS) with packet-switched GPRS core networks. Before GPRS, BSS elements communicated with MSC (Mobile Switching Center) using circuit-switched protocols optimized for voice calls. The introduction of packet data services required a new approach that could handle bursty data traffic, support multiple simultaneous connections, and provide efficient routing without requiring physical circuit establishment for each data session.

BVC solved several specific problems in early GPRS deployments. First, it provided a logical abstraction layer that allowed multiple virtual connections to share the same physical transport resources between BSS and SGSN. This was crucial because establishing dedicated physical circuits for each packet data connection would have been prohibitively expensive and inefficient. Second, BVC enabled the separation of control plane (signaling) and user plane (data) traffic within the same logical framework, allowing for coordinated management of both types of traffic. Third, it supported the mobility requirements of packet data users by providing logical connections that could be maintained as users moved between cells, without requiring physical reconfiguration.

The historical context for BVC development was the transition from 2G voice-centric networks to 2.5G data-capable networks. Existing BSS infrastructure needed to be reused for GPRS services to minimize deployment costs, but the traditional A-interface protocols were unsuitable for packet data. BVC, as part of the BSSGP protocol suite, provided the necessary adaptation layer that allowed existing BSS hardware to support packet switching while maintaining backward compatibility with circuit-switched services. This approach enabled network operators to introduce GPRS services incrementally without replacing their entire radio access network infrastructure.

Key Features

• Logical point-to-point connection abstraction between BSS and SGSN
• Supports multiple virtual connections over shared physical transport resources
• Enables independent flow control per virtual connection using BSSGP mechanisms
• Provides routing area-based logical grouping for efficient mobility management
• Supports both signaling (control plane) and user data (user plane) transmission
• Includes error recovery mechanisms through BVC-RESET and BVC-FLUSH operations

Evolution Across Releases

Defining Specifications