BSSID

Basic Service Set Identifier

Identifier →
Introduced in Rel-12 Also in: Core Network, Services

BSSID is the unique 48-bit identifier, equivalent to a MAC address, for a Wi-Fi Basic Service Set used in 3GPP WLAN interworking to identify specific access points.

Category
Identifier
Introduced
Rel-12
Where
Radio Access Network › NG-RAN (5G)
Also touches
2 segments
Specifications
11 specs
BSSID Description Purpose Related Classification Detected Changes Specifications

Description

The Basic Service Set Identifier (BSSID) is a fundamental identifier in IEEE 802.11 (Wi-Fi) networks that uniquely identifies a Basic Service Set (BSS), which is essentially a single access point and its associated stations. In the context of 3GPP standards, BSSID becomes crucial for cellular-WLAN interworking scenarios defined starting from Release 12. The BSSID is a 48-bit address that typically corresponds to the MAC address of the wireless access point's radio interface. When a User Equipment (UE) with both cellular and Wi-Fi capabilities performs network discovery and selection, it can report detected BSSIDs to the cellular network infrastructure, enabling network-controlled traffic steering between cellular and Wi-Fi access.

From an architectural perspective, BSSID information flows through multiple 3GPP network elements. The UE measures and collects BSSID information during WLAN scanning procedures. This information can be reported to the Radio Access Network (eNodeB/gNodeB) via measurement reports (specified in 36.305 and 38.305) or to the core network via Non-Access Stratum (NAS) signaling. The Access Network Discovery and Selection Function (ANDSF) or the Access Traffic Steering, Switching and Splitting (ATSSS) functionality in 5GC can use BSSID information to provide the UE with policies for selecting specific Wi-Fi access points. Policy and Charging Rules Function (PCRF) or Policy Control Function (PCF) may also utilize BSSID information for applying QoS and charging policies specific to certain Wi-Fi access points.

In operation, BSSID enables several key functions in 3GPP-WLAN interworking. For network-controlled WLAN selection, the network can instruct the UE to connect to specific BSSIDs based on network conditions, subscription information, or service requirements. For mobility management, BSSID information helps in seamless handover between cellular and Wi-Fi networks, particularly in scenarios like LTE-WLAN Aggregation (LWA) or ATSSS in 5G. The network can also use BSSID for location services, as specified in 36.355 and 37.355, where BSSID measurements contribute to determining UE position when GPS is unavailable or insufficient.

The technical implementation involves BSSID being carried in various 3GPP protocol messages. In LTE, it appears in WLAN measurement configurations and reports between UE and eNodeB. In 5G, it's part of the WLAN mobility information reported by the UE. The BSSID works alongside other WLAN identifiers like SSID (Service Set Identifier) and HESSID (Homogeneous Extended Service Set Identifier) to provide a complete picture of available Wi-Fi networks. While SSID identifies a network name that may be broadcast by multiple access points, BSSID uniquely identifies a specific physical access point, enabling precise network control and management.

Purpose & Motivation

The integration of BSSID into 3GPP standards addresses the growing need for seamless cellular-Wi-Fi interworking as mobile operators increasingly deploy heterogeneous networks combining licensed cellular spectrum with unlicensed Wi-Fi spectrum. Prior to Release 12, 3GPP-WLAN interworking was relatively basic, primarily focusing on access network discovery through SSIDs without the granularity to identify specific access points. This limitation made it difficult for operators to implement sophisticated traffic steering, load balancing, and policy enforcement across specific Wi-Fi access points within their managed networks.

The inclusion of BSSID in 3GPP specifications enables network-controlled selection of specific Wi-Fi access points rather than just Wi-Fi networks in general. This addresses several practical deployment challenges: operators can steer traffic to particular access points based on real-time load conditions, apply different QoS policies for different physical locations, implement more accurate location-based services, and enable advanced features like LTE-WLAN Aggregation where specific radio links are managed at a granular level. Without BSSID identification, the network would only know that a UE is connected to a particular SSID but not which specific access point, limiting optimization possibilities.

