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

Glossary term · Core Network

BCSM

Basic Call State Model

Core Network →

BCSM is a finite state machine model defined by 3GPP that describes the processing stages of a call or session in the core network, enabling Intelligent Network services like call forwarding and prepaid billing.

Introduced
R99
Where
Core Network › Evolved Packet Core
Specifications
13 specs
Also in
Services
BCSM Description Purpose What changed Neighbours Specifications

Description

The Basic Call State Model (BCSM) is a core concept within the 3GPP Intelligent Network (IN) architecture, specifically defined in the CAMEL (Customised Applications for Mobile network Enhanced Logic) specifications. It provides an abstract, standardized representation of the call and session control logic from the perspective of the Service Switching Function (SSF). The BCSM is essentially a finite state machine that models the progression of a call or session through a series of distinct processing stages, known as Points In Call (PICs). Each PIC represents a significant milestone in call setup, management, or teardown, such as 'Authorize_Origination_Attempt', 'Collect_Information', 'Analyze_Information', 'Routing_and_Alerting', and 'Active'.

Between these PICs are Detection Points (DPs). DPs are specific events or conditions during call processing where the SSF can suspend its normal procedure and interact with an external Service Control Function (SCF). DPs are classified as Trigger Detection Points (TDPs), which are armed statically by subscription data, and Event Detection Points (EDPs), which are armed dynamically by the SCF during an active service logic session. When a DP is encountered and armed, the SSF sends a notification to the SCF, which can then instruct the SSF on how to proceed—for example, to continue, to connect to a different number, or to play an announcement.

Architecturally, the BCSM is implemented within the Service Switching Function (SSF), which resides in network nodes like the Mobile Switching Center (MSC) or the Call Session Control Function (CSCF) in IMS. The SSF uses the BCSM to monitor call states and manage the dialogue with the SCF. There are two primary BCSM instances: the Originating BCSM (O-BCSM), which models the call from the calling party's perspective, and the Terminating BCSM (T-BCSM), which models it from the called party's perspective. This dual-model approach allows service logic to be applied independently based on the subscriber's role in the call.

The BCSM's role is to decouple the basic call processing in the switch from the execution of complex, value-added service logic. By providing a standardized state model and well-defined interaction points (DPs), it enables network operators to deploy and manage a wide array of supplementary services—such as prepaid charging, call forwarding, freephone numbers, and VPN services—in a flexible and vendor-independent manner. The model ensures that service logic applications have a consistent and predictable view of network events, which is crucial for reliable service execution across different network equipment.

Purpose & Motivation

The BCSM was created to address the limitations of traditional telephony switches, where service logic was tightly integrated and hard-coded into the switching software. This made introducing new services a slow, expensive, and vendor-specific process, requiring software upgrades to every switch in the network. The primary motivation was to enable rapid service creation and deployment independent of the underlying switch infrastructure, a concept central to the Intelligent Network (IN) paradigm.

Its creation solved the problem of service portability and flexibility. By defining a standardized abstract model of call states, the BCSM allowed service logic to be developed once and deployed across networks from different vendors. This abstraction layer meant that service applications, running on external Service Control Points (SCPs), only needed to understand the BCSM's states and detection points, not the proprietary internals of each manufacturer's switch. This dramatically reduced time-to-market for new services.

Historically, the BCSM concept was inherited from fixed-line IN standards (ITU-T CS-1) and adapted by 3GPP for mobile networks, most notably within the CAMEL framework for GSM and UMTS. It provided the foundational mechanism for implementing operator-specific, real-time control over mobile calls and sessions, which was essential for advanced billing schemes (like prepaid), location-based services, and personalized call handling—services that were becoming critical competitive differentiators for mobile operators.

What changed in its specifications

The latest release-to-release comparison of specifications that define BCSM. Each summary describes the whole specification, not only this term.

TS 23.078Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 23.078: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 23.078 →
TS 23.172Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 23.172: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 23.172 →

Evolution Across Releases

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

R99 Initial

Introduced the Basic Call State Model as part of the CAMEL Phase 3 specifications for GSM/UMTS networks. The initial architecture defined the O-BCSM and T-BCSM with a core set of PICs and DPs to support basic mobile-originated and terminated call control, enabling services like prepaid charging, call forwarding, and advice of charge. It established the fundamental interaction between the Service Switching Function (SSF) and Service Control Function (SCF).

Defining Specifications

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

SpecificationTitleRelease
TR 21.978 v300 CAMEL Control of VoIP Services Feasibility Study R99 read
TS 23.078 vj00 CAMEL Phase 4 Stage 2 Specification Rel-19 read
TS 23.172 vj00 Service Change and UDI Fallback (SCUDIF) Rel-19 read
TS 23.218 vj00 IMS Call Model Specification Rel-19 read
TS 23.226 vj00 Global Text Telephony (GTT) Stage 2 Rel-19 read
TS 23.228 vk10 IP Multimedia Core Network Subsystem Rel-20 read
TS 23.278 vj00 CAMEL for IMS Stage 2 Specification Rel-19 read
TS 23.417 v700 IMS Core Component for NGN Architecture Rel-7 read
TS 23.517 v800 IMS Core Architecture for TISPAN NGN Rel-8 read
TS 29.078 vj00 CAMEL Phase 4 CAP Specification Rel-19 read
TS 29.278 vj00 CAMEL Application Part (CAP) for IMS Phase 4 Rel-19 read
TS 32.272 vj00 Charging for Push-to-Talk over Cellular (PoC) Rel-19 read
TS 32.273 vj00 MBMS Charging Management Rel-19 read