Glossary term · Core Network

Circuit switched domain

Circuit Switched Domain

Core Network →

Circuit switched domain is the portion of a GSM or UMTS network that provides dedicated connections for voice and circuit data services using circuit switched mode.

Introduced
Rel-8
Where
Services
Specifications
8 specs
Also in
Management

3GPP QuarterlyThe next issue by email, at most eight a year.

Category
Core Network
Introduced
Rel-8
Where
Services
Also touches
1 segments
Specifications
8 specs
Circuit switched domain Description Purpose Specifications

Description

The Circuit Switched (CS) domain, as defined in 3GPP management and charging specifications, refers to the domain within GSM and UMTS networks in which information is transferred in circuit switched mode. This definition, introduced in Rel-8, is used primarily in the context of network management, charging, and performance measurement specifications (TS 32.240, 32.250, 32.270, 32.271, 32.272, 32.281, 32.295, 32.297). It provides a concise architectural characterization of the CS domain that is consistent across the 3GPP management framework.

In the management context, the CS domain is treated as a managed entity with its own set of charging data records (CDRs), performance counters, and fault management parameters. The charging architecture for the CS domain is defined in TS 32.250 (Charging management; Circuit Switched domain charging), which specifies how call detail records are generated by the MSC and how they are transferred to the charging gateway function (CGF) and billing domain. The CS domain charging mechanisms support both event-based and session-based charging, with parameters such as call duration, calling and called party numbers, location information, and supplementary service usage.

Performance management for the CS domain is covered by TS 32.270 (Performance Management; Circuit Switched domain), which defines key performance indicators (KPIs) and measurements such as call setup success rate, call drop rate, handover success rate, and traffic channel utilization. These measurements are collected by the network element management system (EMS) and reported to the network management system (NMS) for monitoring and optimization. The CS domain also has associated fault management specifications that define alarm types and severity levels for CS network elements.

The CS domain in the management context encompasses the MSC, GMSC, VLR, and the circuit-switched portions of the BSS/RNS. It interacts with the PS domain through shared network elements such as the HLR and the radio access network, but the management and charging of CS services are handled independently. This separation allows operators to bill circuit-switched voice and data services differently from packet-switched services, and to monitor the performance of each domain independently.

The Rel-8 definition of the CS domain in management specifications was introduced as part of a broader effort to harmonize terminology across the 3GPP management framework. While the functional definition in TS 22.976 (R99) and the revised definition in Rel-12 describe the CS domain in terms of bearer and teleservice provision, the management-oriented definition focuses on the mode of information transfer. This reflects the different perspectives of service specifications versus management specifications. The definition has remained stable from Rel-8 through Rel-19, underscoring the maturity of the CS domain management framework. As networks transition to all-IP architectures, the CS domain management specifications continue to support legacy GSM/UMTS deployments, while 5G management focuses on network slicing, service-based architecture, and cloud-native network functions.

Purpose & Motivation

The CS domain definition in management specifications exists to provide a clear, consistent architectural boundary for charging, performance management, and fault management of circuit-switched services. By defining the CS domain as the portion of GSM/UMTS where information is transferred in circuit switched mode, the specifications enable operators to unambiguously identify which network elements, interfaces, and services fall under CS domain management. This is essential for generating accurate billing records, monitoring network performance, and troubleshooting faults.

Historically, the need for a management-specific definition arose as 3GPP's management framework expanded in Rel-8 and beyond. The original R99 definition in service specifications was functional and descriptive, focusing on bearer and teleservice provision. However, management specifications required a more concise, mode-based definition that could be applied consistently across charging, performance, and fault management domains. The Rel-8 definition addressed this need by characterizing the CS domain in terms of the mode of information transfer, which is directly observable and measurable by network management systems.

The CS domain management framework also solves the problem of separating CS and PS charging in networks that support both domains. Without a clear definition of the CS domain boundary, charging systems could misattribute calls or data sessions, leading to billing errors. The management-oriented definition ensures that CS and PS domains are treated as distinct managed entities, each with its own charging, performance, and fault management specifications. This separation remains important even as networks evolve toward all-IP, because legacy CS infrastructure continues to operate and require management support.

Release Timeline

Evolution Across Releases

Rel-8 Initial

Initial definition established in management specifications: 'domain within GSM / UMTS in which information is transferred in circuit switched mode.' This definition was introduced to provide a consistent architectural boundary for charging, performance, and fault management of circuit-switched services, complementing the functional definition used in service specifications.

Definition carried over unchanged from Rel-8. The CS domain management definition remained stable as 3GPP focused on LTE and SAE enhancements.

Definition carried over unchanged. Rel-10 introduced LTE-Advanced, but the CS domain management definition was not modified.

Definition carried over unchanged. Rel-11 brought CoMP and eICIC, with no revision to the CS domain management definition.

Definition carried over unchanged. Rel-12 introduced small cells and dual connectivity, but the CS domain management definition remained the same.

Definition carried over unchanged. Rel-13 introduced NB-IoT and eMTC, with no change to the CS domain management definition.

Definition carried over unchanged. Rel-14 focused on V2X and IoT enhancements, but the CS domain management definition was not revised.

Definition carried over unchanged. Rel-15 introduced 5G NR and the 5G System management framework, but the CS domain management definition for GSM/UMTS remained stable.

Definition carried over unchanged. Rel-16 brought NR-U and sidelink enhancements, with no revision to the CS domain management definition.

Definition carried over unchanged. Rel-17 introduced NR multicast/broadcast, RedCap, and NTN, but the CS domain management definition was not modified.

Definition carried over unchanged. Rel-18 marked the start of 5G-Advanced, with the CS domain management definition remaining identical to its Rel-8 formulation.

Definition carried over unchanged. Rel-19 continues 5G-Advanced evolution, with the CS domain management definition remaining stable.

Defining Specifications

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

SpecificationTitleRelease
TS 32.240 vk10 3GPP Charging Architecture and Principles Rel-20
TS 32.250 vj00 Circuit Switched Offline Charging Rel-19
TS 32.270 vj00 MMS Charging Management Specification Rel-19
TS 32.271 vj20 3GPP LCS Charging Management Spec Rel-19
TS 32.272 vj00 Charging for Push-to-Talk over Cellular (PoC) Rel-19
TS 32.281 vj00 Announcement Service for Online Charging Rel-19
TS 32.295 vj00 3GPP Charging: CDR Transfer via GTP' Protocol Rel-19
TS 32.297 vj00 Charging Data Record File Transfer Rel-19