Description
A CS call is a connection established via the circuit-switched domain using the procedures defined for that domain — for example those in 3GPP TS 24.008 for GSM/UMTS mobility management and call control, or 3GPP2 C.S0001-D for cdma2000. The defining characteristic in the 3GPP glossary is that the bearer established for the CS call is used only within that CS connection and is not used as a media stream for a related IM CN subsystem (IMS) session. This distinction matters because 3GPP networks support both circuit-switched and packet-switched domains, and a single user experience may span both — for example, a CS voice call combined with an IMS-based supplementary service or a concurrent IMS session.
The circuit-switched domain provides a dedicated, constant-bit-rate channel between the calling and called parties for the duration of the call. In GSM and UMTS, the CS domain comprises the Mobile Switching Centre (MSC), the Visitor Location Register (VLR), the Gateway MSC (GMSC), and the CS media path through the radio access network. Call setup follows the procedures of TS 24.008 (CC, MM, and GMM protocols), with the MSC acting as the switching node. In cdma2000 networks, the equivalent procedures are defined in 3GPP2 C.S0001-D. The CS bearer is allocated at call setup and released at call teardown, and it is inherently connection-oriented, which gives predictable latency and quality suitable for real-time voice.
The glossary's emphasis on the bearer not being used as an IMS media stream reflects the architecture of IMS Centralized Services (ICS) and related work in 3GPP TS 22.135 and TS 24.292. ICS allows a UE to use a single set of service credentials and a single service-capable number across CS and PS access, with service control hosted in IMS. In some ICS configurations, a CS call may be established while IMS service control is applied to it — for example, the MSC Server Enhanced for ICS routes the call into IMS for service execution. The glossary definition distinguishes a pure CS call, whose bearer is confined to the CS connection, from scenarios where the CS bearer is repurposed or bridged as a media stream for an IMS session (as in certain SR-VCC or ICS media-path configurations). This precision is necessary for specifying charging, supplementary services, and interworking behaviour correctly.
The CS call remains relevant in the 5G era because of fallback mechanisms. EPS Fallback and, more recently, 5G Fallback allow a UE attached to NR or LTE to fall back to a CS-capable access (GERAN, UTRAN, or, in some deployments, a CS core via specific interworking) to establish a CS call when voice over NR or VoLTE is not available or not preferred. The CS call is therefore not merely a legacy concept; it is a defined service state that interacts with IMS session management, SR-VCC procedures, and emergency call handling. The glossary definition, stable from Release 8 through Release 19, anchors these interworking discussions by making clear what counts as a CS call versus an IMS session.
In summary, a CS call is a circuit-switched connection with a dedicated bearer that is not shared with an IMS media stream. Understanding this definition is essential for engineers working on voice continuity, ICS, SR-VCC, and fallback procedures, where the boundary between CS and IMS media paths determines the applicable service logic and charging model.
Purpose & Motivation
The term CS call exists to draw a precise boundary between circuit-switched connections and IMS sessions in 3GPP networks. As networks evolved from pure CS voice to hybrid CS/IMS architectures, specifications needed a way to refer unambiguously to a connection whose bearer is dedicated to the CS domain and is not simultaneously serving as an IMS media stream. Without this distinction, procedures for ICS, SR-VCC, charging, and supplementary services could be ambiguous about which domain owns the media path.
Historically, before IMS, all voice was circuit-switched and the term 'call' was unambiguous. The introduction of IMS in Release 5 created a second, packet-based session model. Subsequent work on ICS (TS 22.135, TS 24.292) allowed CS access to be used with IMS service control, creating configurations where a CS bearer and an IMS session coexist or interact.
The definition also supports the specification of fallback and continuity mechanisms. EPS Fallback and SR-VCC rely on the ability to move a session between domains; knowing whether a given connection is a CS call or an IMS session determines which procedures apply. By keeping the definition stable across Releases 8 through 19, 3GPP ensured that these interworking specifications share a common, unambiguous vocabulary.
What changed in its specifications
The latest release-to-release comparison of specifications that define CS call. Each summary describes the whole specification, not only this term.
Rel-13 added mSRVCC message interworking: CGI/UTRAN SAI parameter inclusion is conditional on availability, and MSC Server can subscribe to conference event package.
Full comparison in TS 24.292 →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.
Defining Specifications
3GPP specifications that define or reference CS call, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.135 vj00 | Multicall Supplementary Service Specification | Rel-19 read |
| TS 24.292 vj00 | IMS Centralized Services (ICS) Protocol | Rel-19 read |