CSI

Combined CS and IMS Services

Services →
Introduced in Rel-2 Also in: Services

CSI is a 3GPP service architecture that enables the seamless integration and delivery of both Circuit-Switched telephony and IP Multimedia Subsystem (IMS) packet-switched services over a single mobile network.

Category
Services
Introduced
Rel-2
Where
Radio Access Network › NG-RAN (5G)
Also touches
1 segments
Specifications
48 specs
CSI Description Purpose Related Classification Detected Changes Specifications

Description

CSI is a comprehensive service architecture defined by 3GPP that bridges the gap between traditional Circuit-Switched (CS) domain services, primarily voice and SMS, and the emerging IP Multimedia Subsystem (IMS) domain services, which include multimedia telephony, video calling, and rich communication services (RCS). The architecture is designed to allow these two distinct service delivery platforms to coexist and interoperate, presenting a unified service logic and user experience to the subscriber. It achieves this through a set of standardized functional entities and reference points that coordinate service execution between the CS core network (MSC) and the IMS core (CSCF).

At its core, CSI introduces the concept of service interaction and coordination. When a CSI-enabled subscriber initiates or receives a session, the network must determine how to route and handle the service components. For a voice call, this might be handled natively by the CS domain for wide-area reliability, while supplementary services or concurrent multimedia sessions (like video or file transfer) are anchored and managed by the IMS. The architecture defines mechanisms, such as the IMS Service Control (ISC) interface and enhancements to the CAMEL (Customised Applications for Mobile network Enhanced Logic) protocol, to facilitate this coordination. A key functional component is the CSI Application Server (AS) within the IMS, which hosts the combined service logic and interacts with both the Serving-CSCF (S-CSCF) via the ISC interface and, indirectly, with the CS domain to orchestrate the service flow.

The technical operation involves session establishment and control procedures. For an originating mobile-originated CSI session, the User Equipment (UE) indicates its CSI capability. The network, often via policy decisions in the IMS, may split the media components: real-time voice is routed over the CS bearer using traditional call control (e.g., via the MSC), while other media streams (e.g., video) are established as separate IP flows via the Packet-Switched (PS) bearer, controlled by the IMS using the Session Initiation Protocol (SIP). The IMS acts as the service control anchor, ensuring that billing, supplementary services (like call hold or transfer), and service logic are applied consistently across both domains. This requires tight synchronization between SIP signaling in the IMS and ISUP/BICC signaling in the CS core.

CSI's role in the network is fundamentally transitional and integrative. It serves as a critical enabler for network operators migrating from 2G/3G CS-centric architectures to 4G/5G all-IP networks based on IMS and VoLTE/VoNR. By allowing the CS network to act as a reliable voice media bearer while IMS provides advanced service control, CSI protects investments in legacy infrastructure and ensures service availability during the migration period. It also enables the early introduction of IMS-based multimedia services to subscribers who may not yet have full IMS-capable devices or radio access, thereby accelerating the adoption of new revenue-generating services.

Purpose & Motivation

CSI was created to address a fundamental challenge in the evolution of mobile networks: the transition from circuit-switched, voice-dominated networks to packet-switched, multimedia-capable all-IP networks. In the early 2000s, with the standardization of IMS in 3GPP Release 5, operators faced a dilemma. IMS promised a future of rich, integrated multimedia services but required a completely new core network architecture. Meanwhile, the existing CS network represented a massive, reliable, and ubiquitous investment for voice telephony, the primary revenue source. A 'big bang' replacement was economically and technically infeasible. CSI was conceived to solve this by allowing both domains to work together, enabling a gradual, risk-managed migration path.

The primary problem CSI solves is service fragmentation and subscriber experience degradation during the transition. Without CSI, a network deploying IMS would create two separate service silos: basic voice/SMS on the CS network and advanced multimedia on IMS, with little to no interaction between them. A subscriber might have two separate identities, address books, and service profiles. CSI eliminates this by providing a unified service layer. It allows operators to introduce IMS-based service innovation—like combining voice with instant messaging or video—while still utilizing the mature, high-quality voice bearer of the CS network. This was particularly important for ensuring seamless service coverage and interoperability with legacy networks and devices.

Historically, CSI addressed the limitations of pre-IMS service architectures, which were either purely CS-based (lacking multimedia flexibility) or early PS multimedia attempts that were non-standardized and lacked robust session control. By standardizing the interaction, CSI provided a clear blueprint for vendors and operators. It motivated the creation of a hybrid service delivery model that maximized asset utilization, ensured backward compatibility, and paved the way for the eventual full migration to IMS-based Voice over LTE (VoLTE) and Voice over NR (VoNR), where the CS bearer is finally retired in favor of a full IP Multimedia Telephony service over the packet core.

Classification

Part ofIMS
Specific typesCSI-RSRQ
Related approachesCAMEL

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 30 changes

