Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

intra-BSS call detection

intra-BSS call detection

Services →

intra-BSS call detection is the procedure by which the network determines that both legs of a mobile-to-mobile call are served by the same Base Station Subsystem, a prerequisite for activating local call local switch and optimizing voice routing.

Introduced
Rel-9
Where
Core Network › 5G Core
Specifications
2 specs
intra-BSS call detection Description Purpose Neighbours Specifications

Description

Intra-BSS call detection is the mechanism used in GSM/EDGE networks to determine that both call legs of a mobile-to-mobile voice call are within the same Base Station Subsystem (BSS). It is a prerequisite for features such as Local Call Local Switch (LCLS), which allows the user plane to be switched locally within the BSS rather than being routed through the core network. The detection is performed by the BSS and/or the MSC using information exchanged over the A interface.

The procedure relies on the BSS identifying the serving cell of each mobile station and reporting it to the MSC. When a call is set up, the MSC receives the cell identity for each leg as part of the BSSAP signalling. The MSC then correlates the two identities: if both belong to the same BSS, the call is flagged as an intra-BSS call. The BSS may also perform its own detection based on internal knowledge of which cells it controls, and it can inform the MSC accordingly. The exact signalling is specified in 3GPP TS 23.284 and TS 23.889, which define the LCLS architecture and the detection procedures.

Once detection is complete, the network can decide whether to activate local switching. If the MSC and BSS support LCLS, the MSC requests the BSS to perform local switching for the call. The BSS then configures its internal switching fabric to connect the two radio bearers directly, bypassing the MSC's media gateway for the user plane. If local switching is not supported or not permitted (e.g., due to lawful interception requirements), the call proceeds with the normal MSC-routed path. Detection itself is transparent to the user and does not affect call setup signalling visible to the MS.

The detection mechanism must be robust because incorrect detection could lead to failed local switching or to routing inconsistencies. The BSS reports cell identities using standard A-interface information elements, and the MSC maintains a mapping of cells to BSSs. In multi-BSC deployments, detection also considers whether both legs are under the same BSC, since local switching is typically performed within a single BSC. The feature therefore depends on accurate cell and BSS configuration data in both the BSS and the MSC.

Intra-BSS call detection is part of the broader LCLS framework introduced in Release 9. It supports operators in reducing backhaul costs and improving voice latency for locally proximate users, such as in enterprise campuses or rural deployments. The feature has been maintained through subsequent releases without changes to its core definition.

Purpose & Motivation

Local call local switch can only be applied when the network knows that both call legs are within the same BSS. Without a reliable detection mechanism, the network cannot safely decide to keep the user plane local, and attempts to do so could result in misrouted or dropped calls. Intra-BSS call detection exists to provide that determination in a standardized way, using A-interface signalling and cell identity information.

The feature was motivated by the LCLS work in Release 9, which aimed to reduce backhaul costs and improve voice quality for mobile-to-mobile calls between nearby users. Previous approaches either always routed calls through the MSC or relied on proprietary detection mechanisms that were not interoperable. Standardizing detection ensures that multi-vendor networks can interoperate and that the MSC retains control over whether local switching is activated.

Detection also supports regulatory and operational requirements: the MSC remains aware of the call and can enforce lawful interception or charging policies even when the user plane is local. This balance between optimization and control is a key reason the detection procedure is defined separately from the switching procedure itself.

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-9 Initial

Initial definition introduced as part of the LCLS framework: determination that both call legs are within the same BSS. The procedure uses A-interface signalling and cell identity correlation.

Definition text carried over unchanged from Release 9; the quoted wording is identical.

Definition text carried over unchanged from Release 9; the quoted wording is identical.

Definition text carried over unchanged from Release 9; the quoted wording is identical.

Definition text carried over unchanged from Release 9; the quoted wording is identical.

Definition text carried over unchanged from Release 9; the quoted wording is identical.

Definition text carried over unchanged from Release 9; the quoted wording is identical.

Definition text carried over unchanged from Release 9; the quoted wording is identical.

Definition text carried over unchanged from Release 9; the quoted wording is identical.

Definition text carried over unchanged from Release 9; the quoted wording is identical.

Definition text carried over unchanged from Release 9; the quoted wording is identical.

Defining Specifications

3GPP specifications that define or reference intra-BSS call detection, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.284 vj00 Local Call Local Switch Stage 2 Rel-19 read
TS 23.889 va00 Core Impacts of Local Call Switching Rel-10 read