Historically, the motivation came from increasing Wi-Fi deployment in operator networks, the need for better traffic management in dense urban environments, and the desire to use all available radio resources efficiently. BSSID provides the necessary granularity for the network to make intelligent decisions about which specific Wi-Fi access point a UE should use, considering factors like signal strength, load, backhaul capacity, and subscription privileges. This represents a significant evolution from earlier 3GPP-WLAN interworking approaches that treated all access points with the same SSID as equivalent.

Classification

Part ofSSID
Related approachesHESSID

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (12 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Studied in Rel-12, normative work from Rel-15.

Rel-15 2 changes

In Release 15, the specification introduced a UE Identifier for routing messages between Core Network Nodes and the RAN. This enhancement facilitates more efficient message handling within the network architecture.

  • Missing AF Transaction Identifier TS 29.514CR0005
  • UE Identifier for routing message between Core Network Nodes and RAN TS 38.305CR0012
Rel-16 4 changes

In Release 16, the new functionality for the BSSID was the introduction of the AF charging identifier. This addition was followed by subsequent corrections to specify the proper data type for this AF charging identifier and to fix the descriptions of resource identifiers used in related notifications.

  • Support of the AF charging identifier TS 29.514CR0111
  • Correction of AF Charging Identifier data type TS 29.514CR0157
  • Correction to resource identifiers descriptions used in notifications TS 29.514CR0278
  • Correction on the object identifier of LPP ASN.1 for R16 TS 37.355CR0329
Rel-17 2 changes

In Release 17, the work on BSSID-related functions focused on clarifications and corrections for identifiers used in network traffic handling and charging. Specifically, enhancements were made to clarify the packet filter identifier and to correct the charging identifier to ensure its uniqueness in roaming scenarios.

  • Clarification of the packet filter identifier TS 29.212CR1708
  • Correction to the charging identifier to enable uniqueness in roaming scenarios TS 29.514CR0407
Rel-18 1 change

In Release 18, no specific changes to the BSSID (Basic Service Set Identifier) function are indicated by the provided Change Request titles. The listed title, "useless AF transaction identifier," pertains to an Application Function transaction identifier and is unrelated to BSSID procedures or capabilities. Therefore, based solely on this input, Release 18 introduced no new BSSID-related features.

  • useless AF transaction identifier TS 29.514CR0437
Rel-19 3 changes

In Release 19, the changes related to the "BSSID" function are not directly addressed in the provided CR titles. The specified updates for this release focus on completing the Satellite Identifier reporting subscription, defining a procedure for PCF-triggered context termination, and updating the identifier tags for E-UTRAN and NG-RAN Tracking Area Identification (TAI) lists.

  • Complete the Satellite Identifier reporting subscription TS 29.514CR0747
  • Procedure for PCF triggered context termination due to released UE address as only key identifier TS 29.514CR0703
  • Update E-UTRAN Tracking Area Identification (TAI) list Identifier tag and NG-RAN Tracking Area Identification (TAI) list Identifier tag in clause 9.3 - R19 TS 31.111CR0861

Explore further

Broader topics and technologies where BSSID plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.271 vj00 LCS Stage 2 Specification Rel-19
TS 24.229 vj50 IMS call control protocol based on SIP and SDP Rel-19
TS 29.212 vj00 Gx/Gxx/Sd/St Diameter Protocol Rel-19
TS 29.514 vj40 5G System; Policy Authorization Service; Stage 3 Rel-19
TS 31.111 vj30 USIM Application Toolkit (USAT) Specification Rel-19
TS 36.305 vj00 UE Positioning in E-UTRAN Stage 2 Rel-19
TS 36.355 vj00 LTE Positioning Protocol (LPP) Rel-19
TS 36.455 vj00 LTE Positioning Protocol Annex (LPPa) Rel-19
TS 37.320 vj00 Minimization of Drive Tests (MDT) Overview Rel-19
TS 37.355 vj20 LTE Positioning Protocol (LPP) Rel-19
TS 38.305 vj00 NG-RAN UE Positioning Stage 2 Rel-19