In Release 15, key enhancements for the CSI function included the introduction of advanced CSI parameter capabilities for FD-MIMO, clarifications and corrections for CSI reporting on PUSCH and PUCCH, and specific procedures for handling Semi-Persistent CSI reporting during DRX operation. The release also addressed the overlapping of CSI resources with PUSCH transmissions, including slot aggregation scenarios, and introduced a capability for aperiodic CSI-RS triggering with different numerologies between PDCCH and CSI-RS.

  • Advanced CSI CBSR CBSR related capability for FD-MIMO TS 36.306CR1593
  • Advanced CSI CBSR CBSR parameter and related capability for FD-MIMO TS 36.331CR3397
  • Removal of CSI request in RAR grant TS 38.213CR0012
  • CR on overlapping of CSI and PUSCH with slot aggregation TS 38.213CR0028
  • Correction on CRC assumption for multi-CSI resource selection and CSI report(s) selection TS 38.213CR0041
  • Correction to aperiodic CSI-RS triggering with different numerology between PDCCH and CSI-RS TS 38.214CR0007

+ 24 more changes

Rel-16 38 changes

In Release 16, enhancements to the CSI function included introducing support for aperiodic CSI-RS triggering with new beam switching timing values of 224 and 336, along with corrections for its operation with unaligned carrier aggregation. The release also provided clarifications and corrections for procedures such as CSI reporting for non-active bandwidth parts, cross-carrier CSI-RS triggering, and CSI/L1-RSRP measurement outside the active time.

  • Aperiodic CSI-RS Triggering for UE reporting beamSwitchTiming values of 224 and 336 TS 38.214CR0060
  • Behaviour for triggered with a CSI report for non-active BWP TS 38.214CR0061
  • Aperiodic CSI-RS triggering with beam switching timing of 224 and 336 TS 38.331CR1716
  • CR to 38.331 on CSI-RS inter-node message TS 38.331CR1354
  • 38331 CR for CSI-RS-ResourceConfigMobility TS 38.331CR2250
  • Clarification on KNZ to codepoint mapping for eType II CSI TS 38.212CR0081

+ 32 more changes

Rel-17 43 changes

In Release 17, key enhancements for CSI included new UE capabilities for cross-PUCCH SCell group reporting and support for Multiple CSI Subframe Sets on periodic reporting. The release also introduced corrections and support for Non-Coherent Joint Transmission (NCJT) and multi-TRP CSI, including refinements to rank combination mapping, multiplexing assumptions, and CSI-RS port restrictions. Furthermore, it addressed CSI procedures for new scenarios such as operation on LP PUSCH with CG-UCI, multiplexing with NACK-only and SR, and corrections for timing related to higher subcarrier spacings and fast SCell activation.

  • Adding UE capability of CSI reporting cross PUCCH SCell group TS 38.331CR3144
  • Support of Multiple CSI Subframe Sets on CQI-ReportPeriodicScell TS 36.306CR1866
  • Support of Multiple CSI Subframe Sets on CQI-ReportPeriodicScell TS 36.331CR4899
  • CR on CSI reporting TS 38.212CR0134
  • Correction for the mapping of rank combination value for Rel-17 NCJT CSI TS 38.212CR0142
  • Correction of CSI assumptions over multiplexing NCJT CSI reports in PUCCH TS 38.213CR0354

+ 37 more changes

Rel-18 28 changes

In Release 18, the enhancements for CSI focused on refining new MIMO capabilities, specifically the Type II Doppler codebook, and correcting its associated triggering and processing procedures. The release also introduced clarifications and corrections for processing criteria related to new network energy saving (NES) capabilities and long-term metrics (LTM) CSI reporting. Furthermore, adjustments were made to the handling of CSI reports for sidelink (SL), the activation/deactivation of semi-persistent (SP) CSI reporting via MAC CE, and various measurement accuracy test cases.

  • Introduction of specification support for MIMO enhancements on CSI TS 38.214CR0437
  • Correction on priority for LTM CSI report TS 38.213CR0643
  • Correction of specification support for MIMO enhancements on CSI TS 38.214CR0483
  • Correction on Rel-18 Type II Doppler codebook based CSI enhancement TS 38.214CR0567
  • Correction on CSI processing criteria for new NES capability signaling TS 38.214CR0584
  • Clarification on SL CSI request in TS 38.214 TS 38.214CR0588

+ 22 more changes

Rel-19 11 changes

In Release 19, key enhancements for CSI focused on improving handover performance and multi-antenna operations. Specifically, the release introduced early CSI acquisition for Layer 3 handover to optimize mobility and delivered enhancements for NR MIMO Phase 5. Furthermore, it addressed the counting and management of simultaneous NZP-CSI-RS resources and reporting settings, and included maintenance corrections for AI/ML-based CSI prediction and semi-persistent resources.

  • Introduction of Rel-19 early CSI acquisition for L3 handover to TS 38.212 [EarlyCSI_L3HO] TS 38.212CR0236
  • Introduction of CSI enhancements for NR MIMO Phase 5 TS 38.214CR0677
  • TEI19 Counting of CSI-RS resource referred by N CSI reporting settings [SimCSI_count] TS 38.214CR0681
  • TEI19 Simultaneous NZP-CSI-RS resource counting with NES [SimCSI_countNES] TS 38.214CR0689
  • Introduction of Rel-19 early CSI acquisition for L3 handover to TS 38.214 [EarlyCSI_L3HO] TS 38.214CR0722
  • Introduction of early CSI acquisition for L3 handover [EarlyCSI_L3HO] TS 38.331CR5587

+ 5 more changes

Explore further

Broader topics and technologies where CSI plays a role.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TR 21.978 v1300 CAMEL Control of VoIP Services Feasibility Study Rel-4
TS 23.279 vj00 Combined CS and IMS Services (CSI) Architecture Rel-19
TS 23.806 v1700 Voice Call Continuity between CS and IMS Rel-7
TS 26.141 vj00 IMS Messaging & Presence Media Formats Rel-19
TS 26.235 vc00 Default Codecs for 3GPP IP Multimedia Subsystem Rel-12
TS 29.078 vj00 CAMEL Phase 4 CAP Specification Rel-19
TS 29.163 vj00 Interworking between 3GPP IM CN and CS networks Rel-19
TS 29.278 vj00 CAMEL Application Part (CAP) for IMS Phase 4 Rel-19
TS 33.126 vj30 Lawful Interception Requirements Rel-19
TS 33.127 vj50 Lawful Interception Architecture and Functions Rel-19
TS 36.201 vj00 LTE Physical Layer General Description Rel-19
TS 36.211 vj10 LTE Physical Layer Specification Rel-19
TS 36.212 vj10 LTE Multiplexing and Channel Coding Rel-19
TS 36.213 vj10 LTE Physical Layer Procedures Rel-19
TS 36.300 vj00 E-UTRAN Radio Interface Protocol Architecture Overview Rel-19
TS 36.302 vj00 E-UTRA Physical Layer Services Rel-19
TS 36.306 vj00 E-UTRA UE Radio Access Capability Parameters Rel-19
TS 36.307 vj10 Release-Independent Frequency Band Support Rel-19
TS 36.321 vj00 E-UTRA MAC Protocol Specification Rel-19
TS 36.331 vj00 LTE RRC Protocol Specification Rel-19
TS 36.741 ve00 Enhancements to Coordinated Multi-Point Operation Rel-14
TS 36.825 vd00 Study on Additional LTE TDD Configurations Rel-13
TS 36.855 vd00 E-UTRA Positioning Enhancements Study Rel-13
TS 36.867 vd00 LTE DL 4 Rx Antenna Port Study TR Rel-13
TS 36.871 vb00 Downlink MIMO Enhancement for LTE-Advanced Rel-11
TS 36.878 vd00 LTE Performance Enhancements for High Speed Scenarios Rel-13
TS 38.133 vj20 5G UE Radio Requirements for RRC_IDLE Mobility Rel-19
TS 38.174 vj10 NR Integrated Access and Backhaul Radio Spec Rel-19
TS 38.176 vj20 IAB Conformance Testing Specification Rel-19
TS 38.211 vj10 NR Physical Channels and Modulation Rel-19
TS 38.212 vj10 NR Multiplexing and Channel Coding Rel-19
TS 38.213 vj10 NR Physical Layer Control Procedures Rel-19
TS 38.214 vj10 NR Physical Layer Procedures for Data Rel-19
TS 38.321 vj00 NR MAC Protocol Specification Rel-19
TS 38.331 vj00 NR Radio Resource Control (RRC) Protocol Specification Rel-19
TS 38.522 vj11 UE Conformance Test Applicability Statement Rel-19
TS 38.551 vi30 User Equipment (UE) Multiple Input Multiple Output (MIMO) Over-the-Air (OTA) performance Rel-18
TR 38.808 vh00 Study on NR above 52.6 GHz to 71 GHz Rel-17
TR 38.810 vg70 NR OTA Test Methods Study Rel-16
TS 38.824 vg00 NR URLLC Physical Layer Enhancements Study Rel-16
TR 38.825 vg00 Study on NR Industrial IoT Rel-16
TR 38.830 vh00 NR Coverage Enhancements Study Rel-17
TR 38.838 vh00 Study on XR Evaluations for NR Rel-17
TS 38.843 vj00 Study on AI/ML for NR Air Interface Rel-19
TR 38.869 vi00 Study on low-power wake up signal and receiver for NR Rel-18
TR 38.889 vg00 NR-based access to unlicensed spectrum study Rel-16
TR 38.903 vj00 Test Tolerances & Measurement Uncertainties Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.